code-mower 1.5.0__tar.gz → 1.5.1__tar.gz

{code_mower-1.5.0 → code_mower-1.5.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-mower
-Version: 1.5.0
+Version: 1.5.1
 Summary: Multi-reviewer AI code audit orchestration
 License-Expression: Apache-2.0
 Project-URL: Homepage, https://github.com/codemower-ai/code-mower
@@ -45,12 +45,12 @@ Code Mower is supervised-pilot, bring-your-own-agent-loop software.
 It is not a drop-in unattended merge gate. Humans still own credentials,
 repository policy, reviewer promotion, and exceptional decisions.
 
-This source defines Code Mower `v1.5.0`, with package spec
-`code-mower==1.5.0`. Confirm the release tag on GitHub Releases and the package
+This source defines Code Mower `v1.5.1`, with package spec
+`code-mower==1.5.1`. Confirm the release tag on GitHub Releases and the package
 version on the selected index before using an index install command; source
 version and publication state are separate facts. See the
-[v1.5.0 release notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-release-notes.md)
-and [qualification contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-qualification.md).
+[v1.5.1 release notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-release-notes.md)
+and [qualification contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-qualification.md).
 After publication, the GitHub Release and linked release issue carry the
 observed source SHA, artifact digests, canary outcomes, publication run and
 reinstall evidence.
@@ -61,7 +61,7 @@ not claimed by its immutable qualification record.
 
 Documentation on `main` follows the source on `main`. For an installed release,
 read its immutable versioned guide, such as the
-[`v1.5.0` guide](https://github.com/codemower-ai/code-mower/blob/v1.5.0/docs/try-in-10-minutes.md),
+[`v1.5.1` guide](https://github.com/codemower-ai/code-mower/blob/v1.5.1/docs/try-in-10-minutes.md),
 and confirm the tag and package exist before using pinned install commands.
 
 ## What Code Mower Adds
@@ -90,13 +90,13 @@ one stable `pipx` installation:
 ```bash
 python3.12 --version
 export CODE_MOWER_PYTHON="$(command -v python3.12)"
-pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 command -v code-mower
 code-mower --version
 ```
 
 `command -v code-mower` should print the path you expect and `code-mower
---version` should print `code-mower 1.5.0` before you point Code Mower at a
+--version` should print `code-mower 1.5.1` before you point Code Mower at a
 repository. If you do not have pipx, install it from the
 [official pipx installation guide](https://pipx.pypa.io/stable/installation/).
 
@@ -321,7 +321,7 @@ for both workflows, supported behavior, and the trust boundary.
 
 ## Current Capabilities And Limits
 
-| Area | v1.5.0 posture |
+| Area | v1.5.1 posture |
 | --- | --- |
 | Default builders and reviewers | Claude Code + Codex |
 | Session hosts | Codex, Claude Code, and Cursor qualified; other identities recognized but require explicit handoff/provider transport |
@@ -335,7 +335,7 @@ for both workflows, supported behavior, and the trust boundary.
 
 GitLab, Bitbucket, broad unattended rollout, uncalibrated merge gates, Devin
 peer-orchestrator/reviewer parity, a hosted work-order CLI, a required Graphify
-dependency, Slack telemetry/Board links, and rich Slack UX are outside v1.5.0. The current priorities
+dependency, Slack telemetry/Board links, and rich Slack UX are outside v1.5.1. The current priorities
 and boundaries are recorded in
 [Current State And Roadmap](https://github.com/codemower-ai/code-mower/blob/main/docs/current-state-and-roadmap.md).
 
@@ -436,9 +436,9 @@ does not need rebuilding. See
 - [Cloud Data Contract](https://github.com/codemower-ai/code-mower/blob/main/docs/cloud-data-contract.md)
 - [Release Qualification](https://github.com/codemower-ai/code-mower/blob/main/docs/release-qualification.md)
 - [Public Release Checklist](https://github.com/codemower-ai/code-mower/blob/main/docs/public-release-checklist.md)
-- [v1.5.0 Release Notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-release-notes.md)
+- [v1.5.1 Release Notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-release-notes.md)
 - [v1.4.2 Release Notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v142-release-notes.md)
-- [v1.5.0 Qualification Contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-qualification.md)
+- [v1.5.1 Qualification Contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-qualification.md)
 - [v1.4.2 Qualification Record](https://github.com/codemower-ai/code-mower/blob/main/docs/v142-qualification.md)
 - [Release History And Archived Plans](https://github.com/codemower-ai/code-mower/blob/main/docs/release-history.md)
 - [Changelog](https://github.com/codemower-ai/code-mower/blob/main/CHANGELOG.md)

{code_mower-1.5.0 → code_mower-1.5.1}/README.md

@@ -9,12 +9,12 @@ Code Mower is supervised-pilot, bring-your-own-agent-loop software.
 It is not a drop-in unattended merge gate. Humans still own credentials,
 repository policy, reviewer promotion, and exceptional decisions.
 
-This source defines Code Mower `v1.5.0`, with package spec
-`code-mower==1.5.0`. Confirm the release tag on GitHub Releases and the package
+This source defines Code Mower `v1.5.1`, with package spec
+`code-mower==1.5.1`. Confirm the release tag on GitHub Releases and the package
 version on the selected index before using an index install command; source
 version and publication state are separate facts. See the
-[v1.5.0 release notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-release-notes.md)
-and [qualification contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-qualification.md).
+[v1.5.1 release notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-release-notes.md)
+and [qualification contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-qualification.md).
 After publication, the GitHub Release and linked release issue carry the
 observed source SHA, artifact digests, canary outcomes, publication run and
 reinstall evidence.
@@ -25,7 +25,7 @@ not claimed by its immutable qualification record.
 
 Documentation on `main` follows the source on `main`. For an installed release,
 read its immutable versioned guide, such as the
-[`v1.5.0` guide](https://github.com/codemower-ai/code-mower/blob/v1.5.0/docs/try-in-10-minutes.md),
+[`v1.5.1` guide](https://github.com/codemower-ai/code-mower/blob/v1.5.1/docs/try-in-10-minutes.md),
 and confirm the tag and package exist before using pinned install commands.
 
 ## What Code Mower Adds
@@ -54,13 +54,13 @@ one stable `pipx` installation:
 ```bash
 python3.12 --version
 export CODE_MOWER_PYTHON="$(command -v python3.12)"
-pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 command -v code-mower
 code-mower --version
 ```
 
 `command -v code-mower` should print the path you expect and `code-mower
---version` should print `code-mower 1.5.0` before you point Code Mower at a
+--version` should print `code-mower 1.5.1` before you point Code Mower at a
 repository. If you do not have pipx, install it from the
 [official pipx installation guide](https://pipx.pypa.io/stable/installation/).
 
@@ -285,7 +285,7 @@ for both workflows, supported behavior, and the trust boundary.
 
 ## Current Capabilities And Limits
 
-| Area | v1.5.0 posture |
+| Area | v1.5.1 posture |
 | --- | --- |
 | Default builders and reviewers | Claude Code + Codex |
 | Session hosts | Codex, Claude Code, and Cursor qualified; other identities recognized but require explicit handoff/provider transport |
@@ -299,7 +299,7 @@ for both workflows, supported behavior, and the trust boundary.
 
 GitLab, Bitbucket, broad unattended rollout, uncalibrated merge gates, Devin
 peer-orchestrator/reviewer parity, a hosted work-order CLI, a required Graphify
-dependency, Slack telemetry/Board links, and rich Slack UX are outside v1.5.0. The current priorities
+dependency, Slack telemetry/Board links, and rich Slack UX are outside v1.5.1. The current priorities
 and boundaries are recorded in
 [Current State And Roadmap](https://github.com/codemower-ai/code-mower/blob/main/docs/current-state-and-roadmap.md).
 
@@ -400,9 +400,9 @@ does not need rebuilding. See
 - [Cloud Data Contract](https://github.com/codemower-ai/code-mower/blob/main/docs/cloud-data-contract.md)
 - [Release Qualification](https://github.com/codemower-ai/code-mower/blob/main/docs/release-qualification.md)
 - [Public Release Checklist](https://github.com/codemower-ai/code-mower/blob/main/docs/public-release-checklist.md)
-- [v1.5.0 Release Notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-release-notes.md)
+- [v1.5.1 Release Notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-release-notes.md)
 - [v1.4.2 Release Notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v142-release-notes.md)
-- [v1.5.0 Qualification Contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-qualification.md)
+- [v1.5.1 Qualification Contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-qualification.md)
 - [v1.4.2 Qualification Record](https://github.com/codemower-ai/code-mower/blob/main/docs/v142-qualification.md)
 - [Release History And Archived Plans](https://github.com/codemower-ai/code-mower/blob/main/docs/release-history.md)
 - [Changelog](https://github.com/codemower-ai/code-mower/blob/main/CHANGELOG.md)

{code_mower-1.5.0 → code_mower-1.5.1}/docs/board-data-contract.md

@@ -16,6 +16,15 @@ to the newest timestamped result in this current-state snapshot. Superseded
 results remain available in prior local history events, but do not drive the
 current next action or owner queue.
 
+Each readable open PR includes a `lineage` posture. When no repository policy
+was loaded, `status: optional` and `reason: lineage_policy_not_configured`
+preserve the independently readable labels, checks, gate state, and PR next
+action; `lineage.next_action` tells the operator to pass
+`--config code-mower.yml` if they want lineage evaluated. When a configured
+policy cannot read or validate the lineage metadata, `status: unavailable`
+and `reason: lineage_unreadable` direct the operator to restore readable
+metadata and rerun status. Neither posture is presented as verified lineage.
+
 `code_mower.board.v1` is the local board wrapper added by
 `code-mower board serve --repo OWNER/REPO`. It adds board display metadata and
 embeds the lane-status snapshot unchanged.
@@ -466,6 +475,11 @@ and at every width. The tabs are a real `tablist` of `tab` buttons controlling
 real `tabpanel` regions; the unselected panels carry `hidden`, so they leave the
 accessibility tree instead of being painted away.
 
+The header labels the running package as `Serving version: VERSION`; this is
+the primary version reading, while the Health view retains installed-version
+and restart detail. An empty Recent Code Mower Workflows section renders
+`none`, matching the terminal status surface.
+
 - **Now** — the work rows, the selected work item's evidence, the participant
   summary, and the existing owner queue, lane work, supervised pilot and open
   PR sections.

{code_mower-1.5.0 → code_mower-1.5.1}/docs/build-loop-in-30-minutes.md

@@ -57,14 +57,14 @@ If path A has not been completed in this repository, do this reviewer-gate
 checkpoint first. If you already have a merged setup PR with Codex and Claude
 audit evidence, skip to section 2.
 
-Confirm `code-mower==1.5.0` is visible on the selected package index before
+Confirm `code-mower==1.5.1` is visible on the selected package index before
 running this install block. Prepublication qualification uses the retained
-candidate wheel from the [v1.5.0 release runbook](v150-release-runbook.md).
+candidate wheel from the [v1.5.1 release runbook](v151-release-runbook.md).
 
 ```bash
 python3.12 --version
 export CODE_MOWER_PYTHON="$(command -v python3.12)"
-pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 gh auth status >/dev/null 2>&1 && echo "gh auth ok" || { echo "gh auth NOT ready"; false; }
 code-mower init --easy
 code-mower init --easy --apply --output-dir .code-mower.generated

{code_mower-1.5.0 → code_mower-1.5.1}/docs/current-state-and-roadmap.md

@@ -22,12 +22,12 @@ dry-run-first.
 
 ## Current Source And Published Baseline
 
-This source defines Code Mower `v1.5.0`, with package spec
-`code-mower==1.5.0`. Confirm the release tag on GitHub Releases and the package
+This source defines Code Mower `v1.5.1`, with package spec
+`code-mower==1.5.1`. Confirm the release tag on GitHub Releases and the package
 version on the selected index before using an index install command; source
 version and publication state are separate facts. See the
-[v1.5.0 release notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-release-notes.md)
-and [qualification contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v150-qualification.md).
+[v1.5.1 release notes](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-release-notes.md)
+and [qualification contract](https://github.com/codemower-ai/code-mower/blob/main/docs/v151-qualification.md).
 After publication, the GitHub Release and linked release issue carry the
 observed source SHA, artifact digests, canary outcomes, publication run and
 reinstall evidence.
@@ -310,7 +310,7 @@ administration/readiness; #920 consumes the immutable candidate to obtain one
 accepted completion and one accepted confirmed cancellation under an explicit
 numeric cap while preserving every attempt and reservation; #923 records the
 tag, publication and independent reinstall evidence.
-Slack telemetry/Board/cloud links and rich UX remain v1.5.1. Slack consumes the
+Slack telemetry/Board/cloud links and rich UX remain v1.6.0. Slack consumes the
 durable lifecycle instead of scraping terminal or Board output and carries no
 raw private context or private reviewer findings.
 

{code_mower-1.5.0 → code_mower-1.5.1}/docs/early-adopter-invite-runbook.md

@@ -1,7 +1,7 @@
 # Early Adopter Invite Runbook
 
 Source target: v1.5.0 supervised-pilot baseline. Release invitations and pinned
-index installs target `code-mower==1.5.0` only after that version is visible on
+index installs target `code-mower==1.5.1` only after that version is visible on
 the selected package index.
 
 Use this runbook for the first 5-10 friendly users before widening Code Mower
@@ -41,8 +41,8 @@ Want to try Code Mower for 10 minutes?
 It is an OSS local-first tool for setting up AI peer-programmer/reviewer lanes
 on your real codebase, with optional privacy-first cloud reporting.
 
-After v1.5.0 is published, start here:
-https://github.com/codemower-ai/code-mower/blob/v1.5.0/docs/try-in-10-minutes.md
+After v1.5.1 is published, start here:
+https://github.com/codemower-ai/code-mower/blob/v1.5.1/docs/try-in-10-minutes.md
 
 Cloud sharing is optional. The default bundle excludes source code, raw diffs,
 model transcripts, raw stdout/stderr, auth output, and secrets.
@@ -57,7 +57,7 @@ Before inviting a user:
    ```bash
    python3.12 --version
    export CODE_MOWER_PYTHON="$(command -v python3.12)"
-   pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+   pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
    code-mower --version
    ```
 

{code_mower-1.5.0 → code_mower-1.5.1}/docs/first-user-install-rehearsal.md

@@ -1,12 +1,12 @@
 # First-User Install Rehearsal
 
-v1.5.0 uses the exact install pin `code-mower==1.5.0`. Verify that version is
+v1.5.1 uses the exact install pin `code-mower==1.5.1`. Verify that version is
 published on the selected index, then verify the command path and version after
-installing. The [v1.5.0 qualification contract](v150-qualification.md) defines
+installing. The [v1.5.1 qualification contract](v151-qualification.md) defines
 the required evidence. After publication, the GitHub Release and linked release
 issue carry the observed source SHA, artifact digests, canary outcomes,
 publication run and reinstall evidence. Use the
-[candidate runbook](v150-release-runbook.md) for
+[candidate runbook](v151-release-runbook.md) for
 prepublication local-wheel rehearsals. Offline preparation does not establish
 live Slack readiness.
 
@@ -59,7 +59,7 @@ Use the current public tag or release candidate:
 
 ```bash
 code-mower migration package-install-rehearsal \
-  --package-spec code-mower==1.5.0 \
+  --package-spec code-mower==1.5.1 \
   --allow-package-index \
   --python "$(command -v python3.12)" \
   --json
@@ -83,7 +83,7 @@ For a fixed output directory:
 
 ```bash
 code-mower migration package-install-rehearsal \
-  --package-spec code-mower==1.5.0 \
+  --package-spec code-mower==1.5.1 \
   --allow-package-index \
   --python "$(command -v python3.12)" \
   --work-dir /tmp/code-mower-first-user-rehearsal \
@@ -127,7 +127,7 @@ deciding the package index or the release is broken. For pipx:
 
 ```bash
 export CODE_MOWER_PYTHON="$(command -v python3.12)"
-PIP_NO_CACHE_DIR=1 pipx install --force --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+PIP_NO_CACHE_DIR=1 pipx install --force --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 code-mower --version
 ```
 
@@ -137,7 +137,7 @@ For uv:
 env -u UV_INDEX -u UV_DEFAULT_INDEX -u UV_INDEX_URL -u UV_EXTRA_INDEX_URL \
   -u UV_FIND_LINKS -u UV_NO_INDEX -u UV_OFFLINE \
   uv --no-config --no-cache tool install --python 3.12 --reinstall \
-  --default-index https://pypi.org/simple/ code-mower==1.5.0
+  --default-index https://pypi.org/simple/ code-mower==1.5.1
 code-mower --version
 ```
 
@@ -168,7 +168,7 @@ repository after the package install succeeds:
 
 ```bash
 code-mower migration package-install-rehearsal \
-  --package-spec code-mower==1.5.0 \
+  --package-spec code-mower==1.5.1 \
   --allow-package-index \
   --repo-path /path/to/external-repo \
   --python "$(command -v python3.12)" \
@@ -260,7 +260,7 @@ When a product repository already has Code Mower wrapper files, the same
 
 ```bash
 code-mower migration package-install-rehearsal \
-  --package-spec code-mower==1.5.0 \
+  --package-spec code-mower==1.5.1 \
   --allow-package-index \
   --repo-path /path/to/product-repo \
   --python "$(command -v python3.12)" \
@@ -321,9 +321,9 @@ If this fails, fix the first-user path before cutting or promoting a release.
 ## Stable Package-Index Release Procedure
 
 The following v1.4.2 publication commands are historical evidence, not the
-v1.5.0 sequence. For v1.5.0 build the merge-SHA candidate first, qualify it in
+v1.5.1 sequence. For v1.5.1 build the merge-SHA candidate first, qualify it in
 #918 and explicitly authorized #920, then tag/publish the unchanged source SHA
-and the same artifacts through #923. Follow [the current runbook](v150-release-runbook.md).
+and the same artifacts through #923. Follow [the current runbook](v151-release-runbook.md).
 
 Publish and rehearse the package-index artifacts in this order. After the
 release tag exists at the release commit, dispatch both package-index

{code_mower-1.5.0 → code_mower-1.5.1}/docs/friendly-user-rollout-v05.md

@@ -1,7 +1,7 @@
 # Friendly-User Rollout Plan
 
 Source target: v1.5.0 supervised-pilot baseline. Release invitations and pinned
-index installs target `code-mower==1.5.0` only after that version is visible on
+index installs target `code-mower==1.5.1` only after that version is visible on
 the selected package index.
 
 This is the operating plan for the first 5-10 friendly users before Code Mower
@@ -33,14 +33,14 @@ out in the invite:
 ```bash
 python3.12 --version
 export CODE_MOWER_PYTHON="$(command -v python3.12)"
-pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 ```
 
-This source defines Code Mower `v1.5.0`, with package spec
-`code-mower==1.5.0`. Confirm the release tag on GitHub Releases and the package
+This source defines Code Mower `v1.5.1`, with package spec
+`code-mower==1.5.1`. Confirm the release tag on GitHub Releases and the package
 version on the selected index before using an index install command; source
 version and publication state are separate facts. After publication, see the
-[v1.5.0 release](https://github.com/codemower-ai/code-mower/releases/tag/v1.5.0).
+[v1.5.1 release](https://github.com/codemower-ai/code-mower/releases/tag/v1.5.1).
 
 ## Invite Criteria
 

{code_mower-1.5.0 → code_mower-1.5.1}/docs/install.md

@@ -1,12 +1,12 @@
 # Install And Bootstrap
 
-v1.5.0 uses the exact install pin `code-mower==1.5.0`. Confirm that version is
+v1.5.1 uses the exact install pin `code-mower==1.5.1`. Confirm that version is
 published on the selected index, then verify the command path and version after
-installing. The [v1.5.0 qualification contract](v150-qualification.md) defines
+installing. The [v1.5.1 qualification contract](v151-qualification.md) defines
 the required evidence. After publication, the GitHub Release and linked release
 issue carry the observed source SHA, artifact digests, canary outcomes,
 publication run and reinstall evidence. Use the
-[candidate runbook](v150-release-runbook.md) for
+[candidate runbook](v151-release-runbook.md) for
 prepublication local-wheel rehearsals. Offline preparation does not establish
 live Slack readiness.
 
@@ -39,6 +39,23 @@ documentation rather than from a copied shell snippet:
 Code Mower does not publish, and you should not use, a
 `curl ... | sh` bootstrap for either installer.
 
+On a hosted Linux image that has Python 3.12 with `venv` support but neither
+installer, bootstrap uv in a small isolated environment instead of piping a
+remote script into a shell or writing into an externally managed system
+Python:
+
+```bash
+UV_BOOTSTRAP="$HOME/.local/share/code-mower-bootstrap/uv"
+python3.12 -m venv "$UV_BOOTSTRAP"
+"$UV_BOOTSTRAP/bin/python" -m pip install --upgrade uv
+"$UV_BOOTSTRAP/bin/python" -m uv --version
+"$UV_BOOTSTRAP/bin/python" -m uv tool install --python 3.12 code-mower==1.5.1
+```
+
+The module form works even when uv is not yet on `PATH`. After installation,
+follow uv's printed path hint, then verify
+`command -v code-mower` and `code-mower --version` before using the repository.
+
 Confirm the installer is on `PATH` before installing Code Mower with it:
 
 ```bash
@@ -61,7 +78,7 @@ code-mower --version
 ```
 
 `command -v code-mower` must print the path belonging to the installer you
-chose, and `code-mower --version` must print `code-mower 1.5.0`. A version that
+chose, and `code-mower --version` must print `code-mower 1.5.1`. A version that
 does not match, or a path from a different installer, means an older command is
 still winning on `PATH`; resolve that before running anything against a
 repository.
@@ -101,7 +118,7 @@ v1.5.0 includes the local audit publisher, which generates
 gate and standalone verification helpers. Commit that generated set to the
 repository's default branch before switching local Claude/Codex wrappers to
 workflow publication. A PR's copy of the verifier has no publication authority.
-Before v1.5.0 is published, use its reviewed candidate wheel; afterward, use the
+Before v1.5.1 is published, use its reviewed candidate wheel; afterward, use the
 exact published pin below.
 
 The generated self-hosted audit job seals the verdict digest in an immutable
@@ -121,7 +138,7 @@ Install with pipx and an explicit Python 3.12+ interpreter:
 ```bash
 python3.12 --version
 export CODE_MOWER_PYTHON="$(command -v python3.12)"
-pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+pipx install --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 code-mower --version
 ```
 
@@ -142,7 +159,7 @@ To replace an existing pipx install with an exact release, use `--force` so the
 old venv cannot keep serving the previous package:
 
 ```bash
-PIP_NO_CACHE_DIR=1 pipx install --force --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+PIP_NO_CACHE_DIR=1 pipx install --force --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 code-mower --version
 ```
 
@@ -155,7 +172,7 @@ export PIPX_HOME="$CODE_MOWER_AGENT_TOOLS/pipx"
 export PIPX_BIN_DIR="$CODE_MOWER_AGENT_TOOLS/bin"
 export PIPX_LOG_DIR="$CODE_MOWER_AGENT_TOOLS/logs"
 mkdir -p "$PIPX_HOME" "$PIPX_BIN_DIR" "$PIPX_LOG_DIR"
-PIP_NO_CACHE_DIR=1 pipx install --force --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+PIP_NO_CACHE_DIR=1 pipx install --force --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 "$PIPX_BIN_DIR/code-mower" --version
 ```
 
@@ -166,7 +183,7 @@ interactive shell profile:
 
 ```bash
 uv python install 3.12
-uv tool install --python 3.12 code-mower==1.5.0
+uv tool install --python 3.12 code-mower==1.5.1
 code-mower --version
 ```
 
@@ -176,7 +193,7 @@ installed command directly from the uv tool bin directory for that session.
 To replace an existing uv tool install with an exact release:
 
 ```bash
-uv tool install --python 3.12 --reinstall --refresh-package code-mower code-mower==1.5.0
+uv tool install --python 3.12 --reinstall --refresh-package code-mower code-mower==1.5.1
 code-mower --version
 ```
 
@@ -227,7 +244,7 @@ command -v code-mower
 code-mower --version
 pipx uninstall code-mower
 uv python install 3.12
-uv tool install --python 3.12 --reinstall --refresh-package code-mower code-mower==1.5.0
+uv tool install --python 3.12 --reinstall --refresh-package code-mower code-mower==1.5.1
 hash -r
 command -v code-mower
 code-mower --version
@@ -247,7 +264,7 @@ For pipx:
 ```bash
 python3.12 --version
 export CODE_MOWER_PYTHON="$(command -v python3.12)"
-PIP_NO_CACHE_DIR=1 pipx install --force --python "$CODE_MOWER_PYTHON" code-mower==1.5.0
+PIP_NO_CACHE_DIR=1 pipx install --force --python "$CODE_MOWER_PYTHON" code-mower==1.5.1
 code-mower --version
 ```
 
@@ -255,7 +272,7 @@ For uv:
 
 ```bash
 uv python install 3.12
-uv tool install --python 3.12 --reinstall --refresh-package code-mower code-mower==1.5.0
+uv tool install --python 3.12 --reinstall --refresh-package code-mower code-mower==1.5.1
 code-mower --version
 ```
 
@@ -430,6 +447,23 @@ code-mower doctor --adoption --hosted-builders --repo OWNER/REPO --json
 code-mower doctor --adoption --orchestrator-only --repo OWNER/REPO --json
 ```
 
+Those commands expect the current checkout to contain `code-mower.yml`. On a
+remote-only host with no repository checkout, select the maintained packaged
+starter explicitly through the easy preset:
+
+```bash
+code-mower doctor --easy --orchestrator-only --repo OWNER/REPO --json
+```
+
+The resulting filesystem and generated-workflow checks describe the packaged
+starter, not the remote repository. Use them for installation posture; use
+`lanes status --repo OWNER/REPO` for current remote PR and gate visibility.
+
+Doctor JSON is local diagnostic evidence. It can include bounded local paths
+such as the selected config, executable, or workflow path. Review or redact it
+before attaching it to an issue or uploading it; the concise text view is the
+safer first status summary.
+
 In those observer/coordinator postures, missing local wrapper environment
 variables and missing `DISPATCH_TOKEN` setup are surfaced as owner setup or
 promotion tasks, not as proof the install is broken. Adoption text output

{code_mower-1.5.0 → code_mower-1.5.1}/docs/local-audit-runner.md

@@ -165,7 +165,7 @@ metadata only while its original head and freshness checks still hold.
 
 Only canonical metadata leaves the machine: schema, numeric repository ID, PR
 number, reviewer lane, PASS/BLOCKED, full start/end head SHAs, artifact creation
-time, and the originating audit run ID/attempt. The repository name, comment prose, findings, code, prompts, transcript,
+time, and the originating audit run, attempt, and job IDs. The repository name, comment prose, findings, code, prompts, transcript,
 paths and provider output stay local. The SHA-256 digest covers those exact
 canonical metadata bytes. The publisher accepts only equal full start/end SHAs,
 an open PR at that SHA, and artifacts no more than 24 hours old. UNKNOWN, STALE,
@@ -185,12 +185,15 @@ attempt is refused. Keep receipts and reservations for at least the 24-hour
 artifact lifetime. The global publication concurrency group serializes claims;
 GitHub may cancel an older queued dispatch, which requires inspecting its result.
 
-The source job stages the metadata, independently validates it, and completes a
+The source job stages the metadata with its exact GitHub Actions job ID,
+independently validates it, and completes a
 `Code Mower reviewer seal <digest>` step before dispatch. The publisher verifies
-that immutable Actions step record in the matching `audit (claude|codex)` job,
+that immutable Actions step record in that exact `audit (claude|codex)` job,
 source run ID/attempt, trusted `local-cli-audit.yml` `repository_dispatch` event,
 same repository and default branch. The sealed digest binds the PR, lane and
-full start/end head. The small `local-audit-request.yml` trigger requests the
+full start/end head plus the source job identity. Another audit lane in the
+same matrix run cannot satisfy or make ambiguous that binding; a duplicate
+seal within the requested lane is refused. The small `local-audit-request.yml` trigger requests the
 review; the source workflow validates the request against the live PR before
 starting a provider. Both source and publisher use `repository_dispatch`, which
 always executes default-branch code: a builder cannot counterfeit a source job

{code_mower-1.5.0 → code_mower-1.5.1}/docs/mirror-removal-runbook.md

@@ -32,7 +32,7 @@ Run:
 
 ```bash
 code-mower migration package-install-rehearsal \
-  --package-spec code-mower==1.5.0 \
+  --package-spec code-mower==1.5.1 \
   --allow-package-index \
   --repo-path /path/to/product-repo \
   --json

{code_mower-1.5.0 → code_mower-1.5.1}/docs/orchestrator-prompt-pack.md

@@ -74,12 +74,25 @@ Run the posture-appropriate doctor:
 - local reviewer/builder machine: code-mower doctor --adoption --repo OWNER/REPO --json
 - hosted builder or observer: code-mower doctor --adoption --hosted-builders --repo OWNER/REPO --json
 - orchestrator-only host: code-mower doctor --adoption --orchestrator-only --repo OWNER/REPO --json
+- remote-only host with no checkout config: code-mower doctor --adoption --orchestrator-only --repo OWNER/REPO --json
 - supervised pilot readiness: code-mower doctor --supervised-pilot --repo OWNER/REPO --json
 
 Read the posture-scoped summary first by rerunning the same posture with
 --concise instead of --json: every check still runs, and the summary leads with
 active failures and owner actions. Keep the --json output as the complete
-machine-readable evidence, and use --advanced for the full text list.
+machine-readable local evidence, and use --advanced for the full text list.
+When the orchestrator-only command has no repository config, doctor labels the
+result as a `packaged_starter_remote_observer` plan. It omits local wrapper,
+provider-login, campaign, optional Cloud, and product-test checks unless they
+were selected explicitly. With no checkout, it also omits workflow-presence
+checks. Repository Actions secret and variable presence still comes from the
+target repository through `gh`; that is separate from `GITHUB_TOKEN` or local
+checkout-path requirements used by direct local-audit wrappers.
+
+That packaged-starter remote-observer JSON uses stable package labels and does
+not include local config, executable, checkout, or workflow paths. Other doctor
+JSON can contain local paths; review or redact it before attaching or uploading
+it.
 
 Provider selection and a working CLI do not qualify an orchestrator. Devin is
 currently limited to bounded builder work and informational review; use a
@@ -94,8 +107,11 @@ SESSION_ID using the saved ID. A later shell must pass that ID explicitly.
 If work intentionally continues, renew only your live lease with code-mower
 session lease renew --session-id SESSION_ID. Use session show --current to
 find the matching saved brief from this checkout.
-Do not force-release another session as routine cleanup. A read-only adoption
-check can use session start --dry-run or --no-lease.
+Do not force-release another session as routine cleanup. An eligible host can
+use session start --dry-run or --no-lease for a read-only adoption check. Host
+role admission still runs before either mode; an ineligible host reports the
+diagnostic and hands orchestration to a qualified host rather than rendering a
+brief under an unqualified identity.
 
 Then run code-mower lanes status --repo OWNER/REPO and, when useful, start or
 check the local Board with code-mower board serve --repo OWNER/REPO.

{code_mower-1.5.0 → code_mower-1.5.1}/docs/oss-v1-checklist.md

@@ -47,7 +47,7 @@ history opens the repository. They should be able to confirm:
 ## Current v1.0 Baseline
 
 The historical public-release baseline below is the published `v1.4.2`.
-For v1.5.0 follow [the immutable candidate-first runbook](v150-release-runbook.md);
+For v1.5.1 follow [the immutable candidate-first runbook](v151-release-runbook.md);
 these publication and dogfood steps record the previous release procedure.
 Before widening that release, record:
 

{code_mower-1.5.0 → code_mower-1.5.1}/docs/package-customization.md

@@ -286,7 +286,7 @@ run:
 
 ```bash
 code-mower migration package-install-rehearsal \
-  --package-spec code-mower==1.5.0 \
+  --package-spec code-mower==1.5.1 \
   --allow-package-index \
   --repo-path /path/to/product-repo \
   --json

{code_mower-1.5.0 → code_mower-1.5.1}/docs/provider-matrix.md

@@ -30,7 +30,7 @@ agent hosting a session is the default orchestrator.
 
 The lease, shared Jira brief, and explicit Cursor qualification have been
 available since `code-mower==1.4.0` and are present in
-`code-mower==1.5.0`; see [Participants And Sessions](sessions.md) for
+`code-mower==1.5.1`; see [Participants And Sessions](sessions.md) for
 the operating contract.
 
 ## Provider Classes