rite-learnlisted

# /rite-learn: the cross-feature learning loop Recurring corrections, dismissed review findings, timeline decisions, and health dips are durable signal. **Capture is automatic**: `/rite-seal` appends lessons to `.devrites/learnings.md` on every GO (step 9a), while the engine can keep `.devrites/timeline.jsonl`, `.devrites/health-history.jsonl`, and per-feature review fingerprints as supporting evidence. The review skills load the learning ledger **before** a fan-out, so a dismissed-finding class stops being re-flagged without anyone running a command. The system learns as it ships. `/rite-learn` is the periodic **review + promote** pass on that auto-populated ledger: cluster the signal across features and decide which recurring lessons graduate into a project rule. **Propose, never impose**: promotion is the human's call, which is why it stays a deliberate command rather than firing on its own. Read-mostly. It reads the auto-populated ledger + the archive; it writes only `.devrites/learnings.md` (consolidation, via `devrites-engine learnings`) and drafts proposed rule/ledger edits for the user to confirm: it never edits source or rule files on its own. ## Modes - `/rite-learn` or `/rite-learn --mine`: **mine + propose** (the default). - `/rite-learn "<lesson>"`: **record one lesson** directly to the ledger and stop. ## Workflow (mine + propose) 1. **Gather the signal.** Start from the **auto-populated ledger** `.devrites/learnings.md` (seal appends to it on every GO