@harness-engineering/cli 1.27.1 → 1.28.0

package/dist/agents/skills/gemini-cli/initialize-harness-project/SKILL.md

@@ -36,7 +36,7 @@
    - Config files like `playwright.config.*`, `cypress.config.*`, `wdio.conf.*`
    - No production runtime — build output consumed only by other test repos (shared library)
 
-   **If a test suite:** complete Phase 2 (scaffolding) here, then dispatch to `initialize-test-suite-project` for Phase 3 configuration and Phase 4 verification, then return here for Phase 4 step 4+ (knowledge graph, roadmap nudge, final commit). The test-suite skill owns archetype selection, layer variants, tags, reporters, and the custom report.
+   **If a test suite:** complete Phase 2 (scaffolding) here, then dispatch to `initialize-test-suite-project` for Phase 3 configuration and Phase 4 verification, then return here for Phase 4 step 4+ (knowledge graph, roadmap question, final commit). The test-suite skill owns archetype selection, layer variants, tags, reporters, and the custom report.
 
    **If a product/service:** continue with the rest of this skill as written.
 
@@ -83,6 +83,48 @@
    - **No:** Set `i18n.enabled: false` in `harness.config.json`. The `harness-i18n-process` skill will still fire gentle prompts for unconfigured projects when features touch user-facing strings.
    - **Not sure yet:** Skip i18n configuration entirely. Do not set `i18n.enabled`. The project can enable i18n later by running `harness-i18n-workflow` directly.
 
+5b. **Configure design system (non-test-suite projects).** Ask: "Will this project have a UI requiring a design system?" Mirror the i18n step's three-way response shape. Use `emit_interaction`:
+
+    ```json
+    emit_interaction({
+      type: "question",
+      question: {
+        text: "Will this project have a UI requiring a design system?",
+        options: [
+          {
+            label: "Yes — capture design intent now",
+            pros: ["Records platforms in harness.config.json", "harness-design-system fires automatically on first design-touching feature"],
+            cons: ["One extra follow-up question (which platforms)"],
+            risk: "low",
+            effort: "low"
+          },
+          {
+            label: "No — this project has no UI",
+            pros: ["No future design nudges", "Permanent decline recorded"],
+            cons: ["Re-running init is required if a UI is added later"],
+            risk: "low",
+            effort: "low"
+          },
+          {
+            label: "Not sure yet",
+            pros: ["Decision deferred without commitment", "Can run harness-design-system later"],
+            cons: ["No design.enabled flag set; on_new_feature will prompt later"],
+            risk: "low",
+            effort: "low"
+          }
+        ],
+        recommendation: { optionIndex: 0, reason: "Most product/service projects benefit from a centralized design system", confidence: "medium" }
+      }
+    })
+    ```
+
+    Based on the answer:
+    - **Yes:** Ask a follow-up: "Which platforms? `web`, `mobile`, or both?" Write `design.enabled: true` and `design.platforms: [...]` (a non-empty array of `web` and/or `mobile`) to `harness.config.json`. Inform the user: "Design tokens will be generated when you start your first design-touching feature — `harness-design-system` fires automatically via `on_new_feature`."
+    - **No:** Write `design.enabled: false` to `harness.config.json`. Do not write `design.platforms`. The `on_new_feature` trigger respects this flag and will not fire `harness-design-system`.
+    - **Not sure yet:** Do not write `design.enabled` or `design.platforms`. The project can enable design later by running `harness-design-system` directly; `on_new_feature` will prompt gently when a feature touches user-facing UI.
+
+    **Skip this step entirely if Phase 1 step 5 classified the project as a test suite.** Test-suite projects will be dispatched at step 6 below to `initialize-test-suite-project` and have no UI to govern.
+
 6. **Test-suite projects only — dispatch to `initialize-test-suite-project`.** If Phase 1 step 5 classified this as a test suite, invoke `initialize-test-suite-project` now and let it own archetype selection, shared-library decision, layer variants (A self-contained vs B consumer), ESLint flat-config fix, tag taxonomy, reporter stack, custom report, and the "prove the guards fire" verification. Return here for Phase 4 step 4+ (knowledge graph, roadmap, commit). Product and service projects skip this step entirely.
 
 ### Phase 4: VALIDATE — Confirm Everything Works
