Issue statuses
Every issue has a status. It’s your team’s record; the audit only measures the website.
| Status | Meaning |
|---|---|
| Open | Active. It counts toward the score. |
| Closed | Closed by you, or by an audit that no longer found it. Not proof of a repair. |
| Not relevant | Stays visible but is left out of the score, in this audit and every later one. |
How audits change statuses
Section titled “How audits change statuses”- Closed by audit. When a newer audit no longer finds an Open issue, Damdit closes it.
- Reappeared. When a later audit finds an issue closed by audit again, it reopens it.
- Your Close stays until an audit started after it finds the issue again. Then the issue reopens.
- Not relevant is never changed by an audit.
- When a check changed between two audits, an issue it no longer finds isn’t closed: the change is the method’s, not the website’s.
An issue keeps its status, comments and history across audits, because one issue is one rule.
Fixed or not?
Section titled “Fixed or not?”Closing an issue changes Damdit’s record, not the website. Only a newer audit that no longer finds the issue shows it as Resolved. Damdit never calls a repair verified without that.
Who changed it
Section titled “Who changed it”The issue’s History tab shows every change and who made it: an audit, you, the damdit command or an AI app through MCP.