@uoyo/mvtt 2.1.0 → 2.2.0

package/sources/skills/mvt-test/manifest.yaml

@@ -31,9 +31,9 @@ sections:
         - scope: "modify the code being tested"
           skill: "/mvt-fix"
         - scope: "make architecture decisions"
-          skill: "(Test against existing design)"
+          guidance: "test against existing design"
         - scope: "skip edge cases or negative tests"
-          skill: "(Never)"
+          guidance: "never"
 
   - type: inline
     content: |
@@ -46,17 +46,14 @@ sections:
       | `/mvt-test --coverage` | Generate tests with coverage analysis |
 
   - type: shared
-    source: sections/activation-load-context.md
+    source: sections/activation-protocol.md
     params:
+      activation_reads:
+        - session.yaml
       extended_context:
         - "Implementation files to be tested"
-
-  - type: shared
-    source: sections/activation-load-config.md
-
-  - type: shared
-    source: sections/activation-preflight.md
-    params:
+        - ".ai-agents/workspace/artifacts/{active_change.id}/design.md -- error paths / data flow that negative-path scenarios trace to (skip if absent)"
+      has_preflight: true
       checks:
         - order: "1"
           field: "session.initialized_at"
@@ -94,7 +91,7 @@ sections:
       Read the document structure template from: `.ai-agents/skills/_templates/test-output.md`
       If a custom version exists at `.ai-agents/skills/_templates/custom/test-output.md`, use the custom version instead.
       The template defines section structure and guidance comments. Generate applicable content based on test design results.
-      Write the artifact to: `.ai-agents/workspace/artifacts/{change-id}/tests/test-design.md`
+      Write the artifact to: `.ai-agents/workspace/artifacts/{change-id}/test-design.md`
 
   - type: shared
     source: sections/session-update.md

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

@@ -74,7 +74,9 @@ After the Step 3 script reports `plan_status: "done"`:
      ```bash
      node .ai-agents/scripts/epic-update.cjs --epic "<active_epic.epic_path>" --complete-child <active_change.id>
      ```
-   - `session-update.cjs --skill mvt-update-plan --summary "..." --close-change`
+  - If the epic-update command fails, STOP and do not call `session-update.cjs`; report stderr and keep the active change open.
+  - If epic-update succeeds, call `session-update.cjs --skill mvt-update-plan --summary "..." --close-change`.
+  - If session-update fails after epic-update succeeded, report the divergence explicitly: the child was marked done in `epic.yaml`, but `session.active_change` was not closed. Tell the user to rerun `/mvt-update-plan` or manually recover session state before continuing.
    - Display: next child info from epic-update stdout. Suggest `/mvt-analyze` to start the next sub-change.
 
 5. On **n**: No action. Display reminder: "Change remains open. Run other skills (e.g., `/mvt-review`, `/mvt-test`, `/mvt-fix`) as needed; run `/mvt-update-plan` again when ready to advance the epic."
@@ -84,7 +86,9 @@ After the Step 3 script reports `plan_status: "done"`:
      ```bash
      node .ai-agents/scripts/epic-update.cjs --epic "<active_epic.epic_path>" --set-child-status <active_change.id> --child-status done
      ```
-   - `session-update.cjs --skill mvt-update-plan --summary "..." --close-change`
+  - If the epic-update command fails, STOP and do not call `session-update.cjs`; report stderr and keep the active change open.
+  - If epic-update succeeds, call `session-update.cjs --skill mvt-update-plan --summary "..." --close-change`.
+  - If session-update fails after epic-update succeeded, report the divergence explicitly: the child was marked done in `epic.yaml`, but `session.active_change` was not closed. Tell the user to rerun `/mvt-update-plan` or manually recover session state before continuing.
    - Display: "Child marked done, current_change unchanged."
 
 ## Edge Cases & Errors

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

@@ -35,26 +35,22 @@ sections:
           skill: "/mvt-implement"
 
   - type: shared
-    source: sections/activation-load-context.md
+    source: sections/activation-protocol.md
     params:
+      activation_reads:
+        - session.yaml
       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/activation-preflight.md
-    params:
+      has_preflight: true
       checks:
         - order: "1"
           field: "session.initialized_at"
           level: "WARN"
-          message: 'Session not initialized. Run `/mvt-init` first.'
+          message: "Session not initialized. Run `/mvt-init` first."
         - order: "2"
           field: "active_change.plan_path"
           level: "BLOCK"
