[steipete]

Remove the duplicate send.tracked persistence entry introduced while rebasing the receipt fixes. The remaining entry retains the issue reference and contributor thanks.

Validation: seven unique Unreleased entries remain; application version stays 0.21.0. Independent P2 review passed. Documentation-only change.

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

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-14T07:58:17.297172Z	4af283d	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[clawsweeper]

Codex review: needs maintainer review before merge.

What this changes

Remove one duplicate tracked-send receipt bullet from the Unreleased changelog.

Example: A reader checks the Unreleased notes for tracked-send receipt verification.

• Before: The exact persisted outgoing GUID requirement appears twice.
• After: It appears once, retaining the issue reference and thanks to @thurstonsand.

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A complete, minimal documentation fix with no findings.
Proof confidence	🌊 off-meta tidepool	Not applicable: Direct comparison verifies this documentation-only deletion; shipped-entry-point proof is unnecessary.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Docs · Worth it: Yes · Fix scope: Complete
User problem: Readers encounter the same tracked-send release note twice.
Reason: The maintainer-authored direction is clear, and a one-line deletion removes duplication without losing content.

Merge readiness

✅ Ready for maintainer review

This PR is a correct, focused documentation cleanup that remains necessary on main; maintainer authorship also prevents automatic closure.

Priority: P3
Reviewed head: 4af283d9f9574593314e38bb59dbccdb764b6e55

Before merge

None.

Findings

None.

Agent review details

How this fits together

CHANGELOG.md records release changes for readers and release tooling; this edit removes repeated prose without changing release headings or executable behavior.

flowchart LR
  A[Merged changes] --> B[Unreleased changelog]
  B --> C[Release preparation]
  C --> D[Published release notes]
  B --> E[Repository readers]

Loading

Technical review

Best possible solution:

Land the single-line deletion while retaining the complete remaining entry.

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

The pinned main changelog directly shows two byte-identical tracked-send receipt bullets.

Is this the best way to solve the issue?

Deleting one copy is the smallest complete fix and preserves all distinct release information.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 2a0a18acd712.

Provenance checked

• Tracked-send Unreleased entry keeps the original intent (3089311: Document that tracked sends require the requested outgoing identity to persist before success is reported.)

Security

None.

Evidence

What I checked:

• Exact introduced change: The pinned diff deletes only the second identical tracked-send bullet; the retained entry preserves its reference and contributor credit. (CHANGELOG.md:7, 4af283d9f957)
• Historical intent preserved: fix: verify recovered and tracked send receipts #399 introduced both identical bullets while documenting persisted tracked-send identity verification; removing one preserves that stated behavior. (CHANGELOG.md:10, 30893116d52d)
• Current main still needs cleanup: The default branch remains at the pinned base, whose Unreleased section contains both copies. (CHANGELOG.md:10, 2a0a18acd712)
• Repository policy applied: The complete root guidance requires focused changes; no nested policy, maintainer notes, or pr-simplify skill applies to this root changelog edit. (AGENTS.md:28, 4af283d9f957)
• Owner direction and discussion: The collaborator-authored PR explicitly requests deduplication; all discussion comments were read and add no unresolved review request. (4af283d9f957)
• Validation state: Exact-head macOS and Linux checks passed; Swift analysis remains in progress, with no failed check reported. (4af283d9f957)

Likely related people:

• Peter Steinberger: Raw commit 3089311 adds CHANGELOG.md:5 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 30893116d52d; files: CHANGELOG.md)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

• add P3: This removes repeated release-note prose without changing runtime behavior.
• 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.

Label justifications:

• P3: This removes repeated release-note prose without changing runtime behavior.
• 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.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 14, 2026, 3:09 AM ET / 08:09 UTC.