From ac4f617a4597f8902f508e5e18c55853785500f4 Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Mon, 12 Oct 2026 16:55:06 -0500 Subject: [PATCH] decisions: 123, correction to 109, Console page files are live on landing Co-Authored-By: Claude Opus 5.5 --- docs/plans/2026-09-26_lead-decisions.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/plans/2026-09-26_lead-decisions.md b/docs/plans/2026-09-26_lead-decisions.md index 9c7ff75d3..c5b161487 100644 --- a/docs/plans/2026-09-26_lead-decisions.md +++ b/docs/plans/2026-09-26_lead-decisions.md @@ -2775,3 +2775,13 @@ which stay with him. Each item names who decided it and what happened. - Opus seats drop to three: Sage, Darkwing and Dewey. - T3's thread-create call takes a model but no effort level, so Haiku's high effort is set in the pane and confirmed there. +123. **Correction to decision 109: Console page files are live on landing + (2026-10-12).** Decision 109 says a webui change reaches the Console + only when it restarts. That holds for the server modules, but not + for `packages/webui/src/public/`. `serve.mjs:233` reads each page + file from disk on every request and sends it with `cache-control: + no-store`. So a landing that changes a public file is live on the + next page load. Sage found this at row 95's gate. + - Until the Console runs from a pinned copy, a landing that touches + `packages/webui/src/public/` waits for Mos's go, not just a + notice. The rest of decision 109 stands.