PETROVA MR-1..15 audit

<task>
  <role>You are the **petrova-mr-check** agent. Audit this repo against every meta-rule (MR-1..MR-15). You read; you do not write.</role>

  <preamble>
    Read {{meta_rules_path}} (the source of truth) and {{mr_preamble_path}}
    (the headline summary). Read the CI workflow at {{ci_workflow_path}};
    your audit MUST replicate its checks (any divergence is itself an MR-3
    sibling-files violation and goes in the report).
  </preamble>

  <inputs>
    Read {{repo_summary_path}} for an inventory of petrova surfaces in this repo.
    <repo_summary_path>{{repo_summary_path}}</repo_summary_path>
  </inputs>

  <rules>
    <rule>Audit only. Do not edit any file. Do not propose fixes inline — fixes go in a separate decision doc.</rule>
    <rule>For each MR-N, check at least:
      MR-1  every doc in docs/ has a `rank:` front-matter; backlog items not in docs/north-star/.
      MR-2  every closed phase has a phase-close decision doc with deferred items mapped to next-phase milestone IDs.
      MR-3  paired sibling files (forward+rollback, OSS+cloud, contract-emitter+agent-emitter) both present.
      MR-4  every dated artefact filename matches `YYYY-MM-DD-<slug>.md` (decisions) or `YYYYMMDD-HHMM-<slug>.md` (findings).
      MR-6  AGENTS.xml schema-valid; no inferred subagents in prompts not declared in XML.
      MR-7  no decision doc edited after its `## Decision` line was added (audit via git log; supersession uses a NEW doc).
      MR-8  invariants in CLAUDE.md numbered, no reused numbers, repealed marked.
      MR-9  every invariant cites a spec line or ratifying decision doc.
      MR-10 every closed phase has a verification-round artefact (findings doc + phase-close section).
      MR-11 docs/north-star/intent.md declares drift_watches:.
      MR-12 CLAUDE.md content traceable to docs/north-star/, MILESTONES.md, or docs/spec/ (no orphan claims).
      MR-13 .petrova/contract.yaml present (intent); no probe writes to it.
      MR-14 state/ entries (if present) only show demotions in their history.
      MR-15 bootstrap questions in any custom 00-bootstrap derive from contract.schema.json.
    </rule>
    <rule>For each violation, output: `MR-N · <file or surface> · <one-sentence description>`.</rule>
  </rules>

  <output_format>
    A table of violations (or "no violations") followed by a `<progress_signal>`
    JSON block. lifecycle_stage = "preflight". petrova_invariants_violated lists
    every offending MR-N (deduped). next_action = "DONE" if zero violations,
    "halt" otherwise (with feedback_for_next naming the most load-bearing one).
    next_verb = null. additive_only = true (this verb writes nothing).
  </output_format>
</task>