Skip to content

fix(prime): retry provider admission after ownership recovery - #664

Merged
rynfar merged 1 commit into
pylonfrom
fix/prime-recovery-reconcile
Sep 19, 2026
Merged

rynfar merged 1 commit into
pylonfrom
fix/prime-recovery-reconcile

Conversation

@rynfar

@rynfar rynfar commented Sep 19, 2026 •

Copy link
Copy Markdown
Collaborator

Managed Prime install could prove a legacy ownership receipt settled, yet still fail with Provider 'primeAgent' is not implemented: refreshing status cannot recreate an instance excluded by startup preflight.

Retry unavailable admission under the registry reconciliation lock using its current configuration before taking the existing maintenance fence. Re-run the complete target-driver preflight, retain unrelated unavailable shadows and live runtimes, and handle retries after a previous operation already removed the receipt. Unresolved quarantine remains unavailable. This changes no wire contracts or platform support.

Validation: 87 focused tests across registry, maintenance, adapter routing, usage and text generation passed; server typecheck and targeted lint passed. Regression covers failed admission, unchanged-config behavior, successful recovery, idempotence and preservation of an unrelated live runtime.

Follow-up to #649. Tracks #557; installed runtime acceptance remains separate.

Model: GPT-6 Astra. Harness: Codex in Pylon.


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

@vercel

vercel Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

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

1 Skipped Deployment
Project Deployment Actions Updated
pylon-marketing Ignored Ignored Preview Sep 19, 2026 2:11am UTC

@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:M labels Sep 19, 2026
@rynfar

rynfar commented Sep 19, 2026

Copy link
Copy Markdown
Collaborator Author

Adversarial review of a0cd083: checked repeated recovery after receipt removal, unresolved quarantine, settings/retry serialization, target-driver set-wide preflight, existing runtime generations, unrelated unavailable shadows, and maintenance fence/CAS ordering. No remaining blocking finding. The regression demonstrates the old unchanged-config failure and successful explicit re-admission while retaining an unrelated runtime.

Validation: 87 focused tests, t3 typecheck and targeted lint passed. Installed Nightly205 accepted the independently published stable4 after equivalent-home re-admission through Settings; it now reports authenticated managed native Prime v0.9.4. #664 removes that manual re-admission step for future recovery. Standing user authorization requests review and green merge; merge remains gated on exact-head CI.

@rynfar
rynfar merged commit 6bd5414 into pylon Sep 19, 2026
19 checks passed
@rynfar
rynfar deleted the fix/prime-recovery-reconcile branch September 19, 2026 02:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M 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