@@ -108,7 +150,38 @@ harness scan [path]
 
 This creates the `.harness/graph/` directory and populates it with the project's dependency and relationship data. Subsequent graph queries (impact analysis, dependency health, test advisor) depend on this initial scan.
 
-4. **Mention roadmap.** After validation passes, inform the user: "When you are ready to set up a project roadmap, run `/harness:roadmap --create`. This creates a unified `docs/roadmap.md` that tracks features, milestones, and status across your specs and plans." This is informational only — do not create the roadmap automatically.
+4. **Set up project roadmap.** Ask: "Set up a project roadmap now? `docs/roadmap.md` tracks features, milestones, and status across your specs and plans." Use `emit_interaction`:
+
+   ```json
+   emit_interaction({
+     type: "question",
+     question: {
+       text: "Set up a project roadmap now?",
+       options: [
+         {
+           label: "Yes — create docs/roadmap.md now",
+           pros: ["Roadmap visible from day one", "Future specs auto-discovered on next sync"],
+           cons: ["Adds one file to the initial commit"],
+           risk: "low",
+           effort: "low"
+         },
+         {
+           label: "No — skip for now",
+           pros: ["Smaller initial footprint"],
+           cons: ["Run `/harness:roadmap --create` later when ready"],
+           risk: "low",
+           effort: "low"
+         }
+       ],
+       recommendation: { optionIndex: 0, reason: "Validation has just passed — a tangible 'project works' signal is the right moment to introduce planning artifacts", confidence: "medium" }
+     }
+   })
+   ```
+
+   Based on the answer:
+   - **Yes:** Invoke `harness-roadmap` (skill) or run `/harness:roadmap --create` to create `docs/roadmap.md`. Verify the file exists. The `manage_roadmap` MCP tool is for managing entries in an existing roadmap, not for creating one.
+     - **If `design.enabled === true` in `harness.config.json`** (set by Phase 3 step 5b), call `manage_roadmap` with `action: add`, `feature: "Set up design system"`, `status: "planned"`, `milestone: "Current Work"`, `summary: "Run harness-design-system to define palette, typography, and generate W3C DTCG tokens. Deferred from project init — fires on first design-touching feature via on_new_feature."`. Skip silently if `manage_roadmap show` reports a duplicate `(feature, milestone)` pair. This closes the loop between deferred design intent and visible planning work.
+   - **No:** Skip silently. The user can still run `/harness:roadmap --create` later — that informational fallback remains valid.
 
 5. **Commit the initialization.** All generated and configured files in a single commit.
 
@@ -120,8 +193,10 @@ This creates the `.harness/graph/` directory and populates it with the project's
 - **`harness validate`** — Verify the full project configuration is valid and complete.
 - **`harness check-deps`** — Verify dependency constraints match the actual codebase (intermediate and above).
 - **`harness-i18n-workflow configure` + `harness-i18n-workflow scaffold`** — Invoked during Phase 3 if the project will support multiple languages. Sets up i18n configuration and translation file structure.
+- **`harness-design-system` (deferred via `on_new_feature`)** — Phase 3 step 5b records `design.enabled` + `design.platforms` in `harness.config.json` but does NOT run the full design-system skill. Token generation defers to the first design-touching feature, where `harness-design-system` fires via `on_new_feature` and reads `design.enabled` to decide whether to proceed.
 - **`initialize-test-suite-project`** — Sub-skill. Invoked during Phase 3 step 6 when Phase 1 step 5 classified the project as a test suite. Owns archetype selection, shared-library vs in-repo decision, layer variants, tag taxonomy, reporter stack, custom report, and "prove the guards fire" verification.
-- **Roadmap nudge** — After successful initialization, inform the user about `/harness:roadmap --create` for setting up project-level feature tracking. Informational only; does not create the roadmap.
+- **`harness-roadmap` skill** — Phase 4 step 4 invokes this skill (or `/harness:roadmap --create`) when the user opts in to creating `docs/roadmap.md`. The `manage_roadmap` MCP tool does not create roadmaps; it manages entries in an existing one.
+- **`manage_roadmap` MCP tool** — Phase 4 step 4, when `design.enabled === true`, calls `manage_roadmap` with `action: add` to insert a `planned` "Set up design system" item under milestone `Current Work` with a summary describing the deferred work.
 
 ## Success Criteria
 
