CommHub #730 / #1138 public queue-policy receipt, 2026-10-13.

Behavior delivered by PR2701:
Only the existing Hub-authenticated Dashboard classifier (source dashboard-chat, auth_origin user, valid dreq request identity) gets the new bounded 4-hour default Codex queue deadline. Machine/scheduler/legacy/unknown sources keep 30 minutes. Explicit runtime options and valid ANET_QUEUE_TIMEOUT_MS retain precedence; execution/startup budgets and Hub cancellation/expiry remain independent. Generic steer permission alone does not enable the longer default. Hub expiry or permissions may terminate earlier.

Exact source / core validation:
Final candidate 153290350123a74013ed87105a84e84b67d185bc; tested PR merge f190635a6efc15572fc3418346a7611dbe2a45a1; public main source 40d1400484e036c0794d5aed642b317e72a98554. Their full Git tree matches 6c1e077e6e62c5b467ac24b9f5074834efe7c723. PR2701 merged normally at 2026-10-13T10:58:33Z.
Final Docker Actions 38386454842/job115259334646: 71 PASS, 200 assertions, and the production-CLI-marker negative mutation raises the expected assertion. Type ratchet 38386454718, exact pair 38386455003, activity 38386454781, docs integrity 38386454774 and all 10 required contexts passed. This is isolated core/installation validation; it is not a native user's live queue acceptance.
Original local 90-second Docker build timeout and 20-second cached-image run timeout (70 PASS / 1 fixture FAIL, missing reportCapacityRetry stub) remain recorded. Final 5-second targeted CLI probe passed after correcting the test stub; total local validation remained below two minutes. Intermediate docs-integrity 38385818438 failed because the new guide assertion was missing from the RELEASE-SOP inventory; the inventory was corrected without bypassing the checker. Own PR's optional Docker E2E 38386454833 and QA 38386454901 were canceled after merge; canceled does not mean PASS. Main/release/peer workflows were not canceled.

Node public proof:
Formal main release 38387150580 built exact 40d1400484e036c0794d5aed642b317e72a98554; build, four gates, publish and aggregate all SUCCESS. Anonymous registry proof observed 2026-10-13T11:08:38Z: @sleep2agi/agent-node 2.5.0-preview.141, 594573 bytes, sha256 35b4086417eed026200894cb399c3c6153c322439ed2e09202be9b95d23c6aa7, sha1 d079cb4c6510a1aa595913090a87b32d59ec5e63, integrity sha512-UOGViQwnJyL9zgxT9HOv5XKsc5wmi0oFU9vZXsfF96gU6/TTpNzapEBlu7VyY2vbyEUpskrWwaYZGUaQQOE44w==. The public tarball equals the CI gated-tarball byte for byte. preview=141; latest=2.5.0-preview.58 matches the baseline captured after Node dispatch and before CLI dispatch.

CLI companion:
First formal main release 38388205218 built the same 40d source. Docker install, pair and notes gates passed, but guide-version gate4/job115265377474 FAILED: both getting-started guides still stamped and described preview.174. Publish was SKIPPED; no CLI175 publication occurred. Corrected both stamp and matching candidate prose to .175 after verifying agent-network/bin/cli.ts is unchanged from the .174 source. Default-password validation remains source continuity from the earlier checked .172, not a newly repeated default-path test. The original failed run is preserved. The corrected CLI175 must be built and gated from the subsequent exact merged main commit; Node141 retains its original public source. Final CLI registry/artifact facts will be recorded only after verification.

Operational scope / recovery:
No production lifecycle, schema, account, credential, provider/model, port, shared app-server or original thread was changed. The reporting node continues its original runtime; public packages do not prove adoption. Mother #730 remains open for active-owned-turn human steering/preemption, queue-position UI and original-device confirmation.
The original Install/Upgrade sections in release-v2.5.0-preview.141.md and release-v2.3.0-preview.175.md specify paired private-prefix installation, original-owner normal-idle adoption, actual entrypoint/version and natural-task verification, previous-prefix rollback, and private-state backup boundaries. Existing ops documentation remains authoritative for startup, proxy/tunnel topology and secure secret sources. Git restores software and recorded procedures, not production data, login state or private conversation history; no fresh-machine disaster-recovery pass is claimed.


Final CLI public proof:
Guide correction / Node receipt PR2702 merged normally at 2026-10-13T11:14:04Z into main 1b85bca7e770d86b7f07cf12b1e8099f2ec3b00f, candidate ef82ded0afcf066281b35cbd472ec654da431d35. All 10 required contexts and docs-integrity 38388648601 passed. Docker human-queue 38388648593/job115266610014 tested merge 75d60b52007bebcdda7730161b839ce054465440: 71 PASS / 200 assertions and the production CLI marker negative ASSERTION RED. Only four documentation files changed from 40d; agent-node, agent-network, server, package and lock inputs are identical. Own merged PR's optional QA 38388648494 was canceled after the required/core checks; this is not PASS.
Corrected formal release 38388847647 checked out exact main 1b85bca7e770d86b7f07cf12b1e8099f2ec3b00f (build job 115267292462); build, all four gates, preview publish and aggregate SUCCESS. No pre-main or skipped-gate artifact was published.
Anonymous public metadata and full tarball observed 2026-10-13T11:22:02.436328+00:00: @sleep2agi/agent-network 2.3.0-preview.175, 2126549 bytes; sha256 d6c623d7fef4c68918b7eb096b6376c9ad039ed0eea459435cfc0da7369bff49; sha1 c121ea5577d47b9a6c2397fc01c3364a0a154e03; integrity sha512-3nCgVXtYculneAwGKZuknDJh2QKO1Iaw7dkwlIa2SFGjui6tSFsIEh4Uwk3BI1q337azziuFCgLyl1tRv0zCEw==. Public bytes exactly equal the same-run CI gated tarball. Dist tags observed {"latest": "2.3.0-preview.76", "preview": "2.3.0-preview.175"}; latest equals the before-CLI baseline (2.3.0-preview.76). Node141 retains its original main40d artifact; both public source commits were verified ancestors of current main.
This completes only #1138's source/core/public pair. Mother #730 still requires human active-owned-turn steering/preemption, position UI and original-device feedback; public availability does not mean a running client adopted the pair. No real node, original thread, account, model/provider, shared app-server, configuration or production data was changed for this proof.
