Repository navigation
v1.5.1: harden cross-provider installation and hosted adoption #1050
Description
Goal
Ship a focused v1.5.1 reliability release from the successful v1.5.0 adoption campaign. No new product surface or Slack telemetry is in scope.
Five independent adoption passes—Claude, Cursor Cloud Agent, hosted Devin, a headless remote orchestrator, and Antigravity—installed or upgraded v1.5.0 without a release-blocking product failure. Their actionable installation, test-isolation, and documentation findings became the five roadmap revisions below.
PR map
- Revision 1: hosted install and role clarity — Docs: clarify hosted v1.5 adoption paths #1051
- Revision 2: host-independent test subprocesses — Tests: isolate Python and Git subprocesses #1052
- Revision 3: lane-exact audit publication seals — issue v1.5.1: bind audit publication seals to exact reviewer lanes #1032, PR Bind audit seals to exact source jobs #1058
- Revision 4: safe init and unique generated output — issue v1.5.1: make easy init and generated output safe #1054, PR Init: preserve repository config in easy mode #1057
- Revision 5: checkout-free remote observer plus precise status/Board/privacy — issues v1.5.1: make remote-observer doctor checkout-independent #1053/v1.5.1: clarify status, Board version, and share-oriented privacy #1055, PRs Doctor: make remote observers checkout-independent #1059/Status: clarify optional lineage and Board version #1060
- Bounded hosted Board canary — Board: integrate head-bound evidence and qualify local and hosted session visibility #951/Epic: Board clarity and provider-neutral session visibility for v1.4.2 #945, qualification PR docs: v1.5.1 hosted Board release-qualification canary (#951) #1062
- Release qualification, codemower.com upload, and publication — Release v1.5.1: qualify, upload evidence, and publish #1056, release PR Release: prepare v1.5.1 reliability candidate #1061
Release boundary
Basic Slack lifecycle remains supported as released in v1.5.0 and requalified for v1.5.1. Slack-specific telemetry and hosted aggregation are deferred to v1.6.0 in #921 and #978.
Acceptance
- Every implementation PR has focused regression coverage, exact-head independent review, green CI, and authoritative Code Mower gate.
- Fresh hosted installation without uv/pipx, v1.5.0 upgrade, remote observer, safe init, Board, Graphify, and basic Slack rehearsals pass.
- Single- and multi-lane audit publication succeed without owner override.
- The bounded Board canary records provider exit, Board projection, privacy boundary, authorized usage, and settled usage separately.
- Approved metadata-only evidence is uploaded to codemower.com and independently observed on a fresh authenticated dashboard view.
- GitHub and PyPI v1.5.1 identities and artifact digests match the accepted release commit.
Activity
jeffhuber commentedon Sep 20, 2026
Documentation slice merged in #1051.
Delivered from the four-provider v1.5.0 adoption evidence:
doctor --easy --orchestrator-onlyguidance;--dry-runand--no-lease;Validation included an isolated public-package bootstrap, 363 release-hygiene tests plus 945 subtests, full Python 3.12/3.13/3.14 CI, Board and containment jobs, exact-head independent Claude PASS, and the authoritative gate. The workflow publisher's fresh source-seal refusal is recorded on #1032 rather than hidden by this merge.
The behavior slices in this issue remain open: remote-observer doctor semantics, init/generated-output safety, and status/privacy polish.
jeffhuber commentedon Sep 20, 2026
Antigravity adoption evidence has been reconciled and the actionable test-harness slice is complete in #1052 (merged as
ba72ac986ab3d24e1c5ace2fbcdcc9e4aed97aaa).Verified and incorporated:
PATH, so shell snippets invokingpythoncannot silently select an older ambient runtime;GIT_TERMINAL_PROMPT=0, so Git subprocesses fail deterministically instead of blocking on an unavailable credential prompt;PATH, 363 release-hygiene tests plus 945 subtests, Ruff, diff check, full CI, and the Code Mower gate;github-actionsat Tests: isolate Python and Git subprocesses #1052 (comment).Corrections applied while curating the report:
197c0c6080afe2a7625d22b897f4027112cf4a01; the report's longer197c0c609...value is not a valid release commit;code-mower campaign run --repo ... --pilotis not a v1.5.0 CLI command and is excluded from guidance;This closes the Antigravity-specific deterministic local-test work. Broader cross-provider adoption work remains tracked by this epic.
jeffhuber commentedon Sep 20, 2026
v1.5.1 kickoff evidence was exported from exact clean main
ba72ac986ab3d24e1c5ace2fbcdcc9e4aed97aaaand uploaded to codemower.com through the storedcodex-code-mowerprofile.board_snapshot; 1 event, 0 reports.9312736d-4ccb-4ee4-b7e8-7a9fd8274252.stale; this proves storage only. A fresh authenticated dashboard observation remains required separately in Release v1.5.1: qualify, upload evidence, and publish #1056.jeffhuber commentedon Sep 20, 2026
The v1.5.1 roadmap is complete.
All five reliability revisions are merged, the hosted Board canary and basic Slack lifecycle are closed, exact-head qualification passed, the metadata-only release snapshot is stored on codemower.com, and the same immutable candidate is now published on GitHub and PyPI.
Final release evidence is recorded in #1056. Slack telemetry and hosted aggregation remain in the v1.6.0 milestone as #921 and #978.