Clarify Discrawl changelog history

[joshka]

Summary

• restore the missing 0.10.0 changelog section for Cloudflare remote archives
• flesh out recent changelog entries so R2, D1, SQLite mirrors, gzip chunks, privacy exclusions, and upload limits explain user-visible behavior
• add changelog guidance in AGENTS.md and the Discrawl skill so future edits preserve rationale-bearing details and avoid style-only churn

Context

This started from trying to answer what was in 0.10.0. That release was missing from the changelog, and several nearby entries required digging through commits and PRs to understand what the implementation nouns meant for users.

The update keeps concrete details when they explain capabilities or constraints: R2 is the restorable SQLite bundle, D1 is the live query path, gzip chunks and 64 MiB parts are upload/runtime constraints, and the privacy exclusions explain why DMs and local-only data stay out of remote/shared archives.

This is intentionally not a broad style-normalization pass. Older entries keep their existing voice and structure unless the change restores missing context, fixes placement, or explains user-facing behavior.

Validation

• git diff --check -- CHANGELOG.md AGENTS.md .agents/skills/discrawl/SKILL.md

[clawsweeper]

Codex review: needs real behavior proof before merge. Reviewed June 17, 2026, 5:51 PM ET / 21:51 UTC.

Summary
The branch rewrites recent CHANGELOG entries, restores a 0.10.0 section, and adds changelog-editing guidance to AGENTS.md and the Discrawl skill.

Reproducibility: not applicable. this is a release-history documentation PR. The focused checks are source/diff review, tag provenance, and Markdown validation rather than a runtime reproduction.

Review metrics: 2 noteworthy metrics.

• Release-history surface: 3 Markdown/policy files changed; 113 additions, 39 deletions. Most of the diff is release-history and agent guidance, so factual review matters more than runtime CI.
• CHANGELOG churn: 105-line CHANGELOG diff. The release-owned file is the highest-risk surface because it changes past release descriptions.

Merge readiness
Overall: 🧂 unranked krab
Proof: 🧂 unranked krab
Patch quality: 🐚 platinum hermit
Result: blocked until real behavior proof is added.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

• [P1] Add terminal output or a terminal screenshot for git diff --check -- CHANGELOG.md AGENTS.md .agents/skills/discrawl/SKILL.md.
• [P1] Have a maintainer spot-check the rewritten changelog against the v0.10.0 and v0.11.0 tags before merge.

Proof guidance:

• [P1] Needs real behavior proof before merge: Needs real behavior proof before merge: add terminal output or a terminal screenshot for the stated git diff --check command, or rendered Markdown proof; redact private details, then update the PR body to trigger a fresh ClawSweeper review or ask a maintainer to comment @clawsweeper re-review.

Risk before merge

• [P1] CHANGELOG.md is release-owned, and this PR rewrites 105 lines of historical release notes, so maintainers should verify the release history before merging.
• [P1] The PR body lists git diff --check but does not include terminal/live output or rendered proof, so the external-PR proof gate remains unsatisfied.

Maintainer options:

1. Require proof and history spot-check (recommended)
   Have the contributor add terminal or rendered proof, then have a maintainer compare the rewritten changelog against the v0.10.0 and v0.11.0 release tags before merge.
2. Land as maintainer-owned release history
   A maintainer may intentionally accept the release-history rewrite after manual verification because this is a release-owned file.
3. Keep release notes maintainer-only
   If maintainers do not want contributor PRs rewriting historical changelog entries, close or replace this with a maintainer-authored release-history update.

Next step before merge

• [P1] Human review is needed because this edits release-owned changelog/policy text and contributor proof is missing; there is no narrow code repair for automation.

Security
Cleared: The diff changes Markdown release-history and agent guidance only; it does not alter dependencies, workflows, secrets handling, install scripts, or code execution paths.

Review details

Best possible solution:

Have a maintainer verify the historical changelog against the relevant release tags, accept the AGENTS/skill guidance if desired, and merge only after contributor proof output is added.

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

Not applicable; this is a release-history documentation PR. The focused checks are source/diff review, tag provenance, and Markdown validation rather than a runtime reproduction.

Is this the best way to solve the issue?

