8e6da2f6c9322f4897000fdce7fd4005374edc88
Read the four honker.dev guides (queues/streams/pubsub/scheduler) + packages/honker-rs/src/lib.rs (v0.5.0, 1706 lines): - honker's Rust binding exposes the exact surface shape alkstore wants (queue claim/ack/visibility, streams with tx-aware offsets, notify/ listen, leader-elected scheduler, outbox, locks/rate-limits/results) — the unified-API question shifts from shape-invention to contract- pinning on that surface (new 'Interface finding' section) - honker's own processing-guarantees table (per-binding auto-checkpoint vs manual offset save) is the named seam a single-crate contract cleans up - honker-rs is sync-only (std threads, no tokio) — SQLite side is a port-and-adapt under any posture, folded into driver-conflict corrections + OQ-ST-03/04/06 refinements - pgboss-rs LISTEN/NOTIFY absence (verified earlier) now stated as the substantive fork-or-derive comparison point (OQ-ST-05)
Languages
Rust
99.4%
Python
0.5%