Roadmap through v1.5.0: bounded builders, Graphify, Board, and supervised Slack

[jeffhuber]

Completion roadmap through v1.5.0

Current position and release order

v1.4.0 is released. Its five-task hosted-Devin campaign is complete: Devin delivered 3/5; Codex independently completed #865 through #971 and #935 through #973. The final #935 recovery was user-cancelled before delivery, not a completed failed repair. Devin is qualified for bounded, well-scoped hosted builder work; orchestration and merge-authority review require separate evidence. Qualification scorecard · Operational closeout.

Release order remains v1.4.0 complete → v1.4.1 Graphify → v1.4.2 Board → v1.5.0 supervised Slack. An explicit evidence-backed Graphify deferral recorded in #915/#902 may satisfy that dependency; elapsed time, implementation difficulty, or a draft PR never changes release order automatically. Already merged post-v1.4.0 fixes, including #935/#973, are recorded as on main until a subsequent published package is verified to contain them.

Workstream	Epic	Verified position	Remaining delivery / release gate
Released Devin transport and bounded builder qualification	#901 closed	v1.4.0 published; five-task campaign complete	follow-up reliability is #979; no broader role promotion
Qualification, handoff, operational evidence	#979	#965/#981, #967/#980, #962/#984, #975/#987 and #976/#985 merged; #974 verified closed	two remaining OSS implementation PRs, both before #915
Graphify local context	#902	#876/#924 and #913/#926 merged; adopted	#914 / draft #982 query/packet PR, then #915 v1.4.1 release PR
Board clarity and session visibility	#945	implementation underway; #956/#957 draft, behind main; #935/#973 merged	refresh existing drafts, finish presentation/producers/service/qualification, then #952 v1.4.2
Supervised Slack ingress	#903	#916/#929 and #917/#933 merged	OAuth, qualified supervisor, durable interactions, bridge, paired telemetry, setup, then #923 v1.5.0

The maintained first-run default remains Claude + Codex. Devin, Coworker, Graphify, Slack, and optional reviewers remain explicit selections grouped by role.

Five approved revisions and their PR mapping

Revision	Result	Delivery mapping
1. Precise Devin qualification	Separate implemented transport, bounded builder eligibility, orchestrator qualification, and effective review authority. Preserve cancellation and unknown billing evidence.	#975 policy/admission PR; #955 effective-authority reporting PR; #965 supported-command/current-roadmap docs PR
2. Handoff reliability becomes a dependency	A replacement writer starts only after verified source quiescence; ordered contributors, current writer, labels, and review exclusion agree at the exact head.	#962 quiescence/Git/runner PR → #963 lineage/exclusion PR → #949 and #977 integration
3. Supervised Slack scope	A real qualified Codex/Claude supervisor controls bounded hosted Devin work. Missing supervisor readiness blocks dispatch; selecting a provider never promotes its role.	#975 → #977 OSS supervisor adapter → #919/#920 hosted integration; acceptance in #923
4. Independent operational evidence	Keep implementation completion, provider exit, reviewed head, authorized versus settled spend, ingest receipt, and fresh aggregate views independent.	#976 local acceptance/reporting PR; #974 existing-view verification; #961 managed Board service PR; #921 OSS + #978 hosted telemetry PRs
5. Accurate live tracker and release state	#935 is complete, Board implementation is underway, completed release blockers are removed, and old draft-head reviews remain historical evidence.	this roadmap, #902/#945/#903/#979 and child dependencies updated; #956/#957 retained and refreshed; #965 updates checked-in current-state docs

Execution waves and dependencies

