Repository navigation
Published on 2026-10-12 from main commit 8937dba, with content identical to the approved candidate 412f701 prepared on 2026-10-11.
The HTTP run API now accepts an optional conversationKey to keep related external events in one persistent Slack thread. idempotencyKey remains separate for event deduplication. Queued events preserve the thread's existing Claude/Codex session; deleted roots are replaced once, while inaccessible roots return an error without starting a separate conversation. Responses expose thread timestamps, reuse flags and permalinks.
This focused stable backport includes additive database migrations 32/33 and the compatible dependency-lock security refresh. It does not promote unrelated beta runtime changes.
Validation: 3,196 automated tests passed with 24 environment-dependent skips; static/security/secrets/DCO/audit and both Node CI legs passed. Real Slack/native-engine API context, process persistence, queueing, deleted-root recovery, aliases/isolation and deduplication passed. Live approved-user Slack continuation/stop and actual bot membership removal/restoration were explicitly deferred by an organization admin and remain unpassed.
The signed release evidence includes checksums, source/build metadata, dependency and runtime-image inventories, model inventory and the exact built runtime-image archive. Verify checksums and GitHub artifact attestations as described in docs/MAINTAINER-RELEASE.md.
The runtime-image archive is published in two byte-preserving parts because it exceeds GitHub's per-asset limit. Follow RUNTIME-IMAGE-DOWNLOAD.md to reconstruct the original signed archive and verify its checksum and attestation. The original complete artifact is also linked from the successful release evidence workflow.