Repository navigation
fix(prime): recover settled legacy ownership during managed install - #649
Conversation
Refs #557. Preserve quarantine unless the verified target SDK proves exact prior root settlement under the ownership receipt lock.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 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.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
|
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. |
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.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.