code-mower 0.5.0b53__tar.gz → 0.6.0b2__tar.gz

{code_mower-0.5.0b53 → code_mower-0.6.0b2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-mower
-Version: 0.5.0b53
+Version: 0.6.0b2
 Summary: Multi-reviewer AI code audit orchestration
 License-Expression: Apache-2.0
 Requires-Python: >=3.11
@@ -59,9 +59,8 @@ Code Mower should feel like an engineering tool, not a demo harness:
 
 `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 name for the
-versioned v0.5 first-run preset, so `doctor --v05` remains equivalent for
-scripts.
+private-repo Actions cost traps. `--preflight` is the friendly first-run preset;
+`doctor --v05` remains an equivalent compatibility alias for older scripts.
 
 Example, shortened:
 
@@ -86,6 +85,10 @@ boundaries visible before you promote any reviewer lane.
 
 See a fuller static transcript: [docs/first-run-transcript.md](docs/first-run-transcript.md).
 
+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.
+
 ## See The Value Shape First
 
 If you want to understand the product before installing anything, start with
@@ -103,14 +106,18 @@ fast, or eligible for stronger merge policy on your actual codebase.
 ## Start Here
 
 Choose one path. Each path has one guide and gets to one visible outcome.
+Cold adopters should start with the reviewer gate, then add builders, then
+measure builder experiments; provider experiments come after that base loop is
+observable.
 
 | 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) |
+| 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 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)
+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.
 
 ## What Calibration Does And Does Not Prove
@@ -135,13 +142,13 @@ 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).
+Provider-contract baseline for the next release train:
+[docs/v06-truth-baseline.md](docs/v06-truth-baseline.md).
 
-The beta.53 package-index release is prepared:
+For release verification,
 [First-User Install Rehearsal](docs/first-user-install-rehearsal.md) records
-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`.
+the package-index procedure for `v0.6.0-beta.2` / `code-mower==0.6.0b2`. The
+GitHub release records the workflow and rehearsal evidence for the exact tag.
 
 ## Optional: Plan Before Coding
 
@@ -200,6 +207,11 @@ 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.
 
+The reference adoption shape is Claude Code as orchestrator; Claude Code,
+Codex, and Cursor as builder lanes; Claude Code and Codex as reviewer lanes;
+and Gitar or Antigravity as informational reviewer signal until local
+calibration says otherwise.
+
 ## Why Not Just Run Codex Or Claude Yourself?
 
 You should, at first. Code Mower is not a replacement for a good local agent or
@@ -260,6 +272,12 @@ code-mower cloud setup \
   --out ~/.config/code-mower/tokens/your-laptop.env
 ```
 
+`cloud setup` stores a private `0600` token env file and records it as the
+current local cloud profile. Future `cloud doctor`, `cloud upload`, `cloud
+dogfood`, `cloud reviewer-runs`, and `cloud repo-sync` commands can load that
+profile automatically; pass `--install-id` or `--token-file` when a machine has
+multiple stored profiles.
+
 Cloud sharing details, historical catch-up, and repo-sync commands live in
 [docs/cloud-sharing.md](docs/cloud-sharing.md).
 
@@ -277,6 +295,10 @@ Everything else starts manual or informational until your own calibration data
 proves it is useful: Antigravity/Gemini, Hermes, CodeRabbit CLI, Cursor BugBot,
 Qodo, Greptile, Devin, local LLMs, and future ACP bridges.
 
+Gemini CLI and Antigravity are distinct lane ids even though both are Google
+surfaces and may use Gemini model infrastructure. Keep their auth, model
+provenance, calibration evidence, and release notes separate.
+
 Provider details: [docs/provider-matrix.md](docs/provider-matrix.md).
 Setup/auth fixes: [docs/troubleshooting.md](docs/troubleshooting.md).
 
@@ -288,12 +310,13 @@ engineer can:
 1. install Code Mower in a clean repo;
 2. understand the local/cloud trust boundary;
 3. run `init --easy` and `doctor --preflight`;
-4. detect and run the repo's native lint/test/build surface instead of assuming
+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
    every project uses the same tools;
-5. produce a local value report from known PR outcomes;
-6. decide which lanes should stay informational, selective, or merge-gating;
+6. produce a local value report from known PR outcomes;
+7. decide which lanes should stay informational, selective, or merge-gating;
    and
-7. optionally upload sanitized metadata to CodeMower.com and see useful team
+8. 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
@@ -305,11 +328,10 @@ measurement work.
 
 ## Installation Status
 
-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`.
+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
+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
 release notes.
 
@@ -322,6 +344,8 @@ scripts/dev-python -m venv .venv
 ```
 
 The wrapper resolves Python 3.12+ and refuses stale or old system Python shims.
+Do not run the CLI by hand-wiring source import paths; install the editable venv
+first so local work exercises the same package entrypoint users install.
 
 ## Known Limitations
 
@@ -363,6 +387,8 @@ The wrapper resolves Python 3.12+ and refuses stale or old system Python shims.
 - [First-User Demo Transcript](docs/first-user-demo-transcript.md)
 - [First-User Install Rehearsal](docs/first-user-install-rehearsal.md)
 - [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)
 - [Demo Calibration Example](examples/demo-calibration/README.md)
 - [PyPI Release Runbook](docs/pypi-release.md)
 - [Sample Doctor Output](docs/sample-doctor-output.md)

{code_mower-0.5.0b53 → code_mower-0.6.0b2}/README.md

@@ -44,9 +44,8 @@ Code Mower should feel like an engineering tool, not a demo harness:
 
 `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 name for the
-versioned v0.5 first-run preset, so `doctor --v05` remains equivalent for
-scripts.
+private-repo Actions cost traps. `--preflight` is the friendly first-run preset;
+`doctor --v05` remains an equivalent compatibility alias for older scripts.
 
 Example, shortened:
 
@@ -71,6 +70,10 @@ boundaries visible before you promote any reviewer lane.
 
 See a fuller static transcript: [docs/first-run-transcript.md](docs/first-run-transcript.md).
 
+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.
+
 ## See The Value Shape First
 
 If you want to understand the product before installing anything, start with
@@ -88,14 +91,18 @@ fast, or eligible for stronger merge policy on your actual codebase.
 ## Start Here
 
 Choose one path. Each path has one guide and gets to one visible outcome.
+Cold adopters should start with the reviewer gate, then add builders, then
+measure builder experiments; provider experiments come after that base loop is
+observable.
 
 | 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) |
+| 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 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)
+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.
 
 ## What Calibration Does And Does Not Prove
@@ -120,13 +127,13 @@ 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).
+Provider-contract baseline for the next release train:
+[docs/v06-truth-baseline.md](docs/v06-truth-baseline.md).
 
-The beta.53 package-index release is prepared:
+For release verification,
 [First-User Install Rehearsal](docs/first-user-install-rehearsal.md) records
-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`.
+the package-index procedure for `v0.6.0-beta.2` / `code-mower==0.6.0b2`. The
+GitHub release records the workflow and rehearsal evidence for the exact tag.
 
 ## Optional: Plan Before Coding
 
@@ -185,6 +192,11 @@ 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.
 
+The reference adoption shape is Claude Code as orchestrator; Claude Code,
+Codex, and Cursor as builder lanes; Claude Code and Codex as reviewer lanes;
+and Gitar or Antigravity as informational reviewer signal until local
+calibration says otherwise.
+
 ## Why Not Just Run Codex Or Claude Yourself?
 
 You should, at first. Code Mower is not a replacement for a good local agent or
@@ -245,6 +257,12 @@ code-mower cloud setup \
   --out ~/.config/code-mower/tokens/your-laptop.env
 ```
 
+`cloud setup` stores a private `0600` token env file and records it as the
+current local cloud profile. Future `cloud doctor`, `cloud upload`, `cloud
+dogfood`, `cloud reviewer-runs`, and `cloud repo-sync` commands can load that
+profile automatically; pass `--install-id` or `--token-file` when a machine has
+multiple stored profiles.
+
 Cloud sharing details, historical catch-up, and repo-sync commands live in
 [docs/cloud-sharing.md](docs/cloud-sharing.md).
 