@@ -134,17 +209,21 @@ This creates the `.harness/graph/` directory and populates it with the project's
 - The adoption level matches what was agreed upon with the human
 - All generated files are committed in a single atomic commit
 - i18n configuration is set if the human chose to enable it during init
+- For non-test-suite projects, the design-system question was asked and `harness.config.json` reflects the answer: `design.enabled: true` (with `design.platforms` populated) for yes, `design.enabled: false` for no, or absent for not-sure.
+- The roadmap question was asked. If the user answered yes, `docs/roadmap.md` exists and was created via `harness-roadmap` (or the documented `/harness:roadmap --create` fallback).
+- When `design.enabled === true` AND the user answered yes to the roadmap question, `docs/roadmap.md` contains a `planned` entry titled "Set up design system" under milestone `Current Work` with a summary describing the deferred work. The entry is absent in all other answer combinations.
 - For test suites: `initialize-test-suite-project` ran to completion and its Success Criteria are also met
 
 ## Rationalizations to Reject
 
-| Rationalization                                                          | Why It Is Wrong                                                                                                                                                                                                           |
-| ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| "The generated AGENTS.md template looks fine -- no need to customize it" | Phase 3 says do not blindly accept generated content. Without project-specific descriptions, agents receive generic instructions.                                                                                         |
-| "We should start at the advanced level since we want full coverage"      | The skill recommends basic for new projects. Each level builds on the previous. Jumping to advanced creates misconfigured rules.                                                                                          |
-| "I will skip the i18n question to keep setup fast"                       | Phase 3 requires asking about i18n and recording the decision. Skipping creates ambiguity about whether the omission was intentional.                                                                                     |
-| "Validation passed, so the project is ready"                             | Phase 4 includes harness check-deps for intermediate+ projects and knowledge graph initialization. Validation alone is not sufficient.                                                                                    |
-| "This is a test suite, we'll configure layers in this skill"             | Phase 3 step 6 dispatches to `initialize-test-suite-project` for archetype selection, layer variants, and the rest. Do not inline test-suite-specific configuration here — the sub-skill owns it and carries the gotchas. |
+| Rationalization                                                          | Why It Is Wrong                                                                                                                                                                                                                                                                 |
+| ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| "The generated AGENTS.md template looks fine -- no need to customize it" | Phase 3 says do not blindly accept generated content. Without project-specific descriptions, agents receive generic instructions.                                                                                                                                               |
+| "We should start at the advanced level since we want full coverage"      | The skill recommends basic for new projects. Each level builds on the previous. Jumping to advanced creates misconfigured rules.                                                                                                                                                |
+| "I will skip the i18n question to keep setup fast"                       | Phase 3 requires asking about i18n and recording the decision. Skipping creates ambiguity about whether the omission was intentional.                                                                                                                                           |
+| "I will skip the design-system question to keep setup fast"              | Phase 3 step 5b requires asking about design and recording the answer in `design.enabled`. Skipping creates ambiguity about whether the omission was intentional and bypasses the linkage between init and the deferred `harness-design-system` invocation on `on_new_feature`. |
+| "Validation passed, so the project is ready"                             | Phase 4 includes harness check-deps for intermediate+ projects and knowledge graph initialization. Validation alone is not sufficient.                                                                                                                                          |
+| "This is a test suite, we'll configure layers in this skill"             | Phase 3 step 6 dispatches to `initialize-test-suite-project` for archetype selection, layer variants, and the rest. Do not inline test-suite-specific configuration here — the sub-skill owns it and carries the gotchas.                                                       |
 
 ## Examples
 
