Serve forge and repository readiness from archied #1044

Open
opened 2026-10-27 13:38:47 +00:00 by sam · 0 comments
Owner

Forge and repository badges are derived from page state plus a manual access check. Archied should report saved/applied/verified/failed per the readiness contract (forge type, extension enabled and running, token resolved, client active, live repository access) and the UI should render that instead. Done when the badges read the served state.


Imported from beads archie-core-3z4fd.1.1 · GitHub #1923 · type task · priority P2 · created 2026-10-27

Forge and repository badges are derived from page state plus a manual access check. Archied should report saved/applied/verified/failed per the readiness contract (forge type, extension enabled and running, token resolved, client active, live repository access) and the UI should render that instead. Done when the badges read the served state. --- _Imported from beads `archie-core-3z4fd.1.1` · GitHub #1923 · type task · priority P2 · created 2026-10-27_
sam added the mediumtask labels 2026-10-27 13:38:48 +00:00
sam self-assigned this 2026-10-27 13:38:48 +00:00
sam added the deferred label 2026-11-15 17:26: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#1044