1. Now — complete stabilization and Graphify. Docs: replace the nonexistent hosted-Devin work-order command #965/Docs: replace the nonexistent hosted-Devin work-order command #981, Work orders: keep optional Gitar out of the default review lanes #967/Work orders: default to Codex and Claude reviews #980, Local builder handoff: make takeover quiescent, Git-write capable, and runner-consistent #962/Make builder takeovers quiescent and Git-capable #984, Participants: enforce role-specific qualification for hosted builders #975/Enforce participant role qualification before new work #987 and Release evidence: separate completion, provider exit, usage settlement, and cloud freshness #976/Release evidence: distinguish completion, exit, settlement and freshness #985 are accepted on main. Continue Graphify: bounded query normalization and context packets #914/Graphify: bounded query normalization and context packets #982 while Adoption polish: report effective review authority and superseded Devin bridge drift #955 and Builder takeover: make provenance, labels, and reviewer exclusion handoff-aware #963 run in parallel from the accepted role and handoff contracts. Cloud: verify aggregate freshness after accepted release metadata #974 fresh aggregate visibility is verified without repeating its accepted upload. Release: qualify and publish optional Graphify context in v1.4.1 #915 requires all Epic: qualification, handoff reliability, and operational evidence through v1.5.0 #979 evidence plus Graphify: bounded query normalization and context packets #914, followed by candidate/published-package and headless-adoption qualification. The original v1.4.0 artifacts remain immutable.
2. Next — Board foundations and delivery. After v1.4.1 is published and qualified, refresh existing Board: freeze provider-neutral observation contract #956/Board: correct existing-data truth and hierarchy #957 and their exact-head audits. Board: freeze the provider-neutral observation contract and truth fixtures #946/Board: correct existing-data truth, hierarchy, and attention semantics #947 → Board: implement the work-first Now, Timeline, Releases, and Health views #948 presentation; Board: freeze the provider-neutral observation contract and truth fixtures #946 + completed Sessions: discover the current local brief and lease from a checkout #935 + Builder takeover: make provenance, labels, and reviewer exclusion handoff-aware #963 → Board: connect exact local sessions, work, runs, and worktrees #949 → Board: connect provider-neutral remote lifecycle observations #950 (also Release evidence: separate completion, provider exit, usage settlement, and cloud freshness #976). Complete Board: manage persistent services and reject stale keepalive bindings during release restart #961 persistent services, including exact repository-aware stop selection. Converge in Board: integrate head-bound evidence and qualify local and hosted session visibility #951, then publish/qualify Release: publish and qualify Board clarity v1.4.2 #952 v1.4.2.
3. Then — supervised Slack implementation. CodeMower.com: Slack OAuth installation binding and policy store #918 OAuth/policy follows merged Slack: app manifest and authenticated bounded ingress envelope #917. OSS Slack: connect authorized tasks to a qualified Code Mower supervisor #977 consumes Participants: enforce role-specific qualification for hosted builders #975/Local builder handoff: make takeover quiescent, Git-write capable, and runner-consistent #962/Builder takeover: make provenance, labels, and reviewer exclusion handoff-aware #963. CodeMower.com: Slack OAuth installation binding and policy store #918 + Slack: connect authorized tasks to a qualified Code Mower supervisor #977 → Slack: durable inbox/outbox and start/status/cancel interaction #919 durable interactions → Slack: Devin dispatch, clarification, completion, and cancellation bridge #920 supervised hosted bridge. Slack: Devin dispatch, clarification, completion, and cancellation bridge #920 + frozen Board: freeze the provider-neutral observation contract and truth fixtures #946 → Slack: freeze telemetry contract and implement OSS Board/cloud emitters #921 OSS telemetry contract/emitter → CodeMower.com: implement the frozen Slack telemetry contract and fresh views #978 hosted validator/aggregation/views. Slack: optional integration setup, doctor, and operating guidance #922 integrates setup/doctor after both telemetry sides, qualification and supervisor readiness. Independent isolated headless Codex campaign authentication Campaign: support isolated Codex authentication on headless Linux #983 can run in this wave without contending for the current Graphify critical path.
4. v1.5.0 convergence. Release: qualify and publish Slack session ingress in v1.5.0 #923 requires Slack: optional integration setup, doctor, and operating guidance #922, released/qualified Release: publish and qualify Board clarity v1.4.2 #952, completed Campaign: support isolated Codex authentication on headless Linux #983, fresh aggregate evidence Cloud: verify aggregate freshness after accepted release metadata #974 and Epic: qualification, handoff reliability, and operational evidence through v1.5.0 #979 closeout. Run authorized completion/cancellation canaries, restart/privacy/tenant and package/upgrade qualification, hosted deployment/rollback verification; then publish and verify v1.5.0. Update epic evidence, Board observations and metadata-only cloud receipts plus fresh views.

Parallel work follows independent source ownership, one current writer and Code Mower sessions/audits. Release, tag and deployment actions are serial. Board and Slack work do not compete with ready stabilization/Graphify work under the owner's current priority.

Epic-to-PR inventory

Epic	Remaining implementation issues, one PR each	Existing PRs
#979 stabilization	#955, #963	active parallel implementation; completed #965 → #981, #967 → #980, #962 → #984, #975 → #987, #976 → #985; #974 verified closed
#902 Graphify	#914, #915	active #914 → draft #982; completed foundations #924/#926
#945 Board	#946, #947, #948, #949, #950, #961, #951, #952	#946 → #956; #947 → #957; reuse completed #935 → #973
#903 Slack	#918, #977, #919, #920, #921, #978, #922, #923	completed foundation PRs #929/#933 retained as evidence

After merging #980/#981/#984/#985/#987 and adding #983, there are 21 remaining mapped implementation PR slots: three existing drafts (#956/#957/#982) and 18 planned PRs, including the three release PRs. #983 is one additional OSS campaign-authentication PR required before #923, scheduled after #915. Future PR numbers are assigned only when a real branch/change exists. There is no umbrella implementation PR. #918/#919/#920/#978 are hosted repository PRs; #977/#921/#922 and all other listed implementation units are OSS PRs. Keep the exact private hosted repository/PR binding in the authorized record and publish only approved metadata. #921 owns the frozen cross-repository telemetry contract; #978 owns its hosted implementation, with separate reviews and deployment evidence.

Delivery and operational contract

