@uoyo/mvtt 2.0.0-beta.1 → 2.0.0-beta.2

package/sources/skills/mvt-update-plan/business.md

@@ -1,72 +1,72 @@
-## Execution Flow
-
-### Step 1: Resolve Target
-
-Required inputs:
-
-- **task_id** -- which task to update
-- **new_status** -- one of: `pending`, `in_progress`, `done`, `blocked`, `skipped`
-- **artifacts** (optional, comma-separated paths) -- files produced or touched
-- **notes** (optional) -- free-form note string
-
-Resolution rules:
-
-- If `task_id` is omitted AND exactly one task currently has status `in_progress` -> default to that task.
-- If `task_id` is omitted AND zero or multiple tasks are in_progress -> ask the user to specify.
-- If the user reply is the natural-language form `done` / `blocked: <reason>` (from a workflow skill's soft-prompt) -> map to:
-  - `done` -> task = plan.current_task, new_status = done
-  - `blocked: <reason>` -> task = plan.current_task, new_status = blocked, notes = `<reason>`
-
-### Step 2: Load and Validate Existing Plan
-
-1. Read `active_change.plan_path` (the file location is fixed by `/mvt-plan-dev`).
-2. Parse YAML; if parse fails or schema is invalid -> stop and report. Do not attempt to repair silently.
-3. Verify the target `task_id` exists in `tasks[]`. If not, list valid ids and stop.
-
-### Step 3: Apply the Update
-
-Mutate the in-memory plan:
-
-1. Find the target task; capture `old_status` for the report.
-2. Set `tasks[i].status = new_status`.
-3. If `artifacts` provided -> append to `tasks[i].artifacts` (de-duplicate).
-4. If `notes` provided -> overwrite `tasks[i].notes`.
-5. Update `plan.updated_at` to current ISO 8601 timestamp.
-
-### Step 4: Recompute current_task
-
-Selection logic, in order:
-
-1. If any task has status `in_progress` AND it is **not** the task we just changed to a terminal status (done/blocked/skipped) -> `current_task` = that task's id.
-2. Otherwise pick the first task (by array order) where:
-   - `status == pending`
-   - All ids in `depends_on` reference tasks with status `done`
-3. If no such task exists AND every task is `done` -> set `plan.status = done`, `current_task = null`.
-4. If no such task exists but some tasks are still `pending` (because their dependencies are not done -- e.g., everything reachable is blocked) -> set `current_task = null`, leave `plan.status = in_progress`. Surface a warning in the output ("All remaining tasks are blocked by dependencies; resolve a blocker before continuing").
-
-If the selected next task is currently `pending` -> promote it to `in_progress` (so the plan accurately reflects the active focus). Skip this promotion if `plan.status` just transitioned to `done`.
-
-### Step 5: Validate and Write
-
-1. Run the plan validator on the mutated structure.
-2. If validation fails -> abort the write, report the validation errors, leave the original file untouched.
-3. Otherwise, write back to `active_change.plan_path`.
-
-### Step 6: Update Session State
-
-Apply the standard State Update rules (see shared section above) AND the update-plan-specific updates:
-
-- Refresh the matching entry in `recent_changes[]`: `last_updated` -> current ISO 8601 timestamp.
-- Do NOT touch `active_change.has_plan` / `active_change.plan_path`.
-
-### Step 7: Output
-
-Emit the Plan Update summary block defined in the Output Format section. Include:
-
-- The task that changed (id, title, old -> new status).
-- A compact table of all tasks with their current status.
-- The new `current_task` (or "(plan complete)" if `plan.status == done`).
-- A one-line "Next" hint:
-  - If a new `current_task` is set -> recommend the skill matching its `skill_hint`.
-  - If plan complete -> recommend `/mvt-cleanup` or starting a new change via `/mvt-analyze`.
-  - If all remaining tasks are blocked -> recommend resolving the blocker (point at the `notes` of the blocked task).
+## Execution Flow
+
+### Step 1: Resolve Target
+
+Required inputs:
+
+- **task_id** -- which task to update
+- **new_status** -- one of: `pending`, `in_progress`, `done`, `blocked`, `skipped`
+- **artifacts** (optional, comma-separated paths) -- files produced or touched
+- **notes** (optional) -- free-form note string
+
+Resolution rules:
+
+- If `task_id` is omitted AND exactly one task currently has status `in_progress` -> default to that task.
+- If `task_id` is omitted AND zero or multiple tasks are in_progress -> ask the user to specify.
+- If the user reply is the natural-language form `done` / `blocked: <reason>` (from a workflow skill's soft-prompt) -> map to:
+  - `done` -> task = plan.current_task, new_status = done
+  - `blocked: <reason>` -> task = plan.current_task, new_status = blocked, notes = `<reason>`
+
+### Step 2: Load and Validate Existing Plan
+
+1. Read `active_change.plan_path` (the file location is fixed by `/mvt-plan-dev`).
+2. Parse YAML; if parse fails or schema is invalid -> stop and report. Do not attempt to repair silently.
+3. Verify the target `task_id` exists in `tasks[]`. If not, list valid ids and stop.
+
+### Step 3: Apply the Update
+
+Mutate the in-memory plan:
+
+1. Find the target task; capture `old_status` for the report.
+2. Set `tasks[i].status = new_status`.
+3. If `artifacts` provided -> append to `tasks[i].artifacts` (de-duplicate).
+4. If `notes` provided -> overwrite `tasks[i].notes`.
+5. Update `plan.updated_at` to current ISO 8601 timestamp.
+
+### Step 4: Recompute current_task
+
+Selection logic, in order:
+
+1. If any task has status `in_progress` AND it is **not** the task we just changed to a terminal status (done/blocked/skipped) -> `current_task` = that task's id.
+2. Otherwise pick the first task (by array order) where:
+   - `status == pending`
+   - All ids in `depends_on` reference tasks with status `done`
+3. If no such task exists AND every task is `done` -> set `plan.status = done`, `current_task = null`.
+4. If no such task exists but some tasks are still `pending` (because their dependencies are not done -- e.g., everything reachable is blocked) -> set `current_task = null`, leave `plan.status = in_progress`. Surface a warning in the output ("All remaining tasks are blocked by dependencies; resolve a blocker before continuing").
+
+If the selected next task is currently `pending` -> promote it to `in_progress` (so the plan accurately reflects the active focus). Skip this promotion if `plan.status` just transitioned to `done`.
+
+### Step 5: Validate and Write
+
+1. Run the plan validator on the mutated structure.
+2. If validation fails -> abort the write, report the validation errors, leave the original file untouched.
+3. Otherwise, write back to `active_change.plan_path`.
+
+### Step 6: Update Session State
+
+Apply the standard State Update rules (see shared section above) AND the update-plan-specific updates:
+
+- Refresh the matching entry in `recent_changes[]`: `last_updated` -> current ISO 8601 timestamp.
+- Do NOT touch `active_change.has_plan` / `active_change.plan_path`.
+
+### Step 7: Output
+
+Emit the Plan Update summary block defined in the Output Format section. Include:
+
+- The task that changed (id, title, old -> new status).
+- A compact table of all tasks with their current status.
+- The new `current_task` (or "(plan complete)" if `plan.status == done`).
+- A one-line "Next" hint:
+  - If a new `current_task` is set -> recommend the skill matching its `skill_hint`.
+  - If plan complete -> recommend `/mvt-cleanup` or starting a new change via `/mvt-analyze`.
+  - If all remaining tasks are blocked -> recommend resolving the blocker (point at the `notes` of the blocked task).

package/sources/skills/mvt-update-plan/manifest.yaml

@@ -1,132 +1,132 @@
-name: mvt-update-plan
-output: .claude/skills/mvt-update-plan/SKILL.md
-
-frontmatter:
-  name: mvt-update-plan
-  description: "Update a single task in the active change's plan.yaml: change status, attach artifacts, leave notes, and auto-advance current_task. This skill should be used after a workflow skill finishes work that maps to a plan task, or whenever the user wants to mark a task as done, blocked, or skipped."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Update Plan
-
-      ## Purpose
-
-      Apply incremental updates to the active plan.yaml: mark a task done/blocked/skipped, attach the artifacts produced, and let the skill auto-advance `current_task` to the next executable task. AI may invoke this skill on the user's behalf when the user replies to a soft-prompt with `done` / `blocked: <reason>`.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Architect
-      role_desc: "a Development Planner"
-      decision_rules:
-        - rule: "Task id provided AND target status valid -> Apply update, advance current_task, write back"
-        - rule: "Task id missing AND only one task is in_progress -> Default to that task"
-        - rule: "Target status would create an invalid current_task -> Recompute current_task automatically"
-        - rule: "All tasks become done -> Set plan.status = done, current_task = null"
-        - rule: "active_change.has_plan is false -> Stop and suggest /mvt-plan-dev"
-
-      boundaries:
-        - scope: "create new tasks or restructure the plan"
-          skill: "/mvt-plan-dev"
-        - scope: "create or modify the active change itself"
-          skill: "/mvt-analyze"
-        - scope: "implement code"
-          skill: "/mvt-implement"
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - "{active_change.plan_path} -- The plan to update (resolved from session.yaml)"
-
-  - type: shared
-    source: sections/activation-load-config.md
-
-  - type: shared
-    source: sections/output-language-constraint.md
-
-  - type: shared
-    source: sections/activation-preflight.md
-    params:
-      checks:
-        - order: "1"
-          field: "session.initialized_at"
-          level: "WARN"
-          message: 'Session not initialized. Run `/mvt-init` first.'
-        - order: "2"
-          field: "active_change.has_plan"
-          level: "BLOCK"
-          message: 'No active plan. Run `/mvt-plan-dev` to create one before updating.'
-
-  - type: inline
-    content: |
-      ### Shortcut Operation Rules
-      - Can execute at any time when an active plan exists
-      - Performs surgical edits only -- never overwrites the whole plan structure
-      - Re-validates the resulting plan before writing; aborts on validation failure
-
-  - type: file
-    source: ./business.md
-
-  - type: inline
-    content: |
-      ## Output Format
-
-      Render an inline summary (no external template). Structure:
-
-      ```markdown
-      ## Plan Update
-
-      ### Change Applied
-      - **Task**: {task_id} -- {task_title}
-      - **Status**: {old_status} -> {new_status}
-      - **Artifacts attached**: {comma_separated_list_or_"(none)"}
-      - **Notes**: {notes_or_"(unchanged)"}
-
-      ### Plan Progress
-      | # | id | title | status |
-      |---|----|----|--------|
-      | ... |
-
-      Progress: {done_count}/{total_count}
-      Current task: {new_current_task_id_or_"(plan complete)"}
-
-      ### Next
-      {one-line guidance: continue to next task, resolve blocker, or run /mvt-cleanup}
-      ```
-
-      Every response MUST end with a Suggested Next Steps section.
-
-  - type: shared
-    source: sections/session-update.md
-
-  - type: inline
-    content: |
-      ### Update-Plan Specific State Updates
-
-      In addition to the mandatory updates above, this skill MUST refresh `recent_changes` for the active change:
-
-      - Find the entry where `id == active_change.id`. If absent, append one (this should be rare; happens when the plan was created out-of-band).
-      - Set `last_updated` to the current ISO 8601 timestamp.
-      - Trim to max 5 entries (drop the oldest by `last_updated` ascending).
-
-      Do NOT modify `active_change.has_plan` or `active_change.plan_path` here -- those are owned by `/mvt-plan-dev`.
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      current_skill: mvt-update-plan
-      conditional_suggestions:
-        conditions:
-          - condition: "plan_done"
-            primary: mvt-cleanup
-            primary_desc: "All tasks complete -- clean up artifacts and prepare to start the next change"
-          - condition: "default"
-            primary: mvt-implement
-            primary_desc: "Continue with the next current_task"
-        alternatives:
-          - skill: mvt-resume
-            desc: "Refresh context after task transitions"
-          - skill: mvt-status
-            desc: "Inspect overall progress across changes"
+name: mvt-update-plan
+output: .claude/skills/mvt-update-plan/SKILL.md
+
+frontmatter:
+  name: mvt-update-plan
+  description: "Update a single task in the active change's plan.yaml: change status, attach artifacts, leave notes, and auto-advance current_task. This skill should be used after a workflow skill finishes work that maps to a plan task, or whenever the user wants to mark a task as done, blocked, or skipped."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Update Plan
+
+      ## Purpose
+
+      Apply incremental updates to the active plan.yaml: mark a task done/blocked/skipped, attach the artifacts produced, and let the skill auto-advance `current_task` to the next executable task. AI may invoke this skill on the user's behalf when the user replies to a soft-prompt with `done` / `blocked: <reason>`.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Architect
+      role_desc: "a Development Planner"
+      decision_rules:
+        - rule: "Task id provided AND target status valid -> Apply update, advance current_task, write back"
+        - rule: "Task id missing AND only one task is in_progress -> Default to that task"
+        - rule: "Target status would create an invalid current_task -> Recompute current_task automatically"
+        - rule: "All tasks become done -> Set plan.status = done, current_task = null"
+        - rule: "active_change.has_plan is false -> Stop and suggest /mvt-plan-dev"
+
+      boundaries:
+        - scope: "create new tasks or restructure the plan"
+          skill: "/mvt-plan-dev"
+        - scope: "create or modify the active change itself"
+          skill: "/mvt-analyze"
+        - scope: "implement code"
+          skill: "/mvt-implement"
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "{active_change.plan_path} -- The plan to update (resolved from session.yaml)"
+
+  - type: shared
+    source: sections/activation-load-config.md
+
+  - type: shared
+    source: sections/output-language-constraint.md
+
+  - type: shared
+    source: sections/activation-preflight.md
+    params:
+      checks:
+        - order: "1"
+          field: "session.initialized_at"
+          level: "WARN"
+          message: 'Session not initialized. Run `/mvt-init` first.'
+        - order: "2"
+          field: "active_change.has_plan"
+          level: "BLOCK"
+          message: 'No active plan. Run `/mvt-plan-dev` to create one before updating.'
+
+  - type: inline
+    content: |
+      ### Shortcut Operation Rules
+      - Can execute at any time when an active plan exists
+      - Performs surgical edits only -- never overwrites the whole plan structure
+      - Re-validates the resulting plan before writing; aborts on validation failure
+
+  - type: file
+    source: ./business.md
+
+  - type: inline
+    content: |
+      ## Output Format
+
+      Render an inline summary (no external template). Structure:
+
+      ```markdown
+      ## Plan Update
+
+      ### Change Applied
+      - **Task**: {task_id} -- {task_title}
+      - **Status**: {old_status} -> {new_status}
+      - **Artifacts attached**: {comma_separated_list_or_"(none)"}
+      - **Notes**: {notes_or_"(unchanged)"}
+
+      ### Plan Progress
+      | # | id | title | status |
+      |---|----|----|--------|
+      | ... |
+
+      Progress: {done_count}/{total_count}
+      Current task: {new_current_task_id_or_"(plan complete)"}
+
+      ### Next
+      {one-line guidance: continue to next task, resolve blocker, or run /mvt-cleanup}
+      ```
+
+      Every response MUST end with a Suggested Next Steps section.
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: inline
+    content: |
+      ### Update-Plan Specific State Updates
+
+      In addition to the mandatory updates above, this skill MUST refresh `recent_changes` for the active change:
+
+      - Find the entry where `id == active_change.id`. If absent, append one (this should be rare; happens when the plan was created out-of-band).
+      - Set `last_updated` to the current ISO 8601 timestamp.
+      - Trim to max 5 entries (drop the oldest by `last_updated` ascending).
+
+      Do NOT modify `active_change.has_plan` or `active_change.plan_path` here -- those are owned by `/mvt-plan-dev`.
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-update-plan
+      conditional_suggestions:
+        conditions:
+          - condition: "plan_done"
+            primary: mvt-cleanup
+            primary_desc: "All tasks complete -- clean up artifacts and prepare to start the next change"
+          - condition: "default"
+            primary: mvt-implement
+            primary_desc: "Continue with the next current_task"
+        alternatives:
+          - skill: mvt-resume
+            desc: "Refresh context after task transitions"
+          - skill: mvt-status
+            desc: "Inspect overall progress across changes"

package/sources/templates/analyze-output/body.md

@@ -1,15 +1,15 @@
-# Requirements Analysis: {Feature Name}
-
-## Feature Overview
-
-## Actors
-
-## Requirements
-
-## Domain Concepts
-
-## Business Rules
-
-## Ambiguities & Questions
-
-## Change Tracking
+# Requirements Analysis: {Feature Name}
+
+## Feature Overview
+
+## Actors
+
+## Requirements
+
+## Domain Concepts
+
+## Business Rules
+
+## Ambiguities & Questions
+
+## Change Tracking

package/sources/templates/design-output/body.md

@@ -1,17 +1,17 @@
-# Architecture Design: {Feature Name}
-
-## Overview
-
-## Architecture Decision Records
-
-## Module Design
-
-## Key Interfaces
-
-## Data Flow
-
-## File Structure
-
-## Implementation Guidelines
-
-## Change Tracking
+# Architecture Design: {Feature Name}
+
+## Overview
+
+## Architecture Decision Records
+
+## Module Design
+
+## Key Interfaces
+
+## Data Flow
+
+## File Structure
+
+## Implementation Guidelines
+
+## Change Tracking

package/sources/templates/implement-output/body.md

@@ -1,11 +1,11 @@
-# Implementation: {Feature Name}
-
-## Implementation Plan
-
-## Changes
-
-## Implementation Details
-
-## Design Compliance
-
-## Change Tracking
+# Implementation: {Feature Name}
+
+## Implementation Plan
+
+## Changes
+
+## Implementation Details
+
+## Design Compliance
+
+## Change Tracking

package/sources/templates/review-output/body.md

@@ -1,11 +1,11 @@
-# Code Review Report
-
-## Summary
-
-## Critical Issues
-
-## Warnings
-
-## Suggestions
-
-## Highlights
+# Code Review Report
+
+## Summary
+
+## Critical Issues
+
+## Warnings
+
+## Suggestions
+
+## Highlights

package/sources/templates/test-output/body.md

@@ -1,7 +1,7 @@
-# Test Design: {Feature Name}
-
-## Test Cases
-
-## Test Code
-
-## Coverage Analysis
+# Test Design: {Feature Name}
+
+## Test Cases
+
+## Test Code
+
+## Coverage Analysis

package/dist/fs/protection.d.ts

@@ -1,15 +0,0 @@
-export interface InstallManifest {
-    version: number;
-    generated: Array<{
-        pattern: string;
-        source: string;
-    }>;
-    create_once: Array<{
-        path: string;
-        source: string;
-    }>;
-    user_data_dirs: string[];
-}
-export declare function loadInstallManifest(packageRoot: string): InstallManifest;
-export declare function isGeneratedFile(filePath: string): boolean;
-//# sourceMappingURL=protection.d.ts.map

package/dist/fs/protection.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"protection.d.ts","sourceRoot":"","sources":["../../src/fs/protection.ts"],"names":[],"mappings":"AAIA,MAAM,WAAW,eAAe;IAC9B,OAAO,EAAE,MAAM,CAAC;IAChB,SAAS,EAAE,KAAK,CAAC;QAAE,OAAO,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IACtD,WAAW,EAAE,KAAK,CAAC;QAAE,IAAI,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAA;KAAE,CAAC,CAAC;IACrD,cAAc,EAAE,MAAM,EAAE,CAAC;CAC1B;AAED,wBAAgB,mBAAmB,CAAC,WAAW,EAAE,MAAM,GAAG,eAAe,CAIxE;AAID,wBAAgB,eAAe,CAAC,QAAQ,EAAE,MAAM,GAAG,OAAO,CAIzD"}

package/dist/fs/protection.js

@@ -1,16 +0,0 @@
-import { existsSync, readFileSync } from "node:fs";
-import path from "node:path";
-import { parse as parseYaml } from "yaml";
-export function loadInstallManifest(packageRoot) {
-    const manifestPath = path.resolve(packageRoot, "install-manifest.yaml");
-    const raw = readFileSync(manifestPath, "utf-8");
-    return parseYaml(raw);
-}
-const GENERATED_MARKER = "<!-- GENERATED by mvtt";
-export function isGeneratedFile(filePath) {
-    if (!existsSync(filePath))
-        return false;
-    const content = readFileSync(filePath, "utf-8");
-    return content.trimStart().startsWith(GENERATED_MARKER);
-}
-//# sourceMappingURL=protection.js.map

package/dist/fs/protection.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"protection.js","sourceRoot":"","sources":["../../src/fs/protection.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACnD,OAAO,IAAI,MAAM,WAAW,CAAC;AAC7B,OAAO,EAAE,KAAK,IAAI,SAAS,EAAE,MAAM,MAAM,CAAC;AAS1C,MAAM,UAAU,mBAAmB,CAAC,WAAmB;IACrD,MAAM,YAAY,GAAG,IAAI,CAAC,OAAO,CAAC,WAAW,EAAE,uBAAuB,CAAC,CAAC;IACxE,MAAM,GAAG,GAAG,YAAY,CAAC,YAAY,EAAE,OAAO,CAAC,CAAC;IAChD,OAAO,SAAS,CAAC,GAAG,CAAoB,CAAC;AAC3C,CAAC;AAED,MAAM,gBAAgB,GAAG,wBAAwB,CAAC;AAElD,MAAM,UAAU,eAAe,CAAC,QAAgB;IAC9C,IAAI,CAAC,UAAU,CAAC,QAAQ,CAAC;QAAE,OAAO,KAAK,CAAC;IACxC,MAAM,OAAO,GAAG,YAAY,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;IAChD,OAAO,OAAO,CAAC,SAAS,EAAE,CAAC,UAAU,CAAC,gBAAgB,CAAC,CAAC;AAC1D,CAAC"}