refactor: drop dev-cycle-profile.yml for conventions + CLAUDE.md facts

The profile was never parsed — it was prose the skill bodies told the model to read, so most slots were dead, constant across every project, or fiction (the whole pipeline block, including the "tdd is opt-in" claim, was enforced by nothing).

Split it in two: constants become fixed conventions named directly by the skills (new docs/conventions.md), and the few genuinely per-project facts move to each project's CLAUDE.md under '## Skills plugin: project facts'. tdd/fieldtest/docwriter are now always available; the only behavioural toggle left is spec auto-sign.

Delete docs/profile-schema.md and templates/project-profile.yml; add docs/conventions.md and a project-facts section to templates/CLAUDE.md.fragment; rewrite all SKILL/agent prose and the pipeline/design/migration/README/INSTALL docs accordingly.

planner/agents/plan-recon.md

@@ -32,21 +32,21 @@ naming where work lands.
 
 ## Standing reading list
 
-Read the files configured under `standing_reading.always`
-plus `standing_reading.by_role.plan-recon` in the project
-profile.
+The standing reading is `CLAUDE.md` plus
+`git log -10 --format=full`, then the per-role standing
+reading the project lists in its CLAUDE.md project facts.
 
 In addition:
 
-- If the project has a design ledger configured under
-  `paths.design_ledger`, walk it to the contracts the carrier
+- If the project has a design ledger (its CLAUDE.md project
+  facts), walk it to the contracts the carrier
   flags or that the spec touches; do not skim sections the
   spec does not touch.
 - `git log -5 --format=full` — full bodies of the most
   recent iter commits; tells you what just shipped, so the
   file-map does not double-count fresh work.
 - `../SKILL.md` (the planner SKILL) — the role the recon
-  serves. Do NOT open files under `paths.plan_dir`; plan
+  serves. Do NOT open files under `docs/plans`; plan
   files are output downstream of recon, never input.
 
 ## Carrier contract — what the controller hands you
@@ -58,7 +58,7 @@ it.
 
 | Field | Content |
 |-------|---------|
-| `spec_path` | Path to the spec under `paths.spec_dir` (mandatory) |
+| `spec_path` | Path to the spec under `docs/specs` (mandatory) |
 | `iteration_scope` | Which sections of the spec this dispatch covers (mandatory) |
 | `focus_hint` | Optional: orchestrator may flag a specific subsystem or symbol to prioritise |
 
@@ -85,7 +85,7 @@ never to fix or write.
 2. Read the spec in full. Note every reference to a path,
    type, function, or invariant.
 3. Read the standing list in order, plus the design ledger's
-   relevant contracts (if configured).
+   relevant contracts (if the project has one).
 4. For each path or symbol the spec references, run
    `git grep` or `Glob`+`Read` to anchor it to exact line
    numbers in the current tree. Record: