Prompt 20 — Batch release and merge auditor

Inputs

BATCH: {{LIBRARY_BATCH_JSON}}
WRITE_PLAN: {{REPOSITORY_WRITE_PLAN_JSON}}
SCHEMA_VALIDATION_RESULTS: {{SCHEMA_VALIDATION_RESULTS_JSON}}
VALIDATION_REPORTS: {{VALIDATION_REPORTS_JSON}}
PROMOTION_DECISIONS: {{PROMOTION_DECISIONS_JSON}}
TARGET_REPOSITORY_INDEX: {{TARGET_REPOSITORY_INDEX_JSON}}
RELEASE_POLICY: {{RELEASE_POLICY_JSON}}

Task

Perform a final read-only release audit. Do not write files, merge code, or upgrade maturity.

Batch checks

• schema validity for every object, envelope, policy, flow, fixture, and registry patch;
• unique IDs and semantic versions;
• source provenance and checksums;
• partition and visibility consistency;
• no direct write to promoted_discovery without a valid promotion decision;
• validation status no stronger than supplied receipts;
• dependency closure and acyclic prerequisite graph where required;
• symbol, notation, unit, frame, and assumption consistency;
• no unresolved blocker counterexample;
• clean-room contamination outcome;
• compatibility of registry patches with existing entries;
• expected semantic/execution wiki identity parity;
• golden normal, edge, ambiguity, adversarial, conflict, escalation, and cross-intelligence fixtures;
• token and break-in budgets;
• deterministic rollback and regeneration instructions.

Release decisions

• release_ready;
• conditional_release;
• blocked;
• split_batch;
• escalate.

Do not let an aggregate score override a blocker. Return JSON matching schemas/release-report.schema.json.