Repository navigation
feat(worker): add production runtime - #53
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
oneshot | da65a16 | Sep 09 2026, 06:30 PM |
SuPuHe
marked this pull request as ready for review
September 9, 2026 18:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a runnable production worker process for durable OneShot settlement and recovery.
Scope and acceptance criteria
Dockerfile.worker, worker scripts, and documented environment contract.Product and security invariants
Invariant notes:
Privy policy identity is re-observed, Arc receipts are identity-bound, Graph and Vertex remain candidate/advisory only, and settlement permission is never inferred from external-index absence or delay.
Validation
Commands and results:
The first CI run exposed a 500 in the production-runtime E2E because its API-side
IntentLedgerwas missing requirednowandnextAttemptIddependencies. Commitda65a162308c2652807672f32919c7fe431876fcsupplies deterministic dependencies; the test still asserts create 202, COMMITTED, replay 200, and exactly one submission.Independent review evidence
Gate A — original worker-runtime candidate
c38511c3981bbd70c6f4abd7a4ce469000cda87852ec4ffc958e5515d5a47b29d290ee6aa48ac5053b23a3c4401d68dd1e4ca540f00fece7a6eabed9free-pi-cli/glm-5.3-flashVERDICT: PASSGate A — E2E fix candidate
Base commit SHA:
c38511c3981bbd70c6f4abd7a4ce469000cda878Reviewed staged tree SHA:
10f94fa9a5e8f5345ff92afd5b1d16497e53c977Committed head SHA:
da65a162308c2652807672f32919c7fe431876fcCommitted tree SHA:
10f94fa9a5e8f5345ff92afd5b1d16497e53c977Reviewer tool/model:
free-pi-cli/glm-5.3-flashVerdict:
VERDICT: PASSFindings/residual risks: Testcontainers E2E and Docker image build require a container-capable environment; worker test sources are outside the current tsc project.
The current committed tree equals the Gate A reviewed tree.
Gate B — exact remote PR head
Pull request URL/number: feat(worker): add production runtime #53
Remote head commit SHA: pending CI
Remote head tree SHA:
10f94fa9a5e8f5345ff92afd5b1d16497e53c977Reviewer tool/model: pending
Verdict: pending
Findings or residual risks: pending
Gate B reviewed the current remote head and matches Gate A's approved tree.
All applicable CI checks pass.
Risk and rollback
da65a162308c2652807672f32919c7fe431876fcor redeploy the prior API/worker image; durable UNKNOWN intents remain reconciliation-bound.Human merge