review-comments

To prevent agents from deleting inline code review comments, you need a lifecycle management system that links markers like // @mai: comments to backed tickets and enforces safe editing rules. This blocks edits that would remove unresolved markers and detects disappearance-based drift via comment scanning.

You can track inline code annotation resolution by linking each comment to a mai ticket. Agents can then add resolution notes, close the linked ticket, and safely remove the corresponding comment line, maintaining consistent lifecycle management across ongoing work sessions.

Drift detection for inline review markers works by scanning source files to detect when comments disappear without their linked mai tickets being closed. It blocks edits that would cause drift, reads open marker threads, and verifies if unresolved annotations have been accidentally removed.

Yes, multi-line code review comments can be managed as a single ticket payload. The system captures continuation lines under the same comment prefix, treating the entire multi-line block as one linked issue tied to a single mai ticket for resolution tracking.

Yes, blocking edits that remove unresolved review markers works with existing source files. The system reads open marker threads embedded in the code, checks for drift, and prevents agents from editing out any unresolved inline annotations during active work sessions.

The best way to list and verify open code annotations is to use an agent workflow that scans the file for // @mai: comments, shows open threads, and checks for drift. This ensures all unresolved markers are visible and backed by tickets before any fixes are applied.