OQ-06 resolved: honker-core quality read fires the fork trigger (ADR-011)

Quality read of honker-core's watcher/transactional core cross-checked
against the published crates.io artifact: the core itself is clean
(Writer/Readers, polling-watcher failure handling, WatcherDeathGuard
all verified), but published 0.5.0 predates upstream's unreleased fix
train carrying the issue-#133 savepoint hardening (silent job loss in
the dead-letter paths) and five .ok() error swallows — and ADR-010's
queue depth requires engine-owned queue SQL in any posture. Resolution:
fork honker-core at the reference revision, inherit the clean machinery
and test suites, re-derive queue ops on contract v1, rename tables to
__alkstore_*.

- docs/research/quality-read-honker-core.md — full evidence
- docs/architecture/decisions/011-sqlite-substrate-fork.md — decision
- OQ-06 resolved in open-questions.md; ADR-003/005/008, engine-sqlite,
  queues, README annotated for consistency

docs/architecture/decisions/003-sqlite-driver.md

@@ -83,7 +83,9 @@ comparable reuse.
 
 - honker-core pins rusqlite ^0.40.1; version movement in honker-core
   moves our rusqlite. A honker-core quality read is the recorded fork
-  trigger ([ADR-005], OQ-06).
+  trigger ([ADR-005], OQ-06) — *(resolved 2026-10-05: the trigger
+  fired, [ADR-011](011-sqlite-substrate-fork.md) forks the substrate;
+  its rusqlite pin is then ours to move deliberately.)*
 - rustc ≥ 1.99 required by rusqlite 0.40.x — binaries linking this
   engine carry that toolchain floor (deployment-matrix row,
   [deployment.md](../deployment.md)).