You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
release(prime): graduate and deliver the September reliability fixes #557
Exact Prime source 72899e4e4fdaef52cfffca58152f769a6aef91b1 passed merged-source CI 35397638314. Immutable preview pylon-build-g72899e4e4fda-r2 published successfully.
Stable promotion 35413885588 succeeded. Immutable stable sequence 4 published at 2026-09-19T02:02:28Z after protected attestation and final-publication approvals with fresh policy readback.
Supported Install stable in Nightly 205 verified and installed the stable4 files. The verified SDK successfully proved the old ownership settled; Pylon removed the exact legacy receipt through its supported recovery hook. No manual live-state edits were made.
Initial activation attempt failed. Install receipt prime-managed:install:1789783390595:1 failed at 02:04:48Z with Provider 'primeAgent' is not implemented; the unavailable provider instance had not been recreated.
Root cause: ProviderRegistry.refreshInstance only probes live sources; a preflight-quarantined instance is absent and is not recreated. An unchanged settings reconciliation also retains its unavailable shadow. PR #664 retries unavailable admission under the instance registry lock before the normal maintenance fence, including retries after ownership cleanup has already completed. 87 focused tests, server typecheck and targeted lint passed. fix(prime): retry provider admission after ownership recovery #664 merged as 6bd54148e03c18a5608680cc6c44b0e592b5133c; CI 35414900300 completed successfully, including Windows/Linux packaged smoke and all server/client jobs.
Installed runtime activation succeeded at 02:12:49Z. Through supported Settings, re-saved the same Agent home from ~/.prime/agent to its equivalent absolute path /Users/rynfar/.prime/agent, triggering provider re-admission without an app restart. Then supported Install stable command prime-managed:install:1789783960273:2 succeeded, selecting managed pylon-build-g72899e4e4fda-r2, stable4. The former local686c binary remains the recorded stock fallback.
Fresh installed UI reports v0.9.4, Authenticated, Pylon managed · stable feat: adopt the multi-provider pull requests page (DEF-1, DEF-2) #4, Native daemon. Actual persisted selection matches the UI. Existing authentication and canonical Agent home are preserved; no direct live-state edits, global shutdowns, or app restart were used.
Completed: all reviewed fixes are merged, stable4 is published, and the installed Nightly runtime is selected and authenticated. #664 is merged for subsequent app builds; installed Nightly205 used supported equivalent-home re-admission. No app restart is needed for this completed runtime update, and no new Prime publication is needed for the server-side follow-up.
The reviewed source batch is merged: prime-agent#70, commit 0bc94405920fbc3b3baf9bb0984d88399c7f31b5. All required PR checks passed, including the full Linux/macOS publication crash suites, reproducible artifacts and installed-runtime checks; 183 focused local regressions and npm run check also passed.
The companion Pylon fixes are merged in #548 and #553 (740a8a2626c0a41f18e8c5a3c56d6d6c56f10381), with #555 repairing the Windows CI installer. This closes implementation for the first reliability batch. Publication, artifact graduation and managed update remain the work of this issue; no new installed runtime is claimed.
Installed Nightly delivery — current checkpoint
Target: installed Pylon Nightly, not the separate fresh-follower environment.
Installed Nightly 205, source
a3bb71bd360a, includes Pylon fix(prime): recover settled legacy ownership during managed install #649 (confirmed ancestry). No app restart was performed in this step; the user requested waiting for other threads before any restart.Prime Prime Agent active turns fail after daemon reconnect #79 and Pylon fix(prime): recover settled legacy ownership during managed install #649 are merged with green checks. Earlier reviewed Prime fix(web): keep the contrast slider from flattening text hierarchy #70–75/Prime Agent sessions do not receive Pylon browser tools #77 and Pylon fix(prime): preserve transcript continuity after harness refinement #548/fix(prime): preserve applied refinement notices across synchronization #553/fix(prime): verify native transcript and compaction continuity #570/fix(prime): preserve turns through startup and restart snapshots #577/fix(ci): provision uv for Prime artifact graduation #637/fix(prime): verify signed publications in Electron #641 are also merged.
Exact Prime source
72899e4e4fdaef52cfffca58152f769a6aef91b1passed merged-source CI 35397638314. Immutable previewpylon-build-g72899e4e4fda-r2published successfully.Protected Pylon graduation 35413884125 passed 34/34, zero failures or skips, evidence artifact
10574857483.Stable promotion 35413885588 succeeded. Immutable stable sequence 4 published at 2026-09-19T02:02:28Z after protected attestation and final-publication approvals with fresh policy readback.
Supported Install stable in Nightly 205 verified and installed the stable4 files. The verified SDK successfully proved the old ownership settled; Pylon removed the exact legacy receipt through its supported recovery hook. No manual live-state edits were made.
Initial activation attempt failed. Install receipt
prime-managed:install:1789783390595:1failed at 02:04:48Z withProvider 'primeAgent' is not implemented; the unavailable provider instance had not been recreated.Root cause:
ProviderRegistry.refreshInstanceonly probes live sources; a preflight-quarantined instance is absent and is not recreated. An unchanged settings reconciliation also retains its unavailable shadow. PR #664 retries unavailable admission under the instance registry lock before the normal maintenance fence, including retries after ownership cleanup has already completed. 87 focused tests, server typecheck and targeted lint passed. fix(prime): retry provider admission after ownership recovery #664 merged as6bd54148e03c18a5608680cc6c44b0e592b5133c; CI 35414900300 completed successfully, including Windows/Linux packaged smoke and all server/client jobs.Installed runtime activation succeeded at 02:12:49Z. Through supported Settings, re-saved the same Agent home from
~/.prime/agentto its equivalent absolute path/Users/rynfar/.prime/agent, triggering provider re-admission without an app restart. Then supported Install stable commandprime-managed:install:1789783960273:2succeeded, selecting managedpylon-build-g72899e4e4fda-r2, stable4. The former local686c binary remains the recorded stock fallback.Fresh installed UI reports v0.9.4, Authenticated, Pylon managed · stable feat: adopt the multi-provider pull requests page (DEF-1, DEF-2) #4, Native daemon. Actual persisted selection matches the UI. Existing authentication and canonical Agent home are preserved; no direct live-state edits, global shutdowns, or app restart were used.
Completed: all reviewed fixes are merged, stable4 is published, and the installed Nightly runtime is selected and authenticated. #664 is merged for subsequent app builds; installed Nightly205 used supported equivalent-home re-admission. No app restart is needed for this completed runtime update, and no new Prime publication is needed for the server-side follow-up.