prizmkit 1.0.101 → 1.0.103

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.101",
-  "bundledAt": "2026-03-23T16:44:31.127Z",
-  "bundledFrom": "7da7d80"
+  "frameworkVersion": "1.0.103",
+  "bundledAt": "2026-03-24T17:11:59.061Z",
+  "bundledFrom": "5e837b4"
 }

package/bundled/dev-pipeline/run.sh

@@ -1125,8 +1125,8 @@ case "${1:-run}" in
             run_one "$@"
         else
             # Parse positional and --features flag
-            local _run_feature_list="feature-list.json"
-            local _run_features_filter=""
+             _run_feature_list="feature-list.json"
+             _run_features_filter=""
             while [[ $# -gt 0 ]]; do
                 case "$1" in
                     --features)

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.101",
+  "version": "1.0.103",
   "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/app-planner/SKILL.md

@@ -75,12 +75,31 @@ Actions:
 3. Append features with next sequential `F-NNN` IDs
 4. Preserve style/language/detail consistency with existing plan
 
+## Intent Confirmation (Mandatory First Step)
+
+After scenario routing, immediately confirm the user's deliverable intent:
+
+1. **Ask explicitly**:
+   - "本次规划的目标是生成可执行的 `feature-list.json` 吗？还是只想先讨论想法？"
+   - (English: "Is the goal to produce a `feature-list.json` for pipeline execution, or just explore ideas?")
+
+2. **Route by answer**:
+   - **"Produce feature-list.json"** → Continue to Core Workflow. Set session goal = `produce`.
+   - **"Just explore ideas"** → Enter **Exploration Mode**:
+     - Run Phases 1-5 normally (vision, constraints, feature proposals, refinement, DAG)
+     - At Phase 5 completion, re-ask: "Ideas are taking shape. Ready to generate `feature-list.json` now?"
+     - If yes → continue to Phase 6
+     - If no → summarize discussion, suggest saving notes, end session
+
+3. **Session goal tracking**: Track the intent (`produce` or `explore`) throughout the session. If `explore`, always re-prompt before ending.
+
 ## Core Workflow
 
 Execute the selected scenario workflow in conversation mode with mandatory checkpoints:
 
 ### Interactive Phases
 1. clarify business goal and scope
+   1.1 confirm deliverable intent (→ Intent Confirmation)
 2. confirm constraints and tech assumptions
 3. propose feature set with dependencies
 4. refine descriptions and acceptance criteria
@@ -95,6 +114,7 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 
 | Checkpoint | Artifact/State | Criteria | Phase |
 |-----------|----------------|----------|-------|
+| **CP-AP-0** | Intent Confirmed | User confirmed session goal (produce / explore) | 1 |
 | **CP-AP-1** | Vision Summary | Goal/users/differentiators confirmed by user | 1-2 |
 | **CP-AP-2** | Feature Proposals | Feature set with titles+deps identified (pre-validation) | 3-5 |
 | **CP-AP-3** | DAG Validity | No cycles, dependencies resolved (validation dry-run) | 6 |
@@ -331,6 +351,29 @@ The pipeline reads `feature-list.json` from the project root by default. If the
 
 Maintainer note: evaluation workflow moved to `assets/evaluation-guide.md`.
 
+## Session Exit Gate
+
+Prevent accidental session exit without deliverable completion.
+
+### Trigger Conditions
+
+Activate exit gate when ALL of these are true:
+- Session goal = `produce` (user confirmed they want feature-list.json via CP-AP-0)
+- Current phase < Phase 7 (final validation not yet passed)
+- No valid `feature-list.json` has been written in this session
+
+### Gate Behavior
+
+When the session appears to be ending (user says "thanks", "that's all", "bye", or conversation goes idle after Phase 3+):
+
+1. **Remind**: "You set out to produce `feature-list.json` but we haven't completed it yet."
+2. **Offer 3 options**:
+   - **(a) Continue to completion** — resume from current phase
+   - **(b) Abandon** — confirm user explicitly wants to exit without output
+3. **If (b) Save draft**: Write the draft file and remind user: "This is a draft, not validated. Run `/app-planner` again to resume and finalize."
+4. **If (c) Abandon**: Accept without further prompting.
+
+
 ## Handoff Message Template
 
 After successful validation, report:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.0.101",
+  "version": "1.0.103",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {

package/src/gitignore-template.js

@@ -17,9 +17,6 @@ export function generateGitignore(options = {}) {
     '# Prizm 文档（按需决定是否提交）',
     '# .prizm-docs/',
     '',
-    '# PrizmKit 工作流制品',
-    '.prizmkit/',
-    '',
   ];
 
   if (options.pipeline) {

package/src/scaffold.js

@@ -655,18 +655,8 @@ export async function installGitignore(projectRoot, options, dryRun) {
   }
 
   if (await fs.pathExists(targetPath)) {
-    const existing = await fs.readFile(targetPath, 'utf8');
-
-    // If .prizmkit/ is already ignored, nothing to do
-    if (existing.includes('.prizmkit/')) {
-      console.log(chalk.yellow(`      ⚠ .gitignore 已包含 .prizmkit/ 条目，跳过`));
-      return;
-    }
-
-    // No PrizmKit entries at all — append full .prizmkit/ block
-    const prizmkitSection = '\n\n# PrizmKit\n.prizmkit/\n';
-    await fs.appendFile(targetPath, prizmkitSection);
-    console.log(chalk.green(`      ✓ .gitignore (追加 PrizmKit 条目)`));
+    console.log(chalk.yellow(`      ⚠ .gitignore 已存在，跳过`));
+    return;
   } else {
     const content = generateGitignore({ pipeline: options.pipeline });
     await fs.writeFile(targetPath, content);