T-6KS9-orchestrate-periodic-entities-audit

Status: closed/superseded · Impact: medium · Complexity: small

Goal

Pre-existing entity-schema drift on a consumer project’s main branch (e.g. a milestone body missing its schema-required ## Goal H2) surfaces only when an unrelated task happens to edit the drifted file — at which point it blocks that task’s gate instead of being fixed on its own schedule. Give /sdlc:entities-audit a periodic trigger (e.g. an orchestrator-tick cadence in /sdlc:orchestrate, or a scheduled run) so drift is caught and queued as its own work before it lands in the critical path of unrelated tasks.

M-0008’s milestone body was missing the schema-required ## Goal H2 at HEAD (pre-existing validation failure on main, only surfaced when this task edited the file) — periodic /sdlc:entities-audit runs would catch such drift before it blocks unrelated tasks.

— T-UDPO-extract-single-binary-example post-mortem