@staix/agent-hub 0.12.44 → 0.13.0

package/docs/verification/2026-10-23-0.13.0.md

@@ -0,0 +1,89 @@
+# 0.13.0 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.13.0, from merged main at 1423a0c6. On 2026-10-22 the person directed: finish the work in progress and release agent-hub and agent-mem. They also set the version rule: a release with any feature bumps the minor version, and a fix-only release bumps the patch. This release adds features, so it is 0.13.0 rather than 0.12.46. The rule is now in AGENTS.md "Releasing".
+
+- Version policy for native agent CLIs (#691, #692): `ahub agents`, person trust, and named refusals. Receipts for Codex reviewer 0.163.0 (#697), and for Kimi reviewer 2.3.0 and Qwen Code 0.26.0 (#714).
+- Extra Jcode instances with hub tools bound to an owned launch (#685, #693).
+- Usage, in three slices (#683):
+  - U1, ledger events (#698);
+  - U2, the roll-up and `ahub usage` (#702);
+  - U3, the console Usage panel (#706).
+- Code structure (#682, #684):
+  - optional code facts (#703);
+  - head-bound task symbols (#708);
+  - console changed symbols (#709) and overlaps (#710);
+  - normalized plan-symbol overlap (#715).
+- SDLC:
+  - issue and PR identity linking (#694, #695);
+  - test integrity (#481 S4, #674);
+  - person release approval (#481 S6, #690);
+  - the dogfood scorecard (#687, #701, #704);
+  - profile review checklists (#507, #675).
+- Console review guidance (#711, #712) and the pull-only queue drain with person bulk discard (#713, #716). Empty pull-only polling is detected (#681, #696).
+- The action-policy foundation (#636 slice 1, #678). Adapter pre-tool gates are still pending.
+- Fixes:
+  - check exit and pipes (#558, #676);
+  - snapshot attribution (#612, #672);
+  - WIP-respecting readiness (#655, #671);
+  - sandbox kill markers (#700);
+  - flaky macOS tests (#375, #376, #378).
+- Still open:
+  - #689, config editing from the console and dashboard;
+  - #683 U4, the dashboard Usage view (board #358);
+  - agent-mem#13 P3 and P4, the hooks and the switch from the hub to amem;
+  - #684 phases 3 and 4.
+
+## Reviews
+
+Each PR was reviewed by the planner. Where a PR changed shared storage, concurrency or privacy, an independent read-only reviewer also checked it in an isolated worktree. Every codex-connector thread was fixed or answered and resolved before merge, and each PR merged only on exact-head CI success on Ubuntu and macOS.
+
+| PR | Final head | Review | CI |
+| --- | --- | --- | --- |
+| #692 (#691) | see PR | Registry guard, seed re-anchor | exact head, success |
+| #695 (#694) | see PR | Pre-effect identity semantics | exact head, success |
+| #706 (#683 U3) | b7bacde5 | Two rounds. The first-answer test asserted a fold time; it now asserts the complete-or-behind contract | exact head, success |
+| #707 (#378) | e2387aea | Two rounds; the seed now fails on a named assertion, not a timeout | exact head, success |
+| #708 (#684 2a) | 3c762864 | Separate-table receipt, flow-revision fence, PII drop | exact head, success |
+| #709 (#684 2b) | 23a0d7c6 | A connector P1 (a raw receipt rendered unscreened) fixed with a `repositoryKey` guard | exact head, success |
+| #710 (#379) | 3212f667 | Shared disjointness predicate, PII pairs excluded | exact head, success |
+| #712 (#711) | f571745c | Six changes per the issue; the agent-shell cause offers no bypass | exact head, success |
+| #714 (#373) | c959f131 | A connector finding (stale version guidance) fixed by deriving it from COMPAT | exact head, success (the local gate rerun at the hosted 1260 s ceiling) |
+| #715 (#682 1b) | e72578c0 | The dogfood row and two nits added by the reviewer, who said so in the PR | exact head, success |
+| #716 (#713) | a6206f0a | Eight items, including busy-peer queued discard and closed-list refusal causes; console-only discard | exact head, success |
+
+## Document review
+
+Fourteen documents were stale against the 0.12.45 stamps (`help.ts` against c969a519). Read-only reviewers in five groups checked each one against `git log <stamp>..HEAD` over its paths, plus PR #715's diff. They corrected every statement a merged change made wrong or missing, with a code reference for each.
+
+| Document | Result | Checked claims and correction |
+| --- | --- | --- |
+| `README.md` | corrected | Status 0.13.0; `ahub usage`; `ahub agents` and trust under Upgrading; verification link. |
+| `docs/quickstart.md` | corrected | Install pin `v0.13.0`; "Upgrading to 0.13.0" covers version policy, Jcode re-registration and instances, `ahub init`, Usage, dogfood, review choice, symbols, the pull drain and queue discard, and the release guard. Two working-day rows. |
+| `docs/operations.md` | corrected | The doc version; `usage` in the shared-table commands; the Usage console table; `[--json]` on queue discard; the usage telemetry; `ahub report --dogfood`; the Kimi TUI drain; agent versions and the `unknown` verdict; the scope of the weekly watch; headless Jcode instances. |
+| `docs/security.md` | corrected | `action_policy` is machine-local; the new events and usage access; console-only discard and version trust; refusals under `--live-test`; the trust record; the Jcode line plus trust and its owned-launch binding; agy trust; symbol screening; release authorization. |
+| `src/cli/help.ts` | corrected | `[--full]` on budget, board and doctor; `[--json]` on queue discard; the `unknown` agents verdict. Every other row matches the parsers in main.ts and launch.ts. |
+| `docs/agent-notes/adapters.md` | corrected | Scope paths; Jcode async preflight; `ahub agents` is console-only; instance home rules; Codex reviewer `notify=[]`; the inbox polling rule. |
+| `docs/agent-notes/budget.md` | corrected | `usage-rollup.ts` in scope; expired-pause resume; reset thresholds; planner refused during a private turn. |
+| `docs/agent-notes/bus.md` | corrected | Scope paths; the #713 rules checked against the code. |
+| `docs/agent-notes/local-worker.md` | corrected | Kill markers (#700). The `"direct"` removal is no longer promised for 0.13.0, because it remains. |
+| `docs/agent-notes/daemon.md` | corrected | Queue `D` discard; `action_policy` trust; the #612 HEAD-move rules. |
+| `docs/agent-notes/tasks.md` | corrected | Notice grouping pointer; normalized symbol overlap; task code symbols; test integrity; release authorization; the dogfood scorecard. |
+| `docs/agent-notes/tests.md` | corrected | Run local tests with `env -u AGENTHUB_HOME`, because the preload keeps an inherited hub home; ripwire test fakes. |
+| `docs/agent-notes/README.md` | corrected | Background section for the rationale moved out for 0.13.0. |
+| `docs/agent-notes/benchmarks.md` | no change | Its only source change, in sandbox.ts, is outside its scope. |
+
+Follow-ups noted by the reviewers, not changed in this release:
+- `scripts/check.sh` should unset `AGENTHUB_HOME`.
+- `usage-rollup.ts`, `inbox-polling.ts`, `task-code-symbols.ts`, `symbol-normalizer.ts`, `test-integrity.ts`, `sdlc-release-authorization.ts`, `dogfood*.ts` and `console-review/symbols/usage.ts` are not yet in the AGENTS.md area lists or the `verified.json` paths.
+
+## Retirement in this release
+
+The version bump closes the #481 deprecation window (`RETIRED_WORKFLOW_FROM = "0.13.0"`). `sdlc.workflow` no longer loads, and the `phase` receipt name is refused. Three workflow tests that used `phase` inside the window failed on the first release CI run. They now assert the refusal and record `criteria`, and their other assertions are unchanged. This project uses neither setting. `local.bash_network: "direct"` is not version-gated and only warns, so its removal moves to a later release. `docs/agent-notes/tests.md` was rechecked against that test change (no rule affected) and restamped at the test commit.
+
+## Release mechanics
+
+Merge the release PR with a merge commit, because the stamps name release-branch commits. Run `node scripts/check-docs.mjs --require-fresh` on the merged main, then tag `v0.13.0`. Afterwards read the published version back from the registry with a cache-busting request.