salvage: uncommitted work from dewey-r176 (disk cleanup #824, 2026-11-06)

This commit is contained in:
mos committed 2026-11-06 10:00:48 -06:00
1 parent 473258a51e
commit b73ba94810
16 files changed
+663 -68

No files matched your search

+37 -10
View File
@@ -449,16 +449,15 @@ copy fails its gate and rolls back. Use two phases instead (row 169, Gitea
gate check but the PM's, and writes the pointer with `pm` false and
`pmPending` true. The log's final line is `result ok` with `pm pending`.
`status` and `--plan` print the pending state and the next step.
2. Jason sets `harness` with `plugins set` through the live bus. Until row
175 lands, `scripts/mosaic` doesn't dispatch `plugins`, so the command is
`node <copy>/packages/cli/src/cli.mjs plugins set --file P --business ID`.
`<copy>` is the copy the bus runs from, the pointer's; the bus refuses
`human-required` from any other tree. P holds one patch,
`{"revision":"<64 hex>","plugins":{"<kind>":<value>|null}}`. The revision
comes from `node <copy>/packages/cli/src/cli.mjs plugins --business ID`.
A kind with a value is set to it, `null` removes the kind, and a kind the
patch doesn't name keeps its setting. Row 175's fixed `mosaic plugins
set` replaces this form once that row lands.
2. Jason sets `harness` with `plugins set` through the live bus. Copies from
before 98d29769e use `node <copy>/packages/cli/src/cli.mjs plugins set --file P
--business ID`; later copies dispatch `mosaic plugins set --file P --business ID`.
On the Q173 test system, the tester can run the latter with `--tester`.
`<copy>` is the pointer's copy, the one the bus runs from; human commands from
any other tree refuse `human-required`. P holds one patch,
`{"revision":"<64 hex>","plugins":{"<kind>":<value>|null}}`. Read the revision
with the same copy's `plugins --business ID` command (`--tester` for the tester).
A value sets the kind, null removes it, and an unnamed kind keeps its setting.
3. `pm-on BUSINESS` refuses `not-pending` without a pending pointer and
`harness-unset` unless `harness` is a non-empty list the pointer's copy
loads. It restarts the bus alone, with `--pm` on the same copy, and runs
@@ -813,3 +812,31 @@ oldest-first in pages of 100, with a 200-message display window. Sending does
not claim an assistant answer; an uncertain receipt is never retried. Read the
current list/history before trying again. Activation still needs Mos's separate
window; changing these files does not authorize a live Console action.
### Console tester listener (`serve --tester-port N`, row 176)
`node packages/webui/src/cli.mjs serve --tester-port N` adds a second listener
bound only to `127.0.0.1:N`. N must be an integer in 1024..65535, different
from `--port` and never 7332 (the tunnel's forwarded port). It requires the
bus configuration. It calls only the tester shim; the main listener keeps its
existing human transport and rejects every `x-mosaic-tester` request.
The tester listener rejects the main preview auth header and only accepts its
own loopback Host/port. Its Settings banner identifies the tester. Its instance,
route and name editors use the tester's three writes; settings, document saves,
assistant stop, role messages and chat writes stay refused. Writes require the
exact `http://127.0.0.1:N` Origin, same-origin Fetch Metadata, JSON and the existing
bounded strict bodies. `tester-off` and `tester-required` answer HTTP 403.
`scripts/webui-service.sh render|install --tester-port N` carries the flag into
ExecStart, and status names its URL. Bad tester ports exit 4. Install remains a
unit write for the authorized operator, with no start/restart verb.
`stack-release.sh activate ID BUSINESS --tester-port N` replaces or adds this
Console flag in both the installed unit and the pointer. It checks the target
copy's own Console before stopping anything; an explicit unsupported request
refuses `tester-port-target`. Without an explicit flag, activate and rollback
keep it between supporting copies, or drop it when the target predates support.
The plan prints the final Console flags and any dropped `--tester-port N`;
the steps log records a drop too. `pm-on` keeps the pointer's Console flags.
These operations retain their existing Mos/Jason window authority. Nothing in
this row forwards the tester port through the tunnel or changes live units.