chore: release 0.8.1

[steipete]

Prepare clawpatch 0.8.1 by updating the package version and finalizing the September 13 changelog. The patch fixes nested-project repair scoping, retains provider edits after failed patch attempts, and includes the doctor, deadline, provider-validation, tooling, and documentation fixes already on main.

A Node 24 CI run also exposed a fixture teardown race: removing a temporary Git repository returned ENOTEMPTY for .git/objects/pack. Shared fixture cleanup now uses three bounded filesystem retries; persistent errors still fail the test. This changes test cleanup only.

The release will use the existing signed-tag workflow and npm trusted publishing after CI passes on the merged release commit. Independent review of the complete candidate found no actionable P0–P2 findings.

Validation: the initial local gate passed frozen install, typecheck, lint, formatting, all 957 tests (two platform skips) with coverage, build, package-content checks, packaged CLI smoke (13 features, including three CUDA), and website smoke. The full local gate passed again with the cleanup fix: 957 tests passed, two platform skips, 89.45% line coverage, build, package smoke, and website smoke. All GitHub checks passed on fd0fd10, including Node 22/24/26, Windows, CodeQL, dependency review, and secret scanning.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

[clawsweeper]

Codex review: needs real behavior proof before merge. Reviewed September 13, 2026, 9:39 PM ET / September 14, 2026, 01:39 UTC (Revision 2).

ClawSweeper review

What this changes

Prepares version 0.8.1 with dated release notes and adds three bounded retries when removing temporary test repositories.

Merge readiness

⛔ Blocked before merge - 2 items remain

The release preparation remains necessary: current main and the latest release still identify 0.8.0. No actionable patch defect was found, but the previously requested packaged-version proof remains outstanding.

Priority: P3
Reviewed head: fd0fd10b6edc5f2c7436b396e660111bfeb93012

Review scores

Measure	Result	What it means
Overall readiness	🦪 silver shellfish (2/6)	The patch is focused and has no blocking correctness finding; observable packaged-version evidence remains thin.
Proof confidence	🦪 silver shellfish (2/6)	Needs stronger real behavior proof before merge: The body now reports a successful installed-package mapping smoke, which is useful progress, but provides no captured result showing the packaged CLI's changed version output is 0.8.1. The earlier request for that narrow release proof remains unresolved. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Needs proof	Needs stronger real behavior proof before merge: The body now reports a successful installed-package mapping smoke, which is useful progress, but provides no captured result showing the packaged CLI's changed version output is 0.8.1. The earlier request for that narrow release proof remains unresolved. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Evidence reviewed	7 items	Verified introduced scope: The complete pinned base-to-head delta contains only CHANGELOG.md, the package version, and fixture cleanup: 9 additions and 6 deletions. The supplied verified test merge has the pinned main and PR head as its parents. Current main still needs the version bump: The pinned main package identifies version 0.8.0; this release metadata change is not already implemented there. Published release check: GitHub reports v0.8.0 as the latest release, published September 7, 2026.
Findings	None	None.
Security	None	None.

How this fits together

Clawpatch packages its code-review CLI for npm; package metadata supplies the CLI version and is checked against the release tag before publishing. Shared test fixtures create temporary repositories and remove them after each test.

flowchart TD
  A[Package version] --> B[CLI version output]
  A --> C[Release metadata checks]
  D[Dated changelog] --> C
  C --> E[npm release]
  F[Temporary test repositories] --> G[Cleanup with bounded retries]

Loading

Before merge

• Add real behavior proof - Needs stronger real behavior proof before merge: The body now reports a successful installed-package mapping smoke, which is useful progress, but provides no captured result showing the packaged CLI's changed version output is 0.8.1. The earlier request for that narrow release proof remains unresolved. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
• Complete next step (P2) - Add the completed package-smoke transcript and packaged CLI output showing 0.8.1; redact private paths, endpoints, credentials, and other private details. Updating the PR body should trigger a fresh review; otherwise ask a maintainer to comment @clawsweeper re-review.

Agent review details

Security

None.

Review metrics

None.

Technical review

Best possible solution:

Ship consistent 0.8.1 package metadata and release notes through the existing validated release workflow, with bounded fixture cleanup remaining test-only.

Do we have a high-confidence way to reproduce the issue?

Not applicable to the release metadata update. The reported cleanup race was assessed from source and supplied CI context; it was not independently reproduced.

Is this the best way to solve the issue?

Yes: updating the existing release metadata and using the filesystem API's bounded cleanup retries is a narrow solution without introducing a competing release or cleanup mechanism.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 0885c9372069.

Labels

Label justifications:

• P3: This is bounded release bookkeeping and test-fixture cleanup with no introduced production behavior change beyond the version.
• rating: 🦪 silver shellfish: Overall readiness is 🦪 silver shellfish; proof is 🦪 silver shellfish and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs stronger real behavior proof before merge: The body now reports a successful installed-package mapping smoke, which is useful progress, but provides no captured result showing the packaged CLI's changed version output is 0.8.1. The earlier request for that narrow release proof remains unresolved. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence

What I checked:

• Verified introduced scope: The complete pinned base-to-head delta contains only CHANGELOG.md, the package version, and fixture cleanup: 9 additions and 6 deletions. The supplied verified test merge has the pinned main and PR head as its parents. (package.json:3, fd0fd10b6edc)
• Current main still needs the version bump: The pinned main package identifies version 0.8.0; this release metadata change is not already implemented there. (package.json:3, 0885c9372069)
• Published release check: GitHub reports v0.8.0 as the latest release, published September 7, 2026.
• Cleanup stays outside the published build: Fixture cleanup retains recursive removal and rejection on persistent failure while adding maxRetries: 3. The build configuration explicitly excludes src/test-helpers.ts. (tsconfig.build.json:7, fd0fd10b6edc)
• Proof and re-review continuity: The complete supplied body, sourceRevision 02faef06425f75d51b3e7502c41a9aa8db575768585fc4d6941d2c7ec931d514, now reports successful packaged smoke mapping 13 features, including three CUDA features. It supplies no captured packaged-version output or linked artifact. The previous completed review requested a redacted package-smoke transcript and version output showing 0.8.1. The current smoke script exercises installed CLI initialization and mapping but does not invoke --version. (scripts/package-smoke.mjs:171, fd0fd10b6edc)
• Release and security boundary: The existing release workflow checks package/tag agreement and a dated changelog before validation and trusted publishing. This PR changes no workflow permissions, dependencies, lifecycle scripts, or publishing implementation. (.github/workflows/release.yml:47, fd0fd10b6edc)

Likely related people:

• steipete: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

• Attach the completed package-smoke transcript and installed CLI version output showing 0.8.1, with private details redacted.

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (1 earlier review cycle)

• reviewed 2026-09-14T01:33:47.653Z sha e56f5f2 :: needs real behavior proof before merge. :: none