@@ -262,6 +280,10 @@ Everything else starts manual or informational until your own calibration data
 proves it is useful: Antigravity/Gemini, Hermes, CodeRabbit CLI, Cursor BugBot,
 Qodo, Greptile, Devin, local LLMs, and future ACP bridges.
 
+Gemini CLI and Antigravity are distinct lane ids even though both are Google
+surfaces and may use Gemini model infrastructure. Keep their auth, model
+provenance, calibration evidence, and release notes separate.
+
 Provider details: [docs/provider-matrix.md](docs/provider-matrix.md).
 Setup/auth fixes: [docs/troubleshooting.md](docs/troubleshooting.md).
 
@@ -273,12 +295,13 @@ engineer can:
 1. install Code Mower in a clean repo;
 2. understand the local/cloud trust boundary;
 3. run `init --easy` and `doctor --preflight`;
-4. detect and run the repo's native lint/test/build surface instead of assuming
+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
    every project uses the same tools;
-5. produce a local value report from known PR outcomes;
-6. decide which lanes should stay informational, selective, or merge-gating;
+6. produce a local value report from known PR outcomes;
+7. decide which lanes should stay informational, selective, or merge-gating;
    and
-7. optionally upload sanitized metadata to CodeMower.com and see useful team
+8. 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
@@ -290,11 +313,10 @@ measurement work.
 
 ## Installation Status
 
-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`.
+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
+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
 release notes.
 
@@ -307,6 +329,8 @@ scripts/dev-python -m venv .venv
 ```
 
 The wrapper resolves Python 3.12+ and refuses stale or old system Python shims.
+Do not run the CLI by hand-wiring source import paths; install the editable venv
+first so local work exercises the same package entrypoint users install.
 
 ## Known Limitations
 
@@ -348,6 +372,8 @@ The wrapper resolves Python 3.12+ and refuses stale or old system Python shims.
 - [First-User Demo Transcript](docs/first-user-demo-transcript.md)
 - [First-User Install Rehearsal](docs/first-user-install-rehearsal.md)
 - [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)
 - [Demo Calibration Example](examples/demo-calibration/README.md)
 - [PyPI Release Runbook](docs/pypi-release.md)
 - [Sample Doctor Output](docs/sample-doctor-output.md)

