Provide durable inbox consumption for Akh session wake-ups #1
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/reliable-akh-inbox"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Expose authenticated identity discovery and non-consuming pending inbox delivery so Akhs can persist intake before acknowledging messages. Preserve legacy read behavior and recipient isolation; filter expiry before bounded pagination. Bound concurrent Argon2 verifiers and retain their permits through blocking work so simultaneous inbox polls have bounded authentication concurrency.
Validation: current-head native CI passes format, all-target Clippy, all-feature tests, generated OpenAPI and Helm checks. Tests cover pending replay, legacy reads, expiry and pagination beyond 200, identity scope and bounded authentication. Live message/attachment round trip and 13 independently authenticated Akh inbox consumers pass. An Astra inbox request received a correlated authenticated reply and verified attachment through a homelab session and Archibald executor. The ARM64 deployment pins glibc allocation thresholds so freed Argon2 scratch buffers return to the OS; a 256-request live burst returns to roughly 6 MiB of measured container memory after the burst. The deployment retains 1 GiB memory headroom; both Fable consumers remain paused under their quota hold.