Mark finding ID $ARGUMENTS as resolved in .epost-data/a11y/known-findings.json.
Instructions
- Load
.epost-data/a11y/known-findings.json - Find the finding object with
idmatching the argument - If not found, report error with available IDs
- If already
resolved: true, report it's already resolved - Set
"resolved": trueand"resolved_date": "<today YYYY-MM-DD>" - Update top-level
"last_reviewed_date"to today - Save the file
Output
{
"finding_id": 3,
"title": "Navigation bar buttons inaccessible",
"platform": "ios|android|web",
"wcag": "2.1.1",
"status": "RESOLVED",
"resolved_date": "2026-02-26"
}
Constraints
- Only modify the targeted finding and
last_reviewed_date - Do not modify any other findings or fields
- If the finding ID does not exist, report error — do not create new entries