Deleting the runtime config overlay (archie-core-f9nw, commit 31622ec5) left
docs/architecture/ describing it as live. CLAUDE.md makes that directory
authoritative for settled design, so it now asserts a subsystem that does not
exist.
The dangerous one is docs/architecture/safe-change-and-recovery.md:132, which
lists the dashboard reset (POST /api/config/reset) as a recovery step for
removing a bad override. That route is deleted. An operator following the
runbook during an incident finds nothing there.
Surface:
docs/architecture/configuration.md: 23 overlay mentions in 425 lines,
including the PATCH /api/config request contract at :345 and the status-code
table at :351. Needs judgement, not sed: the -config-overlay FILE overlay
survives and is still correct, only the SQLite runtime overlay is gone.
docs/architecture/migration-decisions.md:482: the note that the three write
routes answer 503 in the UI process. They no longer exist at all.
.agents/skills/: 9 mentions across archie-architecture-contract,
archie-debugging-playbook, archie-codebase-discovery, archie-run-and-operate,
and delivery-snapshot.sh.
archie-config-and-flags was corrected already; the rest were not.
This should have landed inside 31622ec5. Deleting a subsystem includes deleting
its documentation of record.
Close reason
Done: docs/architecture and .agents/skills no longer describe the runtime overlay as live. configuration.md and the archie-config-and-flags skill state it was deleted; safe-change-and-recovery.md no longer lists POST /api/config/reset; migration-decisions.md keeps the historical decision text followed by the note that the routes were deleted in 31622ec5.
Imported from beads archie-core-b7dn · GitHub #1052 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26
Deleting the runtime config overlay (archie-core-f9nw, commit 31622ec5) left
docs/architecture/ describing it as live. CLAUDE.md makes that directory
authoritative for settled design, so it now asserts a subsystem that does not
exist.
The dangerous one is docs/architecture/safe-change-and-recovery.md:132, which
lists the dashboard reset (POST /api/config/reset) as a recovery step for
removing a bad override. That route is deleted. An operator following the
runbook during an incident finds nothing there.
Surface:
- docs/architecture/configuration.md: 23 overlay mentions in 425 lines,
including the PATCH /api/config request contract at :345 and the status-code
table at :351. Needs judgement, not sed: the -config-overlay FILE overlay
survives and is still correct, only the SQLite runtime overlay is gone.
- docs/architecture/safe-change-and-recovery.md: 14 mentions.
- docs/architecture/migration-decisions.md:482: the note that the three write
routes answer 503 in the UI process. They no longer exist at all.
- .agents/skills/: 9 mentions across archie-architecture-contract,
archie-debugging-playbook, archie-codebase-discovery, archie-run-and-operate,
and delivery-snapshot.sh.
archie-config-and-flags was corrected already; the rest were not.
This should have landed inside 31622ec5. Deleting a subsystem includes deleting
its documentation of record.
### Close reason
Done: docs/architecture and .agents/skills no longer describe the runtime overlay as live. configuration.md and the archie-config-and-flags skill state it was deleted; safe-change-and-recovery.md no longer lists POST /api/config/reset; migration-decisions.md keeps the historical decision text followed by the note that the routes were deleted in 31622ec5.
---
_Imported from beads `archie-core-b7dn` · GitHub #1052 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26_
sam
added the highbug labels 2026-10-27 13:39:34 +00:00
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.
Deleting the runtime config overlay (archie-core-f9nw, commit
31622ec5) leftdocs/architecture/ describing it as live. CLAUDE.md makes that directory
authoritative for settled design, so it now asserts a subsystem that does not
exist.
The dangerous one is docs/architecture/safe-change-and-recovery.md:132, which
lists the dashboard reset (POST /api/config/reset) as a recovery step for
removing a bad override. That route is deleted. An operator following the
runbook during an incident finds nothing there.
Surface:
including the PATCH /api/config request contract at :345 and the status-code
table at :351. Needs judgement, not sed: the -config-overlay FILE overlay
survives and is still correct, only the SQLite runtime overlay is gone.
routes answer 503 in the UI process. They no longer exist at all.
archie-debugging-playbook, archie-codebase-discovery, archie-run-and-operate,
and delivery-snapshot.sh.
archie-config-and-flags was corrected already; the rest were not.
This should have landed inside
31622ec5. Deleting a subsystem includes deletingits documentation of record.
Close reason
Done: docs/architecture and .agents/skills no longer describe the runtime overlay as live. configuration.md and the archie-config-and-flags skill state it was deleted; safe-change-and-recovery.md no longer lists POST /api/config/reset; migration-decisions.md keeps the historical decision text followed by the note that the routes were deleted in
31622ec5.Imported from beads
archie-core-b7dn· GitHub #1052 · type bug · priority P1 · created 2026-09-21 · closed 2026-09-26