Repository navigation
chore(deep-scan): reconcile finding convergence with main - #762
Hughhhhcoder wants to merge 8 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. |
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! 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". |
…lineage-convergence # Conflicts: # plugins/codex-security/mcp-app/src/deep-scan/artifact-validation.ts
|
Updated this branch with a normal merge commit ( Validation on the merged tree:
No force-push was used. |
|
@codex review |
|
Codex Review: Didn't find any major issues. You're on a roll. 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". |
…lineage-convergence
|
I refreshed this branch with the latest Validation after the update:
The focused regression coverage still exercises discovery validation, reducer validation, lineage convergence, and empty-artifact handling. |
|
Friendly follow-up at the one-week mark: this remains mergeable and ready for maintainer review on head |
# Conflicts: # plugins/codex-security/mcp-app/src/deep-scan/artifact-validation.ts # plugins/codex-security/mcp-app/tests/test_deep_scan_artifact_validation.mjs
|
Resolved the new merge conflicts with current main using a regular merge; no force-push was used. The lineage-based convergence behavior remains intact alongside the newer deep-reducer parsing and validation changes.\n\nValidation on the merged head:\n- deep scan artifact validation regression suite: passed\n- MCP app TypeScript typecheck: passed\n- Prettier check for both touched files: passed |
…lineage-convergence # Conflicts: # plugins/codex-security/mcp-app/src/deep-scan/artifact-validation.ts # plugins/codex-security/mcp-app/tests/test_deep_scan_artifact_validation.ts
…rgence' into codex/codex-security-lineage-convergence # Conflicts: # plugins/codex-security/mcp-app/tests/test_deep_scan_artifact_validation.ts
|
I merged current main normally and resolved the conflicts in the lineage reconciliation path and regression test. The alias-convergence behavior remains covered, with the test using the current TypeScript fixture.\n\nValidation on head 736e5e5:\n- Focused lineage regression test — passed.\n- Prettier check and git diff checks — passed.\n- Full MCP suite — 287 passed, 6 failed, 1 skipped. The local full-suite run was not clean because of environment-dependent startup, path, and bundled-artifact failures; the focused regression passed.\n- Typecheck remains blocked locally by module-resolution errors outside the changed files, so I am not claiming a clean package-wide typecheck. |
…lineage-convergence
|
Resolved the conflict with current base Validation on the merged head:
The PR is mergeable; CI is queued. |
Summary
PR #1912 incorporated the alias-consolidation case proposed here and shipped in
version 0.7.0, resolving #711. When the reducer merges two accepted aliases and
preserves all their source references, it counts zero new findings.
Changes
Merge current main into the contributor branch. The resulting tree is identical
to main.
Testing
The same alias merge was rejected in version 0.6.0 and accepted in 0.7.0. Ten
writer cases and twelve saved-result replays covered consolidation and
independent findings. After a coordinator restart with a local worker fixture,
the updated branch retained the findings and the correct no-new streak. All five
portable plugin checks passed.
Risk and rollout
There is no product change to release.
Public disclosure review