workflow-violation: SWE skipped task_update_status + bro_atomic_close after consolidation commit (#45)

[ZaxShen]

Full content on GitLab: https://gitlab.com/trustmybot/plugin/-/issues/2933

(Tri-source sync schema landed in MR !208 but mirror logic not yet bidirectional; this issue is a stub for v0.7.x board review.)

[ZaxShen]

3rd recurrence — SWE skipped close-flow again on phase 1

Task #28 on branch feat/agent-create-and-lego (issue #198) completed today; SWE delivered all 7 deliverables cleanly with explicit checklist self-review, but skipped task_update_status + bro_atomic_close again.

Bro filled in (task_update_status to commit_sha=024a6e4, atomic_close called with 20 file summaries).

Pattern is now 3 consecutive recurrences across v0.8.0 work (MR !206 consolidation, MR !208 sandbox+schema, MR pending agent-create). Each time bro silently fills in the missing close-flow.

Structural fix (PostToolUse close-gate hook that blocks SWE termination when commits exist on a task branch without status_update + atomic_close in the same turn) is OVERDUE. Bumping priority within v0.8.0.

Original spec in issue body has the option-(a) implementation outline.