chore(release): prepare v0.13.3

[steipete]

Stamps the changelog for v0.13.3.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

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

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 17, 2026, 12:26 AM ET / 04:26 UTC.

ClawSweeper review

What this changes

The branch converts the Unreleased changelog section into v0.13.3 dated 2026-08-17 while preserving its two completed fixes.

Merge readiness

⚠️ Ready for maintainer review - 3 items remain

The focused release-stamp patch is correct, but it remains open for explicit collaborator/release-owner handling.

Priority: P3
Reviewed head: 7d8c034924459bc6a0ed5fb7ac0e440ab3c20d69
Owner decision: Required. See Decision needed.

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused release-note update following the prior tagged release-stamp pattern.
Proof confidence	🌊 off-meta tidepool	Not applicable: This changelog-only PR does not require runtime behavior proof.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This changelog-only PR does not require runtime behavior proof.
Evidence reviewed	4 items	Focused diff: The branch changes only CHANGELOG.md: it stamps v0.13.3 and removes the preceding separator blank line, while retaining both fix entries. Release integration: The unified workflow receives the release version as an input and includes CHANGELOG.md in artifacts; GoReleaser automatic changelog generation is disabled. Established release pattern: The previous release-stamp commit is tagged v0.13.2; the current changelog history shows the two v0.13.3 entries were added after it.
Findings	None	None.
Security	None	None.

How this fits together

Discrawl’s unified release workflow receives a maintainer-selected SemVer and packages the repository changelog in signed release artifacts. This update turns accumulated release notes into the versioned record shipped with that release.

flowchart LR
  A[Completed fixes] --> B[Unreleased changelog]
  B --> C[Release stamp]
  C --> D[Versioned release notes]
  D --> E[Signed release artifacts]

Loading

Decision needed

Question	Recommendation
Should the release owner include this v0.13.3 changelog stamp in the pending release?	Include in v0.13.3: Merge the focused stamp when v0.13.3 is the release being published.

Why: This collaborator-authored change selects release-facing documentation, which requires explicit maintainer handling.

Before merge

• Resolve merge risk (P1) - The advisory structured-review helper could not run because the read-only environment has no usable temporary directory; manual diff and release-process review completed.
• Complete next step (P2) - Release-owner confirmation is the remaining action; no repair is needed.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog delta	1 file; 1 added, 2 removed	The branch is confined to the release heading and spacing, with no runtime or packaging-code change.

Merge-risk options

Maintainer options:

1. Decide the mitigation before merge
   Land the existing dated changelog entry as part of the v0.13.3 release after the release owner confirms that version is being cut.
2. Pause or close
   Do not merge this PR until maintainers decide whether the risk is worth taking.

Technical review

Best possible solution:

Land the existing dated changelog entry as part of the v0.13.3 release after the release owner confirms that version is being cut.

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

Not applicable: this changelog-only PR does not alter executable product behavior.

Is this the best way to solve the issue?

Yes: the release workflow takes the version separately and packages CHANGELOG.md, so stamping the existing notes is the narrow established release-documentation path.

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning high; reviewed against 2fd32a3446cd.

Labels

Label changes:

• add P3: This is routine release-note maintenance with no product behavior change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This changelog-only PR does not require runtime behavior proof.

Label justifications:

• P3: This is routine release-note maintenance with no product behavior change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This changelog-only PR does not require runtime behavior proof.

Evidence

What I checked:

• Focused diff: The branch changes only CHANGELOG.md: it stamps v0.13.3 and removes the preceding separator blank line, while retaining both fix entries. (CHANGELOG.md:1, 7d8c03492445)
• Release integration: The unified workflow receives the release version as an input and includes CHANGELOG.md in artifacts; GoReleaser automatic changelog generation is disabled. (.github/workflows/release-unified.yml:1, 2fd32a3446cd)
• Established release pattern: The previous release-stamp commit is tagged v0.13.2; the current changelog history shows the two v0.13.3 entries were added after it. (CHANGELOG.md:1, 54eb70cfb320)
• Structured-review limitation: The repository-provided structured review helper was invoked for the exact PR commit but could not create an isolated temporary directory in the read-only review environment; direct source and diff inspection completed.

Likely related people:

• steipete: Authored the tagged v0.13.2 release stamp and this release-stamp commit. (role: recent release-process contributor; confidence: high; commits: 54eb70cfb320, 7d8c03492445; files: CHANGELOG.md, .github/workflows/release-unified.yml)

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.