@thanh01.pmt/domain-kit 0.2.1 → 0.3.0

package/dist/graph/index.cjs

@@ -2305,6 +2305,8 @@ function auditPhasePlan(plan, features, concepts, links, warnings, log) {
   const phases = [];
   const featurePhase = /* @__PURE__ */ new Map();
   const newIntroPhase = /* @__PURE__ */ new Map();
+  const previewsSeen = /* @__PURE__ */ new Set();
+  const previewPhase = /* @__PURE__ */ new Map();
   const errors = [];
   plan.forEach((rp, idx) => {
     const id = String(rp.id || "PH" + (idx + 1));
@@ -2336,7 +2338,22 @@ function auditPhasePlan(plan, features, concepts, links, warnings, log) {
         errors.push("Phase " + id + ": introduces unknown concept " + cid);
         continue;
       }
-      const aspect = String(ri.aspect || "new") === "advanced" ? "advanced" : "new";
+      const rawAspect = String(ri.aspect || "new");
+      const aspect = rawAspect === "advanced" || rawAspect === "preview" ? rawAspect : "new";
+      if (aspect === "preview") {
+        if (newIntroPhase.has(cid)) {
+          errors.push("Phase " + id + ": preview of " + cid + " after its new introduction in phase " + newIntroPhase.get(cid) + " - preview must precede the anchor teach");
+          continue;
+        }
+        if (previewsSeen.has(cid)) {
+          errors.push("Phase " + id + ": duplicate preview of " + cid);
+          continue;
+        }
+        previewsSeen.add(cid);
+        previewPhase.set(cid, order);
+        introductions.push({ concept_id: cid, aspect, note: String(ri.note || "") });
+        continue;
+      }
       if (aspect === "advanced") {
         const first = newIntroPhase.get(cid);
         if (first === void 0) {
@@ -2384,10 +2401,17 @@ function auditPhasePlan(plan, features, concepts, links, warnings, log) {
   }
   for (const [cid, consumerOrder] of firstConsumerPhase) {
     const intro = newIntroPhase.get(cid);
-    if (intro === void 0) {
+    const prev = previewPhase.get(cid);
+    if (intro === void 0 && prev === void 0) {
       errors.push("Concept " + cid + " is consumed from phase " + consumerOrder + " but never introduced in any phase");
-    } else if (intro > consumerOrder) {
-      errors.push("Concept " + cid + " introduced in phase " + intro + " but first consumed in phase " + consumerOrder + " - introduction must come no later than first consumption");
+    } else if (intro !== void 0 && intro > consumerOrder && (prev === void 0 || prev > consumerOrder)) {
+      errors.push("Concept " + cid + " introduced in phase " + intro + " but first consumed in phase " + consumerOrder + " - introduction must come no later than first consumption (or a preview must cover the dependency)");
+    }
+  }
+  for (const [cid, pOrder] of previewPhase) {
+    const anchor = newIntroPhase.get(cid);
+    if (anchor !== void 0 && anchor <= pOrder) {
+      errors.push("Concept " + cid + " previewed in phase " + pOrder + " but fully introduced in phase " + anchor + " - preview must precede the anchor introduction");
     }
   }
   return { phases, errors };
@@ -2403,7 +2427,7 @@ async function decomposePhases(args) {
   const linkList = links.map(
     (l) => "- " + l.feature_id + " -> " + l.concept_id + " (" + l.depth + ")"
   ).join("\n") || "(none)";
-  const systemPrompt = "You decompose a software project build into PROGRESSIVE COMPLETION PHASES for learning purposes.\n\nA phase is NOT a feature and NOT a milestone list: it is a cross-feature slice of the\nproduct whose completion yields a DEMONSTRABLY more complete product. Build up gradually:\nthe product grows feature by feature across phases, and each phase adds its features to\nwhat previous phases already built.\n\nRULES:\n1. Every feature must be assigned to EXACTLY ONE phase (no feature reused, none skipped).\n2. Phases are ordered; later phases depend on earlier ones and yield a more complete product.\n3. product_completion describes concretely what the product can DO once the phase is done.\n4. introduces lists which concepts the phase must teach BEFORE its feature work starts:\n   - aspect new: first time the concept appears in the course\n   - aspect advanced: a concept introduced in an EARLIER phase, revisited here at a\n     higher depth (an advanced aspect of the same concept, e.g. validation rules on top\n     of basic data modeling). Use the note field to say which aspect.\n5. A concept MUST be introduced (new) no later than the first phase that consumes it.\n6. A concept must not be introduced before its own prerequisites are introduced.\n7. Typically 3-6 phases for a small project; keep phases balanced.\n8. Phase 1 usually covers project setup/foundation features plus the first minimal slice.\n9. Return JSON only.";
+  const systemPrompt = 'You decompose a software project build into PROGRESSIVE COMPLETION PHASES for learning purposes.\n\nA phase is NOT a feature and NOT a milestone list: it is a cross-feature slice of the\nproduct whose completion yields a DEMONSTRABLY more complete product. Build up gradually:\nthe product grows feature by feature across phases, and each phase adds its features to\nwhat previous phases already built.\n\nRULES:\n1. Every feature must be assigned to EXACTLY ONE phase (no feature reused, none skipped).\n2. Phases are ordered; later phases depend on earlier ones and yield a more complete product.\n3. product_completion describes concretely what the product can DO once the phase is done.\n4. introduces lists which concepts the phase must teach BEFORE its feature work starts:\n   - aspect new: first time the concept appears in the course\n   - aspect advanced: a concept introduced in an EARLIER phase, revisited here at a\n     higher depth (an advanced aspect of the same concept, e.g. validation rules on top\n     of basic data modeling). Use the note field to say which aspect.\n   - aspect preview: a light awareness pass ("know it exists", ULO depth only, ~5 min)\n     placed in an EARLIER phase when its feature work needs the vocabulary before the\n     full teach. The anchor phase still owns the full new introduction.\n5. A concept MUST be introduced (new) no later than the first phase that consumes it.\n6. A concept must not be introduced before its own prerequisites are introduced.\n7. Typically 3-6 phases for a small project; keep phases balanced.\n8. Phase 1 usually covers project setup/foundation features plus the first minimal slice.\n9. Return JSON only.';
   const baseUserPrompt = "FEATURES:\n" + featureList + "\n\nCONCEPTS:\n" + conceptList + "\n\nFEATURE-CONCEPT LINKS:\n" + linkList + "\n\nReturn JSON with a phases array. Each phase: { id: PH1, name, product_completion, feature_ids: [F0, F1], introduces: [{ concept_id: C1, aspect: new or advanced, note }] }.\n";
   const MAX_DECOMPOSE_ATTEMPTS = 3;
   let auditErrors = [];