Forge client is built once and never re-resolves its token #1187

Closed
opened 2026-10-27 13:39:22 +00:00 by sam · 0 comments
Owner

openForge runs once after runtime layering. If the token names an extension engine that is not up on that first sync, the forge stays disabled until restart, unlike provider credentials which re-resolve each reconcile tick. Done when a forge token held by an extension engine recovers without a restart.

Close reason

Decided: forge configuration is file-only and restart-bound (no control-plane kind), so its token resolving at boot is consistent. The boot warning names the engine and key.


Imported from beads archie-core-8r2r.4 · GitHub #1482 · type bug · priority P3 · created 2026-10-03 · closed 2026-10-03

openForge runs once after runtime layering. If the token names an extension engine that is not up on that first sync, the forge stays disabled until restart, unlike provider credentials which re-resolve each reconcile tick. Done when a forge token held by an extension engine recovers without a restart. ### Close reason Decided: forge configuration is file-only and restart-bound (no control-plane kind), so its token resolving at boot is consistent. The boot warning names the engine and key. --- _Imported from beads `archie-core-8r2r.4` · GitHub #1482 · type bug · priority P3 · created 2026-10-03 · closed 2026-10-03_
sam added the lowbug labels 2026-10-27 13:39:22 +00:00
sam self-assigned this 2026-10-27 13:39:22 +00:00
sam closed this issue 2026-10-27 13:39:22 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1187