oficina / docs Public

Merge main, and two things that answer confidently instead of failing

a6fa843 brought live sync to main. The only conflict was the build
script's rename (build-editor.mjs became build-bundles.mjs when it
started emitting two): the live-update test step is kept exactly as it
was and only the reference repointed. The editor bundle is rebuilt on
top of that branch's own changes to editor-entry.js, which is why a
rebuilt bundle is never hand-merged.

Merged rather than rebased because this branch is already pushed, and
rewriting pushed history would need a force push.

Two entries for AGENTS.md's section on tools that answer wrongly rather
than failing.

`carlos channels` reports which release a channel POINTS AT, not which
one the box is SERVING, and adoption runs on an hourly timer — so the
two disagree for as long as an hour after a promote. Observed
2026-09-01: edge read the new version while the live host served the
previous one for five minutes, closed within seconds by a restart.
Neither command fails and nothing says "not live yet". Marked as one
observation rather than a measurement, because this branch did not
re-verify it.

And the one this session earned. A merge commit on main was reported as
a breach of the shipping cadence, and I passed it on to Paul as one —
including "two sessions noticed it independently", when the second
session was the one who told me. `amadan branch merge` produces a merge
commit itself; the branch had landed correctly through the sanctioned
gate. A minute with the tool would have caught it. What is written down
now is that another session's report is evidence about what they saw
rather than a fact you have checked, and relaying it flatly launders one
into the other.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YYB9fUAfxXNzkeC3fsFYzR