Yes, if maintainers want this release-history correction in core. The patch is narrow to Markdown guidance and changelog content, but release-owned history should be maintainer-verified before merge.

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning high; reviewed against 7ba9fa595787.

Label changes

Label changes:

• add P3: This is low-risk documentation and policy cleanup with no runtime behavior change.
• add merge-risk: 🚨 other: Merging rewrites release-owned historical changelog content and adds agent policy guidance that CI cannot fact-check.
• add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• add status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: Needs real behavior proof before merge: add terminal output or a terminal screenshot for the stated git diff --check command, or rendered Markdown proof; redact private details, then update the PR body to trigger a fresh ClawSweeper review or ask a maintainer to comment @clawsweeper re-review.

Label justifications:

• P3: This is low-risk documentation and policy cleanup with no runtime behavior change.
• merge-risk: 🚨 other: Merging rewrites release-owned historical changelog content and adds agent policy guidance that CI cannot fact-check.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
• status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: Needs real behavior proof before merge: add terminal output or a terminal screenshot for the stated git diff --check command, or rendered Markdown proof; redact private details, then update the PR body to trigger a fresh ClawSweeper review or ask a maintainer to comment @clawsweeper re-review.

Evidence reviewed

What I checked:

• Current main lacks target AGENTS.md: At current main, AGENTS.md is absent from the target repository root; the only AGENTS.md found was outside the target checkout. (7ba9fa595787)
• Current main skips 0.10.0: The current CHANGELOG.md goes from 0.11.0 at line 11 to 0.9.1 at line 38, so the requested 0.10.0 history is not already on main. (CHANGELOG.md:11, 7ba9fa595787)
• PR restores release history: The PR head adds a 0.10.0 section at line 37 and clarifies 0.11.0 remote archive, R2, privacy, and chunking behavior in user-facing terms. (CHANGELOG.md:37, 1846f6d263f9)
• PR adds changelog guidance: The PR adds root AGENTS.md changelog guidance and mirrors the release-note guidance in the Discrawl skill. (AGENTS.md:5, 1846f6d263f9)
• 0.10.0 provenance: Tag v0.10.0 points to dcf0c9c, a Cloudflare remote archive commit from 2026-05-27; that tag's changelog contains the unreleased remote archive bullets this PR turns into a released 0.10.0 section. (CHANGELOG.md:3, dcf0c9c8dbb3)
• PR state and checks: GitHub reports the PR mergeable and clean with CI, CodeQL, secret scanning, Docker, release-check, and Socket checks successful; the PR body lists a diff-check command but does not include proof output. (1846f6d263f9)

Likely related people:

• Peter Steinberger: Current main blame and log history show the recent 0.11.1 changelog opening, 0.11.0 release changelog, and Discrawl skill snapshot are primarily from this path. (role: recent release-history and skill contributor; confidence: high; commits: 7ba9fa595787, 1da64f583db6, 37a9338fdcdb; files: CHANGELOG.md, .agents/skills/discrawl/SKILL.md)
• vincentkoc: The restored 0.10.0 content traces to the Cloudflare remote archive feature commit and nearby changelog/skill documentation work. (role: remote archive feature and docs contributor; confidence: high; commits: dcf0c9c8dbb3, 89d35a67a4d8, f32dae98cc1f; files: CHANGELOG.md, .agents/skills/discrawl/SKILL.md, internal/cli/remote_commands.go)

What the crustacean ranks mean

• 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
• 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
• 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
• 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
• 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
• 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
• 🌊 off-meta tidepool: rating does not apply to this item.

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.

How this review workflow works

• 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.

[steipete]

Reworked to a focused, verifiable history repair: restored the v0.10.0 entries from the tagged release, moved those entries out of v0.11.0 to avoid duplicate attribution, and removed the broad style rewrite and duplicated agent guidance. Generated docs-site proof, autoreview, and all CI/security checks pass.

[steipete]

Landed as e6f719b7fa9b415174be95e6b64414f0c4ba42c5.

The final patch restores the tagged v0.10.0 remote-archive history, removes those entries from v0.11.0 to avoid duplicate release attribution, preserves the rest of the historical wording, and credits @joshka. Proof: generated docs page contains the restored section; autoreview's duplicate-history finding was fixed and the rerun passed; lint, tests, release check, Docker, CodeQL, dependency, and secret checks all passed.