Repository navigation
[Task] Implement PostgreSQL event admission with enforced local execution authority and offline bootstrap #8658
Description
Program: #8194
Parent: #8229
Related requirements: #8200, #8236, #8199, #8221
Accepted prerequisite: #8655 main-promotion acceptance
Status and authoritative design
Accepted, 2026-10-08. PR #8660 merged as a866284727cce19068b417a908bbe4a2573815d5. Its tree cad830aba6d6bd55d1cb58ab6a47ecffbbd642bc exactly equals reviewed/tested head bbe9a4823553ee80ba7492655e92e47d5199f260. Main and the shared program branch were verified at this merge. All nine criteria below are accepted within the declared offline PostgreSQL/isolated local-runtime scope.
The acceptance record maps every criterion to actual hosted evidence and records full hashes, 158 admission cases, execution-cycle tests, repository CI, package proof, intentional skips and limitations. Independent review is APPROVE / HIGH and Greptile is 5/5 on the same head. The checkpoint-observer defect was corrected and verified before merge. No live transport, outbound messaging, publication or parent closeout is implied; #8661 owns the next seven-package prerequisite.
Implement the approved admission/guard/bootstrap checkpoint, including its scope clarification. Conceptual approval binds 978635eb…, guard approval 73590232…, and bootstrap approval 47226ac2…; full hashes and canonical text are in that checkpoint. Source review binds 12365b98791b5333fcbe9781abd0346314fc195b; refresh the exact implementation base after #8655. This issue summarizes acceptance without replacing the canonical safety contract.
Outcome and supported scope
Deliver one transport-independent, EF Core/PostgreSQL durable pre-instance admission boundary, an enforced Core-neutral execution guard, and a reviewed bootstrap path for one isolated execution host using in-process LocalWorkflowRuntime. An eligible synthetic Slack event becomes durably accountable before acknowledgement eligibility; duplicate/reordered delivery, uncertain creation/start and restart cannot silently lose work or replay ambiguous effects. The later Socket Mode adapter can call this boundary.
Use existing tenant/DbContext/migration, deterministic process-fixture, credential lifecycle and exact-instance grant patterns. Preserve public signatures/constructor compatibility, unowned workflow behavior, activity/package identities and Core's dependency boundary. Add only the reviewed necessary guard extension; do not introduce another credential store, generic queue/framework or universal provider/adaptor promise. Admission-store concurrency proof is not distributed workflow-execution support.
Acceptance criteria
- Trusted identity and durable admission. Resolve tenant/environment, stable logical Slack app/workspace-or-enterprise installation, channel, logical subscription and pinned published definition/content from trusted configuration. Apply human-message/loop filters before admission. Use unique
(tenant, environment, installation, subscription, provider-event-id)identity, independently of envelopes, credentials, reconnects or token rotation. Edits retain identity; explicit subscription fan-out is intentional; reinstall reconciles the namespace; retirement/fresh activation prevents automatic reuse and old-event replay. Commit admission before returning acknowledgement eligibility; failed/uncertain writes never report acknowledgement success. Indexed bounded recovery and capacity accounting share the ledger's transaction/revision contract. - Explicit states and materialization uncertainty. Implement
Admitted → Creating → Materialized → StartPreparing → StartAuthorized → ExecutionObserved, with conservativeRecoveryRequiredand explicitly qualifiedTerminaldispositions. Allocate the instance ID durably before real insert-only workflow creation. Matching instance identity does not prove the saved-notification chain completed. Unknown insertion/notification effects require reconciliation without repeating creation/notifications; no Pending-only inference or cross-store atomicity claim. - One-shot authority. Only definitive success of the first permit commit returns a process-local, nonserializable capability, consumed atomically before runner entry. Persisted StartAuthorized is never invocable authority. Uncertain commit/readback, restart, duplicate request or lease expiry cannot mint/reset a capability or replay effects. Duplicates preserve known state; classify genuine uncertainty conservatively. Record the authority linearization boundary: already-issued/delayed authority may run after withdrawal and is not retroactively cancelled by fencing or a final read.
- Enforced execution guard. Implement the checkpoint's optional Core-neutral guard/preflight, built-in runner authorization before WorkflowExecuting/Started, and invocation-time guards for every public ExecuteAsync/Pipeline/Setup/Build delegate, including cached/reset/replaced compositions. Only the authorized built-in runner uses a private internal composition path. Bind immutable trusted identity/revision/attempt/pinned content plus exact prepared context, input, graph, scheduler plan and ExecuteDelegate; reject mutation, copied state, concurrent reuse and distinct same-ID contexts without rebinding. No ambient or serialized permission. Audit earlier registry/materialization/descriptor/notification callbacks; unsupported effectful chains disable support. Validate both classic and ShellFeatures registration.
- Local adapter, owned controls and continuation. Intercept the actual runtime client factory; preserve execution ownership through all trailing writes/unwind using accepted Keep execution cycles tracked through checkpoints and final writes #8652. Ordinary callers cannot mint initial authority. Owned Cancel/Delete/Import/UpdateBookmark/Alteration fail before callbacks, notifications or writes; unowned operations remain compatible. Exclude management mutation/import routes and Alterations from this host with startup/route inventory validation. A legitimate continuation requires a definitively recorded committed checkpoint/full-state-and-bookmark fingerprint, unconsumed lineage and serialized invocation lane after the previous owner's final writes/unwind. Forged Suspended state, imports, stale consumed snapshots, missing bookmark owners and ambiguous checkpoints cannot authorize execution. Retain instance ownership while startable even after dedup cleanup.
- Withdrawal and recovery. Coordinate authoritative ledger withdrawal before any supported unpublish/disconnect/tenant-delete entrypoint reports completion; fail closed if coordination is absent. A failed subsequent external mutation stays withdrawn with an explicit reconciliation disposition. Cover both sides of the start-authority race without claiming cross-store atomicity or provider-call cancellation. RecoveryRequired exposes safe operator-visible health and requires explicit audited resolution; no automatic effect replay.
- Retention, expiry and capacity. Require explicit validated payload retention, identity horizon, event-age/skew/invalid-or-late disposition, capacity and cleanup authority; fixture values are declared and there are no implicit production defaults. Terminality requires actual Completed, SuppressedBeforeStart or audited Resolved conditions. Resolved includes quiescence of every outstanding capability/delayed authorized owner, no active execution and no unknown effects; lease expiry/runner return are insufficient. Suspended/long-running/ambiguous work is nonterminal. Use terminal-clock origin and atomic state/revision cleanup; test duplicate/admission/claim/cleanup/capacity races, late forgotten identities, namespace retirement and no double release.
- Safe bootstrap and outbound boundary. The same guarded host, with admission inactive, provisions/verifies an allowlisted predefined workflow with fixed identity/content fingerprint and an inactive trusted subscription from explicit host configuration. Validate publication/provider chain, no autonomous start, existing-content match and all bindings before explicit activation. Repeat bootstrap verifies rather than overwrites. No arbitrary instance/bookmark imports, owned-record resets or second unguarded store-sharing host. Ingress/bootstrap grants no outbound authority; existing exact-instance credential-use grants remain separately required and default-deny.
- Documentation and integration. Add the dated ADR and supported setup/recovery/retention guide, honest delivery guarantees, unsupported paths and lifecycle entrypoint inventory. Keep grants/credential infrastructure reused, sanitized health/export/log data free of synthetic credential markers, and accepted execution/drain ownership intact. Obtain exact-head lead integration review, independent review and hosted proof below; report limitations and intentional skips explicitly.
Required hosted validation
Use real PostgreSQL with two independent processes, deterministic barriers and process termination/restart, reusing existing fixture conventions without sleeps. Use real insert-only workflow creation, actual built-in runner/default pipeline and actual awaited final writes. A single execution host remains the supported runtime; a competing process must never bypass its admission ownership boundary.
Cover duplicate envelopes/reordering/restart, trusted scope conflicts, fan-out/edit/reinstall/retirement; fault points before admission commit, admission-before-ack, uncertain insert/notification, permit commit uncertainty, definite capability before consumption, consumption before entry, and effect-before-final-write. Assert actual notification/middleware/activity counters and durable dispositions, not merely method returns. Uncertain cases must not replay effects or mint authority.
Hold a valid capability while competing client/dispatcher/legacy/HTTP/direct-runner and public pipeline/delegate paths attempt execution: zero start notifications/middleware/activity effects, then exactly one authorized entry. Exercise mutable-context rejection, earlier callbacks, cached delegates and both registration paths. Prove real suspension plus final-write/unwind followed by legitimate bookmark continuation; forged/imported/consumed snapshots cannot manufacture it. Test withdrawal through every supported actual entrypoint, delayed authorized owner versus operator resolution/cleanup, true-terminal expiry, explicit age/skew/late policy, cleanup/capacity races, and bootstrap positives/mismatches/forbidden routes. Include unowned compatibility and no-grant outbound denial.
Build affected production closure for net8/net9/net10 and run targeted tests on the repository's supported test framework, with exact source/input hashes, actual PostgreSQL/container/process identity and sanitized per-method results. Fail zero-result or unexplained-skip proof; no live Slack event, credential, transport acknowledgement or remote message-post proof is inferred. Lead owns the final CI closure and acceptance.
Separate future acceptance and live activation gates
Required later pilot outcomes remain under #8236/#8229: real Socket Mode ack/reconnect/restart integration; additive WatchPublicChannelMessages/CreateMessage and explicit legacy Token compatibility/migration; durable outbound call-start/timestamp/unknown-post handling; live human-message → workflow → same-thread reply; and operational health/reconciliation/runbook acceptance. This offline leaf does not close those parents.
Before live activation the owner supplies retention/capacity/late-event settings, subscription/delegation and exact reply-binding authority, reconciliation/operator responsibility, and sandbox app/workspace/channel consent plus credential bindings. No numeric choices, credentials or automatic grants are approved here; explicit fixture settings suffice for this offline contract. Generic management/import/alteration support and distributed/Proto.Actor adapters remain unsupported unless a concrete requirement warrants separate design review; they are not invented initial-pilot gates.
Delivery and ownership
Read-only discovery on 2026-10-08 found no matching existing admission Task or functional Socket/admission PR to adopt. Refresh again when claiming. Native parent is #8229; the only blocking dependency is #8655. References to #8236/#8199/#8221 and accepted #8652/#8345/#8362/#8376 supply requirements and reusable infrastructure, not additional blockers.
Work only in an isolated worktree. After promotion, branch from refreshed codex/elsa-integration-program with accepted main integrated; preserve source history and existing user changes. Use Sol 6.1 for the coupled implementation and bounded Luna 6 Extra High workers where appropriate. The lead retains integration, independent review, exact-head CI and final QA; hosted heavy proof is required while the shared local machine is loaded. No live Slack setup, credential access, message posting, publication, deployment or archival is authorized by this Task.
Activity
sfmskywalker commentedon Oct 8, 2026
Claimed as the sole active delivery Task after #8655 exact-main acceptance. Main and shared target
codex/elsa-integration-programare179749636fd4ddce07b186d4fe3456a43fa91162; the native dependency is satisfied, and refreshed Core intake found no matching open admission/Socket/bootstrap implementation PR.Sol6.1 owns the coupled implementation in isolated branch
codex/durable-event-admission-8658; the lead owns a separate integration worktree and retains final integration/review/QA. Existing user changes remain preserved. The first concrete contract checkpoint is aligned with the approved design: distinct admission/EF/PostgreSQL modules; an optional Core-neutral guard with a runner-local opaque revalidation result (no public execution authority); exact prepared-context binding with runtime-distinct input types preserved; narrow selected-provider insert-only bootstrap followed by audited publication/indexing; and separate explicit active-admission and retained-identity capacity bounds. No live numeric policy or credential grant is selected.All nine acceptance groups and the two-process PostgreSQL/real-runtime hosted proof remain required. Hosted heavy verification will follow coherent source review; no implementation or runtime result is yet accepted. The next transport/outbound leaf remains dependent on these concrete interfaces; no second Task is activated. Live Slack transport, legacy compatibility, outbound unknown-write safety, thread reply and operations remain later required outcomes.
sfmskywalker commentedon Oct 8, 2026
Implementation checkpoint — 2026-10-08
#8658 remains the sole active delivery Task (In Progress / Assigned / Verification Pending). #8655, #8294 and #8286 are accepted and closed; the program and #8229 remain open.
Implementation is split across isolated worktrees: Sol 6.1 owns the execution guard/local adapter/bootstrap orchestration, a second Sol 6.1 owns PostgreSQL persistence and process fixtures, and Luna 6 Extra High prepares hosted verification. The lead owns shared wiring, integration, review and final proof.
The first contract review requested corrections before runtime acceptance. Those corrections include immutable admitted configuration and event fingerprints, separate activation epochs, audited resolution fields, explicit storage bounds, and strict timestamp/deduplication boundaries. Pipeline composition must also remain bound to the authorized invocation through notification callbacks. The PostgreSQL implementation now has its first local commit; review and fixture work continue.
Bootstrap uses the existing Management definition-state codec and an atomic insert boundary. A pre-existing unverified definition cannot authorize publication replay. Session locks serialize cooperating bootstrap calls; supported-host validation must exclude other writers and autonomous execution. No universal store-sharing guarantee is claimed.
Hosted verification will require reviewed case identities to match both test results and observed runtime effects, including real PostgreSQL/two-process races and actual process/container cleanup. No .NET/runtime proof has run for this implementation yet, and no acceptance criterion is marked complete from source inspection. No publication, deployment, publisher cutover, live Slack setup or message delivery occurred.
sfmskywalker commentedon Oct 8, 2026
Source review checkpoint, 2026-10-08. Verification remains Pending; #8658 is still the sole active delivery Task.
The lead integration worktree now contains the PostgreSQL ledger/bootstrap implementation, classic and selected-provider Shell registration, and 40 provider cases mapped to sanitized observations. This includes actual two-process cases for duplicate/capacity races, commit-response loss, withdrawal ordering, bootstrap serialization and cleanup. These are source mappings, not executed test results. The hosted catalog remains explicitly incomplete until the real execution-host cases are integrated.
Independent review identified and corrected two retention replay risks in source: PostgreSQL timestamp precision/clock rollback shortening retention, and widening the accepted event-age window after identities could have been purged. Dedicated PostgreSQL regressions now discriminate those corrections. The reviewed 39-case provider checkpoint and receipt boundary had no remaining source findings; one additional unknown-admission-response case has since been integrated. The receipt-policy suite passed all 10 checks both normally and with Python optimization.
Runtime review is still requesting changes. Corrections are underway for ownership registration before creation, graph-edge and completion-callback identity binding, fixed workflow/activity composition, and public activity APIs that could otherwise bypass workflow entry. The supported host will use explicitly reviewed fixed compositions; unsupported contributors remain excluded. Public activity entry must remain denied for owned contexts even during an authorized invocation.
No .NET build, PostgreSQL fixture execution or runtime proof has yet run for this task. Nothing is accepted from source review alone. No live Slack setup/messages, publication, deployment, publisher cutover or archival occurred. The full program and remaining transport, compatibility, outbound and operational outcomes remain open.
sfmskywalker commentedon Oct 8, 2026
Delivery checkpoint: draft PR #8660 is pushed at
a93563fffcc485a2440bceeca350653d7ad07362.The isolated runtime now includes reviewed ownership/continuation guards, actual withdrawal-before-pinned-retraction, fixed execution-cycle/variable middleware, classic/Shell host policy tests and a same-host test using existing durable exact-instance credential grants. Review caught and corrected a missing active-connection prerequisite in that last fixture. The dated ADR and supported setup/recovery guide are included.
The source-mapped catalog contains 127 cases (40 provider, 74 runtime/process/outbound, 13 host policy). These counts describe authored coverage, not passing runtime evidence. The manifest remains explicitly incomplete while final bootstrap/retention coverage and full verification continue. Eleven receipt-policy tests pass normally and with Python optimization; the ADR index and diff checks pass. Independent reviews are bounded source approvals, not task acceptance.
Earlier hosted verification found a Core guard fixture graph error, two worker registration/population API errors and a net8/net9 callback-comparison overload ambiguity. All have source fixes in this head. Earlier package testing passed 450 existing integration tests before the worker compilation failure; no new PostgreSQL runtime pass is claimed. Studio net9 Razor diagnostics occurred on unchanged source and are being rechecked on the fresh build without a speculative source patch.
Fresh hosted runs include Packages, execution-cycle proof and consolidated package proof. Final exact-head CI, independent review and Greptile gates remain required. Task #8658 stays the sole active delivery task; parent #8229 and program #8194 remain open. No live Slack, publication, deployment or publisher cutover occurred.
sfmskywalker commentedon Oct 8, 2026
The authored admission catalog is ready for full hosted verification at PR #8660 head
a47c6d946f296946003d147c16e0a5d0cef39ae2.Independent source review and the nine-acceptance-criterion coverage audit closed the remaining identity-reconciliation, forbidden-bootstrap-graph and business-telemetry regression gaps. Exact source preflight matched 151 selected PostgreSQL cases to 151 catalog rows (50 Facts and 101 Theory rows), including every emitted identity/fact/assertion key and all 22 process-case worker bindings. The catalog completion flag describes authored coverage only; no PostgreSQL runtime acceptance is claimed.
The full admission proof, Packages, execution ownership proof and consolidated package proof are running. Exact combined-head independent integration review is also underway. The board now records In Progress / In Review / Verification Running; this remains the sole active Task.
At earlier head
a93563fff…, execution proof passed 879 tests with zero failures/skips and all 12 production builds. The package run compiled Admission and Studio Designer across net8/net9/net10 before the two now-corrected fixture compile errors stopped it. The previous Studio Razor diagnostics did not recur. These earlier results are diagnostic evidence, not substitutes for final-head gates.The fresh source/release audit also confirms all 35 advertised 3.8.x/3.9.0 refs are in their source main and Core main, with all 73 ancestry checks passing. Latest published releases remain 3.9.0 in Core, Studio and Extensions. Unmerged source PR dispositions and the program's remaining cutover, publication, transport, outbound and operational outcomes stay open.
sfmskywalker commentedon Oct 8, 2026
Hosted verification checkpoint for PR #8660 at
a47c6d946f296946003d147c16e0a5d0cef39ae2:The task remains the sole active delivery leaf, now Assigned / Verification Failed while corrections are integrated. A newly reviewed delayed-caller race is also being checked and corrected: an old Materialized snapshot can acquire the local owner after a prior run has finished, then incorrectly classify its newer checkpoint as recovery. The fix must preserve conservative handling of genuinely unknown commits. No admission acceptance or merge is claimed. Parent program and operational/live Slack acceptance remain open.
sfmskywalker commentedon Oct 8, 2026
Full offline admission proof passed at
90d8a70633b4d9174f81b2e3e70276e308826e1d, tree0d292eefd01e60108c3d5e96409308fdc2f7a1ea: https://github.com/elsa-workflows/elsa-core/actions/runs/37726660308Lead revalidation of the downloaded receipt against the current tracked source passed. Receipt SHA-256:
c019a9c53ec6935613b087ee7b85413f0022e637ba437beff3b5691a25e039a6. Independent acceptance audit is in progress.This establishes the bounded offline proof, not final task acceptance: remaining repository CI and required Greptile review still gate merge of #8660. The task stays In Progress / In Review / Verification Running. Publication, live Socket Mode acknowledgement, outbound messaging and operational pilot outcomes remain separate program work; parents remain open.
sfmskywalker commentedon Oct 8, 2026
Independent QA now confirms PASS / HIGH for the complete scoped offline admission proof at
90d8a70633b4d9174f81b2e3e70276e308826e1d(tree0d292eefd01e60108c3d5e96409308fdc2f7a1ea). The audit independently matched the hosted artifact digest, all 9,348 tracked source-input hashes, all 154 observation/test identities, 22 multi-process cases, actual crash/restart records, all 24 production framework builds, and verified container cleanup. All nine leaf acceptance criteria have evidence within the approved offline, single synchronous local-executor scope. Receipt SHA-256:c019a9c53ec6935613b087ee7b85413f0022e637ba437beff3b5691a25e039a6.The separate execution-cycle proof also passed independent QA at the same head: 879 tests, zero failures/skips, five fixture builds and 12 production framework builds. Receipt SHA-256:
e922dcc5fc109f517cb53f0b6e62846a85df8b8c6c2585eeb40f0012f52bce60. This receipt binds its 12 declared project/script inputs; the admission receipt provides the complete tracked-source inventory.CodeQL, Code Quality and Integration program tools are now green. Broad Packages, consolidated package proof, package impact artifact proof, ordinary PR CI and Greptile remain in progress. No source change or duplicate review request was made. Merge/task acceptance is still pending these gates; board remains In Progress / In Review / Verification Running. This does not accept live Socket Mode, outbound messaging, distributed execution, publication, or the parent program outcomes.
sfmskywalker commentedon Oct 8, 2026
Review found material rework at
90d8a70633b4d9174f81b2e3e70276e308826e1d. Greptile returned 4/5 with a post-checkpoint observer failure. Lead and independent source review confirm that an exception after the definite checkpoint commit can reach inner/outer recovery catches, demote a healthy suspended checkpoint and block its legitimate continuation. Independent source approval is withdrawn. #8658 returns to In Progress / Assigned / Verification Failed while the bounded fix and actual PostgreSQL regressions are implemented in the existing isolated worktree.The existing 154-case admission proof and 879-test execution-cycle proof remain valid observations for their declared cases, but miss this throwing-observer scenario and do not establish final acceptance. Broad unit/integration completed with 5,046 passed, zero failures and 144 explicit UserTasks provider skips; the actual PostgreSQL admission/credentials fixture passed 187/187 without skips. Component tests passed 226 with one explicit clustered skip. Coverage, ordinary PR CI and package-impact proof passed; final package builds are still running. Skipped cases are not claimed as passed.
The fix must preserve conservative recovery when checkpoint commit throws before returning, and for failures before checkpoint confirmation. A later observer failure must leave the confirmed checkpoint/bookmarks/revision intact and allow genuine resume. Fresh exact-head review and hosted proof will follow. #8660 remains unmerged; no parent closeout or live/publication acceptance.
sfmskywalker commentedon Oct 8, 2026
Fresh offline admission proof passed at
bbe9a4823553ee80ba7492655e92e47d5199f260, treecad830aba6d6bd55d1cb58ab6a47ecffbbd642bc: https://github.com/elsa-workflows/elsa-core/actions/runs/37729085353c9dd1a404535b4dea365ed1f62461a2af6db5d283285676974c287c79b1fa625.09246346f44488ab3124302cc106712d380e54b038a524dcfd716e6cce733f2d.Independent source and scoped hosted-proof review are APPROVE/PASS with HIGH confidence on this head. Broader repository CI and required current-head Greptile still gate merge; #8658 remains In Progress / In Review / Verification Running. No live Slack, remote message, package publication or parent acceptance is inferred.
sfmskywalker commentedon Oct 8, 2026
Current-head repository CI checkpoint, not task acceptance.
Candidate
bbe9a4823553ee80ba7492655e92e47d5199f260, treecad830aba6d6bd55d1cb58ab6a47ecffbbd642bc.b126e2aa0074836fb76ea2818e39d9cae1952be7has exactly the candidate tree. NUKE's project summary reports 7,688; the extra 166 successful net8/net9 Studio Designer cases explain the framework-aware total. Performance application compilation does not establish benchmark execution..nupkgand 103.snupkg, version3.10.0-preview.5851, artifact11529713729, ZIP digest238056a2485bd25f3648687f0f1042e23e369210f1ab82f98e51740c242735e7. Metadata and upload-log consistency were verified; this does not establish the consolidated inventory or per-package consumer provenance.The consolidated package proof is still running. Merge and the nine acceptance checkboxes remain gated on that result, its evidence audit and the final head/base/review refresh. Publication/deployment steps were intentionally skipped; no packages were published by these runs. #8658 remains the sole active Task; #8661 remains queued behind its acceptance.
Sanitized independent audit SHA-256: PR
e7fa752fabdcecd66df7dbb3e35966a8a3d8763bba892560090c00804c1ebae1; Packages58346364014a17d14196cc971727a81f60be93cb26d496a726939ce4ce660909.sfmskywalker commentedon Oct 8, 2026
Accepted #8658 through merged PR #8660, within this Task's approved offline PostgreSQL and isolated local-runtime scope.
Reviewed/tested head:
bbe9a4823553ee80ba7492655e92e47d5199f260. Main merge:a866284727cce19068b417a908bbe4a2573815d5, parents179749636fd4ddce07b186d4fe3456a43fa91162and the reviewed head. The merge tree is exactlycad830aba6d6bd55d1cb58ab6a47ecffbbd642bc, equal to the candidate and the successful PR test-merge tree. Main and the sharedcodex/elsa-integration-programref now point to this merge; the program ref advanced without force. GitHub closed this Task through the merged PR.All required premerge gates passed on the same head: independent Elsa 3 APPROVE + HIGH, Greptile 5/5, repository CI, and all 21 review threads resolved. Copilot was requested but no delivered review is claimed. The confirmed checkpoint-observer finding was corrected and proven with three throwing-observer regressions plus a real committed-then-unknown control; unknown commits and earlier execution failures remain conservative.
Evidence retained by the successful runs:
11529466835; receipt SHA-256c9dd1a404535b4dea365ed1f62461a2af6db5d283285676974c287c79b1fa625.09246346f44488ab3124302cc106712d380e54b038a524dcfd716e6cce733f2d.11530816500, ZIP SHA-256d2593186fc9bd35f560b9a5fc72b505838397c215d06547d5f57fbcdd2c97e67; receiptb21f4c18a81b3f6448b29f8c4c8cb4c7c8b99f12235aa48a0de2824fe64834d1. Lead independently re-executed the byte-only artifact verifier; independent audit SHA-256ad37bc0544016ec91063e5dc1b93592a63a2e86c751cc8e9fb13a2c8d1a60953.This accepts one isolated synchronous LocalWorkflowRuntime execution host, with concurrent ledger/controller processes and sequential executor restart. It does not certify distributed/concurrent executors, Proto.Actor admission adapters, arbitrary management/import/Alterations paths, hostile trusted extensions, or raw external store writers. Package consumers are representative; consumer cache replay and generator regeneration were not independently rerun locally. Heavy runtime validation was hosted.
No live Slack credentials, Socket Mode acknowledgement/reconnect, remote posting, package publication, deployment, cutover or archival is accepted here. The seven nonpackable Admission/Connections modules remain deliberately excluded; #8661 is their next package prerequisite. Parents #8229/#8236/#8194 remain open with their transport, legacy compatibility, exact-instance outbound authority, unknown remote-write handling, live reply and operational outcomes intact. Other program migration/release/browser/updater/cutover work remains open. Post-merge automation is tracked separately; this acceptance relies on the verified identical tree and completed exact-head premerge gates, not an unverified claim about new main-run results.