code-mower 0.5.0b31__tar.gz → 0.5.0b32__tar.gz

{code_mower-0.5.0b31 → code_mower-0.5.0b32}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-mower
-Version: 0.5.0b31
+Version: 0.5.0b32
 Summary: Multi-reviewer AI code audit orchestration
 License-Expression: Apache-2.0
 Requires-Python: >=3.11
@@ -103,11 +103,11 @@ 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.0b31
+pipx install --python python3.12 code-mower==0.5.0b32
 code-mower --version
 ```
 
-`0.5.0b31` is a beta release. Until Code Mower publishes a stable `1.0`
+`0.5.0b32` is a beta release. Until Code Mower publishes a stable `1.0`
 line, use the explicit beta version above or allow prereleases with:
 
 ```bash
@@ -150,7 +150,7 @@ First-time command map: [docs/launch-command-surface.md](docs/launch-command-sur
 
 The current PyPI beta has been rehearsed end-to-end from a clean install:
 [First-User Install Rehearsal](docs/first-user-install-rehearsal.md) records
-the latest 10/10 public-package readiness proof for `code-mower==0.5.0b31`.
+the latest 10/10 public-package readiness proof for `code-mower==0.5.0b32`.
 
 ## Optional: Plan Before Coding
 
@@ -160,19 +160,33 @@ surface, then keep pull requests focused on code review and merge readiness:
 ```bash
 code-mower project-context init --project-name "My Product"
 code-mower context add --external ~/Downloads/product-requirements.md
-code-mower plan from-issue \
-  --repo OWNER/REPO \
-  --title "Add billing settings" \
-  --body-file issue-body.md \
+code-mower plan from-github-issue OWNER/REPO#123 \
   --output .code-mower/work-orders/billing-settings-plan.md
 code-mower work-order draft \
   --issue-plan .code-mower/work-orders/billing-settings-plan.md \
   --output .code-mower/work-orders/billing-settings.md
 ```
 
-The work-order path is local-only by default. External docs are recorded as
-metadata manifests unless you explicitly ask for bounded previews. See
-[docs/planning-work-orders.md](docs/planning-work-orders.md).
+The GitHub issue remains the source of truth. The local plan and work order are
+derived working artifacts, and `work-order draft` also writes a metadata-only
+`*.cloud-event.json` sidecar that can tie later builder/reviewer evidence back
+to the issue on CodeMower.com. That sidecar excludes source, raw diffs, raw
+transcripts, stdout/stderr, auth output, secrets, and issue body text. External
+docs are recorded as metadata manifests unless you explicitly ask for bounded
+previews. See [docs/planning-work-orders.md](docs/planning-work-orders.md).
+
+After a PR exists, attach source-free delivery metadata to the same sidecar:
+
+```bash
+code-mower work-order attach-delivery \
+  .code-mower/work-orders/billing-settings.cloud-event.json \
+  --pr OWNER/REPO#124 \
+  --from-github
+```
+
+That lets CodeMower.com show `issue -> plan -> work order -> PR -> reviewer
+checks -> merge` lineage without receiving source, diffs, transcripts, or issue
+body text.
 
 ## Why Not Just Run Codex Or Claude Yourself?
 
@@ -277,9 +291,9 @@ best?" to "which AI builder plus reviewer loop ships best on this product?" See
 
 ## Installation Status
 
-The current public beta is `v0.5.0-beta.31` from
+The current public beta is `v0.5.0-beta.32` from
 [codemower-ai/code-mower](https://github.com/codemower-ai/code-mower), published
-as `code-mower==0.5.0b31` on [PyPI](https://pypi.org/project/code-mower/).
+as `code-mower==0.5.0b32` on [PyPI](https://pypi.org/project/code-mower/).
 GitHub releases remain the auditable source for tags, build artifacts, and
 release notes.
 

{code_mower-0.5.0b31 → code_mower-0.5.0b32}/README.md

@@ -88,11 +88,11 @@ 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.0b31
+pipx install --python python3.12 code-mower==0.5.0b32
 code-mower --version
 ```
 
-`0.5.0b31` is a beta release. Until Code Mower publishes a stable `1.0`
+`0.5.0b32` is a beta release. Until Code Mower publishes a stable `1.0`
 line, use the explicit beta version above or allow prereleases with:
 
 ```bash
@@ -135,7 +135,7 @@ First-time command map: [docs/launch-command-surface.md](docs/launch-command-sur
 
 The current PyPI beta has been rehearsed end-to-end from a clean install:
 [First-User Install Rehearsal](docs/first-user-install-rehearsal.md) records
-the latest 10/10 public-package readiness proof for `code-mower==0.5.0b31`.
+the latest 10/10 public-package readiness proof for `code-mower==0.5.0b32`.
 
 ## Optional: Plan Before Coding
 
@@ -145,19 +145,33 @@ surface, then keep pull requests focused on code review and merge readiness:
 ```bash
 code-mower project-context init --project-name "My Product"
 code-mower context add --external ~/Downloads/product-requirements.md
-code-mower plan from-issue \
-  --repo OWNER/REPO \
-  --title "Add billing settings" \
-  --body-file issue-body.md \
+code-mower plan from-github-issue OWNER/REPO#123 \
   --output .code-mower/work-orders/billing-settings-plan.md
 code-mower work-order draft \
   --issue-plan .code-mower/work-orders/billing-settings-plan.md \
   --output .code-mower/work-orders/billing-settings.md
 ```
 
-The work-order path is local-only by default. External docs are recorded as
-metadata manifests unless you explicitly ask for bounded previews. See
-[docs/planning-work-orders.md](docs/planning-work-orders.md).
+The GitHub issue remains the source of truth. The local plan and work order are
+derived working artifacts, and `work-order draft` also writes a metadata-only
+`*.cloud-event.json` sidecar that can tie later builder/reviewer evidence back
+to the issue on CodeMower.com. That sidecar excludes source, raw diffs, raw
+transcripts, stdout/stderr, auth output, secrets, and issue body text. External
+docs are recorded as metadata manifests unless you explicitly ask for bounded
+previews. See [docs/planning-work-orders.md](docs/planning-work-orders.md).
+
+After a PR exists, attach source-free delivery metadata to the same sidecar:
+
+```bash
+code-mower work-order attach-delivery \
+  .code-mower/work-orders/billing-settings.cloud-event.json \
+  --pr OWNER/REPO#124 \
+  --from-github
+```
+
+That lets CodeMower.com show `issue -> plan -> work order -> PR -> reviewer
+checks -> merge` lineage without receiving source, diffs, transcripts, or issue
+body text.
 
 ## Why Not Just Run Codex Or Claude Yourself?
 
@@ -262,9 +276,9 @@ best?" to "which AI builder plus reviewer loop ships best on this product?" See
 
 ## Installation Status
 
-The current public beta is `v0.5.0-beta.31` from
+The current public beta is `v0.5.0-beta.32` from
 [codemower-ai/code-mower](https://github.com/codemower-ai/code-mower), published
-as `code-mower==0.5.0b31` on [PyPI](https://pypi.org/project/code-mower/).
+as `code-mower==0.5.0b32` on [PyPI](https://pypi.org/project/code-mower/).
 GitHub releases remain the auditable source for tags, build artifacts, and
 release notes.
 

{code_mower-0.5.0b31 → code_mower-0.5.0b32}/pyproject.toml

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

{code_mower-0.5.0b31 → code_mower-0.5.0b32}/src/code_mower/__init__.py

@@ -1,3 +1,3 @@
 """Code Mower package."""
 
-__version__ = "0.5.0b31"
+__version__ = "0.5.0b32"

{code_mower-0.5.0b31 → code_mower-0.5.0b32}/src/code_mower/cli.py

@@ -14,7 +14,7 @@ from pathlib import Path
 if __package__ in {None, ""}:
     raise SystemExit(
         "code_mower.cli is a packaged entrypoint. Install Code Mower with "
-        "`pipx install code-mower==0.5.0b31`, or run source checkouts with "
+        "`pipx install code-mower==0.5.0b32`, or run source checkouts with "
         "`PYTHONPATH=src python -m code_mower.cli`."
     )
 

{code_mower-0.5.0b31 → code_mower-0.5.0b32}/src/code_mower/cloud_client/bundle.py

@@ -28,6 +28,7 @@ SAFE_EVENT_TYPES = {
     "provider_catalog_snapshot",
     "reviewer_run",
     "value_report_snapshot",
+    "work_order",
     "workflow_run",
 }
 EXCLUDED_CONTENT = (