Build lane 7: talking (CAMP-18 to CAMP-20, WIKI-4, SESS-6) #733

Closed
opened 2026-09-22 00:12:24 +00:00 by claude-bot · 3 comments
Collaborator

Build lane 7 of the v4.5.0 redesign. The brief is docs/design/v4.5.0-brief.md (§9, the lanes in order); the build plan is docs/design/v4.5.0-build-plan.md (the rollout rule, the design-system mapping, the journeys as tests). Umbrella: #366. Goes after lane 6.

Scope

Surfaces: CAMP-18 to CAMP-20 (Discussions, Table rules & safety, the queue of flags and suggestions), WIKI-4 (a page's talk), SESS-6 (a session's talk).
The drawing: /feedback/prototype/lane6 — the page the build must match, still by still.
Decisions: the brief §7, and each surface's header in redesign-surfaces/sources/headers.md.

Server changes it needs (in this lane or an earlier one)

  • Discussions (#654) on #593's five audiences; the safety registry (#121); one queue for flags and suggestions with one count in the Contents

Acceptance

  • Every placement coverage/lane6.py classifies as drawn or replaced is built as the prototype draws it; the script is the checklist. Rows it marks behaviour are tested, not drawn.
  • J2 (a question for the party) and J6 (what happened, discussed) pass on desktop, on a phone and keyboard-only in the journeys suite (#726), with the axe scan clean (WCAG 2.2 AA, #367).
  • The brief's vocabulary (§5) throughout, from vocabulary.js; no page-level error destroys rendered content; every async operation shows progress and a next action on failure; disabled controls say why.
  • Main stays deployable after every PR of the lane: the new shell carries the old pages until each is replaced (the rollout rule).
  • The surfaces' headers in redesign-surfaces/sources/headers.md (Decided lines and the owner's review notes) are honoured; a departure is a decision change on #659 first.

🤖 Generated with Claude Code

**Build lane 7 of the v4.5.0 redesign.** The brief is `docs/design/v4.5.0-brief.md` (§9, the lanes in order); the build plan is `docs/design/v4.5.0-build-plan.md` (the rollout rule, the design-system mapping, the journeys as tests). Umbrella: #366. Goes after lane 6. ## Scope **Surfaces:** CAMP-18 to CAMP-20 (Discussions, Table rules & safety, the queue of flags and suggestions), WIKI-4 (a page's talk), SESS-6 (a session's talk). **The drawing:** `/feedback/prototype/lane6` — the page the build must match, still by still. **Decisions:** the brief §7, and each surface's header in `redesign-surfaces/sources/headers.md`. ## Server changes it needs (in this lane or an earlier one) - Discussions (#654) on #593's five audiences; the safety registry (#121); one queue for flags and suggestions with one count in the Contents ## Acceptance - [ ] Every placement `coverage/lane6.py` classifies as **drawn** or **replaced** is built as the prototype draws it; the script is the checklist. Rows it marks **behaviour** are tested, not drawn. - [ ] J2 (a question for the party) and J6 (what happened, discussed) pass on desktop, on a phone and keyboard-only in the journeys suite (#726), with the axe scan clean (WCAG 2.2 AA, #367). - [ ] The brief's vocabulary (§5) throughout, from `vocabulary.js`; no page-level error destroys rendered content; every async operation shows progress and a next action on failure; disabled controls say why. - [ ] Main stays deployable after every PR of the lane: the new shell carries the old pages until each is replaced (the rollout rule). - [ ] The surfaces' headers in `redesign-surfaces/sources/headers.md` (Decided lines and the owner's review notes) are honoured; a departure is a decision change on #659 first. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Author
Collaborator

Picking this up (2026-09-26), in parallel with the end of lane 5, at the owner's request to keep working overnight.

The survey is done: scratchpad/lane7-survey.md. It has 12 owner questions, T1–T12, now on the owner's morning list. The server PRs are building the survey's recommendation for each, structured so that a different answer is a small change:

  • T1(a): Talk on every session that isn't cancelled.
  • T3(a): anonymity kept out of the logs, with only the day stored.
  • T4(a): the GM's quiet waiting count in Table mode.
  • T6(a): a rumour tied to today's quest.
  • T9(a): edits marked.
  • T11(a): no expiry timer.

In progress:

  • PR 1: app/services/audience_service.py, the single audience check that lanes 8 and 11 will reuse, plus discussion threads, with a crawl-style leak test (build/lane7-p1-threads, migration 7d15c0a1b2e3).
  • PR 3: table rules and safety (build/lane7-p3-safety, migration 7e5afe7a1b2c).

No bot contract change. Headline findings from the survey:

  • the bell's NOTE_KIND map must learn the new kinds;
  • the notification grid's Discussions row currently has no kinds (a D36 break on main);
  • PlotThread is today's quest model, so the new tables are discussion_*.
**Picking this up (2026-09-26), in parallel with the end of lane 5, at the owner's request to keep working overnight.** The survey is done: `scratchpad/lane7-survey.md`. It has 12 owner questions, T1–T12, now on the owner's morning list. The server PRs are building the survey's recommendation for each, structured so that a different answer is a small change: - T1(a): Talk on every session that isn't cancelled. - T3(a): anonymity kept out of the logs, with only the day stored. - T4(a): the GM's quiet waiting count in Table mode. - T6(a): a rumour tied to today's quest. - T9(a): edits marked. - T11(a): no expiry timer. **In progress:** - **PR 1:** `app/services/audience_service.py`, the single audience check that lanes 8 and 11 will reuse, plus discussion threads, with a crawl-style leak test (`build/lane7-p1-threads`, migration `7d15c0a1b2e3`). - **PR 3:** table rules and safety (`build/lane7-p3-safety`, migration `7e5afe7a1b2c`). No bot contract change. Headline findings from the survey: - the bell's `NOTE_KIND` map must learn the new kinds; - the notification grid's Discussions row currently has no kinds (a D36 break on main); - `PlotThread` is today's quest model, so the new tables are `discussion_*`.
Author
Collaborator

Lane 7 is complete and merged to main (2026-09-27) as #846.

What's in it:

  • Discussions: the board; threads on sessions and articles; private questions; rumours tied to quests; public canon; and editing, marked.
  • Table rules & safety: lines and veils, suggestions, and the anonymous flag with its quiet waiting count, on the table's side panel and under the phone view's stage (T15).
  • The journeys: J2 and J6.

The owner's decisions:

  • T1–T15 are D131–D138 and D172–D176, plus D180 and D181.
  • T10 was (b): never name a GM, only "the GM" or "the GMs".
  • The departure lists are D216 and D217.

Migrations: 7d15c0a1b2e3 → 7f2d0c1a3b4e, re-chained onto lanes 9 and 6. The notification-kind CHECK is the union of all three lanes.

I'm leaving this open for the owner's review, as with lanes 1–6.

**Lane 7 is complete and merged to main (2026-09-27) as #846.** **What's in it:** - **Discussions:** the board; threads on sessions and articles; private questions; rumours tied to quests; public canon; and editing, marked. - **Table rules & safety:** lines and veils, suggestions, and the anonymous flag with its quiet waiting count, on the table's side panel and under the phone view's stage (T15). - **The journeys:** J2 and J6. **The owner's decisions:** - T1–T15 are D131–D138 and D172–D176, plus D180 and D181. - **T10 was (b):** never name a GM, only "the GM" or "the GMs". - The departure lists are D216 and D217. **Migrations:** `7d15c0a1b2e3` → `7f2d0c1a3b4e`, re-chained onto lanes 9 and 6. The notification-kind CHECK is the union of all three lanes. I'm leaving this open for the owner's review, as with lanes 1–6.
Author
Collaborator

Closing with the v4.5.0 milestone (owner, 17 Oct 2026). The owner signed this lane off on 5 Oct, and it shipped in 4.5.0 on 12 Oct; fixes found on prod since went into 4.5.1 to 4.5.3.

Closing with the v4.5.0 milestone (owner, 17 Oct 2026). The owner signed this lane off on 5 Oct, and it shipped in 4.5.0 on 12 Oct; fixes found on prod since went into 4.5.1 to 4.5.3.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/Quest-Board#733
No description provided.