prizmkit 1.1.91 → 1.1.93

package/bundled/dev-pipeline-windows/scripts/update-feature-status.py

@@ -17,7 +17,7 @@ Usage:
         --feature-list <path> --state-dir <path> \
         --action <get_next|start|update|status|pause|reset|clean|complete|unskip> \
         [--feature-id <id>] [--session-status <status>] \
-        [--session-id <id>] [--max-retries <n>] \
+        [--session-id <id>] [--max-retries <n>] [--max-infra-retries <n>] \
         [--features <filter>]
 """
 
@@ -94,7 +94,13 @@ def parse_args():
         "--max-retries",
         type=int,
         default=3,
-        help="Maximum retry count before marking as failed (default: 3)",
+        help="Maximum code retry count before marking as failed (default: 3)",
+    )
+    parser.add_argument(
+        "--max-infra-retries",
+        type=int,
+        default=3,
+        help="Maximum infrastructure retry count before marking as failed (default: 3)",
     )
     parser.add_argument(
         "--feature-slug",
@@ -170,6 +176,9 @@ def load_feature_status(state_dir, feature_id):
             "feature_id": feature_id,
             "retry_count": 0,
             "max_retries": 3,
+            "max_infra_retries": 3,
+            "infra_error_count": 0,
+            "last_infra_error_session_id": None,
             "sessions": [],
             "last_session_id": None,
             "resume_from_phase": None,
@@ -183,6 +192,9 @@ def load_feature_status(state_dir, feature_id):
             "feature_id": feature_id,
             "retry_count": 0,
             "max_retries": 3,
+            "max_infra_retries": 3,
+            "infra_error_count": 0,
+            "last_infra_error_session_id": None,
             "sessions": [],
             "last_session_id": None,
             "resume_from_phase": None,
@@ -565,6 +577,7 @@ def action_get_next(feature_list_data, state_dir, feature_filter=None):
         "feature_id": chosen_id,
         "title": chosen.get("title", ""),
         "retry_count": chosen_status_data.get("retry_count", 0),
+        "infra_error_count": chosen_status_data.get("infra_error_count", 0),
         "resume_from_phase": chosen_status_data.get("resume_from_phase", None),
     }
     print(json.dumps(result, indent=2, ensure_ascii=False))
@@ -585,6 +598,7 @@ def action_update(args, feature_list_path, state_dir):
     session_status = args.session_status
     session_id = args.session_id
     max_retries = args.max_retries
+    max_infra_retries = args.max_infra_retries
 
     if not feature_id:
         error_out("--feature-id is required for 'update' action")
@@ -600,6 +614,8 @@ def action_update(args, feature_list_path, state_dir):
     new_status = current_list_status
 
     if session_status == "success":
+        fs["infra_error_count"] = 0
+        fs["last_infra_error_session_id"] = None
         # No-op guard: if this exact successful session was already recorded,
         # avoid rewriting state files again (prevents post-commit dirty changes).
         existing_sessions = fs.get("sessions", [])
@@ -616,6 +632,8 @@ def action_update(args, feature_list_path, state_dir):
                 "session_status": session_status,
                 "new_status": "completed",
                 "retry_count": fs.get("retry_count", 0),
+                "infra_error_count": fs.get("infra_error_count", 0),
+                "max_infra_retries": max_infra_retries,
                 "resume_from_phase": fs.get("resume_from_phase"),
                 "updated_at": fs.get("updated_at"),
                 "no_op": True,
@@ -654,15 +672,24 @@ def action_update(args, feature_list_path, state_dir):
             return
     elif session_status == "infra_error":
         # AI CLI/provider outage, auth failure, gateway error, etc.
-        # This is outside the code's control, so keep the item pending without
-        # consuming the task's retry budget.
-        new_status = "pending"
-        fs["infra_error_count"] = fs.get("infra_error_count", 0) + 1
+        # Infra failures do not consume the code retry budget, but they still
+        # need their own bounded budget so a flaky provider cannot loop forever.
+        infra_error_count = fs.get("infra_error_count", 0) + 1
+        fs["infra_error_count"] = infra_error_count
         fs["last_infra_error_session_id"] = session_id
+        fs["max_infra_retries"] = max_infra_retries
+        fs["degraded_reason"] = "infra_error"
         if session_id:
             fs["last_session_id"] = session_id
         fs["resume_from_phase"] = None
 
+        if infra_error_count >= max_infra_retries:
+            new_status = "failed"
+            if session_id:
+                fs["last_failed_session_id"] = session_id
+        else:
+            new_status = "pending"
+
         err = update_feature_in_list(feature_list_path, feature_id, new_status)
         if err:
             error_out("Failed to update .prizmkit/plans/feature-list.json: {}".format(err))
@@ -714,6 +741,8 @@ def action_update(args, feature_list_path, state_dir):
         "session_status": session_status,
         "new_status": new_status,
         "retry_count": fs["retry_count"],
+        "infra_error_count": fs.get("infra_error_count", 0),
+        "max_infra_retries": max_infra_retries,
         "resume_from_phase": fs.get("resume_from_phase"),
         "updated_at": fs["updated_at"],
     }
@@ -1143,6 +1172,8 @@ def action_start(args, feature_list_path, state_dir):
         "feature_id": feature_id,
         "old_status": old_status,
         "new_status": "in_progress",
+        "retry_count": fs.get("retry_count", 0),
+        "infra_error_count": fs.get("infra_error_count", 0),
         "updated_at": fs["updated_at"],
     }
     print(json.dumps(result, indent=2, ensure_ascii=False))
@@ -1171,6 +1202,8 @@ def action_reset(args, feature_list_path, state_dir):
 
     # Reset runtime fields
     fs["retry_count"] = 0
+    fs["infra_error_count"] = 0
+    fs["last_infra_error_session_id"] = None
     fs["sessions"] = []
     fs["last_session_id"] = None
     fs["resume_from_phase"] = None
@@ -1264,6 +1297,8 @@ def action_clean(args, feature_list_path, state_dir):
     old_retry = fs.get("retry_count", 0)
 
     fs["retry_count"] = 0
+    fs["infra_error_count"] = 0
+    fs["last_infra_error_session_id"] = None
     fs["sessions"] = []
     fs["last_session_id"] = None
     fs["resume_from_phase"] = None
@@ -1423,6 +1458,8 @@ def action_unskip(args, feature_list_path, state_dir):
     for fid in to_reset:
         fs = load_feature_status(state_dir, fid)
         fs["retry_count"] = 0
+        fs["infra_error_count"] = 0
+        fs["last_infra_error_session_id"] = None
         fs["sessions"] = []
         fs["last_session_id"] = None
         fs["resume_from_phase"] = None

package/bundled/dev-pipeline-windows/scripts/update-refactor-status.py

@@ -16,7 +16,7 @@ Usage:
         --refactor-list <path> --state-dir <path> \
         --action <get_next|start|update|status|pause|reset|clean|unskip> \
         [--refactor-id <id>] [--session-status <status>] \
-        [--session-id <id>] [--max-retries <n>]
+        [--session-id <id>] [--max-retries <n>] [--max-infra-retries <n>]
 """
 
 import argparse
