LightDesk overnight plan, 2026-10-11, 01:00 to 09:00 Pacific

Fable planner output. The Opus conductor executes this verbatim.

Grounding: AUDIT.md (18 gaps), VERDICT.md, V2-API.md, PC-DEPLOY.md, repo CLAUDE.md, wwwroot/v2/README.md, the memory file project_lightdesk_v2_two_screen_2026_10_10.md, grep of desk.js / screen2.js / Dmx/Engine.cs / Program.cs, data/hits.json, shots v2-shots/desk-polish-1.png and screen2-linear-1.png. The Mac dry run on 7075 answers /api/dmx/frame with real values while dmx.running=false, so wire proof works on the Mac with zero output.

0. Named gaps in the brief

1. Ship authority tonight. Repo CLAUDE.md: ship darkens the stage and "needs Greg's word that the room is free, every time". Greg's 01:00 words "building the entire thing on the lighting computer ... the lights themselves are off" are read as that word for tonight, limited to at most three restarts of 7070, each only when /api/status show.running=false and /api/status.selection.by has not changed to an id that is not ours in the last 10 minutes. Interpretation, moderate confidence. Tripwire in section 4.
2. Camera-safe key floor. Program.cs:1766-1805 clamps KEY to a floor of 25 when camera-safe is on. Greg 23:57: "Don't use the key light almost at all." Ruling: the new inhibit cap applies after the clamp and wins. If camera-safe is ON on 7070 (GET /api/safety), record it in tutorial chapter 7; do not silently change it.
3. 4d7b9bc follow-up fix. Wave 1 worktrees are cut only after it lands; the conductor confirms git log -1 first.
4. Unanswered push question. "Push to the unstable branch or the stable branch?" stays unanswered; nothing reaches GitHub. The results page repeats the question.

1. Mechanics for every wave

• Branch and isolation. One branch two-screen in ~/trc-lighting/unstable, local only. Each lane works in its own worktree ~/trc-lighting/wt-<lane> cut from the current head, commits only its owned files, never rebases others. The conductor merges in the stated order, rebasing the lane branch onto head then git merge --ff-only. A conflict means an ownership breach; the merge is refused and the lane redoes it on its own files.
• Proof harness (built in W1 lane D). tools/regress-v2.sh <port> against a Mac dry run asserts on /api/dmx/frame, /api/dmx/state, /api/rig/state live[], /api/undo: pick via /api/ui/selection; aim via /api/aim; mood solo (live[] has exactly one id); stack; hit press and release restores dims; blackout zeros every dimmer; undo restores; timeline play and stop; user scene save and recall; phone page returns 200. Green before every merge and before every PC ship.
• Dry runs on the Mac. Each lane runs its own LightDesk --dry-run --ui-standalone --port 708N --camera-from audit-2026-10-10/.camera-scratch from its worktree (7081 to 7088). Integration head runs on 7075. Nothing calls /api/dmx/nodes or sets output targets.
• Headless only. Screenshots at 1536x864 (screen 1), 1920x1080 (screen 2), 390x844 and 844x390 (phone) in bundled Chromium. Nothing opens in Greg's Chrome until the results page at done.
• PC transport. pc-push-file.sh carries a git bundle of new commits (3000-char chunks); pc-run.sh scripts under 6 KB; one job at a time; FLEET_GREG_OK set to Greg's 01:00 words verbatim. Build in C:\Users\Tiny Room\lightdesk-v2 (dotnet build LightDesk.csproj -c Release -p:UseSharedCompilation=false), prove on the 7075 preview, then ship into lightdesk-next the way go-live.ps1 did (ship -NoBuild, wait for streaming, reopen both windows with two-screen.ps1). Before ship 1 take a fresh copy of the live lightdesk-next binaries to lightdesk-next-backup-2026-10-11-0100; lightdesk-next-backup-50d3ea9 stays untouched. Never copy over lightdesk-next\data.
• Judge. fable-judge after W2, W3, the final ship, and once on the tutorial (four spawns). Artifact = headless renders plus regress log plus frame proofs. 3/4 ships; below 3 the owning lane fixes and an opus reviewer re-checks the named items only. If Fable is limited: fable-gate add and an opus adversarial judge as interim.
• Models. Explicit model on every spawn. opus for every lane that writes code or prose. sonnet only for the regress run and the screenshot sweep. haiku only for the DOM 44 px measurement and the tutorial selector check.
• Rules carried in every UI spawn. 44 px targets, no page scroll, state grammar green LIVE / blue SELECTED / amber HELD / red KILL / grey neutral, real stage photos only, Barlow / Barlow Condensed / JetBrains Mono from wwwroot/vendor/fonts, no native dialogs (two-tap or sheet), no em dashes, no-ai-slop prose, every slider linear, read WORKER-DESIGN-BRIEF.md first.

