archive: remove entire archive/ directory and all references

archive/ contained the old narrative wiki (superseded by DB as source
of truth), hermes-plans, oikos-cards, ledger, secrets-issuance, and
SOPS backups — all Python-era artifacts with no ongoing value.

Updated all cross-references in:
- AGENTS.md, README.md
- .agents/operations/commands.md (point to docs/infrastructure/)
- .agents/shared/llm-wiki.md, page-templates.md
- .agents/domains/knowledge/schema.md, operations/schema.md
- .agents/skills/*/SKILL.md
- docs/infrastructure/*.md (removed archive link targets)
- docs-lint/SKILL.md known-baseline note

.agents/domains/knowledge/schema.md

@@ -20,7 +20,7 @@ investigations, runbooks) in the `knowledge_entities` table.
 | Knowledge content — documents, investigations, runbooks | `knowledge_entities` table (rows linked to `entities` via `documents` / `about` edges) | Seeded from `seeds/knowledge.yaml` at deploy; mutated at runtime via the API |
 | Seed manifest (bootstrap + DR) | `seeds/knowledge.yaml` | Hand-edited or regenerated; ingested idempotently (content-hashed via `seed_versions`) |
 | Structured graph — hosts, services, entity types, relationships | `entities`, `relationships`, `entity_types` tables | Seeded from `seeds/{ontology,inventory}.yaml`; mutated via API/MCP |
-| Archived narrative wiki (read-only history) | `archive/knowledge/` | Frozen 2026-07-07 when the DB became source of truth |
+| Archived narrative wiki (read-only history) | `archive/knowledge/` (deleted 2026-08-16) | Frozen 2026-07-07 when the DB became source of truth; no longer in repo |
 
 ### Seed ingest
 
@@ -67,9 +67,9 @@ Agents register or update knowledge through the API, not by editing the seed:
 
 - The per-document **`## Changelog`** records infrastructure changes to that node. Keep the
   `### YYYY-MM-DD — title` shape so the parsed `changelog` field stays structured.
-- **`archive/knowledge/log.md`** is the append-only record of *documentation-maintenance*
+- **`archive/knowledge/log.md` (deleted)** is the append-only record of *documentation-maintenance*
   operations on the legacy wiki (restructures, source ingests, lint sweeps):
-  `## [YYYY-MM-DD] <op> | <summary>`. It is frozen with the rest of `archive/knowledge/`; new
+  `## [YYYY-MM-DD] <op> | <summary>`. It is frozen; new
   doc-maintenance operations are recorded in the DB audit trail instead.
 
 ## Querying knowledge
@@ -82,7 +82,7 @@ Use MCP, not grep:
   entity, in one call.
 - `get_entity(slug)` / `get_relations(entity)` — the structured graph around an entity.
 
-Grep the clone only when MCP is unreachable, and prefer `archive/knowledge/` for historical
+Grep the clone only when MCP is unreachable, and prefer the DB for all queries
 narrative (it is not updated when the DB changes).
 
 ## Same-session update rule
@@ -90,4 +90,4 @@ narrative (it is not updated when the DB changes).
 A change to a node updates the DB in the same session — the entity's attributes, the relationships
 that reference it, and any document whose `at_glance` or changelog should reflect the new state. See
 [page-templates.md](../../shared/page-templates.md#same-session-update-rule) for the legacy wiki
-equivalent (now scoped to `archive/knowledge/` history).
+equivalent (deleted).

.agents/domains/operations/schema.md

@@ -8,7 +8,7 @@ exception.
 Where each kind lives: runbooks are skills under [`.agents/skills/`](../../skills/); operator
 reference (command cheatsheet, enrollment, Nomos agent) lives in
 [`.agents/operations/`](../../operations/); investigations are `investigation` entities in the DB
-(historically `archive/knowledge/sources/investigations/`); plans stay in the repo-root `plans/`
+(historically investigation entities in the DB); plans stay in the repo-root `plans/`
 folder (below).
 
 ## Plans always live in `plans/`
@@ -49,7 +49,7 @@ Incident records are `investigation` entities in the DB, linked to the entities
 `about` edges. They are **evidence sources** — written once at incident time, then back-linked from
 the changelogs of the nodes they implicate. Sections: `## Summary`, `## Timeline`, `## Root cause`,
 `## Mitigations applied`, `## Open questions`. The legacy file-based investigations live at
-`archive/knowledge/sources/investigations/` (frozen 2026-07-07); new investigations go in the DB.
+investigation entities in the DB.
 
 ## The operations log