codesage-revalidate

Revalidate CodeSage findings

Review the owning feature again, apply the same evidence and identity gates as /codesage-review, and reconcile through codesage-review-state.

Parse and resolve

Require an absolute onboarded project path and exactly one selector:

• --finding <id>: locate one finding under $PROJECT/.codesage/findings/*.json.

Every .codesage/... path below lives under the project, not the session's working directory; always write it as $PROJECT/.codesage/....

• --feature <id>: select findings in one feature.
• --all: select across the project, grouped by feature.

--status defaults to open. --max-verify-findings defaults to 5 and caps new regression candidates sent to each feature verifier.

If no findings match, print the selector and available status counts, then stop. Warn before dispatch when the selection spans more than 50 findings or 20 features.

Prepare feature-local inputs

Use rev_$(date -u +%Y%m%dT%H%M%SZ) as RUN_ID. For each feature:

1. Run codesage-review-state inventory --project "$PROJECT" --feature <feature_id> --output <run-inventory.json> for fresh, complete feature metadata; do not use the budget-limited MCP list. If the CLI explicitly reports that this feature ID no longer exists, use the findings document's persisted entry_path, title, kind, and feature_files as a historical scope, record metadata_source: persisted-retired-feature, and disclose that it may not cover the current feature map. Other inventory errors fail this feature rather than silently falling back. If a retired legacy document lacks its file list, record a partial run and an unavailable scope; do not infer the slice from one finding.
2. Write the complete feature record under $PROJECT/.codesage/reviews/<RUN_ID>/features/. Normalize persisted feature_files to files when using historical scope. Union target finding paths missing from that list as explicit context paths so selected findings remain in the bounded plan, without pretending those paths are current mapped ownership.
3. Project only the targeted findings. Include ID, location, severity, category, title, summary, evidence, suggested fix, status, and optional magnitude and acknowledgement unchanged. Strip history. Run codesage-review-state sweep-acks --project <absolute-path> and exclude transferred source records from targets, directing explicit source-ID requests to their destination. Write their ID array to $PROJECT/.codesage/reviews/<RUN_ID>/targets/<feature_id>.json.
4. Collect existing entry and owned paths, save the requested path array, and call mcp__codesage__assess_risk_batch in batches of at most 100 unique paths. Run codesage-review-state check-risk --paths <requested-paths.json> --risk <response.json> for every batch before using scores. Truncation, missing or extra rows, duplicate paths, and invalid scores fail this check. Retry smaller batches or use CLI risk-batch --json from the project; never synthesize a zero score. If complete coverage remains unavailable, mark the feature errored and the run partial. Write the complete batch-shaped result to $PROJECT/.codesage/reviews/<RUN_ID>/risk/<feature_id>.json.
5. Run codesage-review-state changed-files --project "$PROJECT" --feature "$PROJECT/.codesage/reviews/$RUN_ID/features/<feature_id>.json" --target-ids "$PROJECT/.codesage/reviews/$RUN_ID/targets/<feature_id>.json" --output "$PROJECT/.codesage/reviews/$RUN_ID/changed/<feature_id>.json". The helper reads the feature's findings document and unions targeted finding paths with committed changes since reviewed_at_sha when present, staged, unstaged, and untracked slice paths. It uses project-relative, NUL-delimited Git output, excludes siblings of nested projects, and retains both rename endpoints. Without a prior SHA, it collects pending changes and target paths; outside Git it returns only the target paths. Collection errors and unavailable recorded commits fail the feature; never substitute an empty array.
6. Run codesage-review-state plan-feature with the feature, risk, and changed/target path files, passing --project "$PROJECT" so deleted files drop out of the plan instead of deadlocking coverage. Write $PROJECT/.codesage/reviews/<RUN_ID>/plans/<feature_id>.json and pass it to the reviewer as must_read.