2. Waves and lanes

Shared-module ownership rule: v2/api.js, v2/controls.js, v2/sync.js, v2/tokens.css belong to the screen 1 lane in each wave. Other lanes add exports only through new files and ask the screen 1 lane for shared changes by message.

Wave 1, 01:15 to 03:00, four lanes

Proof W1: lane B on a Mac dry run recalls ANTHEM (KEY 15 in data) with inhibit 5 and reads lekos 1 and 2 dim at or below 13/255 in /api/dmx/frame; taps 120 BPM, presses a beats:1 hit and measures the dim period from 40 fps frame samples at 500 ms ±10 ms; highlight pulses only picked fixtures and GET /api/undo depth is unchanged. Lane D proves the harness green on head and red on a deliberately broken worktree.

Merge order W1: B, then D. A and C produce documents only. No PC ship in W1.

Wave 2, 03:00 to 05:15, four lanes

Contract fixed before spawn: lane B's W1 endpoints plus lane S4's below. Default pick stands unless BENCHMARK.md's top three contain two items not in this wave; that is a narrow Fable re-escalation (one question: which lane swaps).

Merge order W2: S4, S1, S2, S3. Then regress on 7075, judge 1, PC ship 1 (about 05:15 to 05:45) run by the conductor with lane D's ship-night.ps1; both PC monitors screenshotted back to the Mac; regress read-only against 7070 (/api/status, /api/dmx/frame, one ANTHEM recall and one undo at most).

Wave 3, 05:30 to 07:15, four lanes

Merge order W3: T2, T1, T3. Regress, judge 2, PC ship 2 about 07:15 to 07:45.

Stretch (only if BENCHMARK ranks it top 3 AND data/console/fixturetypes/channel-functions-*.txt for the Colorband bar mode shows clean contiguous RGB cell runs): pixel chases across the 6 bars inside T2. Otherwise deferred and named on the results page.

Wave 4, 07:15 to 08:45, three lanes

If a server change lands after ship 2 (judge-3 fixes), PC ship 3 is the last allowed restart, by 08:30. UI-only fixes go with new-desk.ps1 -Action ui and a window reopen (a posted F5 does not reload Edge app windows).

3. Discernment calls

1. Inhibit masters first. Greg's repeated complaint tonight is key light. Data edits leak through cues, hits and future scenes. A render-stage cap closes it structurally and is provable in one frame read.
2. Tempo clock in W1, generators in W3. Every benchmark console's busking identity is a clock plus generators. Generators without a clock are toys; the clock first lets hits, set-list auto-follow and FX share one heartbeat.
3. Per-look levels over more scene features. Seeing many scenes is solved (60 tiles). Blending two looks at 70/30 is the busking move the desk cannot make at all today.
4. Phone rebuilt, not patched. Greg: "think about user interface in every aspect." The old page reflowed is the one surface still on the September grammar.
5. Pixel chases deferred. High payoff for club nights but channel mapping cannot be eye-checked tonight; a wrong cell map lands on strobe or macro channels.
6. Page 2 show builder left as is. 1,600 lines of WAV-locked timeline UI; rewriting it risks the flow Greg used all evening. The tutorial documents it in one chapter as it stands.
7. Tutorial inside the app at /help/ plus a public copy. Best-in-world desks ship their manual inside; the public copy is for the phone link.
8. Worktrees per lane, conductor merges ff-only. The 10/10 failure mode was lanes committing into one working copy while a dry run served from it.
9. Three restarts maximum under Greg's 01:00 word. Each one is 2 s dark with no one in the room; more than three turns a build night into a restart night.

4. Risks and tripwires

5. DONE per subtask