@@ -87,7 +87,8 @@ def parse_args():
         help="Session outcome status (required for 'update' action)",
     )
     parser.add_argument("--session-id", default=None, help="Session ID (optional, for 'update' action)")
-    parser.add_argument("--max-retries", type=int, default=3, help="Maximum retry count (default: 3)")
+    parser.add_argument("--max-retries", type=int, default=3, help="Maximum code retry count (default: 3)")
+    parser.add_argument("--max-infra-retries", type=int, default=3, help="Maximum infrastructure retry count (default: 3)")
     parser.add_argument("--project-root", default=None, help="Project root directory. Required for 'clean' action.")
     return parser.parse_args()
 
@@ -103,6 +104,9 @@ def _default_status(refactor_id):
         "refactor_id": refactor_id,
         "retry_count": 0,
         "max_retries": 3,
+        "max_infra_retries": 3,
+        "infra_error_count": 0,
+        "last_infra_error_session_id": None,
         "sessions": [],
         "last_session_id": None,
         "resume_from_phase": None,
@@ -268,6 +272,7 @@ def action_get_next(refactor_list_data, state_dir):
         "priority": chosen.get("priority", "medium"),
         "complexity": chosen.get("complexity", "medium"),
         "retry_count": chosen_status_data.get("retry_count", 0),
