code-mower 1.1.0__tar.gz → 1.1.1__tar.gz

{code_mower-1.1.0 → code_mower-1.1.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-mower
-Version: 1.1.0
+Version: 1.1.1
 Summary: Multi-reviewer AI code audit orchestration
 License-Expression: Apache-2.0
 Project-URL: Homepage, https://github.com/codemower-ai/code-mower
@@ -245,7 +245,7 @@ agent report its actual host posture, exact installed version, doctor result,
 Board URL, and any owner-only click-list before it mutates the repo.
 
 The current package-index announcement entry point is the tagged
-[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v1.1.0/docs/try-in-10-minutes.md)
+[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v1.1.1/docs/try-in-10-minutes.md)
 guide. The v1.0 supervised-pilot release includes the native Board, the
 controller dry-run and policy contract, adoption and upgrade hardening from
 recent install rehearsals, package-index release checks, provider-diversity
@@ -348,7 +348,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 `v1.1.0` / `code-mower==1.1.0`. The
+the package-index procedure for `v1.1.1` / `code-mower==1.1.1`. The
 GitHub release records the workflow and rehearsal evidence for the exact tag.
 After publication, [Release Qualification](docs/release-qualification.md)
 coordinates provider-specific install and operational checks without treating
@@ -542,8 +542,8 @@ measurement work.
 
 ## Installation Status
 
-The current package-index release baseline is `v1.1.0`, with pinned package
-install spec `code-mower==1.1.0`. Release evidence is recorded on the GitHub
+The current package-index release baseline is `v1.1.1`, with pinned package
+install spec `code-mower==1.1.1`. 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
@@ -629,6 +629,7 @@ first so local work exercises the same package entrypoint users install.
 - [v1.0.13 Release Notes](docs/v1013-release-notes.md)
 - [v1.0.14 Release Notes](docs/v1014-release-notes.md)
 - [v1.0.15 Release Notes](docs/v1015-release-notes.md)
+- [v1.1.1 Release Notes](docs/v111-release-notes.md)
 - [v1.1 Release Notes](docs/v11-release-notes.md)
 - [Post-v0.8 Effectiveness Assessment](docs/post-v08-effectiveness-assessment.md)
 - [v1.0.1 Effectiveness Assessment](docs/v101-effectiveness-assessment.md)

{code_mower-1.1.0 → code_mower-1.1.1}/README.md

@@ -215,7 +215,7 @@ agent report its actual host posture, exact installed version, doctor result,
 Board URL, and any owner-only click-list before it mutates the repo.
 
 The current package-index announcement entry point is the tagged
-[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v1.1.0/docs/try-in-10-minutes.md)
+[Try Code Mower In 10 Minutes](https://github.com/codemower-ai/code-mower/blob/v1.1.1/docs/try-in-10-minutes.md)
 guide. The v1.0 supervised-pilot release includes the native Board, the
 controller dry-run and policy contract, adoption and upgrade hardening from
 recent install rehearsals, package-index release checks, provider-diversity
@@ -318,7 +318,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 `v1.1.0` / `code-mower==1.1.0`. The
+the package-index procedure for `v1.1.1` / `code-mower==1.1.1`. The
 GitHub release records the workflow and rehearsal evidence for the exact tag.
 After publication, [Release Qualification](docs/release-qualification.md)
 coordinates provider-specific install and operational checks without treating
@@ -512,8 +512,8 @@ measurement work.
 
 ## Installation Status
 
-The current package-index release baseline is `v1.1.0`, with pinned package
-install spec `code-mower==1.1.0`. Release evidence is recorded on the GitHub
+The current package-index release baseline is `v1.1.1`, with pinned package
+install spec `code-mower==1.1.1`. 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
@@ -599,6 +599,7 @@ first so local work exercises the same package entrypoint users install.
 - [v1.0.13 Release Notes](docs/v1013-release-notes.md)
 - [v1.0.14 Release Notes](docs/v1014-release-notes.md)
 - [v1.0.15 Release Notes](docs/v1015-release-notes.md)
+- [v1.1.1 Release Notes](docs/v111-release-notes.md)
 - [v1.1 Release Notes](docs/v11-release-notes.md)
 - [Post-v0.8 Effectiveness Assessment](docs/post-v08-effectiveness-assessment.md)
 - [v1.0.1 Effectiveness Assessment](docs/v101-effectiveness-assessment.md)

{code_mower-1.1.0 → code_mower-1.1.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "code-mower"
-version = "1.1.0"
+version = "1.1.1"
 description = "Multi-reviewer AI code audit orchestration"
 requires-python = ">=3.12"
 readme = "README.md"

{code_mower-1.1.0 → code_mower-1.1.1}/src/code_mower/__init__.py

@@ -1,3 +1,3 @@
 """Code Mower package."""
 
-__version__ = "1.1.0"
+__version__ = "1.1.1"

{code_mower-1.1.0 → code_mower-1.1.1}/src/code_mower/campaign_adapters.py

@@ -604,8 +604,20 @@ def build_qualification_prompt(
             else "runtime_class is python_<major>.<minor>; provider and"
         ),
         "executor are lowercase safe identifiers; steps is a non-empty list of",
-        "{id, status, elapsed_seconds, warning_count, owner_action_count} with",
-        "id one of board, doctor, lanes_status, overhead, package_install or a namespaced",
+        "{id, status, elapsed_seconds, warning_count, owner_action_count} with an",
+        "optional failure_reason on a failed package_install step and nowhere else.",
+        "A failed package_install step must carry exactly one failure_reason:",
+        "network for connection or TLS failures (connection refused, timeout,",
+        "DNS, SSL or certificate validation), package_index for a missing version",
+        "or 404 from the package index, runtime for Python or dependency",
+        "incompatibility (unsupported Python version, missing module, conflicting",
+        "dependencies), sandbox_permission for permission, disk, or sandbox",
+        "denials (permission denied, disk full, read-only filesystem). Use",
+        "unknown only for a command that was actually attempted and cannot be",
+        "classified from local diagnostics. Report only the closed reason word;",
+        "never include raw output, logs, paths, commands, source, diffs,",
+        "transcripts, or secrets. Step id is",
+        "one of board, doctor, lanes_status, overhead, package_install or a namespaced",
         "<namespace>__<name> provider extension (both halves lowercase safe",
         "identifiers); any other id is rejected. Status is one of",
         "pass, fail, warn, unavailable, planned. A step with a",

{code_mower-1.1.0 → code_mower-1.1.1}/src/code_mower/doctor_checks/adoption.py

@@ -599,6 +599,7 @@ def check_adoption_campaign_readiness(
     which_fn: Callable[[str], str | None] = shutil.which,
     command_runner: Any = None,
     auth_probe_runner: Any = None,
+    gh_auth_probe: Any = None,
     capability_runner: Any = None,
     token_dir: Path | None = None,
     providers: Sequence[str] = DEFAULT_CAMPAIGN_PROVIDERS,
@@ -606,7 +607,14 @@ def check_adoption_campaign_readiness(
     provider_profile: str = "",
     provider_config_dir: Path | None = None,
 ) -> tuple[DoctorCheck, ...]:
-    """Validate release campaign readiness across configured providers and storage."""
+    """Validate release campaign readiness across configured providers and storage.
+
+    ``gh_auth_probe`` is the optional zero-argument GitHub credential probe the
+    campaign command uses (``release_campaigns.AuthProbe``). Supplied, a
+    GitHub-comment hosted lane with no token variable exported is credentialed
+    when `gh` is already authenticated, so this report and an actual dispatch
+    reach the same verdict; omitted, the verdict is environment-only.
+    """
     from code_mower import lane_status
     from code_mower.campaign_adapters import (
         check_antigravity_readiness,
@@ -959,6 +967,7 @@ def check_adoption_campaign_readiness(
                     credential_file=provider_credential_file,
                     profile=provider_profile,
                     config_dir=provider_config_dir,
+                    auth_probe=gh_auth_probe,
                 )
                 effective_env = current_env
 
@@ -980,6 +989,7 @@ def check_adoption_campaign_readiness(
                 credential_file=provider_credential_file,
                 profile=provider_profile,
                 config_dir=provider_config_dir,
+                auth_probe=gh_auth_probe,
             )
             dispatch_blockers = hosted_dispatch_blockers(dispatch_profile)
             dispatch_summary = {

{code_mower-1.1.0 → code_mower-1.1.1}/src/code_mower/doctor_checks/runner.py

@@ -277,6 +277,8 @@ def run_doctor(
     )
 
     if adoption:
+        from code_mower import release_campaigns
+
         checks.extend(
             check_adoption_campaign_readiness(
                 config=config,
@@ -286,6 +288,11 @@ def run_doctor(
                 provider_credential_file=provider_credential_file,
                 provider_profile=provider_profile,
                 provider_config_dir=provider_config_dir,
+                # Report the same credential verdict the campaign command
+                # reaches: a GitHub-comment hosted lane dispatches through `gh`,
+                # so an authenticated CLI is credentials even with no token
+                # variable exported. Doctor and dispatch must not disagree.
+                gh_auth_probe=release_campaigns.run_gh_auth_probe,
             )
         )