-          message: 'No active plan. Run `/mvt-plan-dev` to create one.'
+          message: "No active plan. Run `/mvt-plan-dev` to create one."
 
   - type: shared
     source: sections/language-constraint.md

package/sources/sections/activation-load-config.md

@@ -1,8 +0,0 @@
-### Stage 4: Load Config & Apply Preferences (Config Foundation)
-Read `.ai-agents/config.yaml` and enforce it for the whole session:
-
-- `preferences.interaction_language`: language for chat, prompts, status lines, tables, and summaries.
-- `preferences.document_output_language`: language for files written to disk.
-- `preferences.output.no_emojis`: if true, never use emojis.
-- `preferences.output.data_format`: format for artifact data sections.
-- `preferences.context_routing.relevance_threshold`: AI routing threshold for `/mvt-manage-context add` (default 70).

package/sources/sections/activation-load-context.md

@@ -1,49 +0,0 @@
-## Activation Protocol
-
-### Stage 1: Load Context
-Load foundational context:
-- `.ai-agents/workspace/project-context.yaml` -- Project index (structural info)
-- `.ai-agents/registry.yaml` -- Available skills registry and knowledge declarations
-{{?extended_context}}
-
-Extended context for this skill:
-{{/extended_context}}
-{{#extended_context}}
-- {{.}}
-{{/extended_context}}
-
-### Stage 2: Resolve Project Scope (PS)
-
-Read `project-context.yaml > projects[]`.
-
-**Single project** (`projects.length == 1`): PS = [sole project name]; skip the rest of this step.
-
-**Multi-project** (`projects.length > 1`):
-**Mode A -- Plan-driven** (active plan exists and skill operates on plan tasks):
-1. **Plan signal**: PS = current task `project` values from plan `current_tasks`; drop names absent from `projects[]`.
-2. **Path match**: Match current paths against `projects[].path` and `source_paths`.
-3. **Prompt**: If unresolved, list candidates and ask user. Never silently load all projects.
-
-**Mode B -- Non-plan** (no active plan or ad-hoc changes):
-Defer PS to execution: identify change target, match against `projects[].path` and `source_paths`, load project-specific knowledge on demand (Stage 3).
-
-### Stage 3: Load Knowledge
-
-Registry knowledge maps are project-keyed; `_all` is reserved for all projects. This applies to top-level `knowledge` and `skills.<name>.knowledge`.
-
-**Knowledge Loading Protocol**:
-For each registry knowledge entry:
-1. Read its `source` field, e.g. `knowledge/project/_generated/`.
-2. Base dir = `.ai-agents/` + `source`, e.g. `.ai-agents/knowledge/project/_generated/`.
-3. Load `files` entries from that base dir; if `files_from_manifest: true`, read `manifest.yaml` there and load entries with `auto_load: true`.
-4. **Skip non-existent paths** silently (do not error or warn).
-
-Example: `source: knowledge/project/_generated/` + `files: [project-context.md]` resolves to `.ai-agents/knowledge/project/_generated/project-context.md`.
-
-**Anti-pattern -- DO NOT**:
-- Guess or hardcode base directories (e.g., `.ai-agents/workspace/`).
-- Assume a default path structure. The `source` field value is the authoritative path component.
-
-**At activation** (both modes): load `knowledge._all` + `skills.<current-skill>.knowledge._all`.
-**Mode A** (additionally): for each P in PS, load `knowledge[P]` + `skills.<current-skill>.knowledge[P]`.
-**Mode B** (during execution): on demand, load `knowledge[P]` + `skills.<current-skill>.knowledge[P]` for identified project(s).

package/sources/sections/activation-preflight.md

@@ -1,14 +0,0 @@
-### Stage 5: Pre-flight Checks
-
-For each check below, if the condition holds, perform the action implied by its **Level**:
-
-- **WARN** -- emit the message, then ask "Continue anyway? (y/n)". Default to **y** if the user does not respond.
-- **BLOCK** -- emit the message and stop. Do not proceed until the prerequisite is satisfied.
-- **REQUIRED** -- same as BLOCK; the prerequisite is mandatory.
-- **INFO** -- emit the message and proceed; no confirmation needed.
-
-| # | Condition | Level | Message |
-|---|-----------|-------|---------|
-{{#checks}}
-| {{order}} | `{{field}}` is empty | {{level}} | {{message}} |
-{{/checks}}