+        "infra_error_count": chosen_status_data.get("infra_error_count", 0),
         "resume_from_phase": chosen_status_data.get("resume_from_phase", None),
     }
     print(json.dumps(result, indent=2, ensure_ascii=False))
@@ -282,6 +287,7 @@ def action_update(args, refactor_list_path, state_dir):
     session_status = args.session_status
     session_id = args.session_id
     max_retries = args.max_retries
+    max_infra_retries = args.max_infra_retries
 
     if not refactor_id:
         error_out("--refactor-id is required for 'update' action")
@@ -296,6 +302,8 @@ def action_update(args, refactor_list_path, state_dir):
     new_status = get_refactor_status_from_list(refactor_list_path, refactor_id)
 
     if session_status == "success":
+        rs["infra_error_count"] = 0
+        rs["last_infra_error_session_id"] = None
         new_status = "completed"
         rs["resume_from_phase"] = None
         err = update_refactor_in_list(refactor_list_path, refactor_id, "completed")
@@ -320,11 +328,25 @@ def action_update(args, refactor_list_path, state_dir):
             error_out("Failed to update .prizmkit/plans/refactor-list.json: {}".format(err))
             return
     elif session_status == "infra_error":
-        new_status = "pending"
-        rs["infra_error_count"] = rs.get("infra_error_count", 0) + 1
+        # AI CLI/provider outage, auth failure, gateway error, etc.
+        # Infra failures do not consume the code retry budget, but they still
+        # need their own bounded budget so a flaky provider cannot loop forever.
+        infra_error_count = rs.get("infra_error_count", 0) + 1
+        rs["infra_error_count"] = infra_error_count
         rs["last_infra_error_session_id"] = session_id
+        rs["max_infra_retries"] = max_infra_retries
+        rs["degraded_reason"] = "infra_error"
+        if session_id:
+            rs["last_session_id"] = session_id
         rs["resume_from_phase"] = None
 
+        if infra_error_count >= max_infra_retries:
+            new_status = "failed"
+            if session_id:
+                rs["last_failed_session_id"] = session_id
+        else:
+            new_status = "pending"
+
         err = update_refactor_in_list(refactor_list_path, refactor_id, new_status)
         if err:
             error_out("Failed to update .prizmkit/plans/refactor-list.json: {}".format(err))
@@ -379,6 +401,8 @@ def action_update(args, refactor_list_path, state_dir):
         "session_status": session_status,
         "new_status": new_status,
         "retry_count": rs["retry_count"],
+        "infra_error_count": rs.get("infra_error_count", 0),
+        "max_infra_retries": max_infra_retries,
         "resume_from_phase": rs.get("resume_from_phase"),
         "updated_at": rs["updated_at"],
     }
@@ -728,6 +752,8 @@ def action_reset(args, refactor_list_path, state_dir):
     old_retry = rs.get("retry_count", 0)
 
     rs["retry_count"] = 0
+    rs["infra_error_count"] = 0
+    rs["last_infra_error_session_id"] = None
     rs["sessions"] = []
     rs["last_session_id"] = None
     rs["resume_from_phase"] = None
@@ -799,6 +825,8 @@ def action_clean(args, refactor_list_path, state_dir):
     old_retry = rs.get("retry_count", 0)
 
     rs["retry_count"] = 0