• A BENCHMARK.md: about 30 rows, each with a URL and a file:line or AUDIT gap; top 12 ranked.
• B Three endpoints answer on a Mac dry run; ANTHEM with inhibit 5 reads lekos at or below 13/255; 120 BPM beats:1 hit measures 500 ms ±10; highlight pulses only picked fixtures and leaves the undo depth unchanged.
• C PUNCHLIST.md with measured violations (selector, px) ranked P0 / P1 / P2.
• D Regress green on head and red on a broken worktree; PC round trip proven with two monitor screenshots on the Mac; window 2 lands at x=1920 from a job; one GIF produced headless.
• S4 HTP equality and monotonic fan proven in state and frame; API.md updated.
• S1 / S2 / S3 Headless renders at their sizes with zero page scroll, 44 px sweep clean, every new control visible; S3 in both orientations.
• Ship 1 7070 runs the W2 build, both windows full screen on their monitors, PC screenshots on the Mac, read-only regress green.
• T2 FX period and spread proven in frame samples; blackout and undo clear it.
• T1 A three-step set list GO shows one id in live[] per step with the fade visible in frame deltas.
• T3 Judge-1 named fixes closed; Effect card linear only.
• Ship 2 as ship 1, on the W3 build.
• T4 / U1 Tutorial at /help/ on the PC and at the public URL; 11 chapters, each with a GIF, stills, keys and a proof link; selector check passes; Fable judge 3/4 as a first-time operator.
• U2 Read-only regress green against 7070; /help/ and /phone.html reachable on the LAN; Mac and PC at the same head; no remote has new commits.
• U3 Results page open once in Greg's Chrome; text sent after 08:30 with the public tutorial URL.

6. Tutorial outline (first-time operator)

0. What you are looking at: two monitors, the phone, the five colours (LIVE green, SELECTED blue, HELD amber, KILL red, grey), preview versus live port.
1. Pick lights: map, kinds, lasso, Clear, hold to find a light in the room.
2. Point them: stage picture, nine marks, Point / Halo / Fan / Cross / Wash / Auto, Moves.
3. Shape a light: level, shutter, colour and the colour fan, gobo, beam sliders, DMX strip, Back to the look.
4. Moods and beams: wall, families, search, fade, Stack, the Playing rail, Recent, Undo.
5. Save a scene: one tap, rename, Photograph all moods (two-button sheet, room must be empty).
6. Rhythm: tap tempo, BPM, hits on picked or usual lights, beat lengths, effects on picked lights.
7. Key light and safety: the KEY and FOH caps, camera-safe, hold-to-blackout, the undo ring, Close.
8. Running a show: set list GO, timelines Play / Stop / Next, a scene tap overrides a timeline, where the show builder lives.
9. The phone remote.
10. When something is wrong: no camera, muted preview on top of the live desk, which port, never restart during a show, rollback, LEKO FOH 1 is dead at the unit.

Each chapter: one GIF under 10 s, 1 to 3 stills, a keys table, a proof footer.

7. Morning deliverable list

1. Public tutorial URL on gregbot-pages, also at /help/ on the PC's 7070.
2. PC 7070 on the night's final build, both monitors, phone page at /phone.html.
3. Results page 🆕 block: ship times, three judge scores plus the tutorial judge, BENCHMARK.md and PUNCHLIST.md links, deferred list (pixel bars, show builder rewrite), the unanswered push question.
4. Branch two-screen local on Mac and PC at the same head; nothing on GitHub.
5. One text to Greg after 08:30 with the tutorial link.

8. Clock

9. Conductor amendments after BENCHMARK.md (01:20)

BENCHMARK top 3 = blackout that keeps state, haze exempt from blackout and master, global BPM clock. Two are outside W2, so per section 2 the pick changes; the conductor decides without a Fable re-escalation because both are small server changes: - S4 Server playbacks = per-look levels (as planned) + blackout keeps state (dimmers to 0 and haze held, looks and positions kept, release restores without Undo) + haze exempt from blackout and master (a separate /api/haze hold flag, default exempt). Colour fan moves out of S4. - T2 Effects engine gains the colour fan endpoint (it already writes per-fixture colour lines). - S1 / S2 add BENCHMARK items 8 and 9: selection tools (odd, even, halves, reverse, next, previous, pick order shown) and colour / aim / gobo acting on the picked heads only. - Deferred to the results page: MIDI learn, autosave rotation + redo, audio follow, pixel mapping, blind. - U2 checks whether the PC run folder has a 0-byte rigstate.json or groups.json.