Align design language: learnings land as proposal PRs

.cursor/rules/learnings-index.mdc

@@ -13,7 +13,7 @@ territory. Detail skills live in `.cursor/skills/learnings/<slug>/`
 org skills are pointed at wherever their channel installs them.
 
 Capture and curation go through the capture-learning skill (IDE sessions)
-or ai-flow's `/learn` (GitHub comments) — both land as draft PRs; human
+or ai-flow's `/learn` (GitHub comments) — both land as proposal PRs; human
 merge is the gate. Soft cap ~50 entries: at the cap, an addition must
 propose a retirement, a consolidation, or a glob-scoped sub-index split.
 

README.md

@@ -375,7 +375,7 @@ dev distributes agent-facing skills (Cursor-style `SKILL.md` directories) over t
 
 ### Repo learnings
 
-Alongside the distributed channels, a repo can carry **committed learnings** — lessons distilled from review feedback, builds, and scans — as an always-on index (`.cursor/rules/learnings-index.mdc`, one `[domain/slug]` line + trigger sentence per learning) pointing at on-demand detail skills (`.cursor/skills/learnings/<slug>/SKILL.md`; architecture digests under `.cursor/skills/architecture/<topic>/`). Committed files need no distribution step: every checkout — IDE, runner, worktree — has them by construction. The index defines its own format in its preamble; this repo's copy is the reference. Capture goes through the `capture-learning` skill (shipped in `share/cursor-skills/`, so it is available in every IDE session) or ai-flow's `/learn` command on GitHub surfaces — both stage learnings as draft PRs, and human merge is the curation gate.
+Alongside the distributed channels, a repo can carry **committed learnings** — lessons distilled from review feedback, builds, and scans — as an always-on index (`.cursor/rules/learnings-index.mdc`, one `[domain/slug]` line + trigger sentence per learning) pointing at on-demand detail skills (`.cursor/skills/learnings/<slug>/SKILL.md`; architecture digests under `.cursor/skills/architecture/<topic>/`). Committed files need no distribution step: every checkout — IDE, runner, worktree — has them by construction. The index defines its own format in its preamble; this repo's copy is the reference. Capture goes through the `capture-learning` skill (shipped in `share/cursor-skills/`, so it is available in every IDE session) or ai-flow's `/learn` command on GitHub surfaces — both stage learnings as proposal PRs, and human merge is the curation gate.
 
 ## Build container & caching model
 

share/cursor-skills/capture-learning/SKILL.md

@@ -89,7 +89,7 @@ Learnings merge through review, never silently:
   document — index line, skill body, target tier per learning — and
   iterate conversationally ("drop 3, merge 2 into 5, that's org-wide");
   switching to agent mode applies the agreed set. Preferred for scans.
-- **Otherwise:** write the files and open a draft PR on a dedicated
+- **Otherwise:** write the files and open a proposal PR on a dedicated
   branch (`ai/learn-<source>`), the body embedding the motivating
   evidence and a `learned-from: <source>` marker line. Never mix
   learnings into an unrelated code PR — separate PRs give independent