+    rs["infra_error_count"] = 0
+    rs["last_infra_error_session_id"] = None
     rs["sessions"] = []
     rs["last_session_id"] = None
     rs["resume_from_phase"] = None
@@ -887,6 +915,8 @@ def action_start(args, refactor_list_path, state_dir):
         "refactor_id": refactor_id,
         "old_status": old_status,
         "new_status": "in_progress",
+        "retry_count": rs.get("retry_count", 0),
+        "infra_error_count": rs.get("infra_error_count", 0),
         "updated_at": rs["updated_at"],
     }
     print(json.dumps(result, indent=2, ensure_ascii=False))
@@ -1025,6 +1055,8 @@ def action_unskip(args, refactor_list_path, state_dir):
     for rid in to_reset:
         rs = load_refactor_status(state_dir, rid)
         rs["retry_count"] = 0
+        rs["infra_error_count"] = 0
+        rs["last_infra_error_session_id"] = None
         rs["sessions"] = []
         rs["last_session_id"] = None
         rs["resume_from_phase"] = None

package/bundled/skills/_metadata.json

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

package/bundled/skills/bugfix-pipeline-launcher/SKILL.md

@@ -129,7 +129,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```bash
-   VERBOSE=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
+   VERBOSE=1 MAX_RETRIES=5 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
      .prizmkit/dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json
    ```
 

package/bundled/skills/bugfix-pipeline-launcher/references/configuration.md

@@ -12,7 +12,6 @@ Translating user responses to env vars:
 | Verbose: On | `VERBOSE=1` |
 | Max retries: N | `MAX_RETRIES=N` |
 | Critic: On | `ENABLE_CRITIC=1` |
-| Timeout: value | `SESSION_TIMEOUT=<seconds>` |
 | Stop on failure: On | `STOP_ON_FAILURE=1` |
 | Deploy: Yes | `ENABLE_DEPLOY=1` |
 | Effort: value | `PRIZMKIT_EFFORT=<value>` |
@@ -28,9 +27,6 @@ Not exposed in interactive menu, pass via `--env`:
 | `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `bugfix/pipeline-{run_id}`) |
 | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
 | `HEARTBEAT_STALE_THRESHOLD` | `600` | Max seconds without heartbeat before marking stale |
-| `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
-| `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
-| `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
 
 ## Interactive Configuration Options
 
@@ -52,28 +48,22 @@ Present these via `AskUserQuestion` in step 5. Round 1 is one `AskUserQuestion`
 - On — Enable adversarial critic review (`ENABLE_CRITIC=1`): an independent AI agent reviews the diagnosis/plan for completeness and the fix for defects, edge cases, and regression risks. Adds ~5-10 min per bug.
 
 **Question 4 — Advanced config?** (multiSelect: false):
-- No (default) — Use defaults for session timeout and failure behavior
-- Yes — Configure session timeout, stop-on-failure, deploy, and reasoning effort options
+- No (default) — Use defaults for failure behavior
+- Yes — Configure stop-on-failure, deploy, and reasoning effort options
 
 Note: Bug filter defaults to all bugs (by severity order). Default Critic to Off unless bugs have `severity: "critical"` or `severity: "high"` (in which case default to On). If the user selects "Other" on any option, handle their custom input.
 
 ### Round 2 (only if Advanced config = Yes)
 
-**Question 1 — Session timeout** (multiSelect: false):
-- None (default) — No timeout
-- 30 min — `SESSION_TIMEOUT=1800`
-- 1 hour — `SESSION_TIMEOUT=3600`
-- 2 hours — `SESSION_TIMEOUT=7200`
-
-**Question 2 — Stop on failure** (multiSelect: false):
+**Question 1 — Stop on failure** (multiSelect: false):
 - Off (default) — Pipeline continues to next task after failure
 - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
-**Question 3 — Deploy after completion?** (multiSelect: false):
+**Question 2 — Deploy after completion?** (multiSelect: false):
 - No (default) — Skip deployment after pipeline completes
 - Yes — Run /prizmkit-deploy automatically after all bugs fixed successfully (`ENABLE_DEPLOY=1`). Deployment is blocked if any bug was not fixed (status not 'completed', 'skipped', or 'needs_info').
 
-**Question 4 — Reasoning effort** (multiSelect: false):
+**Question 3 — Reasoning effort** (multiSelect: false):
 - Default (none) — Use CLI default
 - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
 - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)

package/bundled/skills/feature-pipeline-launcher/SKILL.md

@@ -150,12 +150,12 @@ Detect user intent from their message, then follow the corresponding workflow:
    - 5
 
    **Question 4 — Advanced config?** (multiSelect: false):
-   - No (default) — Use defaults for session timeout and failure behavior
-   - Yes — Configure session timeout, stop-on-failure, deploy-after-completion, and reasoning effort options
+   - No (default) — Use defaults for failure behavior
+   - Yes — Configure stop-on-failure, deploy-after-completion, and reasoning effort options
 
    Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
 
-   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion` — see the advanced config questions (session timeout, stop-on-failure, deploy-after-completion, reasoning effort) in `${SKILL_DIR}/references/configuration.md`.
+   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion` — see the advanced config questions (stop-on-failure, deploy-after-completion, reasoning effort) in `${SKILL_DIR}/references/configuration.md`.
 
    **Environment variable mapping** and **advanced environment variables** tables — read `${SKILL_DIR}/references/configuration.md` for the full translation tables (8 config→env mappings + 9 advanced variables).
 
@@ -168,7 +168,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```bash
-   VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
+   VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
      .prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json --features F-001:F-005
    ```
 

package/bundled/skills/feature-pipeline-launcher/references/configuration.md

@@ -6,21 +6,15 @@ Environment variable mappings for the feature launcher.
 
 Asked only when the user chose "Yes" to Advanced config in step 6.
 
-**Question 1 — Session timeout** (multiSelect: false):
-- None (default) — No timeout
-- 30 min — `SESSION_TIMEOUT=1800`
-- 1 hour — `SESSION_TIMEOUT=3600`
-- 2 hours — `SESSION_TIMEOUT=7200`
-
-**Question 2 — Stop on failure** (multiSelect: false):
+**Question 1 — Stop on failure** (multiSelect: false):
 - Off (default) — Pipeline continues to next task after failure
 - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
-**Question 3 — Deploy after completion?** (multiSelect: false):
+**Question 2 — Deploy after completion?** (multiSelect: false):
 - No (default) — Skip deployment after pipeline completes
 - Yes — Run /prizmkit-deploy automatically after all features complete successfully (`ENABLE_DEPLOY=1`). Deployment is blocked if any feature did not complete successfully (status not 'completed' or manually 'skipped').
 
-**Question 4 — Reasoning effort** (multiSelect: false):
+**Question 3 — Reasoning effort** (multiSelect: false):
 - Default (none) — Use CLI default
 - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
 - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
@@ -38,7 +32,6 @@ Translating user responses to env vars:
 | Verbose: Off | `VERBOSE=0` |
 | Verbose: On | `VERBOSE=1` |
 | Max retries: N | `MAX_RETRIES=N` |
-| Timeout: value | `SESSION_TIMEOUT=<seconds>` |
 | Stop on failure: On | `STOP_ON_FAILURE=1` |
 | Deploy: Yes | `ENABLE_DEPLOY=1` |
 | Effort: value | `PRIZMKIT_EFFORT=<value>` |
@@ -55,9 +48,6 @@ Not exposed in interactive menu, pass via `--env`:
 | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
 | `HEARTBEAT_STALE_THRESHOLD` | `600` | Max seconds without heartbeat before marking stale |
 | `PIPELINE_MODE` | (none) | Override mode for all features: `lite`\|`standard`\|`full` |