@@ -188,6 +267,67 @@ git add harness.config.json .harness/ AGENTS.md
 git commit -m "feat: initialize harness project at basic level"
 ```
 
+### Example: New TypeScript Web App with Design and Roadmap
+
+**ASSESS:**
+
+```
+Human: "I'm starting a new Next.js web app. Single-language, but it definitely needs a design system."
+Check for .harness/ — not found. Recommend: basic level.
+Phase 1 step 5 classification: not a test suite (Next.js app with src/, no playwright/cypress).
+```
+
+**SCAFFOLD:**
+
+```bash
+harness init --level basic --framework nextjs
+```
+
+**CONFIGURE (Phase 3):**
+
+```
+Step 5 (i18n): "Will this project support multiple languages?"
+  Human: "No, English only."
+  Result: i18n.enabled = false in harness.config.json.
+
+Step 5b (design): "Will this project have a UI requiring a design system?"
+  Human: "Yes."
+  Follow-up: "Which platforms? web, mobile, or both?"
+  Human: "Web."
+  Result: design.enabled = true, design.platforms = ["web"] in harness.config.json.
+  Inform: "Design tokens will be generated when you start your first design-touching
+  feature — harness-design-system fires automatically via on_new_feature."
+
+Step 6 (test-suite dispatch): skipped (not a test suite).
+```
+
+**VALIDATE (Phase 4):**
+
+```
+Step 1: harness validate — pass.
+Step 3: harness check-deps — pass (basic level, no constraints yet).
+Build initial knowledge graph: harness scan — graph populated.
+
+Step 4 (roadmap): "Set up a project roadmap now?"
+  Human: "Yes."
+  Invoke harness-roadmap (or /harness:roadmap --create) — docs/roadmap.md created.
+  design.enabled === true detected → manage_roadmap action: add
+    feature: "Set up design system"
+    status: planned
+    milestone: Current Work
+    summary: "Run harness-design-system to define palette, typography, and generate W3C DTCG tokens..."
+  Result: docs/roadmap.md contains the planned design item.
+
+Step 5: commit.
+```
+
+```bash
+git add harness.config.json .harness/ AGENTS.md docs/roadmap.md
+git commit -m "feat: initialize harness project with design and roadmap"
+```
+
+**Final state:** `harness.config.json` has `design.enabled: true` + `design.platforms: ["web"]`; `docs/roadmap.md` lists "Set up design system" as a `planned` item under `Current Work`; on the first feature touching UI, `on_new_feature` fires `harness-design-system` which reads `design.enabled` and runs the full discover/define/generate/validate flow.
+
 ### Example: Migrating Existing Project from Basic to Intermediate
 
 **ASSESS:**

package/dist/agents/skills/gemini-cli/initialize-harness-project/skill.yaml

@@ -1,6 +1,6 @@
 name: initialize-harness-project
 version: "1.0.0"
-description: Scaffold a new harness-compliant project
+description: Scaffold a new harness-compliant project, including design system and roadmap configuration
 stability: static
 cognitive_mode: constructive-architect
 triggers:
@@ -34,3 +34,4 @@ state:
   files: []
 depends_on:
   - initialize-test-suite-project
+  - harness-design-system

package/dist/{agents-md-2RN666DE.js → agents-md-76IEMV6O.js}

@@ -1,9 +1,9 @@
 import {
   generateAgentsMd
-} from "./chunk-C7RPQWBG.js";
-import "./chunk-IBTHD2UA.js";
+} from "./chunk-77OMOFZL.js";
+import "./chunk-6JBJ5FSW.js";
 import "./chunk-RL4VMEXL.js";
-import "./chunk-GAIOIINV.js";
+import "./chunk-X7XQ3ELM.js";
 import "./chunk-KFQGP6VL.js";
 export {
   generateAgentsMd

package/dist/{architecture-ZR33YKJB.js → architecture-5GVJRRUD.js}

@@ -1,13 +1,13 @@
 import {
   checkDependenciesDefinition,
   handleCheckDependencies
-} from "./chunk-MGPVA2EM.js";
-import "./chunk-YZH4I4JO.js";
+} from "./chunk-TFNQ72RF.js";
+import "./chunk-AJG2LCMA.js";
 import "./chunk-EPUKTTJZ.js";
 import "./chunk-W6Y7ZW3Y.js";
-import "./chunk-IBTHD2UA.js";
+import "./chunk-6JBJ5FSW.js";
 import "./chunk-RL4VMEXL.js";
-import "./chunk-GAIOIINV.js";
+import "./chunk-X7XQ3ELM.js";
 import "./chunk-KFQGP6VL.js";
 export {
   checkDependenciesDefinition,

package/dist/{assess-project-LLWWEQEV.js → assess-project-WDUFL7SO.js}

@@ -1,7 +1,7 @@
 import {
   assessProjectDefinition,
   handleAssessProject
-} from "./chunk-F3Y64VNF.js";
+} from "./chunk-L4RURCSF.js";
 import "./chunk-W6Y7ZW3Y.js";
 import "./chunk-KFQGP6VL.js";
 export {

package/dist/bin/harness-mcp.js

@@ -1,28 +1,28 @@
 #!/usr/bin/env node
 import {
   startServer
-} from "../chunk-EHTUWULH.js";
-import "../chunk-2FOLD76X.js";
-import "../chunk-F3Y64VNF.js";
+} from "../chunk-OPOSSZJS.js";
+import "../chunk-WPSM7WT6.js";
+import "../chunk-L4RURCSF.js";
 import "../chunk-IOW3MW2K.js";
-import "../chunk-BZZNYHRY.js";
-import "../chunk-3AJW7VQ3.js";
-import "../chunk-776JFSPK.js";
-import "../chunk-Q5DKIL46.js";
-import "../chunk-MGPVA2EM.js";
-import "../chunk-YZH4I4JO.js";
-import "../chunk-T7UZOJF4.js";
-import "../chunk-EGRQHLDM.js";
-import "../chunk-CJYNZMOP.js";
+import "../chunk-K5ZOBBQB.js";
+import "../chunk-CS7K6ZQ3.js";
+import "../chunk-VITLE3PS.js";
+import "../chunk-Z7ZF2XDL.js";
+import "../chunk-TFNQ72RF.js";
+import "../chunk-AJG2LCMA.js";
+import "../chunk-QZ46CI6E.js";
+import "../chunk-LINAFNIK.js";
+import "../chunk-E7QD4YHA.js";
 import "../chunk-EPUKTTJZ.js";
 import "../chunk-W6Y7ZW3Y.js";
 import "../chunk-27AJKSQY.js";
-import "../chunk-A4ETL34H.js";
+import "../chunk-KLE6FXWM.js";
 import "../chunk-3ISINLYT.js";
 import "../chunk-6B6UN6SG.js";
-import "../chunk-IBTHD2UA.js";
+import "../chunk-6JBJ5FSW.js";
 import "../chunk-RL4VMEXL.js";
-import "../chunk-GAIOIINV.js";
+import "../chunk-X7XQ3ELM.js";
 import "../chunk-HIK6OEUF.js";
 import "../chunk-EBJQ6N4M.js";
 import "../chunk-3WGJMBKH.js";

package/dist/bin/harness.js

@@ -3,43 +3,43 @@ import {
   createProgram,
   installCommandTelemetry,
   printFirstRunWelcome
-} from "../chunk-VCC47EXU.js";
-import "../chunk-EICASBYP.js";
-import "../chunk-C7RPQWBG.js";
-import "../chunk-FUS4OOGC.js";
-import "../chunk-SDPHFDQS.js";
-import "../chunk-L3Y7L4EG.js";
+} from "../chunk-Z63IDQ7Y.js";
+import "../chunk-YZZVOT7I.js";
+import "../chunk-77OMOFZL.js";
+import "../chunk-3WLXR23L.js";
+import "../chunk-ILVO6LZY.js";
+import "../chunk-OQS7KURX.js";
 import "../chunk-CQ553GZO.js";
 import "../chunk-GISMXMVL.js";
 import "../chunk-WWACIIBA.js";
 import "../chunk-TEFCFC4H.js";
-import "../chunk-3XMOWLK3.js";
-import "../chunk-SDDQPMZK.js";
+import "../chunk-USG7DV5N.js";
+import "../chunk-D25P6763.js";
 import "../chunk-KET4QQZB.js";
-import "../chunk-BO4AJZRE.js";
-import "../chunk-XKU37HGH.js";
+import "../chunk-H43UQY6B.js";
+import "../chunk-DHGL3SF2.js";
 import {
   dispatchSkillsFromGit
-} from "../chunk-EHTUWULH.js";
-import "../chunk-2FOLD76X.js";
-import "../chunk-F3Y64VNF.js";
+} from "../chunk-OPOSSZJS.js";
+import "../chunk-WPSM7WT6.js";
+import "../chunk-L4RURCSF.js";
 import "../chunk-IOW3MW2K.js";
-import "../chunk-BZZNYHRY.js";
-import "../chunk-3AJW7VQ3.js";
-import "../chunk-776JFSPK.js";
-import "../chunk-Q5DKIL46.js";
-import "../chunk-MGPVA2EM.js";
-import "../chunk-YZH4I4JO.js";
-import "../chunk-T7UZOJF4.js";
-import "../chunk-EGRQHLDM.js";
-import "../chunk-CJYNZMOP.js";
+import "../chunk-K5ZOBBQB.js";
+import "../chunk-CS7K6ZQ3.js";
+import "../chunk-VITLE3PS.js";
+import "../chunk-Z7ZF2XDL.js";
+import "../chunk-TFNQ72RF.js";
+import "../chunk-AJG2LCMA.js";
+import "../chunk-QZ46CI6E.js";
+import "../chunk-LINAFNIK.js";
+import "../chunk-E7QD4YHA.js";
 import "../chunk-EPUKTTJZ.js";
 import "../chunk-W6Y7ZW3Y.js";
 import "../chunk-27AJKSQY.js";
 import {
   findConfigFile,
   loadConfig
-} from "../chunk-A4ETL34H.js";
+} from "../chunk-KLE6FXWM.js";
 import "../chunk-3ISINLYT.js";
 import "../chunk-6B6UN6SG.js";
 import {
@@ -52,9 +52,9 @@ import {
   readCheckState,
   shouldRunCheck,
   spawnBackgroundCheck
-} from "../chunk-IBTHD2UA.js";
+} from "../chunk-6JBJ5FSW.js";
 import "../chunk-RL4VMEXL.js";
-import "../chunk-GAIOIINV.js";
+import "../chunk-X7XQ3ELM.js";
 import "../chunk-ZP5E7YET.js";
 import "../chunk-HIK6OEUF.js";
 import "../chunk-EBJQ6N4M.js";

package/dist/{check-phase-gate-ZVG56NT2.js → check-phase-gate-QR3ONJYP.js}

@@ -1,11 +1,11 @@
 import {
   createCheckPhaseGateCommand,
   runCheckPhaseGate
-} from "./chunk-3XMOWLK3.js";
-import "./chunk-A4ETL34H.js";
-import "./chunk-IBTHD2UA.js";
+} from "./chunk-USG7DV5N.js";
+import "./chunk-KLE6FXWM.js";
+import "./chunk-6JBJ5FSW.js";
 import "./chunk-RL4VMEXL.js";
-import "./chunk-GAIOIINV.js";
+import "./chunk-X7XQ3ELM.js";
 import "./chunk-EBJQ6N4M.js";
 import "./chunk-3WGJMBKH.js";
 import "./chunk-KFQGP6VL.js";

package/dist/{chunk-FUS4OOGC.js → chunk-3WLXR23L.js}

@@ -1,6 +1,6 @@
 import {
   init_dist
-} from "./chunk-IBTHD2UA.js";
+} from "./chunk-6JBJ5FSW.js";
 import {
   Err,
   Ok

package/dist/{chunk-IBTHD2UA.js → chunk-6JBJ5FSW.js}

@@ -13,7 +13,7 @@ import {
   NODE_STABILITY,
   init_dist as init_dist2,
   queryTraceability
-} from "./chunk-GAIOIINV.js";
+} from "./chunk-X7XQ3ELM.js";
 import {
   __esm,
   __export
@@ -12645,6 +12645,7 @@ function inferStatus(feature, projectPath, allFeatures) {
       return !blocker || blocker.status !== "done";
     });
     if (blockerNotDone) return "blocked";
+    if (feature.status === "blocked") return "planned";
   }
   if (feature.plans.length === 0) return null;
   const allTaskStatuses = [];

package/dist/{chunk-C7RPQWBG.js → chunk-77OMOFZL.js}

@@ -1,6 +1,6 @@
 import {
   init_dist
-} from "./chunk-IBTHD2UA.js";
+} from "./chunk-6JBJ5FSW.js";
 import {
   Err,
   Ok

package/dist/{chunk-YZH4I4JO.js → chunk-AJG2LCMA.js}

@@ -1,6 +1,6 @@
 import {
   init_dist
-} from "./chunk-IBTHD2UA.js";
+} from "./chunk-6JBJ5FSW.js";
 import {
   Err,
   Ok

package/dist/{chunk-3AJW7VQ3.js → chunk-CS7K6ZQ3.js}

@@ -27,7 +27,7 @@ var runSecurityScanDefinition = {
 };
 async function handleRunSecurityScan(input) {
   try {
-    const core = await import("./dist-CPKL5Y2R.js");
+    const core = await import("./dist-46VOJIG4.js");
     const projectRoot = sanitizePath(input.path);
     let configData = {};
     try {
@@ -114,7 +114,7 @@ var getSecurityTrendsDefinition = {
 };
 async function handleGetSecurityTrends(input) {
   try {
-    const core = await import("./dist-CPKL5Y2R.js");
+    const core = await import("./dist-46VOJIG4.js");
     const projectRoot = sanitizePath(input.path);
     const manager = new core.SecurityTimelineManager(projectRoot);
     const trendOptions = {};

package/dist/{chunk-SDDQPMZK.js → chunk-D25P6763.js}

@@ -4,7 +4,7 @@ import {
 import {
   listPersonas,
   loadPersona
-} from "./chunk-BO4AJZRE.js";
+} from "./chunk-H43UQY6B.js";
 import {
   GENERATED_HEADER_AGENT,
   VALID_PLATFORMS,

package/dist/{chunk-XKU37HGH.js → chunk-DHGL3SF2.js}

@@ -9,7 +9,7 @@ async function runScan(projectPath) {
     KnowledgeIngestor,
     GitIngestor,
     RequirementIngestor
-  } = await import("./dist-BZS2XRLG.js");
+  } = await import("./dist-BP6E6QGG.js");
   const store = new GraphStore();
   const start = Date.now();
   await new CodeIngestor(store).ingest(projectPath);

package/dist/{chunk-CJYNZMOP.js → chunk-E7QD4YHA.js}

@@ -7,10 +7,10 @@ import {
 import {
   findConfigFile,
   loadConfig
-} from "./chunk-A4ETL34H.js";
+} from "./chunk-KLE6FXWM.js";
 import {
   init_dist
-} from "./chunk-IBTHD2UA.js";
+} from "./chunk-6JBJ5FSW.js";
 import {
   Ok
 } from "./chunk-RL4VMEXL.js";
@@ -35,7 +35,7 @@ var checkPerformanceDefinition = {
 };
 async function handleCheckPerformance(input) {
   try {
-    const { EntropyAnalyzer } = await import("./dist-CPKL5Y2R.js");
+    const { EntropyAnalyzer } = await import("./dist-46VOJIG4.js");
     const typeFilter = input.type ?? "all";
     const projectPath = sanitizePath(input.path);
     let entryPoints;
@@ -58,10 +58,10 @@ async function handleCheckPerformance(input) {
     });
     let graphOptions;
     try {
-      const { loadGraphStore } = await import("./graph-loader-QEI7SYOQ.js");
+      const { loadGraphStore } = await import("./graph-loader-BI3OFFFS.js");
       const store = await loadGraphStore(projectPath);
       if (store) {
-        const { GraphComplexityAdapter, GraphCouplingAdapter } = await import("./dist-BZS2XRLG.js");
+        const { GraphComplexityAdapter, GraphCouplingAdapter } = await import("./dist-BP6E6QGG.js");
         const complexityAdapter = new GraphComplexityAdapter(store);
         const couplingAdapter = new GraphCouplingAdapter(store);
         graphOptions = {
@@ -98,7 +98,7 @@ var getPerfBaselinesDefinition = {
 };
 async function handleGetPerfBaselines(input) {
   try {
-    const { BaselineManager } = await import("./dist-CPKL5Y2R.js");
+    const { BaselineManager } = await import("./dist-46VOJIG4.js");
     const manager = new BaselineManager(sanitizePath(input.path));
     const baselines = manager.load();
     return resultToMcpResponse(
@@ -146,7 +146,7 @@ var updatePerfBaselinesDefinition = {
 };
 async function handleUpdatePerfBaselines(input) {
   try {
-    const { BaselineManager } = await import("./dist-CPKL5Y2R.js");
+    const { BaselineManager } = await import("./dist-46VOJIG4.js");
     const manager = new BaselineManager(sanitizePath(input.path));
     manager.save(input.results, input.commitHash);
     const updated = manager.load();
@@ -176,7 +176,7 @@ var getCriticalPathsDefinition = {
 };
 async function handleGetCriticalPaths(input) {
   try {
-    const { CriticalPathResolver } = await import("./dist-CPKL5Y2R.js");
+    const { CriticalPathResolver } = await import("./dist-46VOJIG4.js");
     const resolver = new CriticalPathResolver(sanitizePath(input.path));
     const result = await resolver.resolve();
     return resultToMcpResponse(Ok(result));

package/dist/{chunk-BO4AJZRE.js → chunk-H43UQY6B.js}

@@ -1,6 +1,6 @@
 import {
   init_dist
-} from "./chunk-IBTHD2UA.js";
+} from "./chunk-6JBJ5FSW.js";
 import {
   Err,
   Ok

package/dist/{chunk-SDPHFDQS.js → chunk-ILVO6LZY.js}

@@ -1,6 +1,6 @@
 import {
   init_dist
-} from "./chunk-IBTHD2UA.js";
+} from "./chunk-6JBJ5FSW.js";
 import {
   Ok
 } from "./chunk-RL4VMEXL.js";

package/dist/{chunk-BZZNYHRY.js → chunk-K5ZOBBQB.js}

@@ -33,7 +33,7 @@ var createSelfReviewDefinition = {
 };
 async function handleCreateSelfReview(input) {
   try {
-    const { parseDiff, createSelfReview } = await import("./dist-CPKL5Y2R.js");
+    const { parseDiff, createSelfReview } = await import("./dist-46VOJIG4.js");
     const parseResult = parseDiff(input.diff);
     if (!parseResult.ok) {
       return resultToMcpResponse(parseResult);
@@ -53,11 +53,11 @@ async function handleCreateSelfReview(input) {
         ...input.maxFileCount !== void 0 ? { maxChangedFiles: input.maxFileCount } : {}
       }
     };
-    const { loadGraphStore } = await import("./graph-loader-QEI7SYOQ.js");
+    const { loadGraphStore } = await import("./graph-loader-BI3OFFFS.js");
     const store = await loadGraphStore(projectPath);
     let graphData;
     if (store) {
-      const { GraphFeedbackAdapter } = await import("./dist-BZS2XRLG.js");
+      const { GraphFeedbackAdapter } = await import("./dist-BP6E6QGG.js");
       const adapter = new GraphFeedbackAdapter(store);
       const changedFiles = parseResult.value.files.map((f) => f.path);
       const impact = adapter.computeImpactData(changedFiles);
@@ -119,7 +119,7 @@ var analyzeDiffDefinition = {
 };
 async function handleAnalyzeDiff(input) {
   try {
-    const { parseDiff, analyzeDiff } = await import("./dist-CPKL5Y2R.js");
+    const { parseDiff, analyzeDiff } = await import("./dist-46VOJIG4.js");
     const parseResult = parseDiff(input.diff);
     if (!parseResult.ok) {
       return resultToMcpResponse(parseResult);
@@ -139,10 +139,10 @@ async function handleAnalyzeDiff(input) {
     let graphImpactData;
     if (input.path) {
       try {
-        const { loadGraphStore } = await import("./graph-loader-QEI7SYOQ.js");
+        const { loadGraphStore } = await import("./graph-loader-BI3OFFFS.js");
         const store = await loadGraphStore(sanitizePath(input.path));
         if (store) {
-          const { GraphFeedbackAdapter } = await import("./dist-BZS2XRLG.js");
+          const { GraphFeedbackAdapter } = await import("./dist-BP6E6QGG.js");
           const adapter = new GraphFeedbackAdapter(store);
           const changedFiles = parseResult.value.files.map((f) => f.path);
           const impact = adapter.computeImpactData(changedFiles);
@@ -195,7 +195,7 @@ var requestPeerReviewDefinition = {
 };
 async function handleRequestPeerReview(input) {
   try {
-    const { parseDiff, requestPeerReview } = await import("./dist-CPKL5Y2R.js");
+    const { parseDiff, requestPeerReview } = await import("./dist-46VOJIG4.js");
     const parseResult = parseDiff(input.diff);
     if (!parseResult.ok) {
       return resultToMcpResponse(parseResult);
@@ -206,10 +206,10 @@ async function handleRequestPeerReview(input) {
       ...input.context ? { metadata: { context: input.context } } : {}
     };
     try {
-      const { loadGraphStore } = await import("./graph-loader-QEI7SYOQ.js");
+      const { loadGraphStore } = await import("./graph-loader-BI3OFFFS.js");
       const store = await loadGraphStore(sanitizePath(input.path));
       if (store) {
-        const { GraphFeedbackAdapter } = await import("./dist-BZS2XRLG.js");
+        const { GraphFeedbackAdapter } = await import("./dist-BP6E6QGG.js");
         const adapter = new GraphFeedbackAdapter(store);
         const changedFiles = parseResult.value.files.map((f) => f.path);
         const impactData = adapter.computeImpactData(changedFiles);