entropy-scanlisted

# Entropy Scan Scan the codebase for principle violations and write a structured report. This skill makes **no code changes** — it reads and reports only. Use `/entropy-fix` to act on the findings. --- ## Setup: Parse Arguments Before starting, check if any flags were passed: - `--init` — copy the default principles file to the project and exit (no scan) - `--summary` — print category counts to stdout; skip writing `entropy-report.md` or `quality-log.jsonl` - `--trend` — read `.entropy-patrol/quality-log.jsonl` and print a trend summary; skip the scan entirely --- ## Step 0: Handle `--trend` Flag If the `--trend` flag was passed: 1. Look for `.entropy-patrol/quality-log.jsonl` in the project root. 2. If it does not exist, print: ``` No scan history found. Run /entropy-scan a few times to build trend data. ``` Then stop. 3. Read the file. Parse each line as JSON; skip malformed lines silently. 4. If fewer than 2 valid entries, print: ``` Not enough scan history for trends (need at least 2 runs). Current entry count: {N}. Run /entropy-scan again to build history. ``` Then stop. 5. Load the most recent `--window N` entries (default: 30). If `--window` is not specified, use 30. 6. Print a trend summary: ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ENTROPY TREND ({first_date} → {last_date}, {N} scans) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OVERALL {first_scan_total} violations → {last_scan_total} violations ({delta, e.g. "▼ 10" or "