fix(plugin): keep resolved checkpoint deferrals closed - #771
fix(plugin): keep resolved checkpoint deferrals closed#771rohanpoudel2 wants to merge 3 commits into
Conversation
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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bbbaca48e8
ℹ️ 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".
sylvesterkaczmarek
left a comment
There was a problem hiding this comment.
resolvedCoverageSurfaces() trusts any terminal current surface's authored id. Since the live draft schema allows coverage.surfaces[].id, a later draft can reuse a historical deferred surface ID on an unrelated surface and clear that deferral. Match the ID to the historical surface identity, or strip/reject authored IDs, and add a spoofed-ID regression.
Summary
Fixes #741.
Interim scan checkpoints intentionally preserve deferred coverage so later writers cannot erase unfinished work by omission. That preservation also restored a linked deferral after the final draft had explicitly given every referenced surface a terminal disposition. The restored row downgraded otherwise complete coverage to partial and made the canonical result contradict the final draft.
Treat a deferral linked through
surfaceIdsas resolved only when every referenced surface has an unambiguous terminal outcome in the current draft. Historical checkpoint files remain unchanged.Changes
needs_follow_upsurface only when all of the deferral's surface references resolve.Testing
pnpm --dir plugins/codex-security/mcp-app exec node --test tests/test_artifact_scan_draft.mjs— passed.pnpm --dir sdk/typescript run test:mcp— 23 passed, 0 failed.pnpm run typesfromsdk/typescript/— passed; Node 25 emitted the repository's unsupported-engine warning.pnpm run formatfromsdk/typescript/— passed.uv run --no-project --with ruff==0.16.1 python -m ruff check --config plugins/codex-security/pyproject.toml .github/scripts/check_plugin_source_compatibility.py .github/scripts/test_check_plugin_source_compatibility.py plugins/codex-security— passed.uv run --no-project --with ruff==0.16.1 python -m ruff format --check --config plugins/codex-security/pyproject.toml .github/scripts/check_plugin_source_compatibility.py .github/scripts/test_check_plugin_source_compatibility.py plugins/codex-security— 137 files already formatted.python .github/scripts/check_plugin_source_compatibility.py— passed.git diff --check— passed.pnpm run test --seed 12345was attempted on unsupported Node 25 and was not used as passing validation. It reported seven failures in unchanged deduplication-review fixture cases, one unchanged workflow-fixture parse failure, and one ZIP-path stress test exceeded 30 seconds but passed in an isolated rerun. The broader run later stopped producing output and was interrupted. Focused reruns reproduced the first two unrelated failures; supported Node 22, 24, and 26 remain covered by hosted CI.Risk and rollout
The reconciliation rule is limited to deferred rows with a nonempty
surfaceIdslist whose every reference resolves to one terminal surface. Missing references, follow-up outcomes, and duplicate semantic surfaces remain deferred, so the existing loss-prevention behavior stays in place. No public CLI, schema, stored-artifact format, dependency, or migration changes are required.Public disclosure review