Epic: Board clarity and provider-neutral session visibility for v1.4.2

[jeffhuber]

Part of roadmap #900.

Board clarity and provider-neutral session visibility

Delivered in v1.4.2

The Board implementation and release are complete in the published v1.4.2 package at release commit 55339bf1acf76d33be5937e80bdaad772e0b2bf5.

Unit	Issue / PR	Result
Observation contract and fixtures	#946 / #956	merged bafbac4a
Existing-data truth and hierarchy	#947 / #957	merged 2a07dc54
Work-first views	#948 / #1000	merged 5b32c96e
Exact local observation producer	#949 / #999	merged 5b203388
Provider-neutral remote observations	#950 / #1002	merged f491c681
Persistent service lifecycle	#961 / #1001	merged 6fca7603
Integrated head-bound qualification	#951 / #1003	implementation merged 6501feb4
Release	#952 / #1006	merged and published 55339bf1

All implementation and release PRs passed independent exact-head review with zero unresolved P0/P1/P2 findings, relevant validation, CI and authoritative gate. Fresh install and 1.4.1-to-1.4.2 upgrade rehearsals passed. Both known local Board services were safely restarted and verified on the installed v1.4.2 package.

The Board remains a read-only local observation model. It does not dispatch, retry, cancel, restart, renew a lease, merge, alter cloud fields or expose private source/session/provider content.

Remaining follow-through

#951 remains open for exactly one acceptance item: observe a bounded hosted Devin run through the same closed Board projection. That external action requires new explicit authorization for a campaign-wide 1 ACU cap. Prior #935 create allowances are exhausted and cannot be reused.

The canary is recorded separately because v1.4.2 publication and package qualification are complete. Close this epic after #951 records the observed canary result, or after an explicit roadmap decision removes that follow-through criterion.

Checklist

• Board: freeze the provider-neutral observation contract and truth fixtures #946 — observation contract and truth fixtures
• Board: correct existing-data truth, hierarchy, and attention semantics #947 — existing-data truth, hierarchy and attention semantics
• Board: implement the work-first Now, Timeline, Releases, and Health views #948 — work-first Now, Timeline, Releases and Health views
• Sessions: discover the current local brief and lease from a checkout #935 — exact current session/brief/lease discovery reused
• Board: connect exact local sessions, work, runs, and worktrees #949 — exact local session/work/run/worktree connection
• Board: connect provider-neutral remote lifecycle observations #950 — provider-neutral remote lifecycle observations
• Board: manage persistent services and reject stale keepalive bindings during release restart #961 — managed persistent Board services and exact binding validation
• Board: integrate head-bound evidence and qualify local and hosted session visibility #951 — integrated implementation, local qualification and operator checklist
• Board: integrate head-bound evidence and qualify local and hosted session visibility #951 — newly authorized hosted Devin observation canary
• Release: publish and qualify Board clarity v1.4.2 #952 — v1.4.2 publication and installed-package qualification

[jeffhuber]

Board v1.4.2 activation

The release-order gate is now satisfied: Graphify epic #902 and release #915 are complete, with canonical v1.4.1 at d52bc68396397edfeae782d08a768386f89a00f2.

A new Code Mower coordination session is active for the Board epic. The first writer assignment resumes existing #946 / PR #956 on its existing codex/946-board-observation-contract branch, with named builder Code Mower Codex. It will refresh onto exact accepted v1.4.1 main, preserve the closed observation-contract scope, repeat focused/relevant checks, and then receive a fresh independent Claude exact-head audit plus CI and authoritative gate. Historical evidence remains tied to the old head.

After #956 is accepted, existing #947 / PR #957 resumes with its named Code Mower Claude writer and a fresh independent Codex audit. No replacement PRs will be created. #948 and #949 can then proceed in parallel where their file ownership stays disjoint; #961 remains serialized around shared Board/CLI service files before #951 and #952.

No hosted Devin create is authorized or needed for this refresh. Any later hosted canary under #951 will require its own bounded allowance and will not reuse the exhausted #935 recovery budget.

[jeffhuber]

B0 and B1 accepted; parallel implementation gate open

• B0 Board: freeze the provider-neutral observation contract and truth fixtures #946 / PR Board: freeze provider-neutral observation contract #956 merged as bafbac4a3026b8a41b0591450208d61fd79aea47. Refreshed head 28356d970f391c124927ff4fa64e6a3ca6ee98a2 passed 233 focused/release checks, package builds, Python 3.12–3.14 CI, both containment jobs, independent exact-head Claude PASS with P0/P1/P2=0, and code-mower/gate.
• B1 Board: correct existing-data truth, hierarchy, and attention semantics #947 / PR Board: correct existing-data truth and hierarchy #957 merged as 2a07dc542c8e01ce5c8cfe772276914e6adcf962. Refreshed head 6fae6b87f302ec58313c68276e5a997a3ca76a32 passed 4,096 tests with 17 skips under the corrected private temporary root, all CI/package/containment jobs, independent exact-head Codex PASS with P0/P1/P2/P3=0, and code-mower/gate.

The first #957 full-suite capture exposed nine environment failures caused by the macOS /var alias and reused lane cache; targeted reruns and the full suite with TMPDIR=/private/tmp passed. No source change was required. An automatically repeated full-suite run was interrupted after the exact source tree already passed, avoiding redundant evidence work.

The parallel gate is now open. #948 owns board.py, test_board.py, and presentation docs. #949 may build its local observation producer and producer tests concurrently but must defer its narrow board.py integration hook until #948 merges. Both consume the accepted B0 contract unchanged. Recommended merge order remains #948, then rebased #949.