[atomantic]

Synchronizes the published v2.117.0 - Rhythm Raccoon into main, retaining all development work present at 6f7965912df1e2e8972a26cf72d8053993cc8d52. The published promotion merged without conflicts.

Published release and ancestry

• Release: https://github.com/atomantic/PortOS/releases/tag/v2.117.0
• Promotion: Release v2.117.0 - Rhythm Raccoon #15767, merged at a344eb1e2f0a29926bc0112f4617c10dca55214f
• Successful publication workflow: https://github.com/atomantic/PortOS/actions/runs/43067157518
• Frozen cutoff: c99a8e71e4d84f1f62b54c715c3f02a63efee285; previous release: v2.116.0
• Candidate head: a92217f7a39b496a7a0069183ea0ab9ff7be45fc; release base: 33dc1ebf7271125bb20f9b9ec03a8dde6252d7ed
• Package and root lockfile agree on 2.117.0; the published tag is unchanged.
• All 24 candidate amendments, their evidence and validation are recorded in Release v2.117.0 - Rhythm Raccoon #15767. This PR forward-ports them together with version metadata and release notes.

Post-publication review fixes

These two follow-ups were discovered during synchronization review and will ship with the next release:

• ad5f008c116df384e86f072485cf44c5d9eac777: reimport only refreshes a known local image's origin stamp; existing foreign and unknown ownership remains intact for paired reconciliation.
• bcd6ea47bc678510edf53e3855065377f30271e4: attach each comparison half before saving its partner. Retry reuses the attached half; a failed attachment removes only a new image confirmed absent from the catalog, preserving an attachment whose commit succeeded before its acknowledgement failed.

Review and validation

• Exactly the configured optional gpt-6.1-terra reviewer was invoked. Total budget used: 2/2 rounds across release and synchronization. Release-range round 1 was inconclusive due context capacity; synchronization round 2 produced two valid findings at 8a4578c6f333bff14e18a41696c2172b137cab33.
• Both accepted findings are fixed in the commits above. The budget is exhausted; the final fixes have not been re-reviewed and no approval is implied.
• Focused public-boundary regressions: 4 files, 32 tests passed, including reimport/reconciliation, partial-save retry, attachment failure cleanup, and preserving committed attachments. New negative controls fail with the pre-fix code.
• Stable-tree local pregate passed on bcd6ea47bc678510edf53e3855065377f30271e4 (all 8 selected stages). Current-head hosted checks remain required before merge. Candidate full pregate, isolated database suite, all 26 hosted checks and publication already passed on the frozen candidate.

Decisions for operator review

• Use the reserved temporary synchronization branch and a normal merge PR into main, preserving the published promotion ancestry and newer development work.
• Preserve uncertain ownership until established by paired evidence.
• Persist each comparison half before starting the next; cleanup checks catalog attachment before removing newly saved bytes.
• Keep the published release immutable; the two synchronization follow-ups are development changes for the next release.
• Retain the historical reviewed revision and honor the exhausted optional review budget. Required provider checks and reviews still gate merge.

Verified delivery

• MERGED at 187ebe4dfbb962f679fcfe82867c044aaf439a51; development head observed at 187ebe4dfbb962f679fcfe82867c044aaf439a51 contains the published promotion, candidate and synchronization head.
• CI 43069459678 and runtime security 43069459541 passed on bcd6ea47bc678510edf53e3855065377f30271e4. The 22 successful checks include the required CI Gate; four normal planner skips are Full CI Gate, Windows native contracts, Docker containment live and macOS native release-agent supervision. Those platform checks passed during frozen candidate validation.
• Development package and root lockfile agree on 2.117.0. Required post-publication npm run quality:snapshot returned no-changes, with no provider calls or live-checkout edits.
• Temporary checkouts and review evidence are retained for the server's post-exit capture, settlement and eligible retirement.

The repository delivery verifier independently confirms all eight delivery and quality obligations against the merged synchronization and development snapshot. This inspection does not persist synchronization receipts or claim a clean local review of unreviewed fixes. The only pending obligations are active-process settlement and service-owned checkout retirement after this run exits.