Automate research investigations with Local Codex

[Techris93]

Summary

• add a durable, revisioned research investigation pipeline
• run bounded static intake and optional verified-package comparison before queuing minimized Local Codex analysis
• require analyst acceptance or rejection for every grouped proposal and preserve separate verdict, sandbox, disclosure, and publication gates
• add CLI, privacy minimization, failure recovery, strict structured-output compatibility, and operator documentation

Verification

• 393 Core tests passed, 14 existing warnings, 4 subtests passed
• MkDocs strict build passed
• real disposable npm intake and ChatGPT-subscription bridge run reached awaiting_review with all three jobs complete
• real model output normalized from 194 raw list entries to 19 grouped review cards

[cloudflare-workers-and-pages]

Deploying secopsai with    Cloudflare Pages

Latest commit:	433095b
Status:	✅  Deploy successful!
Preview URL:	https://3ebf698f.secopsai.pages.dev
Branch Preview URL:	https://codex-research-investigation.secopsai.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying website with    Cloudflare Pages

Latest commit:	433095b
Status:	✅  Deploy successful!
Preview URL:	https://9fea5287.website-bks.pages.dev
Branch Preview URL:	https://codex-research-investigation.website-bks.pages.dev

View logs

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 433095b35d

ℹ️ 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".

[chatgpt-codex-connector]

Restart stale running pipelines on resume

If the CLI process is interrupted while the pipeline row is still running (for example after a collection step is marked running but before the exception handler can mark it failed), this early return leaves the pipeline permanently stuck: start_investigation_pipeline also treats running as active and returns the stale record, so the documented retry-from-checkpoint path cannot recover it. Consider detecting stale/running steps and either marking them failed or continuing from the checkpoint instead of returning immediately.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Reconcile terminal AI jobs before returning

When a pipeline is awaiting_ai and the operator is not adding a reference, this returns before checking the Local Codex jobs. If the post-completion _notify_research_pipeline hook failed once after the job was saved, or a queued bridge job was canceled through the intelligence job API, the jobs can already be terminal while the pipeline remains awaiting_ai; subsequent resume calls cannot replay reconcile_intelligence_job, leaving review proposals unreachable. Resume should inspect/reconcile terminal AI jobs before deciding nothing needs to be done.

Useful? React with 👍 / 👎.