@staix/agent-hub 0.12.43 → 0.12.45

package/docs/verification/2026-10-21-469-r2-dashboard-shell.md

@@ -0,0 +1,54 @@
+# #469 R2: dashboard app shell, screenshots and width check
+
+Task #171, branch `feat/469-r2-shell` (on top of `feat/469-r1-tokens`). R2 adds the shell (top bar, sidebar or tabs), the icon sprite
+and the view keys. It keeps the view names, their order, the `agent-hub-view` cookie, the pinned ids and every action.
+
+## Source
+
+A scratch hub outside any git repository, with its own `HOME` and `AGENTHUB_HOME` (never the person's home or live hub): five fake
+pull-only peers, sixteen to twenty-four sample tasks, one console message. Headless Chromium (Chrome for Testing 156) over the
+DevTools protocol with `prefers-color-scheme` emulated. Every one of the seven views was visited at 1440, 1024, 768 and 390 px in
+light and dark (56 combinations), and one representative set is kept here.
+
+| View and size | image |
+| --- | --- |
+| Board 1440, light | `assets/469-r2-board-1440-light.png` |
+| Board 1440, dark | `assets/469-r2-board-1440-dark.png` |
+| Board 1024, light | `assets/469-r2-board-1024-light.png` |
+| Board 768, light (tabs) | `assets/469-r2-board-768-light.png` |
+| Board 390, light | `assets/469-r2-board-390-light.png` |
+| Board 390, dark | `assets/469-r2-board-390-dark.png` |
+| Agents 1440, dark | `assets/469-r2-agents-1440-dark.png` |
+| Agents 768, dark | `assets/469-r2-agents-768-dark.png` |
+
+## AC3: nothing scrolls the page sideways
+
+Measured in the page, not assumed: for each of the 56 combinations the document's `scrollWidth` was compared with the viewport width
+and every element past the right edge (outside the nav) was listed.
+
+- 1440 px: `scrollWidth` 1440 in all 14 view and theme combinations. 1024 px: 1024. 768 px: 768. 390 px: 390.
+- No element extended past the viewport in any of the 56 combinations.
+- The nav is a column of width 199 px at 1440 and 1024, and a row at 768 and 390 whose own `scrollWidth` (769) exceeds its
+  `clientWidth` (768 or 390): the tabs scroll inside the nav, as designed, and the page does not.
+- The top bar is 61 px tall from 1024 px up and 129 px at 768 and 390 (it wraps below 1024 px; the screenshots show it).
+
+## AC4: keys
+
+Tested through the page's own handler in the navigation test harness (`test/dashboard-views.test.ts`): `1`-`7` switch the seven
+views in order and write the cookie, `?` opens the key list, the buttons open and close it, and view keys are ignored inside an
+input, a textarea, a select, an editable node, with Ctrl, Alt or Cmd held, and while the key list or the task detail is open.
+`Esc` is the native dialog's own close and is not handled by the page. Six deliberate breakages of the key handler each fail a test (a seventh, accepting multi-character keys such as `01`, first survived and led to a stronger test), and eight breakages of the sprite, labels and shell CSS each fail a test too. Not covered: a
+real browser key press (no browser-driven test of the keys was run), and `Esc` itself, which rests on the dialog element.
+
+## Icons
+
+Nine Tabler Icons (outline) in one inline sprite, path data copied unchanged from tabler-icons; the MIT notice is in
+`THIRD_PARTY_NOTICES.md`. A test checks the count (at most 20), one stroke width, path-only symbols, no external reference, no
+unused or undefined symbol, `aria-hidden` on every icon, and a text label or `aria-label` next to each.
+
+## Not covered
+
+- Screenshots show Board and Agents only, at the sizes above; Office, Stream, Message, Memory and Settings were measured for width
+  but not photographed.
+- Chrome only. The sidebar's sticky height uses `100vh`, which on a mobile browser with a collapsing toolbar was not tried.
+- The "tabs scroll sideways" behaviour at 390 px is shown by the cut-off fourth tab in the screenshot, not by a scroll gesture.

package/docs/verification/2026-10-21-469-r3-dashboard-board.md

@@ -0,0 +1,51 @@
+# #469 R3: dashboard board, side sheets and the Plan sheet
+
+Task #172, branch `feat/469-r3-board` (on top of `feat/469-r2-shell`). R3 changes the cards, the task detail and where the five board
+forms live. It keeps drag and drop, the Pull and Assign buttons, the Ready and Waiting subheads, "Show N older" and every action.
+
+## Source
+
+A scratch hub outside any git repository with its own `HOME` and `AGENTHUB_HOME` (never the person's home or live hub): five fake
+pull-only peers, eight sample tasks (one in progress, backlog tasks, no owner on some). Headless Chromium (Chrome for Testing 156)
+over the DevTools protocol with `prefers-color-scheme` emulated, at 1440x1000 and 390x900.
+
+| What | image |
+| --- | --- |
+| Board 1440, light | `assets/469-r3-board-1440-light.png` |
+| Board 1440, dark | `assets/469-r3-board-1440-dark.png` |
+| Board 390, light | `assets/469-r3-board-390-light.png` |
+| Detail sheet 1440, light | `assets/469-r3-detail-1440-light.png` |
+| Detail sheet 1440, dark | `assets/469-r3-detail-1440-dark.png` |
+| Detail sheet 390, dark | `assets/469-r3-detail-390-dark.png` |
+| Plan sheet 1440, light | `assets/469-r3-plan-1440-light.png` |
+| Plan sheet 390, light | `assets/469-r3-plan-390-light.png` |
+
+## AC5: cards and the detail sheet
+
+Measured in the page for eight cards at each of the four size and theme combinations:
+
+- every card has two children (the head with the avatar and the title, and one line with the badge and the release chip), exactly one
+  badge, exactly one owner avatar, and a title no taller than two lines (`title height / line height` was 2 at most);
+- the page does not scroll sideways (`scrollWidth` equals the viewport at 1440 and 390);
+- the detail sheet is open and pinned to the right edge at 1440 (x 920, width 520, the full 1000 px height) and fills the screen at 390
+  (x 0, width 390, the full 900 px height); the Plan sheet likewise (x 880, width 560 at 1440).
+
+The detail groups its lines into Status, People, Dates and Links. Each original line (class, stage, waiting, rework, check, SDLC,
+overdue, owner, reviewer, guidance, description, planned and actual dates, release, GitHub link, pinned) appears exactly once, in its
+group; a group with nothing to show is left out. Group headings are `h4`, not `h3`, because the board tests find the five columns by `h3`.
+
+## AC6: the Plan sheet
+
+The five forms (`planning`, `split-backlog`, `release-new`, `release-plan`, `propose`) moved out of five `<details>` blocks (plan, split, releases, delivery evidence, propose) into one native
+`<dialog id="plan-dialog">` opened by a Plan button in the board toolbar. Their controls were compared with `origin/main`: identical
+ids and order in all five (11, 4, 3, 6 and 5 controls), and every submit handler still attaches by id. The Releases panel, the delivery
+evidence panel and the split panel keep their ids. A test now pins the full control list of each form.
+
+## Not covered
+
+- Drag and drop, hover and the pressed (dragging) shadow were not exercised in a browser: the drop handlers are unchanged and covered by
+  the existing board tests, and the hover and drag styles are CSS only, read, not seen.
+- Only the sample data above was rendered: no release chip, no GitHub link, no SDLC lifecycle and no rework round appear in the
+  screenshots; those lines are covered by the DOM tests only.
+- The sheet slide-in animation was not observed, and `Esc` rests on the native dialog.
+- Chrome only.

package/docs/verification/2026-10-21-469-r4-dashboard-views.md

@@ -0,0 +1,77 @@
+# #469 R4 and R5: the other dashboard views, glyphs to icons, Office colour checks
+
+Task #173, branch `feat/469-r4-views` (on top of `feat/469-r3-board`). R4 restyles Agents, Stream, Memory, Settings and Message and
+replaces the symbol glyphs. R5 puts the Office scene's colour use under the contrast test. Behaviour, view names and order, the view
+cookie, element ids and every action are unchanged.
+
+## Source
+
+A scratch hub outside any git repository with its own `HOME` and `AGENTHUB_HOME` (never the person's home or live hub): five fake
+pull-only peers, seven sample tasks plus a backlog task, four short-term memory notes (decision, fail, contract, finding) and three
+console messages. Headless Chromium over the DevTools protocol with `prefers-color-scheme` emulated, at 1440x1000 and 390x900.
+
+| What | image |
+| --- | --- |
+| Agents 1440 light / dark | `assets/469-r4-agents-1440-light.png`, `assets/469-r4-agents-1440-dark.png` |
+| Agents 390 dark | `assets/469-r4-agents-390-dark.png` |
+| Stream 1440 light, 390 light | `assets/469-r4-stream-1440-light.png`, `assets/469-r4-stream-390-light.png` |
+| Memory 1440 light / dark, 390 dark | `assets/469-r4-memory-1440-light.png`, `assets/469-r4-memory-1440-dark.png`, `assets/469-r4-memory-390-dark.png` |
+| Settings 1440 light / dark | `assets/469-r4-settings-1440-light.png`, `assets/469-r4-settings-1440-dark.png` |
+| Message 1440 light | `assets/469-r4-message-1440-light.png` |
+| Office (Flat) 1440 light / dark | `assets/469-r4-office-1440-light.png`, `assets/469-r4-office-1440-dark.png` |
+
+The rig also shot the other combinations (all six views at 1440 and 390, light and dark); only the ones above are attached.
+
+## R4
+
+- **Agents.** Every peer row (five of five) has one summary line (queued count, "Working on #n" or "No active task") and exactly one
+  closed `<details class="peer-fold">` holding the former meta lines. Row height was 144 to 145 px with the fold closed. The status
+  notice stays outside the fold. Approvals stay first.
+- **Stream.** The filter chips and Follow latest are in the section head, above the scrolling list. Each event is a head line (time,
+  sender, kind) above a monospace body; in the page the left edge of every event was the same x (249 at 1440, 29 at 390). That is
+  aligned rows, not four separate columns: the spec's "time column, kind, sender, body" is met as one head line plus the body.
+- **Memory.** Rows show title, a kind badge and a meta line with the id, peer and date and time (not a relative age); the selected row has an accent edge. The graph
+  and the detail pane use tokens only. With four notes: four rows, one pressed, the detail pane filled.
+- **Settings.** Six groups as sections. The reload row now has padding, and a "restart pending" badge and a count by "Pending
+  restart" exist in the markup. The text lines, Preview, Save and Undo are as before.
+- **Message.** Same form, capped at 640 px, with the shared field and label styles.
+- **No page scrolls sideways** in any of the six views at 1440 or 390 in either theme (`scrollWidth` equals the viewport).
+
+## AC7: glyphs
+
+- A test fails if any of `○ ● × ‖ ⚑ ★ → ⟳` is back as a quoted string in the page, and one fails if an Office shape name is renamed.
+  Both were run red (see below).
+- The star, the stream arrow and the Office "checking" mark are Tabler `star`, `arrow-right` and `refresh` (the path data was compared
+  with the upstream files, unchanged). The sprite has twelve symbols of the twenty allowed, and `THIRD_PARTY_NOTICES.md` names all of them.
+- The Office conditions are drawn as shapes (ring, disc, cross, bars, raised hand), each next to its words. The condition names
+  (`idle`, `busy`, `offline`, `paused`, `waiting`) are unchanged.
+- Every icon use sits beside a text label or has an `aria-label`; a test counts the `icon()` and `officeIcon()` call sites.
+
+## R5: Office colours and contrast
+
+The Office rules already named colours only through `var(--token)`, so nothing was remapped. What changed is the checks:
+
+- The colour-literal test no longer skips the Office block.
+- A new test reads the tokens each Office rule uses, fails on a token it does not classify, and checks text tokens at 4.5:1 and mark
+  tokens at 3:1 against the three Office surfaces (`--panel-soft`, `--panel`, `--control`), in both themes. The earlier R1 test
+  already covered text, `--dot`, `--on-accent`, disabled controls and the peer palette.
+- **Decision to review:** the hairline tokens `--line` and `--control-border` carry no information (room, desk and shelf edges,
+  dividers) and measure 1.2 to 1.7:1 on those surfaces, so they are classified as separators and not held to 3:1. If a reviewer wants a
+  3:1 edge, that is a colour change to the tokens, not a test change.
+
+## Checks that were run red
+
+Each was applied to the working tree, the tests run, and the file restored:
+
+- an Office rule using an unknown token: the new Office token test failed;
+- a `⟳` put back into the page script: the AC7 glyph test failed;
+- the Office `ring` shape renamed in `office-model.ts`: the AC7 shape test failed.
+
+## Not covered
+
+- The Office was shot in Flat mode with five idle peers. The busy, offline, paused and waiting shapes, the checking icon and the
+  approval hand were checked by the model tests and the DOM tests, not seen in a browser. Isometric was not shot.
+- The "restart pending" badge on a setting row and the Pending restart count need a pending key, and the sample hub had none, so they
+  were not rendered. They are covered by the DOM tests only.
+- Memory's long-term and tasks tiers, and the graph with more than one hop, were not shot.
+- Chrome only. Of the attached images, the Message and the dark Office were not looked at one by one.

package/docs/verification/2026-10-21-469-r6-dashboard-motion-states.md

@@ -0,0 +1,82 @@
+# #469 R6: keyed rendering, quiet motion, and loading, empty, disconnected and toast states
+
+Task #174, branch `feat/469-r6-motion` (on top of `feat/469-r4-views`). The poll interval, every action, authority rule and pinned
+element id are unchanged.
+
+## Source
+
+A scratch hub outside any git repository with its own `HOME` and `AGENTHUB_HOME` (never the person's home or live hub): five fake
+pull-only peers and eight sample tasks, plus a second hub with no peers and no tasks for the empty views. Headless Chromium over the
+DevTools protocol with `prefers-color-scheme` emulated, at 1440x1000 and 390x900. `/snapshot` was held, failed and released through
+the DevTools Fetch domain to produce the skeleton and the disconnected state.
+
+| What | image |
+| --- | --- |
+| Skeleton, board 1440 light / 390 dark | `assets/469-r6-skeleton-1440-light.png`, `assets/469-r6-skeleton-390-dark.png` |
+| Toast stack 1440 light / dark, 390 light | `assets/469-r6-toasts-1440-light.png`, `assets/469-r6-toasts-1440-dark.png`, `assets/469-r6-toasts-390-light.png` |
+| Disconnected 1440 light / dark, 390 dark | `assets/469-r6-disconnected-1440-light.png`, `assets/469-r6-disconnected-1440-dark.png`, `assets/469-r6-disconnected-390-dark.png` |
+| Empty board 1440 light / dark | `assets/469-r6-board-empty-1440-light.png`, `assets/469-r6-board-empty-1440-dark.png` |
+| Empty peers 390 light / dark | `assets/469-r6-agents-empty-390-light.png`, `assets/469-r6-agents-empty-390-dark.png` |
+| Board after load 1440 light, 390 dark | `assets/469-r6-board-1440-light.png`, `assets/469-r6-board-390-dark.png` |
+
+## AC8: keyed rendering
+
+How it works: a keyed pass (`keyedStart`) hands out one node per key. A card, peer row or memory row whose JSON signature is the same
+as last time is the same node; a changed one is rebuilt (its listeners close over its data, so it is replaced, not patched) and, if
+it held focus, `update()` hands the focus to the replacement. Keys that are gone are dropped. The card signature includes the
+board context, the capabilities its buttons depend on and the release name, so a change to any of those rebuilds the card.
+
+- **vm tests** (`test/dashboard-motion.test.ts`), on the real board code and the real `update()`: after a poll that changes one
+  task the other three cards are the same objects, the changed one is new, and a focused card keeps focus; a focused card that
+  itself changes passes its focus to its replacement; an unchanged poll leaves `children` as the same array; a gone card is removed
+  and the rest are untouched; a card that changes capability is rebuilt.
+- **Chrome**, four theme and size combinations: focus the first card, add a task, wait three polls: `document.activeElement` is
+  still that card, it is still connected, and the three cards after it are the same nodes (`3/3`), with the card count up by one.
+
+## AC9: motion, states
+
+- **Motion test over the CSS:** every `transition` is `none` or on `transform` or `opacity` only, 120 to 200 ms (the Office's own
+  .8 s transform move is pinned elsewhere and allowed up to .8 s); every `@keyframes` moves only `transform` and `opacity`; every
+  animation names one of the known keyframes at 120 to 200 ms (the Office ones keep their pinned timings); the only `infinite`
+  animation in the page is the Office pulse; and one `@media(prefers-reduced-motion:reduce)` rule turns `transition` and
+  `animation` off for `*`, `*::before` and `*::after`.
+- **Chrome with reduced motion emulated:** computed styles at 1440. With no preference: view animation `view-in` 0.16 s, button
+  transition 0.12 s, card transition 0.15 s, toast `toast-in`. With `reduce`: all four are `none` or `0s`.
+- **Skeleton:** five column blocks on the board and three bars in the peer list, `aria-hidden`, with the text "Loading the board..."
+  next to them. With `/snapshot` held they were on screen; after release `.skeleton` was gone from the page (0 left). They do not
+  animate.
+- **Empty views:** the board, peers, stream, approvals, memory (three cases) say what fills them and the command. Every command they
+  name is in `ahub help` (a test). The empty hub showed the board and peers texts in Chrome.
+- **Disconnected:** with `/snapshot` failing, `main` gets `data-stale`, its content measured `opacity 0.6`, the status read
+  "Disconnected / retrying: Failed to fetch", and the line read "Last snapshot at 10:43:11 PM. Polling continues every second."
+  After the fetch came back both were cleared. Seen at 1440 and 390, light and dark.
+- **Toasts:** three notices (one success, two errors) gave a stack of three with a Dismiss button each, the box inside the viewport
+  and no sideways scroll (`scrollWidth` equals the viewport). Five seconds later the success had faded and both errors were still
+  there; pressing Dismiss on each left none. Test: four at most, the same text replaces its toast, an empty text clears the stack,
+  the fade starts at 4 s and the removal 160 ms later, an error never expires, reduced motion keeps a success.
+
+## Pinned contracts changed (named, nothing loosened)
+
+- `test/ui.test.ts`: it read `#notice` as one element (`textContent`, `error`). With a stack those two reads come from the newest
+  toast, defined once in the harness. Every assertion below is unchanged.
+- `test/dashboard-views.test.ts`: it pinned five `setTimeout(` calls in the page. The five are still there; `notice()` adds two
+  (the fade and the removal), and the test now pins both counts, so a timer anywhere else still fails it.
+- The card's own transition was `transform .15s, box-shadow .15s`. It is `transform .15s` now, because the spec limits motion to
+  `transform` and `opacity`; the hover shadow still appears, without easing.
+- `update()` gained focus carry-over and `resetView` clears the keyed caches; neither changes the signature fast path.
+
+## Checks that were run red
+
+Each applied to the page, the new tests run, the file restored: a cache that never hits; no focus hand-off; a success toast that
+never fades; an error toast that fades; a `width` transition; a weakened reduced-motion rule; an `infinite` card animation; a
+disconnected line never cleared; an animated skeleton; a capability left out of the card signature. Each failed the test written
+for it.
+
+## Not covered
+
+- Peer rows and memory rows use the same keyed pass, but only the board's cards were driven through a poll in a browser and in the
+  vm tests; the peer and memory paths are covered by the shared pass test and by the existing tests, which still pass.
+- A card that is replaced and was hovered loses its hover until the pointer moves. That is the browser's behaviour for a new node.
+- The card's enter animation and the toast's fade were checked by computed style and by the test over the CSS, not watched.
+- Dragging a card across a poll was not exercised.
+- Chrome only. The dark skeleton, the 390 empty board and the Stream's empty text were not looked at one by one.

package/docs/verification/2026-10-21-grok-config-acp-t0.md

@@ -0,0 +1,30 @@
+# Grok config-only ACP T0, 2026-10-21
+
+This receipt separates the generic ACP implementation from native Grok readiness. It does not establish #486 AC1-AC6 or #451 AC3 as complete.
+
+## Observed native build and isolation
+
+- Local native binary reports `grok 1.0.62 (1474f9cbdd91)`.
+- Version, agent help and stdio help exited 0 under a temporary HOME, Grok home, XDG config/cache/data directories and project directory outside a Git repository.
+- The protocol probe used `grok agent --no-leader stdio`, with inherited agent markers removed and a probe-specific peer identity. The probe harness copied no personal config or credential files and wrote only to its isolated directories; no production hub was used. The exact native-file check below is bounded, and broader native credential state remains unverified.
+- The saved agent help states that the leader default is `[cli] use_leader` in `config.toml`, rather than a guaranteed foreground default; `--no-leader` forces a new agent. A plain `grok agent stdio` argv therefore does not itself establish foreground ownership in an ambient home. `--leader-socket` is also an attach selector. The config compiler therefore requires explicit standalone `--no-leader` for recognized Grok declarations before any process starts, and still refuses `--leader` and `--leader-socket`; isolated HOME alone is not substituted for the opt-out.
+- Before/after SHA-256 values of the exact real Grok `config.toml` and `version.json` matched. The additionally checked `config.json`, `settings.json` and `mcp.json` were absent before and after. This bounded check is not a claim about every native configuration path.
+
+## Protocol result
+
+- Initialize replied and advertised `loadSession: true`, image/audio prompt support false, embedded context true, HTTP/SSE MCP support and session list/resume/close capabilities.
+- Initialize did not provide `agentInfo`. The config-only adapter requires the observed native name/version pin to match initialize before creating a session or prompting. The native build therefore has no usable runtime identity pin under this contract.
+- The separate raw protocol probe attempted `session/new` in the isolated project with an empty MCP server list. It received an RPC error. Its raw error payload was neither logged nor published; the cause remains unclassified.
+- No model prompt or native MCP tool ran. Session/load echo, session/set_mode, usage/occupancy and a real hub-tool result are unverified. Advertising load or MCP support is not proof of those operations.
+- Because no prompt ran, no process-tree and socket/IPC observation while a prompt was active exists. The required no-detached-leader evidence is unverified.
+
+## Owned group and teardown
+
+- The runtime ownership helper positively verified the direct child, its original process group and shared process signature at start and immediately before teardown.
+- The first probe's teardown returned `unconfirmed`. A fresh process-table read after the probe exited showed no Grok process. This is not recorded as a confirmed stop receipt.
+- A post-SIGKILL defunct-row observation edge was fixed and covered by deterministic regression tests: after the last signal, wait for the original group to disappear within the bound, tolerating command/parent changes of a dying row while preserving PID/start/group identity. Pre-signal ownership checks remain strict, and no process outside the spawned group is signalled.
+- A second isolated probe with the same native build again lacked initialize identity and had session/new refused. With the corrected observation fence, start and pre-stop group checks passed, group disappearance was confirmed, and a separate fresh process-table read found no Grok process. The exact real-config hashes again matched. This confirms teardown for this refused attempt, not foreground behavior during a model prompt.
+
+## Readiness decision
+
+Grok remains unsupported by this receipt. The generic config-only ACP path is covered independently with the repository's fake ACP transport, including identity mismatch, load-echo refusal, owned-group checks, permission ACKs, read-only ceilings, task delivery and project isolation. Native Grok admission still needs a build with matching initialize identity plus successful isolated session creation, actual hub-tool execution, load-echo evidence and foreground tree/IPC proof during a prompt. No permission, quota, sandbox, planner or reviewer claim is inferred from these observations.

package/docs/verification/2026-10-22-0.12.45.md

@@ -0,0 +1,60 @@
+# 0.12.45 release verification
+
+This record covers release preparation and source review. It does not claim publication, installation, a running-hub restart or a live TUI launch.
+
+## Candidate
+
+Version 0.12.45, from merged main at 0612e5d5. The person directed on 2026-10-22 to finish the work in progress and release it.
+
+- Dashboard redesign (#469): tokens (#649), app shell and view keys (#650), board cards with detail and Plan sheets (#651), view restyle and Office colours (#659), keyed rendering, motion and loading, empty, disconnected and toast states (#660), and follow-ups (#662, #664).
+- External adapter modules and the conformance kit (#451 A4, #648, #653); the A5 guide and adapters note pass (#668).
+- Peer lists and the CLI surface derived from adapter definitions (#625, #656), and PeerAdapter capability members (#625 phase 6 slice 1, #667).
+- Structured review findings with an Important gate (#481 S3, #652, #657) and plan conformance with person-only departure acceptance (#481 S2, #665).
+- #230 S10 review-readiness rulings (#641, #643, #644), #428 racy same-size rewrites of large files (#646), #221 channel hints (#647), #225 stale roster keys and the shared git budget (#663), #654 Kimi TUI retained-command diagnostic (#658), and #661 held snapshot clocks for runner-speed-dependent daemon tests (#666, #669).
+- Still open: #655 (dependency-ready auto-assignment ignores the owner's WIP cap), board task #287 (external-kind instances), the later #625 phase 6 slices and #481 S4-S7.
+
+## Reviews
+
+| PR | Final head | Review | CI |
+| --- | --- | --- | --- |
+| #641, #643, #644 (#230) | see PRs | Spec ruling, then code review with red-first regressions | exact head, success |
+| #646 (#428) | e4b3fb9a | Two rounds with an independent reviewer (unbounded hashing and the atHead regression fixed) | exact head, success |
+| #647 (#221) | 0b1ae257 | Reviewer read; a connector P2 (legacy nudge under a held hint) fixed by the reviewer | exact head, success |
+| #648, #653 (#451 A4) | 222a5839, 4a271455 | Two rounds with independent security and packaging reviews; project-cwd SDK resolution, whole-daemon refusal and offline roster fixed; follow-ups in #653 | exact head, success |
+| #649, #650, #651, #659, #660 (#469) | see PRs | Reviewer read per phase; R3 seed rot re-anchored; connector findings fixed or tracked (#293, #296) | exact head, success (R6 after one Ubuntu rerun of the #661 flake) |
+| #652, #657 (#481 S3) | d60d5bd6, ecc4b39f | Two rounds with an independent reviewer (unbound-head bypass and head carry-forward fixed); a connector P1 (supplied head) fixed in #657 | exact head, success |
+| #656 (#625) | d803de2b | Reviewer read against the projection ruling; fixture correction (#294); bundle rebuilt after #658 | exact head, success |
+| #658 (#654) | a6409371 | Reviewer read; root cause reproduced by delay | exact head, success |
+| #662 | f46cb77f | Main-red fix after #656 and #660 crossed | exact head, success |
+| #663 (#225) | fd71191b | Reviewer read; three connector findings (instance eligibility, shared-config removal, result text) fixed red-first | exact head, success |
+| #664 (#296) | 0d21de7a | Reviewer read; fixes two connector P2s from #660 | exact head, success |
+| #665 (#481 S2) | 88bec9ab | Three rounds with an independent reviewer (rename and root-entry bypasses, status writes, off-mode, queue rename regression fixed); a connector P1 (departure scope) fixed red-first (#298) | exact head, success |
+| #666, #669 (#661) | 948b6afd, 389262df | Reviewer read; red-first with a slowed-git stand-in; a connector P1 (20 s per-test ceiling) fixed | exact head, success |
+| #667 (#625) | 17ab88d2 | Reviewer read against the phase 6 rulings | exact head, success |
+| #668 (#451 A5) | fc052e89 | Reviewer read; two connector P2s fixed by the reviewer | exact head, success |
+
+## Document review
+
+Fourteen documents were stale against the 0.12.44 stamps. Each was checked against `git log <stamp>..HEAD` over its paths (with PR #665's diff) by read-only reviewers in four groups, and corrected where a merged change made a statement wrong or missing.
+
+| Document | Result | Checked claims and correction |
+| --- | --- | --- |
+| `README.md` | corrected | Status 0.12.45; dashboard, adapter modules, review findings and plan conformance, stale roster key removal; verification link. |
+| `docs/quickstart.md` | corrected | Install pin `v0.12.45`; "Upgrading to 0.12.45" (dashboard, modules, findings, plan conformance and `accept-departure`, Kimi diagnostic, channel hints, #428). |
+| `docs/operations.md` | corrected | New "External adapter modules" section; recovery floor; conditional source refusal; shared git budget; stale roster keys; SDLC S3 and S2 with pointers to `docs/sdlc.md`. |
+| `docs/security.md` | corrected | A4 trust paragraph (a pin authorizes code, not a sandbox); delegated-CLI refusals include departure acceptance; metadata-only plan conformance reads; stale roster keys grant nothing. |
+| `src/cli/help.ts` | corrected | `release-assign <reason...>`; roster remove deletes a stale instance key; `plan-review` flag grouping; native usage rendered from definitions matches each entry parser. |
+| `docs/agent-notes/tasks.md` | corrected | Supplied-head binding, id-only settlement, hub-proposed recurrence markers, S2 conformance and departure consent rules; `plan-conformance.ts` in scope. |
+| `docs/agent-notes/daemon.md` | corrected | Module recovery floor, conditional source refusal, historical receipt reads, stale keys, external catalog, retained `kimi_cmd` diagnostic. |
+| `docs/agent-notes/adapters.md` | corrected | PeerAdapter capability ports (#667). |
+| `docs/agent-notes/tests.md` | corrected | Held snapshot clocks, the 20 s per-test ceiling, seed re-anchoring, CI tests the PR head, kit and fakes under `src/adapters/conformance/`. |
+| `docs/agent-notes/local-worker.md` | corrected | #428 racy large-file rule. |
+| `docs/agent-notes/budget.md` | corrected | `Budget.report` skips external module kinds. |
+| `docs/agent-notes/README.md` | corrected | Background section holding the rationale moved out of the notes. |
+| `docs/agent-notes/benchmarks.md`, `bus.md` | no change | Rules checked against the diffs; no contradiction. |
+
+`AGENTS.md` and `docs/verified.json` gain the new task-board and test paths, and the pre-0.7.7 issue-numbering note is removed from `AGENTS.md` at the person's request.
+
+## Release mechanics
+
+Merge the release PR with a merge commit (the stamps name release-branch commits), run `node scripts/check-docs.mjs --require-fresh` on the merged main, then tag `v0.12.45`.