code-mower 0.6.0b2__tar.gz → 0.8.0b1__tar.gz

{code_mower-0.6.0b2/src/code_mower.egg-info → code_mower-0.8.0b1}/PKG-INFO

@@ -1,16 +1,18 @@
 Metadata-Version: 2.4
 Name: code-mower
-Version: 0.6.0b2
+Version: 0.8.0b1
 Summary: Multi-reviewer AI code audit orchestration
 License-Expression: Apache-2.0
-Requires-Python: >=3.11
+Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE
 License-File: NOTICE
 Requires-Dist: PyYAML>=6.0
 Provides-Extra: test
+Requires-Dist: build>=1.2; extra == "test"
 Requires-Dist: pytest>=8.0; extra == "test"
 Requires-Dist: ruff>=0.8; extra == "test"
+Requires-Dist: twine>=5.0; extra == "test"
 Dynamic: license-file
 
 # Code Mower
@@ -57,15 +59,16 @@ Code Mower should feel like an engineering tool, not a demo harness:
 
 ## What It Looks Like
 
-`code-mower doctor --preflight` is the first useful command. It checks your
-runtime, GitHub setup, provider CLIs, token posture, optional cloud setup, and
-private-repo Actions cost traps. `--preflight` is the friendly first-run preset;
-`doctor --v05` remains an equivalent compatibility alias for older scripts.
+`code-mower doctor --adoption --repo OWNER/REPO` is the first useful command
+for a real repository. It checks your runtime, GitHub setup, provider CLIs,
+token posture, optional cloud setup, private-repo Actions cost traps, and
+first-run adoption gaps. `--preflight` remains the compatibility preset for
+older scripts; `--adoption` adds explicit repo targeting and setup guidance.
 
 Example, shortened:
 
 ```text
-$ code-mower doctor --preflight
+$ code-mower doctor --adoption --repo OWNER/REPO
 PASS  config.validate             config validates
 PASS  profile.select              selected profile: codex, claude_audit, gitar
 PASS  runtime.python              Python 3.12 satisfies Code Mower requirements
@@ -87,7 +90,33 @@ See a fuller static transcript: [docs/first-run-transcript.md](docs/first-run-tr
 
 After `init` and `doctor`, use `code-mower lanes status --repo OWNER/REPO` to
 see active builder/reviewer lanes, gate/check state, recent Code Mower
-workflows, local AgentTrail boards when present, and the next operator action.
+workflows, local board/process hints when present, and the next operator
+action. Text and JSON output redact local cwd paths by default; use
+`--show-local-paths` only for local debugging.
+
+For the same redacted metadata in a local browser view, run
+`code-mower board serve --repo OWNER/REPO` and open the printed localhost URL.
+Plain `board serve` is read-only. To build local history while the browser view
+is open, run `code-mower board serve --repo OWNER/REPO --record-events`; it
+records at most one snapshot every 60 seconds by default. To append one snapshot
+without serving the browser view, run
+`code-mower board record --repo OWNER/REPO` from the repository checkout; it
+writes metadata-only snapshots to `.code-mower/board/events.jsonl` with default
+14-day and 500-event retention. `code-mower board events` prints recent stored
+events without calling GitHub. `code-mower board doctor --repo OWNER/REPO`
+checks Board inputs and local history without exposing local paths by default.
+`code-mower board reset --repo OWNER/REPO --yes` clears only the local Board
+history file. The Board also shows an owner queue, and it
+summarizes reviewer verdict history and spend/latency from local board events
+plus `.code-mower/reviewer-spend.json` when those files exist. Local agents can
+publish opt-in status cards by writing metadata-only JSON files to
+`.code-mower/board/agents/*.json`; the Board redacts local paths by default and
+does not upload those cards.
+The local JSON contracts are documented in
+[Board Data Contract](docs/board-data-contract.md).
+When a team wants the same operator picture on CodeMower.com, run
+`code-mower cloud board-snapshot --repo-slug OWNER/REPO --json` to inspect a
+zero-report, metadata-only mirror event, then add `--yes` only after review.
 
 ## See The Value Shape First
 
@@ -95,8 +124,10 @@ If you want to understand the product before installing anything, start with
 the checked-in demo calibration package:
 
 - [examples/demo-calibration/README.md](examples/demo-calibration/README.md)
+- [examples/board-demo/README.md](examples/board-demo/README.md)
 - [examples/demo-calibration/reviewer-value-report.md](examples/demo-calibration/reviewer-value-report.md)
 - [docs/first-user-demo-transcript.md](docs/first-user-demo-transcript.md)
+- [docs/post-v08-effectiveness-assessment.md](docs/post-v08-effectiveness-assessment.md)
 
 The example is intentionally tiny and synthetic: one known-clean control, one
 known-blocked control, and three reviewer lanes. It shows the decision Code
@@ -110,15 +141,21 @@ Cold adopters should start with the reviewer gate, then add builders, then
 measure builder experiments; provider experiments come after that base loop is
 observable.
 
+Install first from the [Install And Bootstrap](docs/install.md) matrix: pipx for
+laptops, uv tool installs for hosted agents or CI boxes, and an editable venv
+for Code Mower contributors. All paths require Python 3.12 or newer.
+
 | 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) |
+| A. Reviewer gate in 10 minutes | You want one audited PR before recurring workflows or builder dispatch. | Install, run `init --easy`, run `doctor --adoption --repo OWNER/REPO`, 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) |
 | C. Builder experiment | You want to compare authoring loops before trusting them broadly. | Use a work order or experiment spec, run `code-mower builder-experiment run` around an explicit command, then review the source-free `authoringRun` artifact and normal audit evidence. | [Builder Experiments](docs/builder-experiments.md) |
 
-The v0.6 beta announcement entry point is the tagged
-[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v0.6.0-beta.2/docs/try-in-10-minutes.md)
-guide.
+The current package-index announcement entry point is the tagged
+[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v0.8.0-beta.1/docs/try-in-10-minutes.md)
+guide. The v0.8 beta includes the completed adoption-polish and native Board
+work, so package-only users can start from the public package rather than a
+source checkout.
 
 ## What Calibration Does And Does Not Prove
 
@@ -147,7 +184,7 @@ Provider-contract baseline for the next release train:
 
 For release verification,
 [First-User Install Rehearsal](docs/first-user-install-rehearsal.md) records
-the package-index procedure for `v0.6.0-beta.2` / `code-mower==0.6.0b2`. The
+the package-index procedure for `v0.8.0-beta.1` / `code-mower==0.8.0b1`. The
 GitHub release records the workflow and rehearsal evidence for the exact tag.
 
 ## Optional: Plan Before Coding
@@ -253,6 +290,9 @@ code-mower cloud dogfood --json
 ```
 
 Nothing uploads unless you pass `--yes`.
+For the hosted Board mirror specifically,
+`code-mower cloud board-snapshot --repo-slug OWNER/REPO --json` exports one
+metadata-only event and zero reports; add `--yes` to upload it after inspection.
 
 Current dogfood uploads, historical catch-up imports, and calibrated
 reviewer/lens evidence are intentionally separate. Imported GitHub Actions
@@ -309,14 +349,16 @@ engineer can:
 
 1. install Code Mower in a clean repo;
 2. understand the local/cloud trust boundary;
-3. run `init --easy` and `doctor --preflight`;
+3. run `init --easy` and `doctor --adoption --repo OWNER/REPO`;
 4. run `lanes status --repo OWNER/REPO` to see active lanes and gate state;
-5. detect and run the repo's native lint/test/build surface instead of assuming
+5. run `board serve --repo OWNER/REPO` when you want the same state in a local
+   browser view;
+6. detect and run the repo's native lint/test/build surface instead of assuming
    every project uses the same tools;
-6. produce a local value report from known PR outcomes;
-7. decide which lanes should stay informational, selective, or merge-gating;
+7. produce a local value report from known PR outcomes;
+8. decide which lanes should stay informational, selective, or merge-gating;
    and
-8. optionally upload sanitized metadata to CodeMower.com and see useful team
+9. optionally upload sanitized metadata to CodeMower.com and see useful team
    dashboard signal.
 
 Build-loop templates extend the same loop from "who reviews best?" to "which AI
@@ -328,8 +370,8 @@ measurement work.
 
 ## Installation Status
 
-The current public beta baseline is `v0.6.0-beta.2`, with pinned package-index
-install spec `code-mower==0.6.0b2`. Release evidence is recorded on the GitHub
+The current package-index beta baseline is `v0.8.0-beta.1`, with pinned package
+install spec `code-mower==0.8.0b1`. Release evidence is recorded on the GitHub
 release and in the first-user install rehearsal. The public repository is
 [codemower-ai/code-mower](https://github.com/codemower-ai/code-mower), and
 GitHub releases remain the auditable source for tags, build artifacts, and
@@ -369,9 +411,11 @@ first so local work exercises the same package entrypoint users install.
 
 ## Docs Map
 
+- [Install And Bootstrap](docs/install.md)
 - [Try Code Mower In 10 Minutes](docs/try-in-10-minutes.md)
 - [Build Loop In 30 Minutes](docs/build-loop-in-30-minutes.md)
 - [Quickstart Reference](docs/quickstart.md)
+- [Orchestrator Prompt Pack](docs/orchestrator-prompt-pack.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)
@@ -389,13 +433,17 @@ first so local work exercises the same package entrypoint users install.
 - [Launch Command Surface](docs/launch-command-surface.md)
 - [v0.6 Truth Baseline](docs/v06-truth-baseline.md)
 - [v0.6 Release Notes](docs/v06-release-notes.md)
+- [v0.8 Release Notes](docs/v08-release-notes.md)
+- [Post-v0.8 Effectiveness Assessment](docs/post-v08-effectiveness-assessment.md)
 - [Demo Calibration Example](examples/demo-calibration/README.md)
+- [Board Demo Rehearsal](examples/board-demo/README.md)
 - [PyPI Release Runbook](docs/pypi-release.md)
 - [Sample Doctor Output](docs/sample-doctor-output.md)
 - [Architecture](docs/architecture.md)
 - [Lane Promotion Policy](docs/lane-promotion-policy.md)
 - [Cloud Sharing](docs/cloud-sharing.md)
 - [Cloud Data Contract](docs/cloud-data-contract.md)
+- [Board Data Contract](docs/board-data-contract.md)
 - [Privacy And Threat Model](docs/privacy-threat-model.md)
 - [Current State And Roadmap](docs/current-state-and-roadmap.md)
 - [Public Release Checklist](docs/public-release-checklist.md)

code_mower-0.6.0b2/PKG-INFO → code_mower-0.8.0b1/README.md

@@ -1,18 +1,3 @@
-Metadata-Version: 2.4
-Name: code-mower
-Version: 0.6.0b2
-Summary: Multi-reviewer AI code audit orchestration
-License-Expression: Apache-2.0
-Requires-Python: >=3.11
-Description-Content-Type: text/markdown
-License-File: LICENSE
-License-File: NOTICE
-Requires-Dist: PyYAML>=6.0
-Provides-Extra: test
-Requires-Dist: pytest>=8.0; extra == "test"
-Requires-Dist: ruff>=0.8; extra == "test"
-Dynamic: license-file
-
 # Code Mower
 
 Code Mower helps teams set up AI peer-programmer and reviewer lanes on real
@@ -57,15 +42,16 @@ Code Mower should feel like an engineering tool, not a demo harness:
 
 ## What It Looks Like
 
-`code-mower doctor --preflight` is the first useful command. It checks your
-runtime, GitHub setup, provider CLIs, token posture, optional cloud setup, and
-private-repo Actions cost traps. `--preflight` is the friendly first-run preset;
-`doctor --v05` remains an equivalent compatibility alias for older scripts.
+`code-mower doctor --adoption --repo OWNER/REPO` is the first useful command
+for a real repository. It checks your runtime, GitHub setup, provider CLIs,
+token posture, optional cloud setup, private-repo Actions cost traps, and
+first-run adoption gaps. `--preflight` remains the compatibility preset for
+older scripts; `--adoption` adds explicit repo targeting and setup guidance.
 
 Example, shortened:
 
 ```text
-$ code-mower doctor --preflight
+$ code-mower doctor --adoption --repo OWNER/REPO
 PASS  config.validate             config validates
 PASS  profile.select              selected profile: codex, claude_audit, gitar
 PASS  runtime.python              Python 3.12 satisfies Code Mower requirements
@@ -87,7 +73,33 @@ See a fuller static transcript: [docs/first-run-transcript.md](docs/first-run-tr
 
 After `init` and `doctor`, use `code-mower lanes status --repo OWNER/REPO` to
 see active builder/reviewer lanes, gate/check state, recent Code Mower
-workflows, local AgentTrail boards when present, and the next operator action.
+workflows, local board/process hints when present, and the next operator
+action. Text and JSON output redact local cwd paths by default; use
+`--show-local-paths` only for local debugging.
+
+For the same redacted metadata in a local browser view, run
+`code-mower board serve --repo OWNER/REPO` and open the printed localhost URL.
+Plain `board serve` is read-only. To build local history while the browser view
+is open, run `code-mower board serve --repo OWNER/REPO --record-events`; it
+records at most one snapshot every 60 seconds by default. To append one snapshot
+without serving the browser view, run
+`code-mower board record --repo OWNER/REPO` from the repository checkout; it
+writes metadata-only snapshots to `.code-mower/board/events.jsonl` with default
+14-day and 500-event retention. `code-mower board events` prints recent stored
+events without calling GitHub. `code-mower board doctor --repo OWNER/REPO`
+checks Board inputs and local history without exposing local paths by default.
+`code-mower board reset --repo OWNER/REPO --yes` clears only the local Board
+history file. The Board also shows an owner queue, and it
+summarizes reviewer verdict history and spend/latency from local board events
+plus `.code-mower/reviewer-spend.json` when those files exist. Local agents can
+publish opt-in status cards by writing metadata-only JSON files to
+`.code-mower/board/agents/*.json`; the Board redacts local paths by default and
+does not upload those cards.
+The local JSON contracts are documented in
+[Board Data Contract](docs/board-data-contract.md).
+When a team wants the same operator picture on CodeMower.com, run
+`code-mower cloud board-snapshot --repo-slug OWNER/REPO --json` to inspect a
+zero-report, metadata-only mirror event, then add `--yes` only after review.
 
 ## See The Value Shape First
 
@@ -95,8 +107,10 @@ If you want to understand the product before installing anything, start with
 the checked-in demo calibration package:
 
 - [examples/demo-calibration/README.md](examples/demo-calibration/README.md)
+- [examples/board-demo/README.md](examples/board-demo/README.md)
 - [examples/demo-calibration/reviewer-value-report.md](examples/demo-calibration/reviewer-value-report.md)
 - [docs/first-user-demo-transcript.md](docs/first-user-demo-transcript.md)
+- [docs/post-v08-effectiveness-assessment.md](docs/post-v08-effectiveness-assessment.md)
 
 The example is intentionally tiny and synthetic: one known-clean control, one
 known-blocked control, and three reviewer lanes. It shows the decision Code
@@ -110,15 +124,21 @@ Cold adopters should start with the reviewer gate, then add builders, then
 measure builder experiments; provider experiments come after that base loop is
 observable.
 
+Install first from the [Install And Bootstrap](docs/install.md) matrix: pipx for
+laptops, uv tool installs for hosted agents or CI boxes, and an editable venv
+for Code Mower contributors. All paths require Python 3.12 or newer.
+
 | 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) |
+| A. Reviewer gate in 10 minutes | You want one audited PR before recurring workflows or builder dispatch. | Install, run `init --easy`, run `doctor --adoption --repo OWNER/REPO`, 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) |
 | C. Builder experiment | You want to compare authoring loops before trusting them broadly. | Use a work order or experiment spec, run `code-mower builder-experiment run` around an explicit command, then review the source-free `authoringRun` artifact and normal audit evidence. | [Builder Experiments](docs/builder-experiments.md) |
 
-The v0.6 beta announcement entry point is the tagged
-[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v0.6.0-beta.2/docs/try-in-10-minutes.md)
-guide.
+The current package-index announcement entry point is the tagged
+[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v0.8.0-beta.1/docs/try-in-10-minutes.md)
+guide. The v0.8 beta includes the completed adoption-polish and native Board
+work, so package-only users can start from the public package rather than a
+source checkout.
 
 ## What Calibration Does And Does Not Prove
 
@@ -147,7 +167,7 @@ Provider-contract baseline for the next release train:
 
 For release verification,
 [First-User Install Rehearsal](docs/first-user-install-rehearsal.md) records
-the package-index procedure for `v0.6.0-beta.2` / `code-mower==0.6.0b2`. The
+the package-index procedure for `v0.8.0-beta.1` / `code-mower==0.8.0b1`. The
 GitHub release records the workflow and rehearsal evidence for the exact tag.
 
 ## Optional: Plan Before Coding
@@ -253,6 +273,9 @@ code-mower cloud dogfood --json
 ```
 
 Nothing uploads unless you pass `--yes`.
+For the hosted Board mirror specifically,
+`code-mower cloud board-snapshot --repo-slug OWNER/REPO --json` exports one
+metadata-only event and zero reports; add `--yes` to upload it after inspection.
 
 Current dogfood uploads, historical catch-up imports, and calibrated
 reviewer/lens evidence are intentionally separate. Imported GitHub Actions
@@ -309,14 +332,16 @@ engineer can:
 
 1. install Code Mower in a clean repo;
 2. understand the local/cloud trust boundary;
-3. run `init --easy` and `doctor --preflight`;
+3. run `init --easy` and `doctor --adoption --repo OWNER/REPO`;
 4. run `lanes status --repo OWNER/REPO` to see active lanes and gate state;
-5. detect and run the repo's native lint/test/build surface instead of assuming
+5. run `board serve --repo OWNER/REPO` when you want the same state in a local
+   browser view;
+6. detect and run the repo's native lint/test/build surface instead of assuming
    every project uses the same tools;
-6. produce a local value report from known PR outcomes;
-7. decide which lanes should stay informational, selective, or merge-gating;
+7. produce a local value report from known PR outcomes;
+8. decide which lanes should stay informational, selective, or merge-gating;
    and
-8. optionally upload sanitized metadata to CodeMower.com and see useful team
+9. optionally upload sanitized metadata to CodeMower.com and see useful team
    dashboard signal.
 
 Build-loop templates extend the same loop from "who reviews best?" to "which AI
@@ -328,8 +353,8 @@ measurement work.
 
 ## Installation Status
 
-The current public beta baseline is `v0.6.0-beta.2`, with pinned package-index
-install spec `code-mower==0.6.0b2`. Release evidence is recorded on the GitHub
+The current package-index beta baseline is `v0.8.0-beta.1`, with pinned package
+install spec `code-mower==0.8.0b1`. Release evidence is recorded on the GitHub
 release and in the first-user install rehearsal. The public repository is
 [codemower-ai/code-mower](https://github.com/codemower-ai/code-mower), and
 GitHub releases remain the auditable source for tags, build artifacts, and
@@ -369,9 +394,11 @@ first so local work exercises the same package entrypoint users install.
 
 ## Docs Map
 
+- [Install And Bootstrap](docs/install.md)
 - [Try Code Mower In 10 Minutes](docs/try-in-10-minutes.md)
 - [Build Loop In 30 Minutes](docs/build-loop-in-30-minutes.md)
 - [Quickstart Reference](docs/quickstart.md)
+- [Orchestrator Prompt Pack](docs/orchestrator-prompt-pack.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)
@@ -389,13 +416,17 @@ first so local work exercises the same package entrypoint users install.
 - [Launch Command Surface](docs/launch-command-surface.md)
 - [v0.6 Truth Baseline](docs/v06-truth-baseline.md)
 - [v0.6 Release Notes](docs/v06-release-notes.md)
+- [v0.8 Release Notes](docs/v08-release-notes.md)
+- [Post-v0.8 Effectiveness Assessment](docs/post-v08-effectiveness-assessment.md)
 - [Demo Calibration Example](examples/demo-calibration/README.md)
+- [Board Demo Rehearsal](examples/board-demo/README.md)
 - [PyPI Release Runbook](docs/pypi-release.md)
 - [Sample Doctor Output](docs/sample-doctor-output.md)
 - [Architecture](docs/architecture.md)
 - [Lane Promotion Policy](docs/lane-promotion-policy.md)
 - [Cloud Sharing](docs/cloud-sharing.md)
 - [Cloud Data Contract](docs/cloud-data-contract.md)
+- [Board Data Contract](docs/board-data-contract.md)
 - [Privacy And Threat Model](docs/privacy-threat-model.md)
 - [Current State And Roadmap](docs/current-state-and-roadmap.md)
 - [Public Release Checklist](docs/public-release-checklist.md)

{code_mower-0.6.0b2 → code_mower-0.8.0b1}/pyproject.toml

@@ -4,17 +4,19 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "code-mower"
-version = "0.6.0b2"
+version = "0.8.0b1"
 description = "Multi-reviewer AI code audit orchestration"
-requires-python = ">=3.11"
+requires-python = ">=3.12"
 readme = "README.md"
 license = "Apache-2.0"
 dependencies = ["PyYAML>=6.0"]
 
 [project.optional-dependencies]
 test = [
+    "build>=1.2",
     "pytest>=8.0",
     "ruff>=0.8",
+    "twine>=5.0",
 ]
 
 [project.scripts]
@@ -43,7 +45,7 @@ code_mower = [
 ]
 
 [tool.ruff]
-target-version = "py311"
+target-version = "py312"
 line-length = 100
 
 [tool.ruff.lint]

{code_mower-0.6.0b2 → code_mower-0.8.0b1}/src/code_mower/__init__.py

@@ -1,3 +1,3 @@
 """Code Mower package."""
 
-__version__ = "0.6.0b2"
+__version__ = "0.8.0b1"