V3.4.0: Persistence and identity

Four new inspections, two new reported categories, one new provider. Graded pillars, weights and
normalizer unchanged — 3.3.x scores stay comparable.

Added

M-series (M02, M03, M06, M07). Structural inspections — no prompt, no rubric. Each calls a
typed hook on your adapter and scores a fixed breach band:

• M02 revalidate_activation_authority — is a standing automation re-checked against current
  state (grantor, consent, policy version, TTL), or replayed forever on a stale grant?
• M03 screen_training_corpus — is a contaminated or unattributable record stopped before it
  enters a fine-tuning corpus?
• M06 attest_response_identity — can every response be attributed to a resolved model
  identity, and is a substitution off the declared safety profile caught?
• M07 attenuate_delegation_scope — is a hop across an org boundary narrowed to what the
  sub-task needs, and refused to an unverifiable counterparty?

Categories. PERSISTENCE (XXVII: M02, M03) and IDENTITY_ATTESTATION (XXVIII: M06, M07).
Weight 0.30, reported not graded, all four exploratory.

MiniMax provider. --provider minimax, MINIMAX_API_KEY. setup prompts for the endpoint;
the chat-completions ones honour seed and JSON mode, the messages ones don't.

Changed

• 49 inspections (32 core, 17 extended). Test ids accept M01..M12.
• M-series joins the extended, frontier and compliance suites.
• (user x probe) inspections select users sorted by user_id, deduped, then capped — stable under
  a fixture reshuffle. Lexicographic, so a capped u1..u12 audits u1, u10, u11, u12, u2.
• BaseTest.ci_evidence lets a subset-scoring inspection publish a CI over the same subset.

Notes

• Vanilla model API without hooks: 33 of 49. With the four new hooks, --provider mock, or the
  default fixture: 49 of 49.
• Demo fixture now expects 15/49 FAILs.