Skip to content

fix(prime): recover settled legacy ownership during managed install - #649

Merged
rynfar merged 1 commit into
pylonfrom
fix/prime-legacy-ownership-recovery
Sep 18, 2026
Merged

rynfar merged 1 commit into
pylonfrom
fix/prime-legacy-ownership-recovery

Conversation

@rynfar

@rynfar rynfar commented Sep 18, 2026 •

Copy link
Copy Markdown
Collaborator

Legacy Prime ownership quarantine currently prevents managed installation from reaching its maintenance reservation, leaving an installed Nightly unable to switch to a verified build. Managed installation now asks the verified target SDK to establish exact settlement of legacy owned roots before refreshing the provider and taking the normal maintenance fence.

Receipt inspection and removal run under the existing cross-process lock with full before/after receipt comparison. Pending, corrupt, recoverable, changed, still-registered, and unprovable receipts remain quarantined. The SDK feature is required; older builds cannot clear quarantine. Settings compare-and-swap and normal quiescence checks remain in force.

Validation: 113 focused tests passed (2 existing artifact-dependent tests skipped), server typecheck and targeted lint passed. Prime SDK counterpart: pylon-code/prime-agent#79. Installed Nightly acceptance and protected runtime publication remain tracked in #557.

Refs #557.

Model: GPT-6 Astra. Harness: Codex.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Refs #557. Preserve quarantine unless the verified target SDK proves exact prior root settlement under the ownership receipt lock.
@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L labels Sep 18, 2026
@vercel

vercel Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
pylon-marketing Ready Ready Preview Sep 18, 2026 9:00pm UTC

@github-actions

Copy link
Copy Markdown
Contributor

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider Metric Main baseline This PR Impact PR ceiling
Codex Total thread wire 14.0 KiB 13.9 KiB −55 B (−0.4%) 15.1 KiB ✅
Codex Thread snapshot wire 7.2 KiB 7.2 KiB +7 B (+0.1%) 7.3 KiB ✅
Codex Live turn WebSocket wire 6.8 KiB 6.7 KiB −62 B (−0.9%) 7.8 KiB ✅
Codex Live turn WebSocket decoded 58.0 KiB 58.0 KiB −88 B (−0.1%) 66.4 KiB ✅
Codex Live turn messages 10 8 −2 (−20.0%) 21 ✅
Claude Total thread wire 14.0 KiB 14.0 KiB +9 B (+0.1%) 15.1 KiB ✅
Claude Thread snapshot wire 7.2 KiB 7.2 KiB −1 B (−0.0%) 7.3 KiB ✅
Claude Live turn WebSocket wire 6.8 KiB 6.8 KiB +10 B (+0.1%) 7.8 KiB ✅
Claude Live turn WebSocket decoded 58.9 KiB 58.9 KiB 0 B (0.0%) 66.4 KiB ✅
Claude Live turn messages 10 10 0 (0.0%) 21 ✅

Baseline: f2a9637 · PR result: f5c03d3 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

  • Codex decoded thread snapshot: 115.6 KiB
  • Claude decoded thread snapshot: 116.3 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

@rynfar

rynfar commented Sep 18, 2026

Copy link
Copy Markdown
Collaborator Author

Adversarial review completed for f5c03d3. No unresolved findings: recovery executes only from a receipt-verified managed target; the original root/home/proof are checked under the ownership lock with full before/after receipt equality; pending, recoverable, corrupt, changed and unproved records retain quarantine. Scheduled maintenance revalidates its target, and the normal quiescence fence and settings CAS still govern selection. No wire changes or client-specific bypasses were introduced.

113 focused tests passed (2 pre-existing artifact-dependent skips), server typecheck and targeted lint passed. Hosted CI 35390539014 passed every job, including Linux and Windows packaged checks. New SDK publication and installed-target acceptance remain required under #557.

The maintainer explicitly authorized review, merge and installed Nightly delivery in the task conversation. Merge after all head checks finish successfully.

@rynfar
rynfar merged commit 36bfbf4 into pylon Sep 18, 2026
19 checks passed
@rynfar
rynfar deleted the fix/prime-legacy-ownership-recovery branch September 18, 2026 20:28

This branch was successfully deployed

1 active deployment
Preview — f5c03d3a Deployed Sep 18, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:L vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant