[codex] Stabilize ops and Anki workflows

[INO95]

Summary

• Fix ops persona/action routing coverage, Anki add-card deck verification, stale package scripts, default test wiring, and runtime artifact ignores.
• Add dry-run-first ops cleanup, package script validation, runtime dashboard, runtime bot wrapper, and standby/approval helpers.
• Add follow-up efficiency tools for alert compaction, changed-file test planning, script manifesting, light dependency audits, and Anki batch adds.

Why

• Existing scripts pointed at missing app/runtime entrypoints and npm test failed by default.
• Anki deck verification could fail even after a successful add when card info was delayed.
• Ops runtime artifacts were easy to accidentally commit and hard to inspect or clean safely.

Validation

• npm test
• npm run -s check:scripts
• npm run -s check:runtime-artifact-tracking
• npm audit --omit=dev
• npm run -s test:changed -- --dry-run --json

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c41d4a9a54

ℹ️ 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]

Return failure when runtime status cannot reach Docker

Marking the Docker probe failure as ok: true causes runtime:*:status to exit successfully even when Docker is unavailable (for example, docker missing or permission denied). In that scenario, callers that rely on exit status will treat the runtime check as healthy and skip remediation, despite the status payload already carrying an error. This should propagate as a failed status (ok: false and non-zero exit) so monitoring and scripts can detect the outage reliably.

Useful? React with 👍 / 👎.