Spec Compliance

# User-invoked prompt · spec-compliance (v1.8.2 · Obsidian-style)

> Replaces the deleted `tools/spec_compliance_report.py`. ROUTER reads this
> when the user wants to audit "what does the spec promise vs what's
> actually happening".
>
> **v1.8.2 HARD RULE #11**: Compliance report renders in Obsidian. Apply
> `references/obsidian-style.md` — `> [!info]` for the ratio summary,
> `> [!warning]` for unfulfilled promises, `> [!success]` for fulfilled,
> `[[wikilinks]]` for spec refs, nested tags.

## Trigger keywords

- `检查合规` / `spec compliance` / `承诺核对`
- `spec 上写的真的在跑吗`
- retrospective Mode 0 Conscious Patrol reports `spec-compliance Nd` overdue and user says "跑一下"

## Goal

Cross-check what the spec docs (agents/, hosts/CLAUDE.md, references/)
**promise** against what the runtime evidence (meta/eval-history/,
meta/runtime/) actually **shows**. Surface gaps so the user knows what's
written-but-not-running.

This is the v1.8.0 successor to the cron-driven audit; same logic, now
user-invoked.

## Steps

### 1. Scan promises

Glob `agents/*.md`, `hosts/CLAUDE.md`, `references/*.md`. For each file,
Grep for promise keywords: