reality-checklisted

# Reality Check Verify that a file's actual implementation matches what it should be doing based on its context. ## Usage ``` reality-check <file-path> ``` - `<file-path>` → file to evaluate, relative to the current repository or absolute. - If the request does not resolve exactly one file, return a usage error with the candidates. ## Process 1. **Infer purpose first**: Before reading the target file, review the surrounding codebase and project structure to form a logic inference of the file's purpose and intended functionality - State: "Inferred: {analysis}" 2. **Review actual implementation**: Thoroughly review the file in context of the surrounding code and project structure - State: "Actuality: {analysis}" 3. **Compare and remediate**: Compare inferred purpose versus actual implementation - Identify any discrepancies between what the file should do and what it actually does - Hypothesize about the cause of each discrepancy - Develop a remediation plan for any issues found 4. **Apply the remediation**: Carry out the remediation plan for every discrepancy you confirmed. aidd decides whether this run may write — a review-only run forbids edits outright, turning this step into reporting the plan you would have executed. ## Validation Test the inferred purpose against callers, consumers, tests, and documentation. Clearly label uncertain conclusions. ## Output Report the inferred purpose, actual behavior, discrepancies, supporting evidence