-| `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
-| `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
-| `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
 
 ## Error Handling
 

package/bundled/skills/refactor-pipeline-launcher/SKILL.md

@@ -154,8 +154,8 @@ Detect user intent from their message, then follow the corresponding workflow:
    - Off — Skip post-task test verification (faster but riskier)
 
    **Question 4 — Advanced config?** (multiSelect: false):
-   - No (default) — Use defaults for critic review, session timeout, and failure behavior
-   - Yes — Configure critic review, session timeout, stop-on-failure, and reasoning effort options
+   - No (default) — Use defaults for critic review and failure behavior
+   - Yes — Configure critic review, stop-on-failure, and reasoning effort options
 
    Note: Refactor filter defaults to all refactor items (by priority order). If the user selects "Other" on any option, handle their custom input.
 
@@ -172,7 +172,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```bash
-   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
+   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5 ENABLE_DEPLOY=1 PRIZMKIT_EFFORT=high \
      .prizmkit/dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
    ```
 

package/bundled/skills/refactor-pipeline-launcher/references/configuration.md

@@ -14,7 +14,6 @@ Translating user responses to env vars:
 | Strict behavior: On | `STRICT_BEHAVIOR_CHECK=1` |
 | Strict behavior: Off | `STRICT_BEHAVIOR_CHECK=0` |
 | Critic: On | `ENABLE_CRITIC=true` |
-| Timeout: value | `SESSION_TIMEOUT=<seconds>` |
 | Stop on failure: On | `STOP_ON_FAILURE=1` |
 | Deploy: Yes | `ENABLE_DEPLOY=1` |
 | Effort: value | `PRIZMKIT_EFFORT=<value>` |
@@ -30,9 +29,6 @@ Not exposed in interactive menu, pass via `--env`:
 | `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `refactor/pipeline-{run_id}`) |
 | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
 | `HEARTBEAT_STALE_THRESHOLD` | `600` | Max seconds without heartbeat before marking stale |
-| `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
-| `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
-| `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
 
 ## Error Handling
 
@@ -57,23 +53,17 @@ Not exposed in interactive menu, pass via `--env`:
 
 Only run this when the user answered "Yes" to the **Advanced config?** question in step 6. It applies to a minority of sessions.
 
-Ask a second round of `AskUserQuestion` with these 4 questions:
+Ask a second round of `AskUserQuestion` with these 3 questions:
 
-**Question 1 — Session timeout** (multiSelect: false):
-- None (default) — No timeout
-- 30 min — `SESSION_TIMEOUT=1800`
-- 1 hour — `SESSION_TIMEOUT=3600`
-- 2 hours — `SESSION_TIMEOUT=7200`
-
-**Question 2 — Stop on failure** (multiSelect: false):
+**Question 1 — Stop on failure** (multiSelect: false):
 - Off (default) — Pipeline continues to next task after failure
 - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
-**Question 3 — Critic review** (multiSelect: false):
+**Question 2 — Critic review** (multiSelect: false):
 - Off (default) — Skip adversarial review
 - On — Enable adversarial critic review: an independent AI agent reviews the refactor plan for completeness and the implementation for regressions, missed edge cases, and behavior violations. Adds ~5-10 min per refactor task.
 
-**Question 4 — Deploy after completion?** (multiSelect: false):
+**Question 3 — Deploy after completion?** (multiSelect: false):
 - No (default) — Skip deployment after pipeline completes
 - Yes — Run /prizmkit-deploy automatically after all refactors complete successfully (`ENABLE_DEPLOY=1`). Deployment is blocked if any refactor did not complete successfully (status not 'completed' or manually 'skipped').
 

package/bundled/skills-windows/bugfix-pipeline-launcher/SKILL.md

@@ -155,7 +155,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```powershell
-   $env:VERBOSE = "1"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"; $env:PRIZMKIT_EFFORT = "high"
+   $env:VERBOSE = "1"; $env:MAX_RETRIES = "5"; $env:PRIZMKIT_EFFORT = "high"
    .\.prizmkit\dev-pipeline\run-bugfix.ps1 run .prizmkit/plans/bug-fix-list.json
    ```
 

package/bundled/skills-windows/bugfix-pipeline-launcher/references/configuration.md

@@ -12,7 +12,6 @@ Translating user responses to env vars:
 | Verbose: On | `VERBOSE=1` |
 | Max retries: N | `MAX_RETRIES=N` |
 | Critic: On | `ENABLE_CRITIC=1` |
-| Timeout: value | `SESSION_TIMEOUT=<seconds>` |
 | Stop on failure: On | `STOP_ON_FAILURE=1` |
 | Deploy: Yes | `ENABLE_DEPLOY=1` |
 | Effort: value | `PRIZMKIT_EFFORT=<value>` |
@@ -28,9 +27,6 @@ Not exposed in interactive menu, pass via `--env`:
 | `DEV_BRANCH` | auto-generated | Custom dev branch name (default: `bugfix/pipeline-{run_id}`) |
 | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
 | `HEARTBEAT_STALE_THRESHOLD` | `600` | Max seconds without heartbeat before marking stale |
-| `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
-| `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
-| `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
 
 ## Interactive Configuration Options
 
@@ -52,24 +48,18 @@ Present these via `AskUserQuestion` in step 5. Round 1 is one `AskUserQuestion`
 - On — Enable adversarial critic review (`ENABLE_CRITIC=1`): an independent AI agent reviews the diagnosis/plan for completeness and the fix for defects, edge cases, and regression risks. Adds ~5-10 min per bug.
 
 **Question 4 — Advanced config?** (multiSelect: false):
-- No (default) — Use defaults for session timeout and failure behavior
-- Yes — Configure session timeout, stop-on-failure, and reasoning effort options
+- No (default) — Use defaults for failure behavior
+- Yes — Configure stop-on-failure, and reasoning effort options
 
 Note: Bug filter defaults to all bugs (by severity order). Default Critic to Off unless bugs have `severity: "critical"` or `severity: "high"` (in which case default to On). If the user selects "Other" on any option, handle their custom input.
 
 ### Round 2 (only if Advanced config = Yes)
 
-**Question 1 — Session timeout** (multiSelect: false):
-- None (default) — No timeout
-- 30 min — `SESSION_TIMEOUT=1800`
-- 1 hour — `SESSION_TIMEOUT=3600`
-- 2 hours — `SESSION_TIMEOUT=7200`
-
-**Question 2 — Stop on failure** (multiSelect: false):
+**Question 1 — Stop on failure** (multiSelect: false):
 - Off (default) — Pipeline continues to next task after failure
 - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
-**Question 3 — Reasoning effort** (multiSelect: false):
+**Question 2 — Reasoning effort** (multiSelect: false):
 - Default (none) — Use CLI default
 - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
 - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)

package/bundled/skills-windows/feature-pipeline-launcher/SKILL.md

@@ -176,12 +176,12 @@ Detect user intent from their message, then follow the corresponding workflow:
    - 5
 
    **Question 4 — Advanced config?** (multiSelect: false):
-   - No (default) — Use defaults for session timeout and failure behavior
-   - Yes — Configure session timeout, stop-on-failure, and reasoning effort options
+   - No (default) — Use defaults for failure behavior
+   - Yes — Configure stop-on-failure, and reasoning effort options
 
    Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
 
-   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion` — see the advanced config questions (session timeout, stop-on-failure, reasoning effort) in `${SKILL_DIR}/references/configuration.md`.
+   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion` — see the advanced config questions (stop-on-failure, reasoning effort) in `${SKILL_DIR}/references/configuration.md`.
 
    **Environment variable mapping** and **advanced environment variables** tables — read `${SKILL_DIR}/references/configuration.md` for the full translation tables (8 config→env mappings + 9 advanced variables).
 
