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/005-dependency-ownership.md

@@ -27,7 +27,7 @@ when a named trigger fires. Per subsystem:
 
 | Subsystem | Posture | Notes |
 |---|---|---|
-| honker-core (SQLite engine machinery) | published library, `honker-core = 0.5` | Fork trigger: the Phase 1 quality read of the watcher/transactional core finds a defect, OR a needed change upstream won't take. OQ-06 tracks the read. |
+| honker-core (SQLite engine machinery) | published library, `honker-core = 0.5` — **trigger fired 2026-10-05**: forked per [ADR-011] | Fork trigger: the Phase 1 quality read of the watcher/transactional core finds a defect, OR a needed change upstream won't take. OQ-06 tracked the read; the read fired the trigger (published 0.5.0 carries the unreleased-fix-train defect class + ADR-010's queue depth requires engine-owned queue SQL in any posture). |
 | rusqlite | published, riding honker-core's pin | Pin movement is honker-core's; we ride it ([ADR-003]). |
 | tokio-postgres + deadpool-postgres | published library, as-is | Clean, zero conflicts, actively maintained (POC #2). |
 | postgres-notify | **not adopted** (derive-not-adopt) | Lazy reconnect, connect_script skipped at initial connect, unquoted-identifier LISTENs, single maintainer. Hand-rolled forwarder instead ([ADR-004]). Fallback if upstream improves materially. |
@@ -43,7 +43,9 @@ to this posture.
 **Positive**
 
 - Zero vendored code in the tree by default; upgrades are
-  `cargo update` work, not patch-management work.
+  `cargo update` work, not patch-management work. *(Exception now
+  live: the [ADR-011] fork is a vendored family crate — the named
+  trigger, not a posture change.)*
 - The fork triggers are concrete and named *before* the quality read,
   so the read produces a decision, not a debate.
 - Per-subsystem votes are recorded with evidence, so no future
@@ -53,6 +55,10 @@ to this posture.
 
 - honker-core 0.5 remains alpha-quality software per its own README in
   the link graph; the quality read (OQ-06) is the mitigation gate.
+  *(Resolved 2026-10-05: the read fired the trigger — [ADR-011].
+  This row's negative consequence is retired with it; the
+  "zero vendored code" positive consequence now carries ADR-011's
+  named exception.)*
 - The pg queue machinery is written by us — the pg-boss family's
   battle-tested edge cases must be re-earned by design + tests
   ([queues.md]).