Repository navigation
feat(risk-fork): persist bounded worker boundary observations - #489
Conversation
jmborden1112-beep
left a comment
jmborden1112-beep
left a comment
There was a problem hiding this comment.
LGTM
Needs Fixing
None found for refreshed head 463e7f76a59c3c73b0919e739f2534164695c267, tree 710e6c543e38d58d3c54db9714610c16ea287400.
Requires Human Review
None for authorized source merging. Operational qualification remains separate.
Recommended Optional
None.
Create Follow-up Issue
Existing #375/#301/#302/#303 retain production requirements.
Full changed source, versioned migration, PostgreSQL catalog/role contracts, worker retirement conflict resolution, bounded recorder and diagnostic tests were reviewed. The candidate preserves #499 security fixes and current E2B policy. Focused diagnostics24pass/10PGskips, full managed417pass/175PGskips, hosted artifact16/16 and offline packed consumer pass; fresh source integrity6ea1af7a and clean diff verified. Every applicable exact-head CI check, including PostgreSQL, must pass before merge.
Workflow Trace: inherited real Codex source/privacy and operations/test reviews, root canonical rebuild, final signed head/tree verification and managed suite. Authorized second owner-controlled account approval; no third-party certification, provider call, spend, publication, deployment, activation or live protection claim. No protection bypass.
Codex Review SummaryThis 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. |
Worker boundary failures now produce bounded, durable diagnostic observations without copying provider exceptions or inferring successful cleanup. The recorder retains one pending append per fixed boundary, reports unknown acknowledgements, and exposes only ingested unconfirmed buckets. Telemetry schema v11 adds explicit worker settings while preserving frozen v1–v10 contracts.
Refreshed against main
1c79aac3a5abf6a3e59cfa6b420e5660de98c067. The worker conflict preserves #499 retirement/security behavior; generated artifacts were rebuilt canonically. Final tree710e6c543e38d58d3c54db9714610c16ea287400contains 28 intended paths.Validation: focused diagnostics24 passed/10 PostgreSQL skips; full Windows managed417 passed/175 database skips, zero failures; core647 passed/151 platform/database skips on the refreshed #488-based candidate; hosted artifact16/16 and packed consumer142 files passed; fresh merged-source integrity
sha256:6ea1af7a36f114eefc3bc235edd3a385d49b11b1d0f68b95e015a53db92d0c23; clean diff. Fresh exact-head Linux/PostgreSQL and hosted checks are required before merge.Observations are
host_worker_self_attested, not independent provider or production qualification. Source-only/default-off posture and incomplete issues #375, #301, #302 and #303 remain unchanged. No provider call, spend, publication, deployment or activation occurred.