{code_mower-0.5.0b53 → code_mower-0.6.0b2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "code-mower"
-version = "0.5.0b53"
+version = "0.6.0b2"
 description = "Multi-reviewer AI code audit orchestration"
 requires-python = ">=3.11"
 readme = "README.md"
@@ -47,8 +47,13 @@ target-version = "py311"
 line-length = 100
 
 [tool.ruff.lint]
-select = ["E", "F"]
-ignore = ["E501"]
+select = ["E", "F", "W", "B"]
+ignore = [
+    "E501",
+    # LaneConfig instances are finite config objects; keep the callable helper
+    # shape stable instead of churning call sites for cached_property.
+    "B019",
+]
 
 [tool.ruff.lint.per-file-ignores]
 "tests/*.py" = ["E402"]

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

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

code_mower-0.6.0b2/src/code_mower/antigravity_sdk_probe.py

@@ -0,0 +1,129 @@
+"""Optional Antigravity SDK probe helpers."""
+
+from __future__ import annotations
+
+import importlib
+import importlib.util
+from importlib import metadata
+from typing import Any
+
+PACKAGE_NAME = "google-antigravity"
+IMPORT_NAME = "google.antigravity"
+EXPECTED_EXPORTS = (
+    "Agent",
+    "LocalAgentConfig",
+    "CapabilitiesConfig",
+    "UsageMetadata",
+    "GeminiAPIEndpoint",
+    "VertexEndpoint",
+)
+LOCAL_HARNESS_PATH = "google/antigravity/bin/localharness"
+
+
+def _dependency_name(requirement: str) -> str:
+    text = requirement.split(";", 1)[0].strip()
+    for separator in ("<", ">", "=", "!", "~", " "):
+        if separator in text:
+            text = text.split(separator, 1)[0].strip()
+    return text
+
+
+def _dependency_names(requirements: list[str] | None) -> tuple[list[str], list[str]]:
+    required: set[str] = set()
+    optional: set[str] = set()
+    for requirement in requirements or []:
+        name = _dependency_name(requirement)
+        if not name:
+            continue
+        if "extra ==" in requirement:
+            optional.add(name)
+        else:
+            required.add(name)
+    return sorted(required), sorted(optional)
+
+
+def _distribution_details(package_name: str) -> dict[str, Any]:
+    try:
+        distribution = metadata.distribution(package_name)
+    except metadata.PackageNotFoundError:
+        return {
+            "installed": False,
+            "package_version": "",
+            "dependencies": [],
+            "optional_dependencies": [],
+            "has_local_harness_binary": False,
+        }
+    files = distribution.files or []
+    dependencies, optional_dependencies = _dependency_names(distribution.requires)
+    return {
+        "installed": True,
+        "package_version": metadata.version(package_name),
+        "dependencies": dependencies,
+        "optional_dependencies": optional_dependencies,
+        "has_local_harness_binary": any(
+            str(path).replace("\\", "/") == LOCAL_HARNESS_PATH for path in files
+        ),
+    }
+
+
+def _is_importable(import_name: str) -> bool:
+    try:
+        return importlib.util.find_spec(import_name) is not None
+    except (ImportError, ValueError):
+        return False
+
+
+def probe_antigravity_sdk(*, import_api: bool = False) -> dict[str, Any]:
+    """Return metadata-only facts about the optional Antigravity SDK surface."""
+
+    details = _distribution_details(PACKAGE_NAME)
+    importable = _is_importable(IMPORT_NAME)
+    report: dict[str, Any] = {
+        "mode": "antigravity-sdk-probe",
+        "package": PACKAGE_NAME,
+        "import_name": IMPORT_NAME,
+        "installed": details["installed"],
+        "package_version": details["package_version"],
+        "dependencies": details["dependencies"],
+        "optional_dependencies": details["optional_dependencies"],
+        "has_local_harness_binary": details["has_local_harness_binary"],
+        "importable": importable,
+        "import_api": import_api,
+        "api_exports": {},
+        "research_posture": "optional_research",
+        "privacy": {
+            "model_call": False,
+            "auth_probe": False,
+            "source_or_diff": False,
+            "raw_output": False,
+        },
+    }
+    if import_api and importable:
+        module = importlib.import_module(IMPORT_NAME)
+        report["api_exports"] = {
+            name: hasattr(module, name) for name in EXPECTED_EXPORTS
+        }
+
+    missing_exports = [
+        name for name, present in report["api_exports"].items() if not present
+    ]
+    if not report["installed"]:
+        report["status"] = "warn"
+        report["message"] = (
+            "optional Antigravity SDK package is not installed; install "
+            "google-antigravity in a disposable venv before SDK lane research"
+        )
+    elif not report["importable"]:
+        report["status"] = "warn"
+        report["message"] = "optional Antigravity SDK package is installed but not importable"
+    elif import_api and missing_exports:
+        report["status"] = "warn"
+        report["message"] = (
+            "optional Antigravity SDK import succeeded but expected API exports "
+            "are missing"
+        )
+        report["missing_exports"] = missing_exports
+    else:
+        report["status"] = "pass"
+        report["message"] = "optional Antigravity SDK probe completed without model calls"
+    return report

{code_mower-0.5.0b53 → code_mower-0.6.0b2}/src/code_mower/bootstrap.py

@@ -235,7 +235,7 @@ def _acquire_venv_lock(
                 raise RuntimeError(
                     "timed out waiting for Code Mower venv lock: "
                     f"{lock_dir}"
-                )
+                ) from None
             time.sleep(poll_seconds)
             continue
         owner_id = f"{os.getpid()}-{uuid.uuid4().hex}"