code-mower 0.5.0b51__tar.gz → 0.5.0b53__tar.gz

{code_mower-0.5.0b51 → code_mower-0.5.0b53}/MANIFEST.in

@@ -1,9 +1,11 @@
 recursive-include src/code_mower/templates *.yml *.yaml *.json
 recursive-include src/code_mower/templates *.md
 recursive-include src/code_mower/templates *.j2
+recursive-include src/code_mower/templates/lanes *
 recursive-include src/code_mower/templates/product-support *
 include src/code_mower/*.json
 recursive-include templates *.j2 *.json *.md *.yml *.yaml
+recursive-include templates/lanes *
 include requirements/*.txt
 include LICENSE
 include NOTICE

{code_mower-0.5.0b51 → code_mower-0.5.0b53}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-mower
-Version: 0.5.0b51
+Version: 0.5.0b53
 Summary: Multi-reviewer AI code audit orchestration
 License-Expression: Apache-2.0
 Requires-Python: >=3.11
@@ -19,6 +19,9 @@ Code Mower helps teams set up AI peer-programmer and reviewer lanes on real
 GitHub pull requests, then measure which builders and reviewers are useful on
 their actual codebase.
 
+Code Mower is beta, bring-your-own-agent-loop software for teams willing to
+calibrate reviewers. It is not a drop-in autonomous merge gate.
+
 The short version:
 
 - create safe, manual-first reviewer lanes for Codex, Claude, Gitar, and other
@@ -97,46 +100,26 @@ known-blocked control, and three reviewer lanes. It shows the decision Code
 Mower is built to support: which AI reviewers are useful, noisy, expensive,
 fast, or eligible for stronger merge policy on your actual codebase.
 
-## Try It First
-
-Code Mower currently targets Python 3.11+; Python 3.12 is recommended.
-
-```bash
-python3.12 --version
-pipx install --python python3.12 code-mower==0.5.0b51
-code-mower --version
-```
-
-`0.5.0b51` is a beta release. Until Code Mower publishes a stable `1.0`
-line, use the explicit beta version above or allow prereleases with:
+## Start Here
 
-```bash
-pipx install --python python3.12 --pip-args="--pre" code-mower
-```
+Choose one path. Each path has one guide and gets to one visible outcome.
 
-From the repository you want to pilot:
-
-```bash
-code-mower init --easy
-code-mower doctor --preflight
-code-mower checks detect --json
-```
+| Path | Use When | Route | Guide |
+| --- | --- | --- | --- |
+| A. Reviewer gate in 10 minutes | You want one audited PR before recurring workflows or builder dispatch. | Install, run `init --easy`, run `doctor --preflight`, open a small setup PR, run Codex and Claude audits, then merge manually when the audit evidence is clean. | [Try Code Mower In 10 Minutes](docs/try-in-10-minutes.md) |
+| B. Build loop in 30 minutes | You want builders plus an orchestrator pattern after the reviewer gate works. | Complete path A, then add the automation token, require `code-mower/gate` from Any source, enable repository auto-merge, prove the self-hosted Mac lane runner with `doctor --runner`, run `init --builders`, and dispatch the first issue. | [Build Loop In 30 Minutes](docs/build-loop-in-30-minutes.md) |
 
-In Git worktrees, `checks detect` also offers `code-mower.pr-size`, a local
-PR-size lint that defaults to 300 changed lines and flags large batches of
-near-identical files.
+The beta.53 announcement entry point is the tagged
+[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v0.5.0-beta.53/docs/try-in-10-minutes.md)
+guide.
 
-When those look sane, write the generated setup to a reviewable folder and
-produce the starter local report:
+## What Calibration Does And Does Not Prove
 
-```bash
-code-mower init --easy --apply --output-dir .code-mower.generated
-code-mower calibration value-report .code-mower.generated/calibration-corpus.json \
-  --output .code-mower/reviewer-value-report.md
-```
+The generated starter corpus proves that the commands run and the report path
+works. It does not prove that a reviewer should gate merges. Promote reviewer
+lanes only after repository-specific known-clean and known-blocked evidence
+meets the [lane promotion policy](docs/lane-promotion-policy.md).
 
-The generated setup also includes the configurable owner escalation and weekly
-status digest templates. The generated starter corpus proves the command path.
 To bootstrap a draft from your repository history:
 
 ```bash
@@ -153,9 +136,12 @@ every disposition before using it for lane promotion or merge policy.
 Full walkthrough: [docs/try-in-10-minutes.md](docs/try-in-10-minutes.md).
 First-time command map: [docs/launch-command-surface.md](docs/launch-command-surface.md).
 
-The current PyPI beta has been rehearsed end-to-end from a clean install:
+The beta.53 package-index release is prepared:
 [First-User Install Rehearsal](docs/first-user-install-rehearsal.md) records
-the latest 10/10 public-package readiness proof for `code-mower==0.5.0b51`.
+the release procedure. It is to be published and rehearsed as part of the
+`v0.5.0-beta.53` release execution, with evidence recorded on the release after
+the workflow runs complete. The latest completed public-package rehearsal
+remains beta.52: 10/10 first-user readiness for `code-mower==0.5.0b52`.
 
 ## Optional: Plan Before Coding
 
@@ -205,6 +191,15 @@ That lets CodeMower.com show `issue -> plan -> work order -> builder run -> PR
 transcripts, prompts, or issue body text. See
 [docs/builders-grok-cursor.md](docs/builders-grok-cursor.md).
 
+## Roles
+
+Code Mower records builder provenance for Claude Code, Codex, Cursor-style
+hosted builders, and similar authoring lanes, then runs reviewer lanes against
+the resulting pull requests. The orchestrator is a workflow convention: issue,
+optional work order, single-writer branch, reviewer lanes, and fix rounds. Code
+Mower's templates now support that loop end to end; humans still own
+credentials, branch protection, calibration, and owner decisions.
+
 ## Why Not Just Run Codex Or Claude Yourself?
 
 You should, at first. Code Mower is not a replacement for a good local agent or
@@ -301,18 +296,20 @@ engineer can:
 7. optionally upload sanitized metadata to CodeMower.com and see useful team
    dashboard signal.
 
-Future builder/orchestrator experiments extend the same loop from "who reviews
-best?" to "which AI builder plus reviewer loop ships best on this product?" See
+Build-loop templates extend the same loop from "who reviews best?" to "which AI
+builder plus reviewer loop ships best on this product?" Start with
+[docs/build-loop-in-30-minutes.md](docs/build-loop-in-30-minutes.md), then use
 [docs/builder-experiments.md](docs/builder-experiments.md) and
-[docs/authoring-intelligence.md](docs/authoring-intelligence.md). For hosted
-builder provenance, start with
-[docs/builders-grok-cursor.md](docs/builders-grok-cursor.md).
+[docs/authoring-intelligence.md](docs/authoring-intelligence.md) for deeper
+measurement work.
 
 ## Installation Status
 
-The current public beta is `v0.5.0-beta.51` from
-[codemower-ai/code-mower](https://github.com/codemower-ai/code-mower), published
-as `code-mower==0.5.0b51` on [PyPI](https://pypi.org/project/code-mower/).
+The prepared public beta is `v0.5.0-beta.53` from
+[codemower-ai/code-mower](https://github.com/codemower-ai/code-mower). It is to
+be published and rehearsed as part of the `v0.5.0-beta.53` release execution,
+with evidence recorded on the release after the workflow runs complete. The
+pinned package-index install spec is `code-mower==0.5.0b53`.
 GitHub releases remain the auditable source for tags, build artifacts, and
 release notes.
 
@@ -349,7 +346,19 @@ The wrapper resolves Python 3.12+ and refuses stale or old system Python shims.
 ## Docs Map
 
 - [Try Code Mower In 10 Minutes](docs/try-in-10-minutes.md)
-- [Quickstart](docs/quickstart.md)
+- [Build Loop In 30 Minutes](docs/build-loop-in-30-minutes.md)
+- [Quickstart Reference](docs/quickstart.md)
+- [Planning And Work Orders](docs/planning-work-orders.md)
+- [Builder Providers: Grok And Cursor](docs/builders-grok-cursor.md)
+- [Build Loop Operations](docs/build-loop.md)
+- [Self-Hosted Mac Runner](docs/self-hosted-mac-runner.md)
+- [Local Audit Runner](docs/local-audit-runner.md)
+- [Lane Standing Instructions](docs/lanes/README.md)
+- [Codex Lane Standing Instructions](docs/lanes/codex.md)
+- [Claude Lane Standing Instructions](docs/lanes/claude.md)
+- [Cursor Hosted Lane Standing Instructions](docs/lanes/cursor.md)
+- [Provider Matrix](docs/provider-matrix.md)
+- [GitHub Setup](docs/github-setup.md)
 - [First Run Transcript](docs/first-run-transcript.md)
 - [First-User Demo Transcript](docs/first-user-demo-transcript.md)
 - [First-User Install Rehearsal](docs/first-user-install-rehearsal.md)
@@ -358,8 +367,7 @@ The wrapper resolves Python 3.12+ and refuses stale or old system Python shims.
 - [PyPI Release Runbook](docs/pypi-release.md)
 - [Sample Doctor Output](docs/sample-doctor-output.md)
 - [Architecture](docs/architecture.md)
-- [Provider Matrix](docs/provider-matrix.md)
-- [GitHub Setup](docs/github-setup.md)
+- [Lane Promotion Policy](docs/lane-promotion-policy.md)
 - [Cloud Sharing](docs/cloud-sharing.md)
 - [Cloud Data Contract](docs/cloud-data-contract.md)
 - [Privacy And Threat Model](docs/privacy-threat-model.md)

{code_mower-0.5.0b51 → code_mower-0.5.0b53}/README.md

@@ -4,6 +4,9 @@ Code Mower helps teams set up AI peer-programmer and reviewer lanes on real
 GitHub pull requests, then measure which builders and reviewers are useful on
 their actual codebase.
 
+Code Mower is beta, bring-your-own-agent-loop software for teams willing to
+calibrate reviewers. It is not a drop-in autonomous merge gate.
+
 The short version:
 
 - create safe, manual-first reviewer lanes for Codex, Claude, Gitar, and other
@@ -82,46 +85,26 @@ known-blocked control, and three reviewer lanes. It shows the decision Code
 Mower is built to support: which AI reviewers are useful, noisy, expensive,
 fast, or eligible for stronger merge policy on your actual codebase.
 
-## Try It First
-
-Code Mower currently targets Python 3.11+; Python 3.12 is recommended.
-
-```bash
-python3.12 --version
-pipx install --python python3.12 code-mower==0.5.0b51
-code-mower --version
-```
-
-`0.5.0b51` is a beta release. Until Code Mower publishes a stable `1.0`
-line, use the explicit beta version above or allow prereleases with:
+## Start Here
 
-```bash
-pipx install --python python3.12 --pip-args="--pre" code-mower
-```
+Choose one path. Each path has one guide and gets to one visible outcome.
 
-From the repository you want to pilot:
-
-```bash
-code-mower init --easy
-code-mower doctor --preflight
-code-mower checks detect --json
-```
+| Path | Use When | Route | Guide |
+| --- | --- | --- | --- |
+| A. Reviewer gate in 10 minutes | You want one audited PR before recurring workflows or builder dispatch. | Install, run `init --easy`, run `doctor --preflight`, open a small setup PR, run Codex and Claude audits, then merge manually when the audit evidence is clean. | [Try Code Mower In 10 Minutes](docs/try-in-10-minutes.md) |
+| B. Build loop in 30 minutes | You want builders plus an orchestrator pattern after the reviewer gate works. | Complete path A, then add the automation token, require `code-mower/gate` from Any source, enable repository auto-merge, prove the self-hosted Mac lane runner with `doctor --runner`, run `init --builders`, and dispatch the first issue. | [Build Loop In 30 Minutes](docs/build-loop-in-30-minutes.md) |
 
-In Git worktrees, `checks detect` also offers `code-mower.pr-size`, a local
-PR-size lint that defaults to 300 changed lines and flags large batches of
-near-identical files.
+The beta.53 announcement entry point is the tagged
+[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v0.5.0-beta.53/docs/try-in-10-minutes.md)
+guide.
 
-When those look sane, write the generated setup to a reviewable folder and
-produce the starter local report:
+## What Calibration Does And Does Not Prove
 
-```bash
-code-mower init --easy --apply --output-dir .code-mower.generated
-code-mower calibration value-report .code-mower.generated/calibration-corpus.json \
-  --output .code-mower/reviewer-value-report.md
-```
+The generated starter corpus proves that the commands run and the report path
+works. It does not prove that a reviewer should gate merges. Promote reviewer
+lanes only after repository-specific known-clean and known-blocked evidence
+meets the [lane promotion policy](docs/lane-promotion-policy.md).
 
-The generated setup also includes the configurable owner escalation and weekly
-status digest templates. The generated starter corpus proves the command path.
 To bootstrap a draft from your repository history:
 
 ```bash
@@ -138,9 +121,12 @@ every disposition before using it for lane promotion or merge policy.
 Full walkthrough: [docs/try-in-10-minutes.md](docs/try-in-10-minutes.md).
 First-time command map: [docs/launch-command-surface.md](docs/launch-command-surface.md).
 
-The current PyPI beta has been rehearsed end-to-end from a clean install:
+The beta.53 package-index release is prepared:
 [First-User Install Rehearsal](docs/first-user-install-rehearsal.md) records
-the latest 10/10 public-package readiness proof for `code-mower==0.5.0b51`.
+the release procedure. It is to be published and rehearsed as part of the
+`v0.5.0-beta.53` release execution, with evidence recorded on the release after
+the workflow runs complete. The latest completed public-package rehearsal
+remains beta.52: 10/10 first-user readiness for `code-mower==0.5.0b52`.
 
 ## Optional: Plan Before Coding
 
@@ -190,6 +176,15 @@ That lets CodeMower.com show `issue -> plan -> work order -> builder run -> PR
 transcripts, prompts, or issue body text. See
 [docs/builders-grok-cursor.md](docs/builders-grok-cursor.md).
 
+## Roles
+
+Code Mower records builder provenance for Claude Code, Codex, Cursor-style
+hosted builders, and similar authoring lanes, then runs reviewer lanes against
+the resulting pull requests. The orchestrator is a workflow convention: issue,
+optional work order, single-writer branch, reviewer lanes, and fix rounds. Code
+Mower's templates now support that loop end to end; humans still own
+credentials, branch protection, calibration, and owner decisions.
+
 ## Why Not Just Run Codex Or Claude Yourself?
 
 You should, at first. Code Mower is not a replacement for a good local agent or
@@ -286,18 +281,20 @@ engineer can:
 7. optionally upload sanitized metadata to CodeMower.com and see useful team
    dashboard signal.
 
-Future builder/orchestrator experiments extend the same loop from "who reviews
-best?" to "which AI builder plus reviewer loop ships best on this product?" See
+Build-loop templates extend the same loop from "who reviews best?" to "which AI
+builder plus reviewer loop ships best on this product?" Start with
+[docs/build-loop-in-30-minutes.md](docs/build-loop-in-30-minutes.md), then use
 [docs/builder-experiments.md](docs/builder-experiments.md) and
-[docs/authoring-intelligence.md](docs/authoring-intelligence.md). For hosted
-builder provenance, start with
-[docs/builders-grok-cursor.md](docs/builders-grok-cursor.md).
+[docs/authoring-intelligence.md](docs/authoring-intelligence.md) for deeper
+measurement work.
 
 ## Installation Status
 
-The current public beta is `v0.5.0-beta.51` from
-[codemower-ai/code-mower](https://github.com/codemower-ai/code-mower), published
-as `code-mower==0.5.0b51` on [PyPI](https://pypi.org/project/code-mower/).
+The prepared public beta is `v0.5.0-beta.53` from
+[codemower-ai/code-mower](https://github.com/codemower-ai/code-mower). It is to
+be published and rehearsed as part of the `v0.5.0-beta.53` release execution,
+with evidence recorded on the release after the workflow runs complete. The
+pinned package-index install spec is `code-mower==0.5.0b53`.
 GitHub releases remain the auditable source for tags, build artifacts, and
 release notes.
 
@@ -334,7 +331,19 @@ The wrapper resolves Python 3.12+ and refuses stale or old system Python shims.
 ## Docs Map
 
 - [Try Code Mower In 10 Minutes](docs/try-in-10-minutes.md)
-- [Quickstart](docs/quickstart.md)
+- [Build Loop In 30 Minutes](docs/build-loop-in-30-minutes.md)
+- [Quickstart Reference](docs/quickstart.md)
+- [Planning And Work Orders](docs/planning-work-orders.md)
+- [Builder Providers: Grok And Cursor](docs/builders-grok-cursor.md)
+- [Build Loop Operations](docs/build-loop.md)
+- [Self-Hosted Mac Runner](docs/self-hosted-mac-runner.md)
+- [Local Audit Runner](docs/local-audit-runner.md)
+- [Lane Standing Instructions](docs/lanes/README.md)
+- [Codex Lane Standing Instructions](docs/lanes/codex.md)
+- [Claude Lane Standing Instructions](docs/lanes/claude.md)
+- [Cursor Hosted Lane Standing Instructions](docs/lanes/cursor.md)
+- [Provider Matrix](docs/provider-matrix.md)
+- [GitHub Setup](docs/github-setup.md)
 - [First Run Transcript](docs/first-run-transcript.md)
 - [First-User Demo Transcript](docs/first-user-demo-transcript.md)
 - [First-User Install Rehearsal](docs/first-user-install-rehearsal.md)
@@ -343,8 +352,7 @@ The wrapper resolves Python 3.12+ and refuses stale or old system Python shims.
 - [PyPI Release Runbook](docs/pypi-release.md)
 - [Sample Doctor Output](docs/sample-doctor-output.md)
 - [Architecture](docs/architecture.md)
-- [Provider Matrix](docs/provider-matrix.md)
-- [GitHub Setup](docs/github-setup.md)
+- [Lane Promotion Policy](docs/lane-promotion-policy.md)
 - [Cloud Sharing](docs/cloud-sharing.md)
 - [Cloud Data Contract](docs/cloud-data-contract.md)
 - [Privacy And Threat Model](docs/privacy-threat-model.md)

{code_mower-0.5.0b51 → code_mower-0.5.0b53}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "code-mower"
-version = "0.5.0b51"
+version = "0.5.0b53"
 description = "Multi-reviewer AI code audit orchestration"
 requires-python = ">=3.11"
 readme = "README.md"
@@ -31,6 +31,7 @@ code_mower = [
     "templates/**/*.yml",
     "templates/**/*.yaml",
     "templates/**/*.j2",
+    "templates/lanes/*",
     "templates/product-support/*",
 ]
 

{code_mower-0.5.0b51 → code_mower-0.5.0b53}/src/code_mower/__init__.py

@@ -1,3 +1,3 @@
 """Code Mower package."""
 
-__version__ = "0.5.0b51"
+__version__ = "0.5.0b53"