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_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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