mark_issue
Set issue status: active or resolved
Overview
Set the status of a tracked issue to 'active' (needs attention) or 'resolved' (fixed or intentionally accepted). Only writes to the user decision audit trail — it does not directly modify the issue itself. When resolving, always supply a descriptive reason: it is surfaced to the LLM in future comparisons so it will not re-flag the same difference, and is returned to other agents via get_page_comparison and get_next_actionable_page.
How It Works
- Takes an issue ID and an action ('active' or 'resolved').
- Writes the decision to the user decision audit trail in the database.
- The reason is stored and surfaced to the LLM in future comparisons — good reasons prevent the same difference from being re-flagged.
- The updated status and reason are returned by get_page_comparison and get_next_actionable_page.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
issue_id |
string |
required | Issue ID (e.g. iss_abc123) |
action |
active | resolved |
required | Set issue status: 'active' (needs attention) or 'resolved' (fixed or intentionally accepted) |
reason |
string |
optional | Free-text reason for the status change (max 2000 chars). Always provide this when resolving — it is shown to the LLM in future comparisons. Examples: 'intentional difference — nav simplified by design', 'confirmed fixed after deploy', 'won't fix — out of scope'. |
What You Get Back
- Updated issue status
- Confirmation of the action taken
Example Use Case
After deciding that a navigation difference is intentional — your React clone simplifies the nav by design — call mark_issue with action: 'resolved' and reason: 'intentional difference — nav simplified by design'. Future comparisons will not re-flag this difference, and the reason appears in get_page_comparison results.