prizmkit 1.1.112 → 1.1.114

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.112",
-  "bundledAt": "2026-07-08T16:44:52.355Z",
-  "bundledFrom": "544bc17"
+  "frameworkVersion": "1.1.114",
+  "bundledAt": "2026-07-09T06:02:07.402Z",
+  "bundledFrom": "b1b5595"
 }

package/bundled/adapters/codex/skill-adapter.js

@@ -21,6 +21,10 @@ function applyCodexInteractionCompatibility(content) {
 
   return content
     .replace(/\bAskUserQuestion\b/g, 'request_user_input')
+    .replace(
+      /Use `request_user_input`; do not render path options as plain text\./g,
+      fallbackInstruction
+    )
     .replace(
       /Do NOT render options as plain text — the user must be able to click\/select\./g,
       fallbackInstruction

package/bundled/dev-pipeline/SCHEMA_ANALYSIS.md

@@ -81,8 +81,8 @@ acceptance_criteria, status
 
 **Optional fields:**
 ```
-priority, affected_feature, affected_modules, environment, critic, 
-critic_count, model
+priority, dependencies, affected_feature, affected_modules, environment, critic, 
+critic_count, model, browser_interaction
 ```
 
 | Property | Type | Enum/Pattern | Notes |
@@ -95,7 +95,8 @@ critic_count, model
 | `error_source` | object | type enum: `stack_trace, user_report, failed_test, log_pattern, monitoring_alert` | ✓ REQUIRED |
 | `verification_type` | string | `automated, manual, hybrid` | ✓ REQUIRED |
 | `acceptance_criteria` | array | N/A | minItems: 1 |
-| `status` | string | `pending, triaging, reproducing, fixing, verifying, completed, failed, needs_info, skipped` | ✓ REQUIRED; more states than Feature |
+| `status` | string | `pending, in_progress, completed, failed, skipped, needs_info` | ✓ REQUIRED; external list status only |
+| `dependencies` | array | Pattern: `^B-\d{3}$` | Optional; bug IDs that must complete first |
 | `affected_feature` | string | Pattern: `^F-\d{3}(-[A-Z])?$` | Optional; link to original feature |
 | `affected_modules` | array | N/A | Optional; module names |
 | `environment` | object | N/A | Optional; os, runtime, browser, version |
@@ -209,12 +210,11 @@ design_system, ci_pipeline
 pending, in_progress, completed, failed, skipped, split, auto_skipped
 ```
 
-**Bug Fix Status (9 values):**
+**Bug Fix Status (6 external values):**
 ```
-pending, triaging, reproducing, fixing, verifying, completed, failed, needs_info, skipped
+pending, in_progress, completed, failed, skipped, needs_info
 ```
-*Includes intermediate workflow states: triaging, reproducing, fixing, verifying, needs_info*
-*NO "split" or "auto_skipped"*
+*External bug-list status stays coarse. Fine-grained triage/reproduction/fix/verification phases belong in logs, checkpoints, and session metadata, not `bugs[].status`.*
 
 **Refactor Status (5 values):**
 ```
@@ -227,10 +227,10 @@ pending, in_progress, completed, failed, skipped
 | Schema | Dependencies | Pattern |
 |--------|--------------|---------|
 | Feature | `dependencies` (required) | `^F-\d{3}(-[A-Z])?$` - can reference sub-features |
-| Bug Fix | N/A | No `dependencies` field ❌ |
+| Bug Fix | `dependencies` (optional) | `^B-\d{3}$` - can reference prerequisite bug fixes |
 | Refactor | `dependencies` (required) | `^R-\d{3}$` - ONLY refactor IDs, no sub-IDs |
 
-**Issue:** Bug Fix schema lacks dependency tracking. Bugs cannot declare prerequisites. Feature dependencies support sub-features; Refactor dependencies do not.
+**Contract:** Bug Fix dependencies are supported as optional prerequisites. Runtime selects eligible bugs in stable list order after dependencies are completed.
 
 ### 4.5 Acceptance Criteria vs Task Lists
 
@@ -493,7 +493,7 @@ Located in `/dev-pipeline/templates/`:
 
 ### Status Enums
 - **Feature**: `[pending, in_progress, completed, failed, skipped, split, auto_skipped]` (7 values)
-- **Bug Fix**: `[pending, triaging, reproducing, fixing, verifying, completed, failed, needs_info, skipped]` (9 values)
+- **Bug Fix**: `[pending, in_progress, completed, failed, skipped, needs_info]` (6 external values)
 - **Refactor**: `[pending, in_progress, completed, failed, skipped]` (5 values)
 
 ### Complexity/Estimated Complexity Enums

package/bundled/dev-pipeline/scripts/generate-bootstrap-prompt.py

@@ -1906,6 +1906,7 @@ def build_replacements(args, feature, features, global_context, script_dir):
         "{{HAS_PLAN}}": "true" if artifacts["has_plan"] else "false",
         "{{BROWSER_VERIFY_STEPS}}": browser_verify_steps,
         "{{BROWSER_TOOL}}": browser_tool,
+        "{{BROWSER_BLOCKING}}": "true" if browser_blocking else "false",
         "{{AC_CHECKLIST}}": format_ac_checklist(
             feature.get("acceptance_criteria", [])
         ),

package/bundled/dev-pipeline/scripts/generate-bugfix-prompt.py

@@ -417,6 +417,13 @@ def assemble_bugfix_sections(pipeline_mode, sections_dir, critic_enabled, browse
         sections.append(("phase-browser", load_section(sections_dir, "phase-browser-verification-auto.md")))
     if manual_gate:
         sections.append(("bugfix-manual-gate", load_section(sections_dir, "bugfix-phase-manual-verification.md")))
+        sections.extend([
+            ("bugfix-session-status", load_section(sections_dir, "bugfix-session-status.md")),
+            ("bugfix-critical-paths", load_section(sections_dir, "bugfix-critical-paths.md")),
+            ("failure-capture", load_section(sections_dir, "failure-capture.md")),
+            ("bugfix-reminders", load_section(sections_dir, "bugfix-reminders.md")),
+        ])
+        return sections
     sections.extend([
         ("bugfix-phase-commit-report", load_section(sections_dir, "bugfix-phase-commit-report.md")),
         ("bugfix-session-status", load_section(sections_dir, "bugfix-session-status.md")),

package/bundled/dev-pipeline/scripts/utils.py

@@ -746,12 +746,17 @@ def resolve_prompt_platform(project_root):
     )
 
 def read_platform_conventions(project_root):
-    """Resolve the platform-specific project conventions file.
+    """Resolve the platform-specific main project conventions file.
 
     Returns a path reference for the AI agent to read at runtime,
-    rather than inlining the full file content into the prompt.
+    rather than inlining the full file content into the prompt. Private
+    framework memory files are intentionally excluded because project
+    conventions and Infrastructure live in the user-facing main files.
     """
-    platform = os.environ.get("PRIZMKIT_PLATFORM", "claude")
+    try:
+        platform = resolve_prompt_platform(project_root)
+    except RuntimeError:
+        platform = os.environ.get("PRIZMKIT_PLATFORM", "claude")
     if platform == "codebuddy":
         candidates = ["CODEBUDDY.md", "CLAUDE.md", "AGENTS.md"]
     elif platform == "codex":

package/bundled/dev-pipeline/templates/bootstrap-tier1.md

@@ -338,7 +338,13 @@ Append results to `context-snapshot.md`:
    Browser cleanup: confirmed
    ```
 
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
+Browser blocking policy: `{{BROWSER_BLOCKING}}`.
+
+If verification fails:
+- If `{{BROWSER_BLOCKING}}` is `true`: mark checkpoint step `browser-verification` as `failed`, write `failure-log.md` with browser evidence, clean up the dev server/browser, and stop before commit.
+- If `{{BROWSER_BLOCKING}}` is `false`: log the failure details, mark checkpoint step `browser-verification` according to the evidence, clean up the dev server/browser, and continue.
+
+You MUST attempt verification and MUST clean up the dev server in both cases.
 {{END_IF_BROWSER_INTERACTION}}
 
 ### Phase 4: Architecture Sync & Commit (SINGLE COMMIT)

package/bundled/dev-pipeline/templates/bootstrap-tier2.md

@@ -488,7 +488,13 @@ Append results to `context-snapshot.md`:
    Browser cleanup: confirmed
    ```
 
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
+Browser blocking policy: `{{BROWSER_BLOCKING}}`.
+
+If verification fails:
+- If `{{BROWSER_BLOCKING}}` is `true`: mark checkpoint step `browser-verification` as `failed`, write `failure-log.md` with browser evidence, clean up the dev server/browser, and stop before commit.
+- If `{{BROWSER_BLOCKING}}` is `false`: log the failure details, mark checkpoint step `browser-verification` according to the evidence, clean up the dev server/browser, and continue.
+
+You MUST attempt verification and MUST clean up the dev server in both cases.
 {{END_IF_BROWSER_INTERACTION}}
 
 ### Phase 6: Architecture Sync & Commit (SINGLE COMMIT)

package/bundled/dev-pipeline/templates/bootstrap-tier3.md

@@ -483,7 +483,13 @@ Append results to `context-snapshot.md`:
    Browser cleanup: confirmed
    ```
 
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
+Browser blocking policy: `{{BROWSER_BLOCKING}}`.
+
+If verification fails:
+- If `{{BROWSER_BLOCKING}}` is `true`: mark checkpoint step `browser-verification` as `failed`, write `failure-log.md` with browser evidence, clean up the dev server/browser, and stop before commit.
+- If `{{BROWSER_BLOCKING}}` is `false`: log the failure details, mark checkpoint step `browser-verification` according to the evidence, clean up the dev server/browser, and continue.
+
+You MUST attempt verification and MUST clean up the dev server in both cases.
 {{END_IF_BROWSER_INTERACTION}}
 
 ### Phase 6: Retrospective & Commit (SINGLE COMMIT) — DO NOT SKIP

package/bundled/dev-pipeline/templates/sections/bugfix-phase-commit-report.md

@@ -1,6 +1,6 @@
 ### Phase 4: Commit & Learn
 
-Skip this phase only when the Manual / Hybrid Verification Gate stopped the fresh session before commit.
+This phase is included only for sessions allowed to commit. Fresh manual/hybrid bugfix prompts omit this phase entirely and stop as partial before retrospective/commit.
 
 **Bug Fix Documentation Policy**:
 - Default: run `/prizmkit-retrospective` with structural sync only.

package/bundled/dev-pipeline/templates/sections/phase-browser-verification-auto.md

@@ -117,5 +117,11 @@ Append results to `context-snapshot.md`:
    Browser cleanup: confirmed
    ```
 
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
+Browser blocking policy: `{{BROWSER_BLOCKING}}`.
+
+If verification fails:
+- If `{{BROWSER_BLOCKING}}` is `true`: mark checkpoint step `browser-verification` as `failed`, write `failure-log.md` with browser evidence, clean up the dev server/browser, and stop before commit.
+- If `{{BROWSER_BLOCKING}}` is `false`: log the failure details, mark checkpoint step `browser-verification` according to the evidence, clean up the dev server/browser, and continue.
+
+You MUST attempt verification and MUST clean up the dev server in both cases.
 

package/bundled/dev-pipeline/templates/sections/phase-browser-verification-opencli.md

@@ -114,5 +114,11 @@ Append results to `context-snapshot.md`:
    Browser cleanup: confirmed
    ```
 
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
+Browser blocking policy: `{{BROWSER_BLOCKING}}`.
+
+If verification fails:
+- If `{{BROWSER_BLOCKING}}` is `true`: mark checkpoint step `browser-verification` as `failed`, write `failure-log.md` with browser evidence, clean up the dev server/browser, and stop before commit.
+- If `{{BROWSER_BLOCKING}}` is `false`: log the failure details, mark checkpoint step `browser-verification` according to the evidence, clean up the dev server/browser, and continue.
+
+You MUST attempt verification and MUST clean up the dev server in both cases.
 

package/bundled/dev-pipeline/templates/sections/phase-browser-verification.md

@@ -101,5 +101,11 @@ Server cleanup: confirmed
 Browser cleanup: confirmed
 ```
 
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
+Browser blocking policy: `{{BROWSER_BLOCKING}}`.
+
+If verification fails:
+- If `{{BROWSER_BLOCKING}}` is `true`: mark checkpoint step `browser-verification` as `failed`, write `failure-log.md` with browser evidence, clean up the dev server/browser, and stop before commit.
+- If `{{BROWSER_BLOCKING}}` is `false`: log the failure details, mark checkpoint step `browser-verification` according to the evidence, clean up the dev server/browser, and continue.
+
+You MUST attempt verification and MUST clean up the dev server in both cases.
 

package/bundled/dev-pipeline/tests/test_generate_bootstrap_prompt.py

@@ -1100,7 +1100,10 @@ def _ensure_agent_files(project, platforms=("claude", "codex")):
             (agents_dir / f"prizm-dev-team-{name}{suffix}").write_text("agent\n", encoding="utf-8")
 
 
-def _render_bugfix_prompt(tmp_path, platform="claude", explicit_platform=None):
+def _render_bugfix_prompt(
+    tmp_path, platform="claude", explicit_platform=None,
+    bug_overrides=None, retry_count="0", resume_phase="null",
+):
     from generate_bugfix_prompt import main as bugfix_main
 
     project = tmp_path / "bugfix-project"
@@ -1112,8 +1115,11 @@ def _render_bugfix_prompt(tmp_path, platform="claude", explicit_platform=None):
     _ensure_agent_files(project)
     bug_list = project / ".prizmkit" / "plans" / "bug-fix-list.json"
     bug_list.parent.mkdir(parents=True)
+    bug = {"id": "B-001", "title": "Broken", "description": "Fix it", "acceptance_criteria": ["Works"]}
+    if bug_overrides:
+        bug.update(bug_overrides)
     bug_list.write_text(json.dumps({
-        "bugs": [{"id": "B-001", "title": "Broken", "description": "Fix it", "acceptance_criteria": ["Works"]}],
+        "bugs": [bug],
         "global_context": {"language": "Python"},
     }), encoding="utf-8")
     output = project / "bugfix-prompt.md"
@@ -1130,8 +1136,8 @@ def _render_bugfix_prompt(tmp_path, platform="claude", explicit_platform=None):
             "--bug-id", "B-001",
             "--session-id", "session-1",
             "--run-id", "run-1",
-            "--retry-count", "0",
-            "--resume-phase", "null",
+            "--retry-count", retry_count,
+            "--resume-phase", resume_phase,
             "--state-dir", str(project / ".prizmkit" / "state" / "bugfix"),
             "--project-root", str(project),
             "--output", str(output),
@@ -1150,7 +1156,7 @@ def _render_bugfix_prompt(tmp_path, platform="claude", explicit_platform=None):
     return output.read_text(encoding="utf-8")
 
 
-def _render_refactor_prompt(tmp_path, platform="claude", explicit_platform=None):
+def _render_refactor_prompt(tmp_path, platform="claude", explicit_platform=None, refactor_overrides=None):
     from generate_refactor_prompt import main as refactor_main
 
     project = tmp_path / "refactor-project"
@@ -1162,14 +1168,17 @@ def _render_refactor_prompt(tmp_path, platform="claude", explicit_platform=None)
     _ensure_agent_files(project)
     refactor_list = project / ".prizmkit" / "plans" / "refactor-list.json"
     refactor_list.parent.mkdir(parents=True)
+    refactor = {
+        "id": "R-001",
+        "title": "Restructure",
+        "description": "Preserve behavior",
+        "acceptance_criteria": ["Behavior preserved"],
+        "scope": {"files": ["src/a.py"], "modules": ["src"]},
+    }
+    if refactor_overrides:
+        refactor.update(refactor_overrides)
     refactor_list.write_text(json.dumps({
-        "refactors": [{
-            "id": "R-001",
-            "title": "Restructure",
-            "description": "Preserve behavior",
-            "acceptance_criteria": ["Behavior preserved"],
-            "scope": {"files": ["src/a.py"], "modules": ["src"]},
-        }],
+        "refactors": [refactor],
         "global_context": {"language": "Python"},
     }), encoding="utf-8")
     output = project / "refactor-prompt.md"
@@ -1189,18 +1198,14 @@ def _render_refactor_prompt(tmp_path, platform="claude", explicit_platform=None)
             "--retry-count", "0",
             "--resume-phase", "null",
             "--state-dir", str(project / ".prizmkit" / "state" / "refactor"),
+            "--project-root", str(project),
             "--output", str(output),
         ]
-        old_cwd = os.getcwd()
-        os.chdir(project)
         try:
-            try:
-                refactor_main()
-            except SystemExit as exc:
-                if exc.code not in (0, None):
-                    raise
-        finally:
-            os.chdir(old_cwd)
+            refactor_main()
+        except SystemExit as exc:
+            if exc.code not in (0, None):
+                raise
     finally:
         os.sys.argv = old_argv
         if old_platform is None:
@@ -1210,6 +1215,67 @@ def _render_refactor_prompt(tmp_path, platform="claude", explicit_platform=None)
     return output.read_text(encoding="utf-8")
 
 
+class TestBrowserBlockingPromptPolicy:
+    def test_feature_bugfix_refactor_blocking_browser_policy_stops_before_commit(self, tmp_path):
+        browser_interaction = {
+            "tool": "auto",
+            "blocking": True,
+            "verify_steps": ["Open the page"],
+        }
+        prompts = [
+            _render_feature_prompt(tmp_path / "feature-browser-blocking", browser_interaction=browser_interaction),
+            _render_bugfix_prompt(tmp_path / "bugfix-browser-blocking", bug_overrides={"browser_interaction": browser_interaction}),
+            _render_refactor_prompt(tmp_path / "refactor-browser-blocking", refactor_overrides={"browser_interaction": browser_interaction}),
+        ]
+
+        for prompt in prompts:
+            assert "Browser blocking policy: `true`" in prompt
+            assert "stop before commit" in prompt
+            assert "Failures do NOT block the commit" not in prompt
+
+    def test_feature_bugfix_refactor_nonblocking_browser_policy_continues(self, tmp_path):
+        browser_interaction = {
+            "tool": "auto",
+            "blocking": False,
+            "verify_steps": ["Open the page"],
+        }
+        prompts = [
+            _render_feature_prompt(tmp_path / "feature-browser-nonblocking", browser_interaction=browser_interaction),
+            _render_bugfix_prompt(tmp_path / "bugfix-browser-nonblocking", bug_overrides={"browser_interaction": browser_interaction}),
+            _render_refactor_prompt(tmp_path / "refactor-browser-nonblocking", refactor_overrides={"browser_interaction": browser_interaction}),
+        ]
+
+        for prompt in prompts:
+            assert "Browser blocking policy: `false`" in prompt
+            assert "clean up the dev server/browser, and continue" in prompt
+            assert "Failures do NOT block the commit" not in prompt
+
+
+class TestManualHybridBugfixPromptPolicy:
+    def test_fresh_manual_bugfix_prompt_stops_before_commit_phase(self, tmp_path):
+        prompt = _render_bugfix_prompt(
+            tmp_path / "fresh-manual-bugfix",
+            bug_overrides={"verification_type": "manual"},
+        )
+
+        assert "Manual / Hybrid Verification Gate" in prompt
+        assert "Stop before `/prizmkit-retrospective` and `/prizmkit-committer`" in prompt
+        assert "### Phase 4: Commit & Learn" not in prompt
+        assert "Run `/prizmkit-committer` with commit prefix" not in prompt
+
+    def test_recovery_manual_bugfix_prompt_includes_commit_phase_with_substitution_policy(self, tmp_path):
+        prompt = _render_bugfix_prompt(
+            tmp_path / "recovery-manual-bugfix",
+            bug_overrides={"verification_type": "manual"},
+            retry_count="1",
+        )
+
+        assert "Manual / Hybrid Verification Gate" not in prompt
+        assert "Recovery-class session: automated verification may substitute for manual/hybrid UAT" in prompt
+        assert "### Phase 4: Commit & Learn" in prompt
+        assert "Run `/prizmkit-committer` with commit prefix" in prompt
+
+
 class TestHeadlessPromptCleanupF033:
     def test_rendered_feature_bugfix_refactor_prompts_are_clean(self, tmp_path):
         prompts = []

package/bundled/dev-pipeline/tests/test_generate_bugfix_prompt.py

@@ -307,6 +307,20 @@ def test_template_source_is_clean_for_headless_prompt_contract():
         assert forbidden not in content
 
 
+def test_bugfix_prompt_keeps_fine_grained_phases_out_of_external_status_contract():
+    content = Path("dev-pipeline/templates/bugfix-bootstrap-prompt.md").read_text(encoding="utf-8")
+    old_statuses = ["triaging", "reproducing", "fixing", "verifying"]
+
+    assert "external bug-list status field" in content
+    assert "pending`, `in_progress`, `completed`, `failed`, `skipped`, or `needs_info`" in content
+    for status in old_statuses:
+        assert f"status=\"{status}\"" not in content
+        assert f"status = \"{status}\"" not in content
+        assert f"status='{status}'" not in content
+        assert f"status = '{status}'" not in content
+        assert f"Set bug status to `{status}`" not in content
+
+
 # ---------------------------------------------------------------------------
 # Anti-Bash regression guardrails (F-039)
 # Note: grep -n, sed -n, grep -q, wc -l excluded — referenced in bugfix context

package/bundled/dev-pipeline/tests/test_python_runner_parity.py

@@ -514,6 +514,48 @@ def test_init_scripts_reject_missing_self_and_cycle_dependencies(tmp_path):
             assert any(expected_fragments[scenario] in error for error in payload["errors"])
 
 
+def test_bug_planner_validator_rejects_dependency_cycles():
+    from importlib.util import module_from_spec, spec_from_file_location
+
+    script_path = REPO_ROOT / "core" / "skills" / "orchestration-skill" / "pipelines" / "bug-planner" / "scripts" / "validate-bug-list.py"
+    spec = spec_from_file_location("bug_planner_validate_bug_list", script_path)
+    module = module_from_spec(spec)
+    spec.loader.exec_module(module)
+
+    result = module.validate({
+        "$schema": "dev-pipeline-bug-fix-list-v1",
+        "project_name": "Fake",
+        "bugs": [
+            {
+                "id": "B-001",
+                "title": "First",
+                "description": "First bug",
+                "severity": "medium",
+                "error_source": {"type": "user_report"},
+                "verification_type": "manual",
+                "acceptance_criteria": ["fixed"],
+                "dependencies": ["B-002"],
+                "status": "pending",
+            },
+            {
+                "id": "B-002",
+                "title": "Second",
+                "description": "Second bug",
+                "severity": "medium",
+                "error_source": {"type": "user_report"},
+                "verification_type": "manual",
+                "acceptance_criteria": ["fixed"],
+                "dependencies": ["B-001"],
+                "status": "pending",
+            },
+        ],
+    })
+
+    assert result["valid"] is False
+    assert any("Dependency cycle detected" in error for error in result["errors"])
+
+
+
 def _family_items(kind, entries):
     items = []
     for item_id, dependencies, status in entries:

package/bundled/dev-pipeline/tests/test_runtime_helper.py

@@ -99,6 +99,29 @@ class TestPlatformExecutableAndPortHelpers:
         assert payload["platform"] == "codex"
         assert payload["path"].endswith(".agents/skills/playwright-cli")
 
+    def test_read_platform_conventions_uses_resolved_main_memory_file(self, tmp_path, monkeypatch):
+        from scripts.utils import read_platform_conventions
+
+        project = tmp_path / "project"
+        (project / ".prizmkit").mkdir(parents=True)
+        (project / ".prizmkit" / "config.json").write_text(
+            json.dumps({"platform": "codex", "ai_cli": "codex"}), encoding="utf-8"
+        )
+        (project / "AGENTS.md").write_text("### Project Conventions\n", encoding="utf-8")
+        (project / "AGENTS.private.md").write_text("framework protocol\n", encoding="utf-8")
+        monkeypatch.delenv("PRIZMKIT_PLATFORM", raising=False)
+
+        assert read_platform_conventions(project) == "`AGENTS.md`"
+
+        (project / ".prizmkit" / "config.json").write_text(
+            json.dumps({"platform": "codebuddy", "ai_cli": "cbc"}), encoding="utf-8"
+        )
+        (project / "CODEBUDDY.md").write_text("### Infrastructure\n", encoding="utf-8")
+        (project / "CODEBUDDY.private.md").write_text("framework protocol\n", encoding="utf-8")
+
+        assert read_platform_conventions(project) == "`CODEBUDDY.md`"
+        assert ".private.md" not in read_platform_conventions(project)
+
     def test_codebuddy_cli_env_wins_over_filesystem_markers(self, tmp_path, monkeypatch):
         from prizmkit_runtime.platform_detection import resolve_platform
 

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.112",
+  "version": "1.1.114",
   "skills": {
     "prizmkit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

package/bundled/skills/app-planner/SKILL.md

@@ -180,7 +180,7 @@ Route by answer:
   - Proactively scan the project (same as brownfield behavior)
   - Generate project-brief.md from inferred context
   - Skip extensive brainstorming and constraint phases
-  - Present brief for user confirmation → write → done
+  - Present brief for user confirmation → write → run CP-AP-6 Generated App-Plan Review Gate → completion summary
 
 Session goal tracking: Track the intent (`produce`, `explore`, or `quick_context`) throughout the session. If `explore`, always re-prompt before ending.
 
@@ -240,6 +240,21 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 | **CP-AP-3** | Frontend Design Evaluated | For frontend projects: checked for existing UI/UX design system; user was asked if missing. **Auto-pass** for backend-only or non-UI projects. | 2 |
 | **CP-AP-4** | Project Brief Accumulated | `.prizmkit/plans/project-brief.md` exists at `.prizmkit/plans/` with at least 3 ideas listed. For brownfield: already-implemented items marked `[x]` count toward this total. | 3 |
 | **CP-AP-5** | Planning Complete | All project-level context captured: conventions, infrastructure config, tech stack, architecture decisions, project brief finalized | 4 |
+| **CP-AP-6** | Local Plan Review Passed | Local generated-plan review loaded `${SKILL_DIR}/references/generated-plan-review.md`, directly reviewed current-session final app-planning artifacts, applied accepted fixes through source/writer paths, and rechecked changed sections | 4 |
+
+## Generated App-Plan Review Gate
+
+User requirement preserved verbatim: `Add generated-plan review in app-planner also .`
+
+Run this gate before any final handoff whenever the current `app-planner` session wrote or rewrote final app-level planning content. In full produce mode this runs after CP-AP-5; in Quick Context Mode it runs after the confirmed `.prizmkit/plans/project-brief.md` write; in conventions, infrastructure, architecture-decision, or rules-only final-write flows it runs after those writes and before the completion summary. This gate reviews generated planning artifacts directly, not implementation diffs.
+
+1. **Load the local reference**: read `${SKILL_DIR}/references/generated-plan-review.md` and follow it as the source of truth for app-planner generated content review.
+2. **Read actual planning artifacts directly**: inspect current-session final outputs such as `.prizmkit/plans/project-brief.md`, selected `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` sections, `.prizmkit/rules/<layer>-rules.md`, and `.prizmkit/prizm-docs/root.prizm` `RULES:` pointer line. Do not rely on `git status`, `git diff`, or `git diff --cached`, because `.prizmkit` planning artifacts are often gitignored or untracked.
+3. **Scope to new/changed app-planning content**: compare against pre-session snapshots or in-memory drafts when available. Preserve unchanged historical brief items, instruction-file sections, rules files, and Prizm doc content. For explore-only sessions, draft-save exits, or flows with no new final planning content, report: `Local generated-plan review: not applicable — no new final planning content written.`
+4. **Run the local checklist** from the reference: project brief completeness, consistency of conventions/infrastructure/architecture decisions, rules pointer consistency, user-provided wording preservation, app-planner writable-boundary compliance, and downstream `feature-planner` readiness to produce `.prizmkit/plans/feature-list.json` without guessing.
+5. **Apply accepted fixes through the source/writer path**: project brief fixes go through the draft/checklist source, instruction-file section fixes go through the selected platform instruction file section source with user confirmation when changing approved wording, rules fixes re-render from rules configuration answers/templates when available, and `root.prizm` fixes are limited to the `RULES:` pointer line.
+6. **Recheck changed sections directly** after every accepted fix batch.
+7. **Report CP-AP-6** in the completion summary: include local generated-plan review verdict, reviewed app-planning artifacts/sections, accepted fixes (or "none"), and final writer/validation result.
 
 ## Architecture Decision Capture
 
@@ -277,7 +292,7 @@ When the session appears to be ending:
 
 ## Completion Summary
 
-After all checkpoints pass, present a summary and end the session:
+After CP-AP-6 passes or is reported not applicable, present a summary and end the session:
 
 1. **Summary** (as text): List all project-level artifacts produced:
    - Project conventions → `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Project Conventions`
@@ -286,6 +301,7 @@ After all checkpoints pass, present a summary and end the session:
    - Architecture decisions (if any) → `AGENTS.md` / `CLAUDE.md` / `CODEBUDDY.md` `### Architecture Decisions`
    - Dev rules (if configured) → `.prizmkit/rules/<layer>-rules.md` (with `root.prizm` `RULES:` pointer)
    - Project brief → `.prizmkit/plans/project-brief.md`
+   - Local generated-plan review → verdict, reviewed app-planning artifacts/sections, accepted fixes (or "none"), and final writer/validation result
 
 2. **Suggest possible next steps** (as text, NOT auto-invoked):
    > Project-level planning is complete. When you're ready, here are some possible next steps:

package/bundled/skills/app-planner/references/generated-plan-review.md

@@ -0,0 +1,67 @@
+# Generated Plan Review — App Planner
+
+Use this local review loop before app-planner presents the final completion summary for current-session final planning artifacts. This is a planner-output review, not an implementation/code-diff review.
+
+## Trigger
+
+Run only when the current `app-planner` session wrote or rewrote final app-level planning content. This includes project brief finalization, project conventions, infrastructure configuration, architecture decisions, rules files, or a `root.prizm` `RULES:` pointer update.
+
+For explore-only sessions, draft-save exits, validate-only checks, or other flows with no new final planning content, report: `Local generated-plan review: not applicable — no new final planning content written.`
+
+## Direct Artifact Reads
+
+Planning artifacts may be gitignored, untracked, or absent from staged and unstaged diffs. Read the actual files and source sections directly when they were produced or changed in the current session:
+
+- Project brief: `.prizmkit/plans/project-brief.md`
+- Draft brief when present: `.prizmkit/plans/project-brief.draft.md`
+- Project instruction files selected by `.prizmkit/manifest.json`: `AGENTS.md`, `CLAUDE.md`, `CODEBUDDY.md`
+- Generated rule files: `.prizmkit/rules/<layer>-rules.md`
+- Prizm docs root pointer: `.prizmkit/prizm-docs/root.prizm` `RULES:` line only
+- In-memory answers, draft brief data, rules configuration answers, or section snapshots captured before writes
+
+Do not rely on `git status`, `git diff`, or `git diff --cached` to decide whether app-planner output exists or changed. Do not invoke `/prizmkit-code-review` for this planner-output gate; `/prizmkit-code-review` remains the implementation/code-diff review gate after `/prizmkit-implement`.
+
+## Review Scope
+
+1. Compare current final artifacts with pre-session snapshots or in-memory drafts when available.
+2. Review only newly added or changed app-planning sections from the current session.
+3. Preserve unchanged historical project brief ideas, instruction-file sections, rules files, and Prizm doc content.
+4. For `.prizmkit/prizm-docs/root.prizm`, review only the `RULES:` pointer line managed by rules configuration.
+5. If no snapshot exists, review only the artifacts the current app-planner session reports as produced.
+
+## Source-of-Truth Map
+
+- `project-brief.md` fixes go through the draft/checklist project brief source representation described in `project-brief-guide.md`, then rewrite the final brief through the existing project brief writer path.
+- Project conventions, infrastructure, and architecture decisions are source sections in `AGENTS.md`, `CLAUDE.md`, or `CODEBUDDY.md`. If a fix changes user-approved wording or meaning, ask for user confirmation before rewriting.
+- `.prizmkit/rules/<layer>-rules.md` fixes should re-render from the rules configuration answers and template inputs when available. If no structured source remains, update the source rule section explicitly and report that source path.
+- `root.prizm` fixes are limited to correcting or adding the `RULES:` pointer line; do not rewrite unrelated root content.
+
+## Review Checklist
+
+For every reviewed app-planning artifact or section, check:
+
+- Project brief completeness: goal, users, differentiators, constraints, tech stack assumptions, and at least three actionable ideas when producing a final brief
+- Consistency among conventions, infrastructure, architecture decisions, and project brief content
+- Infrastructure completeness or explicit deferral for database, deployment, and cloud services topics when those flows ran
+- Rules pointer consistency: generated `.prizmkit/rules/<layer>-rules.md` files are referenced by the `root.prizm` `RULES:` line when rules were configured
+- User-provided wording preservation in project brief ideas, conventions, infrastructure notes, architecture decisions, and rules
+- Downstream readiness: `feature-planner` has enough context to produce `.prizmkit/plans/feature-list.json` without guessing core app purpose, stack, constraints, or implementation conventions
+- No implementation/scaffolding actions are introduced by the app plan; outputs stay within app-planner's writable boundary
+
+## Fix Loop
+
+1. Present findings with artifact path, section name, severity, evidence, and suggested source change.
+2. Accept only findings that improve planner correctness, consistency, user wording preservation, or downstream feature-planner readiness.
+3. Apply accepted fixes to the source representation first: brief draft/checklist, instruction-file section source, rules answer/template source, or `root.prizm` `RULES:` pointer source.
+4. Regenerate or rewrite final artifacts through the same writer path used by app-planner. Do not hand-patch final artifacts as a shortcut when a draft/source representation exists.
+5. Re-read the changed final artifacts directly and re-run the local review only for changed sections.
+
+## Report Format
+
+Report in the final completion summary:
+
+- `Local generated-plan review: PASS` or `NEEDS_FIXES`
+- Reviewed app-planning sections/artifacts
+- Accepted fixes, or `none`
+- Final writer/validation result for each changed artifact
+- Note when review was not applicable because no new final planning content was written