fix: v0.3.0 post-release bugs

1. init: add guideline adopt/migrate/skip flow + compile prompt
   (was detecting guidelines but not offering to import or compile them)
2. gov:compile: warn when ~/.edikt/VERSION differs from config version
   (compiled_by stamp showed 0.2.3 when config said 0.3.0)
3. sdlc:review: remove PRINCIPAL prefix from agent output format
4. sdlc:review: output each agent's full findings before consolidation
   (agents ran in fork so only consolidated summary reached the user)

Author: dcsg

commands/gov/compile.md

@@ -46,6 +46,14 @@ CRITICAL: NEVER write governance files that contain contradictions — detect an
 
 1. Display progress: `Step 1/5: Reading source documents...`
 
+1b. Read the edikt version from `~/.edikt/VERSION`. If this file doesn't exist, fall back to `edikt_version:` in `.edikt/config.yaml`. If BOTH differ (e.g., VERSION says 0.2.3 but config says 0.3.0), warn:
+   ```
+   ⚠ ~/.edikt/VERSION (0.2.3) differs from .edikt/config.yaml edikt_version (0.3.0).
+     The compiled_by stamp will use ~/.edikt/VERSION. To update, re-run the installer:
+     curl -fsSL https://raw.githubusercontent.com/diktahq/edikt/main/install.sh | bash
+   ```
+   Use `~/.edikt/VERSION` as the authoritative version for the `compiled_by` stamp.
+
 2. Read `.edikt/config.yaml`. Resolve paths from the `paths:` section using the Path Defaults in the Reference section.
 
 3. Read source documents:

commands/init.md

@@ -323,6 +323,49 @@ Choice [1]:
 
 **Critical:** whichever choice is made, the generated `.edikt/config.yaml` MUST reflect the actual location of the ADRs. Never leave the default path in config when ADRs live elsewhere. Otherwise `/edikt:gov:compile` and `/edikt:status` will report zero ADRs despite them existing.
 
+### 2a.2 Detected guidelines — Adopt / Migrate / Skip
+
+**If existing guidelines or convention docs were detected** (e.g., files with naming patterns, coding standards, style guides, best practices — often in `docs/`, `guides/`, `conventions/`, or `standards/`), capture the detected path as `$DETECTED_GUIDELINES_PATH`.
+
+If the detected path differs from edikt's default (`docs/guidelines/`), prompt:
+```
+Found {n} existing guidelines/conventions in {path}.
+
+How should edikt handle them?
+  [1] Adopt   — keep them at {path} and configure edikt to use that path (default)
+  [2] Migrate — move them to docs/guidelines/ (edikt's default layout)
+  [3] Skip    — ignore them, don't import
+Choice [1]:
+```
+
+**If the user chooses [1] Adopt:**
+- Write `paths.guidelines: {detected_path}` to `.edikt/config.yaml`
+- Do NOT move or copy files
+- After: "Configured edikt to use {path} for guidelines. Run `/edikt:guideline:compile` to compile them into governance directives."
+
+**If the user chooses [2] Migrate:**
+- Read each guideline file
+- Move to `docs/guidelines/`
+- If the file doesn't follow guideline format (missing `## Rules` section), convert it: extract rules as MUST/NEVER bullets, add a `## Purpose` section from existing content
+- Write `paths.guidelines: docs/guidelines` to config
+- After: "Migrated {n} guidelines to docs/guidelines/. Run `/edikt:guideline:compile` to compile them into governance directives."
+
+**If the user chooses [3] Skip:**
+- Continue with edikt's default paths
+- Remind them they can import later with `/edikt:docs:intake`
+
+**After adoption or migration**, prompt to compile:
+```
+Would you like to compile these guidelines into governance directives now?
+  [1] Yes — run /edikt:guideline:compile (recommended)
+  [2] No  — I'll compile later
+Choice [1]:
+```
+
+If yes, run `/edikt:guideline:compile` to generate sentinel blocks. Then remind: "Run `/edikt:gov:compile` to include these in the governance index."
+
+**Critical:** the generated `.edikt/config.yaml` MUST reflect the actual location of guidelines. Same rule as ADRs — never leave the default path when guidelines live elsewhere.
+
 ### 2b. Project Templates (v0.3.0 Adapt mode)
 
 This step runs once per artifact type (ADRs, Invariant Records, guidelines) and generates `.edikt/templates/<artifact>.md` files that future `/edikt:adr:new`, `/edikt:invariant:new`, and `/edikt:guideline:new` commands will use via the lookup chain documented in each `new.md` file.

commands/sdlc/review.md

@@ -50,9 +50,11 @@ CRITICAL: NEVER spawn agents for domains not detected from the changed files —
    ```
    If a spec exists, run drift detection using `/edikt:sdlc:drift` logic with `--scope=spec` and append findings under a "DRIFT CHECK" section. If no spec exists, skip silently.
 
-11. Display progress: `Step 3/3: Consolidating findings...`
+11. Display progress: `Step 3/3: Collecting and consolidating findings...`
 
-12. Consolidate all agent findings and output using the Output Format in the Reference section.
+12. For EACH agent that returned findings, output the agent's FULL findings immediately — not just a summary. Each agent's output must be visible to the user before consolidation. Format each agent's section using the Output Format (agent name, severity counts, numbered findings with file references).
+
+13. After ALL individual agent sections are output, add the consolidated footer with total critical/warning counts across all agents and the action prompt.
 
 ## Reference
 
@@ -163,7 +165,7 @@ Domains: {detected domains}
 
 If a relevant agent is not installed:
 ```
-PRINCIPAL DBA — not installed (run /edikt:agents add dba)
+DBA — not installed (run /edikt:agents add dba)
 ```
 
 ### Drift Check Output Format