Repository navigation
docs(jarvis): record first update restart results - #43
chrisohearn merged 3 commits into
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e448db92d3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
🛡️ Codex Security Review · Automatically triggeredSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
|
Codex Review: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
🛡️ Codex Security Review · Automatically triggeredSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
c7285ec
into
integration/mcp-events-20261109
Record the first coordinated update's observed restart behaviour in decision 0013, replacing the pending plan with dated results. Separate the eight running turns from the 59 queued messages: seven resumed once, none duplicated, and five providers had no running coverage. Use the 07:47:57 snapshot's queue counts: 21 completed, two running and 36 queued.
Investigate the missed Codex Pro continuation using read-only live events and the effect outbox. A continuation was prepared before shutdown cancellation, then automatic settlement won before its effect completed. Track the existing recovery race in #42 and
r2/restart-gap/codex-pro-run-not-resumed; completing verification does not close that repair.Validation: compared before, +3 and +10 snapshots and durable event/outbox timestamps;
vp run check:changed origin/integration/mcp-events-20261109passed. The decision remains under 200 words. No runtime, migration, updater or upgrade-register changes. No new service update.Model: gpt-6.1-sol. Harness: Codex in T3 Code.
Addendum verified on all seven continuations: same provider instance, complete model selection/options, provider thread, and visible restart notification. The before/after snapshots identify the runs; read-only run/message projections supply the model selections and notification payloads, which those JSON snapshots omit. Source inspection establishes native empty input for the five Codex continuations and shared prompt dispatch for both Claude continuations; one Claude prompt includes cancelled-background-work notes. The global continuation setting is absent and its contract default is true; the audit baseline has no pending requests. All eight running-source provider-thread records have strong native refs.
Coverage limit: later queued-message completion and ordering remain unverified beyond the 07:47:57 snapshot. P2 follow-up #45 tracks any later reconciliation; this record does not claim eventual exactly-once delivery for outstanding messages.