• One named Code Mower builder and one writer per branch. Use qualified Codex/Claude for cross-cutting contracts, supervision, recovery, and release work. Bounded Devin observation canaries may implement a small approved task.
• Every implementation PR has a qualified independent reviewer excluded from all verified contributors to the current diff, the exact current head, focused/relevant tests, privacy checks, normal CI, and authoritative code-mower/gate (or the hosted repository's equivalent required gate). Fix all P0/P1/P2 findings. A changed head invalidates the prior audit; a successful gate publisher is not the gate verdict. If no eligible reviewer remains, stop for one explicit owner action.
• A final writer must be demonstrably quiescent before takeover/final-head acceptance where the workflow requires it. Completion, cancellation acknowledgement, provider exit, review readiness, and merge are distinct observations. Unknown exit fails closed for takeover.
• Future paid campaigns require an explicit initial and aggregate ACU cap, stable private binding, and no automatic uncertain retry. At most one or two explicitly budgeted recovery creates precede splitting or changing builders. This plan creates no additional provider allowance. Track creates, interventions, elapsed time, coverage, observed/settled spend, and outcome; unknown billing is not zero and need not cause an indefinite release wait.
• Each epic carries live PR/head, contributor lineage, review/test/gate, package/deployment, Board, and cloud evidence. Historical results stay historical. A merged feature is marked shipped only after the package/deployment containing it is verified.

Privacy and scope boundaries

Graphify remains optional, deterministic, local, immutable-revision-bound, explicit-refresh, and code-only. Board remains a local observation/read model: refresh never dispatches, retries, cancels, restarts, renews a lease, or merges. Board v1.4.2 adds no cloud fields. Slack remains authorized ingress/conversation transport; a separately qualified supervisor owns orchestration. New Slack telemetry belongs to #921/#978 only. Existing #906 lifecycle and #935 discovery are reused.

Source, diffs, task/answer prose, prompts, transcripts, Slack/private identities, credentials, raw provider records, provider references, graph/context contents, and personal paths stay out of public planning evidence and cloud uploads. Private runtime content follows the existing authorized storage/retention contract.

Broad unattended rollout, Devin orchestrator/reviewer promotion, Cursor cold-install investigation #860, new optional integrations, and general productivity claims are follow-on scope rather than v1.5.0 promises.

Completion gates

• Epic: Devin peer participant and lifecycle support for v1.4.0 #901 — v1.4.0 transport release and bounded hosted-builder campaign, with final qualification limitations recorded.
• Epic: qualification, handoff reliability, and operational evidence through v1.5.0 #979 — qualification, handoff, accurate defaults/docs, and independent operational evidence complete.
• Epic: Graphify local repository context for v1.4.1 #902 — Graphify v1.4.1 published/qualified, or explicit evidence-backed deferral recorded in Release: qualify and publish optional Graphify context in v1.4.1 #915/Epic: Graphify local repository context for v1.4.1 #902 with affected release notes updated.
• Epic: Board clarity and provider-neutral session visibility for v1.4.2 #945 — Board v1.4.2 published, upgraded, persistent services verified after delay, local/hosted observations qualified.
• Epic: Slack session ingress and supervision for v1.5.0 #903 — supervised Slack v1.5.0 published; every required child, private canary, hosted deployment, and package check accepted.
• Final Code Mower Board and CodeMower.com views show the accepted outcomes with source freshness; stored event receipts and freshly observed aggregate visibility pass separately. Cloud: verify aggregate freshness after accepted release metadata #974 and any confirmed-defect child are closed.
• All release artifacts bind the reviewed commit, default/no-optional-provider and upgrade paths pass, and limitations/unknown billing are explicit. No required implementation or canary remains pending when Roadmap through v1.5.0: bounded builders, Graphify, Board, and supervised Slack #900 closes.

Active execution priority

The owner has prioritized fully completing v1.4.0 stabilization and Graphify v1.4.1 first, then Board v1.4.2. This overrides the earlier overlap schedule where it would start Board or Slack work ahead of ready stabilization work.

• Active: Epic: qualification, handoff reliability, and operational evidence through v1.5.0 #979 stabilization and Graphify: bounded query normalization and context packets #914 Graphify implementation. Parallel independent source areas through named Code Mower builder sessions; one writer per branch, independent exact-head peer audits, and serialized merges/releases.
• v1.4.1 release Release: qualify and publish optional Graphify context in v1.4.1 #915 now requires all Epic: qualification, handoff reliability, and operational evidence through v1.5.0 #979 completion evidence, including Cloud: verify aggregate freshness after accepted release metadata #974 verified aggregate freshness, plus Graphify: bounded query normalization and context packets #914. The original v1.4.0 artifacts remain immutable; stabilized changes are recorded on main and ship in the verified v1.4.1 package.
• First concurrent units: Graphify: bounded query normalization and context packets #914 Graphify, Docs: replace the nonexistent hosted-Devin work-order command #965 supported/current docs, Work orders: keep optional Gitar out of the default review lanes #967 review defaults, and Release evidence: separate completion, provider exit, usage settlement, and cloud freshness #976 operational evidence. Then Participants: enforce role-specific qualification for hosted builders #975/Adoption polish: report effective review authority and superseded Devin bridge drift #955 and Local builder handoff: make takeover quiescent, Git-write capable, and runner-consistent #962/Builder takeover: make provenance, labels, and reviewer exclusion handoff-aware #963 as ownership/dependencies allow. Reconcile Cloud: verify aggregate freshness after accepted release metadata #974 in parallel without resubmitting accepted data.
• Next: Board Epic: Board clarity and provider-neutral session visibility for v1.4.2 #945 after the v1.4.1 publication/qualification gate. Retain draft Board: freeze provider-neutral observation contract #956/Board: correct existing-data truth and hierarchy #957 and refresh their heads/audits when Board becomes active. Board Board: manage persistent services and reject stale keepalive bindings during release restart #961 stays in that release's scope.
• Later: Slack Epic: Slack session ingress and supervision for v1.5.0 #903 remains planned; its implementation does not compete with the current stabilization/Graphify critical path.
• No new hosted-Devin session allowance is inferred. Local Code Mower Codex/Claude builders and independent audits drive the current work.

Incorporated v1.4.0 hosted adoption report

The reported upgrade, CLI/wrapper version alignment, loopback Board lifecycle, lanes status, preview/drift and quiet opt-in behavior are positive historical adoption evidence. The report does not establish Devin orchestrator qualification, remote reachability of a loopback Board, or readiness of an isolated campaign from an ordinary CLI login.

Finding / recommendation	Disposition and PR mapping
Implicit session lease; release ID/lifecycle unclear	#975 adds admission-before-lease regression and visible lifecycle/release guidance; #915 rehearses it from the package
Bare builder init fails; irrelevant campaign auth owner action	Already fixed after v1.4.0 by #969 and #966; #915 verifies actual v1.4.1 inclusion and cold/upgrade behavior
Headless isolated Codex campaign login unavailable	New #983, one separate OSS PR after Graphify and before #923; preserve credential isolation and explicit campaign intent
Board stop rejects repository selector	#961 implements exact, unambiguous repository-aware stop with service lifecycle in v1.4.2
Host-specific Devin remediation and missing prompt-pack guidance	#955 portable configured-posture guidance; #975 owns lease/role sections
Repo secrets, auto-merge promotion and generated-file drift	Selected-repository operator actions, not installation failures; preview changes and preserve informational policy until explicitly promoted

Release rehearsal retains successful default/no-optional-provider behavior and distinguishes warn/exit 0, full activation and package shipment. Do not freeze the report's warning count, silently apply its generated setup, or provision credentials from this report.

Current acceptance count for v1.4.1 plus required stabilization: 8 of 12 units accepted (two Graphify foundation units and six #979 units). This is a deliverable count, not an effort-weighted percentage or a claim that the remaining work takes equal time. Active drafts and published-package verification remain outstanding. Other independently owned repository PRs are outside the mapped-slot count and must be reconciled into the final candidate if merged.

[jeffhuber]

Execution started

• Local Board: http://127.0.0.1:5332/
• CodeMower.com dashboard: https://codemower.com/dashboard
• Metadata upload evidence: https://github.com/codemower-ai/code-mower/actions/runs/34684055961
• Active Devin work: Devin: capability model and safe reviewer posture #904, Codex builder
• Active Graphify spike: Context: evaluate official Graphify as a local repository provider for v1.4.1 #876, Claude builder
• Slack contract: Slack: freeze command, identity, lifecycle, privacy, and event contracts #916, planned against the stabilized remote-session lifecycle

The dispatcher selected both active issues in dry-run before applying dispatch. Both builder units use isolated lane checkouts and the normal single-writer contract. Raw task/provider/context/graph content is not part of the cloud upload.

[jeffhuber]

A metadata-only hosted Ubuntu v1.3.1 adoption rehearsal produced three nonblocking follow-ups. These are deliberately outside the Devin v1.4.0 critical path:

• Doctor: scope release-campaign auth readiness to campaign intent on headless hosts #953 — scope release-campaign authentication readiness to actual campaign intent, including truthful headless-host guidance (P2)
• Init: make documented --builders selection work from a fresh repository #954 — make the documented init --builders ... cold-start path work consistently (P2)
• Adoption polish: report effective review authority and superseded Devin bridge drift #955 — render effective reviewer authority, flag superseded Devin bridge drift, and reduce posture noise (P3)

Each should ship as an independently reviewed PR after #912. No P0/P1 issue was reported; install, upgrade, Board, lane status, productivity, and session start --host devin all worked.

[jeffhuber]

Roadmap milestone: Devin v1.4.0 released

The first roadmap capability is complete. Devin peer support shipped in Code Mower v1.4.0, with matching package artifacts, local installation, an exact three-provider cold-install campaign, three upgraded Boards, and accepted metadata-only cloud evidence.

This clears the release-order dependency for Graphify and the later Board and Slack work. The roadmap remains open for those capabilities.

[jeffhuber]

Post-v1.4.0 hosted-Devin dogfood plan

Five representative delivery tasks will be measured through Code Mower:

Order	Issue	Task class	ACU cap	State
1	#960	release/package safety	5	dispatched; sole live writer
2	#954	cold-start init/runtime	2	work order prepared; zero-access preview passed
3	#953	doctor operability/privacy	3	work order prepared; zero-access preview passed
4	#865	repository delivery policy	3	work order prepared; zero-access preview passed
5	#935	session discovery/security	4	work order prepared; zero-access preview passed

Runs 2–5 use the trusted hosted work-order seam with exact repository, issue, branch, base, expected author, PR, and head verification. Run 1 was already created through the provider-neutral remote-session lifecycle; it counts only if hosted Devin remains the sole writer and its resulting PR/branch/author/head are independently verified.

For each run, record create count, dispatch-to-verified-collection time, PR-open-to-merge time, owner and orchestrator interventions, audit/CI fix rounds, recovery episodes, duplicate creates, cap, observed ACU, exact-head audits, gate, merge, and post-merge health. Dollar cost remains unavailable unless the organization-specific contractual ACU rate is available; never report missing cost as zero.

There will be no automatic retry after an uncertain mutation. Subsequent work remains staged until the active run provides a useful completion or intervention signal.

[jeffhuber]

Hosted Devin stabilization dogfood is now 2/5 delivered.

• Release: keep TestPyPI sdist verification source-exclusive without PEP 517 dependency failure #960 / PR Release: keep TestPyPI sdist verification source-exclusive without PEP 517 dependency failure #964: merged; exact-head Codex and Claude reviews passed; one create, no duplicate create.
• Doctor: scope release-campaign auth readiness to campaign intent on headless hosts #953 / PR Doctor: scope release-campaign auth readiness to campaign intent #966: merged; exact-head Codex and Claude reviews passed; one create, one bounded fix round, no duplicate create, no owner intervention.

The second run validated stale-head rejection and same-session recovery, while exposing the post-completion writer quiescence and checked-in labeler parity gaps tracked in #962. Next is #954 from current main, followed by #865 and #935.

[jeffhuber]

Hosted Devin stabilization dogfood is now 3/5 delivered. #954 / PR #969 merged from one create with no fix round, no duplicate create, and no owner intervention. The hosted writer was quiesced before independent Codex and Claude audits, the exact head remained stable, and the gate passed. Next is the tightened #865 delivery-policy work order, followed by #935.

[jeffhuber]

Five-task hosted-Devin qualification scorecard

Decision: Devin is qualified as a bounded hosted builder for small and medium, well-scoped implementation tasks. It is not yet peer-equivalent to Codex or Claude for complex cross-cutting recovery work, orchestration, or merge-eligible independent review. Claude + Codex remain the first-run defaults and required independent review lanes for this campaign.

Observed delivery: 3/5 hosted-Devin samples merged. #865 exhausted five recoveries with a blocked Devin head; #935 remained blocked after two repair commits, and its final authorized recovery was interrupted by an owner task stop before delivering a change. That interruption is not evidence of a completed failed repair. Both user-facing issues were completed separately by Codex; neither replacement counts as a Devin success.

Issue / hosted PR	Class and outcome	Devin head / merge	Dispatch → PR / PR → merge / total seconds	Creates / recovery episodes / fix rounds	Orchestrator / owner interventions	Aggregate ACU cap
#960 / #964	release/package safety; delivered	d6edd41 / db22b1f	668 / 314 / 982	1 / 1 / 0	2 / 0	5
#953 / #966	doctor/headless operability; delivered	ca51eb8 / c28b953	836 / 970 / 1,806	1 / 1 / 1	3 / 0	3
#954 / #969	fresh-install builder selection; delivered	3d0a2dd / e86e486	419 / 243 / 662	1 / 0 / 0	2 / 0	2
#865 / #970	cross-cutting branch/security policy; unsuccessful	b9ef7e4 / unmerged	1,262 / n/a / 13,983 to close	6 / 5 / 5	5 / 0	8 (3 + five × 1)
#935 / #972	checkout session discovery; blocked, final recovery interrupted	541bde0 / unmerged	874 / n/a / 2,973 to close	3 / 2 / 2 completed	7 / 1	6 (4 + two × 1)

Recovery episodes include in-session intervention; they are not all new paid creates. Across the campaign: 12 deliberate creates, zero accidental duplicate creates, and a maximum aggregate authorized cap of 24 ACU. Actual settled ACU and dollar cost remain unavailable. Some collection/provider snapshots returned 0.0; those are unsettled snapshots and must not be reported as zero cost.

The first three delivered samples had zero owner intervention, seven orchestrator interventions, and median total delivery time 982 seconds. #935 adds one owner stop, so the full campaign does not establish zero owner intervention. Its seven grouped operational interventions are label repair, invalid-request handling, first recovery creation, completion prompting, a same-recovery review fix, writer quiescence, and final recovery creation; these are episodes, not raw API-call counts. Its start time is the verified provider create timestamp (2026-09-14 00:33:03 UTC); the public dispatch comment was posted later. The final recovery ran from 01:16:49 to 01:17:19 UTC and delivered no commit.

Sample	Review, validation, and stability evidence
#960	Independent Codex and Claude PASS at d6edd41; 994 focused tests; CI/gate passed. Merged PR #964.
#953	Independent Codex and Claude PASS at ca51eb8; 61 focused tests; CI/gate passed. Post-completion head drift required revalidation. Merged PR #966.
#954	Independent Codex and Claude PASS at 3d0a2dd; 10 focused tests, release readiness 20/20, CI/gate passed. Writer quiesced before review; no final head drift. Merged PR #969.
#865	Final Devin head remained Codex BLOCKED; Claude did not review that final head. Provider suspended; cancel attempt returned invalid_request; settled usage unavailable. Closure evidence. Codex #971 merged as 27aed26 after both exact-head passes.
#935	Initial Claude PASS and Codex BLOCKED; two repaired heads still Codex BLOCKED. Final Devin head passed 110 focused tests but did not clear the merge gate; final-head Claude review did not complete. All hosted writers were confirmed exited before takeover. Supersession evidence. Codex #973 at dcabddf has Codex PASS and Claude PASS; merged as ad4ba61 after full CI regression on Python 3.12/3.13/3.14 and the gate passed. Final immutable-head local regression: 3,492 tests passed (11 skipped). Post-merge: 112 focused tests, tracked-source Ruff, privacy scan, release readiness 20/20; merged tree equals the reviewed tree.

Operating limits: one stable private binding per delivery episode; an explicit ACU cap; no automatic retry after an uncertain provider result; exact PR/head binding for collection and review; quiesce the writer before final review where possible; independent Codex and Claude audits; at most one or two recovery creates before splitting work or switching builders. Target zero owner intervention and record every exception. Devin remains unqualified as an orchestrator or merge-eligible reviewer pending separate evidence.

Lifecycle evidence is recorded on #962: early #935 invalid_request results had invalid request/prose inputs and do not prove the provider refused valid completed-session operations; later keyed fix/cancel succeeded. Repeated manual Devin label repair and replacement lineage are recorded on #963.

Implementation completion: #935 final evidence. Private telemetry has been updated; the final Board snapshot and metadata-only upload are recorded in the campaign closeout.

[jeffhuber]

Hosted-Devin campaign final closeout

The five-task qualification scorecard is final and linked from this roadmap and epic #901. Devin delivered 3/5 samples under the bounded-builder decision. #865 remains unsuccessful Devin #970 / merged Codex #971. #935 remains blocked Devin #972 with a user-cancelled final recovery / merged Codex #973; cancellation is not reported as a demonstrated completed repair failure.

PR #973 merged as ad4ba6129dc90922cba63e20ea0715e424356b79, with exactly the reviewed dcabddf tree. Both independent reviews, CI and the gate passed before merge. The final immutable-head local regression passed 3,492 tests (11 skipped); post-merge checks passed 112 focused tests, tracked-source Ruff, privacy scan, and release readiness 20/20. Issue completion evidence.

Private telemetry records both outcomes, all creates/recoveries/interventions, caps, the interrupted final recovery, and unknown settled billing. Code Mower recorded the final Board state. The local Board now refreshes successfully from the verified checkout and shows the completed campaign with its scorecard link; its transient launchd job was corrected after a refresh failure. Persistent Board service work remains #961.

CodeMower.com returned HTTP 200 and confirmed storage of 3 accepted metadata events (2 builder_run, 1 board_snapshot), 0 duplicate events, 0 reports, and no report text. The exact previewed manifest, repository and private account-profile binding were verified. Author identities, private paths, provider references, raw prompts/responses, and private narrative notes were excluded. No reports were submitted or rejected.

The ingestion response reported aggregateRefreshStatus=stale; this proves accepted event storage, not fresh hosted aggregate views. That freshness limitation remains explicit rather than being reported as a successful aggregate refresh.

Main has no tracked changes. The pre-existing untracked output and temporary directories were preserved.