@@ -195,7 +195,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```powershell
-   $env:VERBOSE = "1"; $env:ENABLE_CRITIC = "true"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"; $env:PRIZMKIT_EFFORT = "high"
+   $env:VERBOSE = "1"; $env:ENABLE_CRITIC = "true"; $env:MAX_RETRIES = "5"; $env:PRIZMKIT_EFFORT = "high"
    .\.prizmkit\dev-pipeline\run-feature.ps1 run .prizmkit/plans/feature-list.json --features F-001:F-005
    ```
 

package/bundled/skills-windows/feature-pipeline-launcher/references/configuration.md

@@ -6,17 +6,11 @@ Environment variable mappings for the feature launcher.
 
 Asked only when the user chose "Yes" to Advanced config in step 6.
 
-**Question 1 — Session timeout** (multiSelect: false):
-- None (default) — No timeout
-- 30 min — `SESSION_TIMEOUT=1800`
-- 1 hour — `SESSION_TIMEOUT=3600`
-- 2 hours — `SESSION_TIMEOUT=7200`
-
-**Question 2 — Stop on failure** (multiSelect: false):
+**Question 1 — Stop on failure** (multiSelect: false):
 - Off (default) — Pipeline continues to next task after failure
 - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
-**Question 3 — Reasoning effort** (multiSelect: false):
+**Question 2 — Reasoning effort** (multiSelect: false):
 - Default (none) — Use CLI default
 - low — Minimize reasoning, fastest output (`PRIZMKIT_EFFORT=low`)
 - medium — Moderate reasoning (`PRIZMKIT_EFFORT=medium`)
@@ -34,7 +28,6 @@ Translating user responses to env vars:
 | Verbose: Off | `VERBOSE=0` |
 | Verbose: On | `VERBOSE=1` |
 | Max retries: N | `MAX_RETRIES=N` |
-| Timeout: value | `SESSION_TIMEOUT=<seconds>` |
 | Stop on failure: On | `STOP_ON_FAILURE=1` |
 | Deploy: Yes | `ENABLE_DEPLOY=1` |
 | Effort: value | `PRIZMKIT_EFFORT=<value>` |
@@ -51,9 +44,6 @@ Not exposed in interactive menu, pass via `--env`:
 | `HEARTBEAT_INTERVAL` | `30` | Heartbeat log interval in seconds |
 | `HEARTBEAT_STALE_THRESHOLD` | `600` | Max seconds without heartbeat before marking stale |
 | `PIPELINE_MODE` | (none) | Override mode for all features: `lite`\|`standard`\|`full` |
-| `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
-| `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
-| `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
 
 ## Error Handling
 

package/bundled/skills-windows/refactor-pipeline-launcher/SKILL.md

@@ -176,8 +176,8 @@ Detect user intent from their message, then follow the corresponding workflow:
    - 5
 
    **Question 3 — Advanced config?** (multiSelect: false):
-   - No (default) — Use defaults for critic review, session timeout, and failure behavior
-   - Yes — Configure critic review, session timeout, stop-on-failure, and reasoning effort options
+   - No (default) — Use defaults for critic review and failure behavior
+   - Yes — Configure critic review, stop-on-failure, and reasoning effort options
 
    Note: Refactor filter defaults to all refactor items (by priority order). If the user selects "Other" on any option, handle their custom input.
 
@@ -195,7 +195,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```powershell
-   $env:VERBOSE = "1"; $env:MAX_RETRIES = "5"; $env:SESSION_TIMEOUT = "3600"; $env:PRIZMKIT_EFFORT = "high"
+   $env:VERBOSE = "1"; $env:MAX_RETRIES = "5"; $env:PRIZMKIT_EFFORT = "high"
    .\.prizmkit\dev-pipeline\run-refactor.ps1 run .prizmkit/plans/refactor-list.json
    ```