Development record

The intent-auditor definition's output rule 1 (agents/intent-auditor.md) says a reply with zero or two fenced json blocks makes the ingest fail the receipt closed, every criterion recorded INCONCLUSIVE, but intent audit ingest --verdict-json decodes the file as bare JSON (internal/core/intent/audit.go, IngestVerdictBytes) and refuses a fenced reply as not parseable JSON, writing nothing, and commands/intent.md tells the host to save the single JSON block without saying the fence lines must go. Only the provider route strips a fence (internal/adapter/openaiapi/client.go, unfence). A host that saves the auditor's reply as it came back is refused, and the fail-closed path the auditor is told about does not exist on the harness route. The consistency ingest decodes bare JSON the same way.