decisions: 123, correction to 109, Console page files are live on landing
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
@@ -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.
|
- Opus seats drop to three: Sage, Darkwing and Dewey.
|
||||||
- T3's thread-create call takes a model but no effort level, so
|
- 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.
|
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.
|
||||||
|
|||||||
Reference in New Issue
Block a user