[steipete]

Prepare 0.16.3: date the changelog section, add highlights, bump package.json, and restore a numbered Unreleased section.

Includes #248 (backup merge-import folds legacy profile rows into canonical profiles; backup validation ignores regular macOS .DS_Store metadata). Verified before landing #248 by merge-importing a real production backup into a copy of the production database with .DS_Store present: validation and import succeeded, no legacy rows or references remained, integrity and foreign-key checks clean.

Release-preflight unit tests pass locally; the full preflight runs in the release workflow dry run on main.

[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

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

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-24T22:45:06.265210Z	a857229	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

Prepare version 0.16.3 with dated release notes, backup-fix highlights, and a new 0.16.4 Unreleased section.

Example: Read the package version and release notes.

• Before: The package reports 0.16.2 and the backup fixes sit under 0.16.3 Unreleased.
• After: The package reports 0.16.3 and the backup fixes appear under the dated 2026-10-24 release.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The release patch is focused and correct on inspection; supplied validation consists of reported preflight unit tests and successful checks rather than a completed release rehearsal.
Proof confidence	🦐 gold shrimp (3/6)	This maintainer-authored release preparation is outside the ordinary contributor proof gate; the body reports preflight unit tests and reserves the full rehearsal for main.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: The landed backup fixes need a versioned release with matching package metadata and release notes.
Reason: Owner authorship establishes direction, and the patch follows the previous release without expanding scope.

Merge readiness

✅ Ready for maintainer review

Keep open: this owner-authored release PR is focused, follows the established release pattern, and introduces no actionable defect.

Priority: P3
Reviewed head: a857229285b57ad5b4414d202510f14ad7c853a0

Before merge

None.

Findings

None.

Agent review details

How this fits together

The package manifest supplies CLI and publication version metadata, while the release preflight extracts the matching dated changelog section for release artifacts.

flowchart LR
  A[Package manifest] --> C[Release preflight]
  B[Dated changelog] --> C
  C --> D[Package build and smoke]
  D --> E[Release artifacts]
  E --> F[Signed tag publication]

Loading

Technical review

Best possible solution:

Land the focused release preparation through the existing release process.

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

This is release preparation rather than a bug report; source inspection confirms the intended metadata changes without executing target code.

Is this the best way to solve the issue?

The two-file patch is the smallest complete release preparation and preserves the established preflight and publication owners.

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning medium; reviewed against 639ed3cf61b8.

Provenance checked

• Release version and changelog rollover keeps the original intent (40e2e23: Prepare the previous patch release while retaining every changelog bullet and restoring a numbered Unreleased section.)

Testing

Proof path: unit tests only.

Security

None.

Evidence

What I checked:

• Pinned release diff: The introduced patch only bumps the manifest version, dates the release, adds highlights, and opens the next Unreleased section; both existing backup bullets remain intact. (CHANGELOG.md:3, a857229285b5)
• Existing release contract: Preflight requires matching package metadata and one nonempty dated changelog section; workflow rehearsals run from current main and publication requires a signed annotated version tag. (scripts/release-preflight.py:19, a857229285b5)
• Prior release and ownership: The prior release used the same two-file preparation pattern and explicitly preserved changelog bullets: chore: prepare 0.16.2 release #247. (CHANGELOG.md:14, 40e2e23af737)
• Current main still needs release preparation: Fetched main retains package version 0.16.2 and the 0.16.3 Unreleased heading; the backup implementation already landed through fix(backup): reconcile legacy profiles and ignore Finder metadata #248. (CHANGELOG.md:3, 639ed3cf61b8)
• Review limits and supplied status: GitHub REST inspection was blocked by the proxy, so discussion and check status rely on the supplied context, which records owner authorship and five successful checks. An older release-automation commit inspection encountered a missing historical object; current files and the prior release diff were readable.

Likely related people:

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

Labels

Label changes:

• add P3: This is routine release metadata preparation with no runtime implementation changes.
• add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp 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 is routine release metadata preparation with no runtime implementation changes.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp 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 October 24, 2026, 6:56 PM ET / 22:56 UTC.