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

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

@@ -1,93 +1,85 @@
-name: mvt-cleanup
-output: .claude/skills/mvt-cleanup/SKILL.md
-
-frontmatter:
-  name: mvt-cleanup
-  description: "Clean up workspace artifacts, summarize old changes, and maintain workspace health. Use when workspace has accumulated old artifacts or to reduce context token footprint."
-
-sections:
-  - type: inline
-    content: |
-      # MVT Cleanup
-
-      ## Purpose
-
-      Clean up workspace artifacts, summarize completed changes, and maintain workspace health. Reduces token footprint by archiving old artifacts and removing stale data.
-
-  - type: shared
-    source: sections/role-header.md
-    params:
-      role: Conductor
-      role_desc: "a Workflow Coordinator"
-      decision_rules:
-        - rule: "No arguments -> Interactive cleanup (review items before action)"
-        - rule: "`--dry-run` flag -> Show what would be cleaned without taking action"
-        - rule: "Completed changes found -> Summarize and archive"
-        - rule: "Orphaned artifacts found -> List for user review"
-        - rule: "Stale session data found -> Summarize into single entry"
-      boundaries:
-        - scope: "analyze requirements"
-          skill: "/mvt-analyze"
-        - scope: "design architecture"
-          skill: "/mvt-design"
-        - scope: "write implementation code"
-          skill: "/mvt-implement"
-
-  - type: inline
-    content: |
-      ## Variants
-
-      | Variant | Description |
-      |---------|-------------|
-      | `/mvt-cleanup` | Interactive cleanup (review before action) |
-      | `/mvt-cleanup --dry-run` | Preview what would be cleaned |
-
-  - type: shared
-    source: sections/activation-load-context.md
-    params:
-      extended_context:
-        - "Scan all files under `.ai-agents/workspace/artifacts/` (all change-id directories)"
-
-  - type: shared
-    source: sections/activation-load-config.md
-
-  - type: shared
-    source: sections/activation-preflight.md
-    params:
-      checks:
-        - order: "1"
-          field: "project not initialized"
-          level: "REQUIRED"
-          message: "Project must be initialized (session.yaml exists)"
-
-  - type: inline
-    content: |
-      ### Step 4: Execute
-      Proceed to Execution Flow below.
-
-      ## Cleanup Rules
-
-      | Category | Rule | Action |
-      |----------|------|--------|
-      | Completed changes | Change with `status: completed` older than current task | Summarize -> archive |
-      | Orphaned artifacts | Files in `artifacts/` not referenced by any active change | List for user review |
-      | Stale session data | Session history entries older than 5 phases ago | Summarize into single entry |
-
-  - type: file
-    source: ./business.md
-
-  - type: inline
-    content: |
-      ## Output Format
-
-      Read and use the output template from: `.ai-agents/skills/_templates/cleanup-output.md`
-
-      If a custom version exists at `.ai-agents/skills/_templates/custom/cleanup-output.md`, use the custom version instead.
-
-      Every response MUST end with a Suggested Next Steps section.
-
-  - type: shared
-    source: sections/footer-next-steps.md
-    params:
-      next_primary: mvt-status
-      next_primary_desc: "Verify workspace state"
+name: mvt-cleanup
+output: .claude/skills/mvt-cleanup/SKILL.md
+
+frontmatter:
+  name: mvt-cleanup
+  description: "Clean up workspace artifacts, summarize completed changes, and maintain workspace health. This skill should be used when workspace has accumulated old artifacts, token footprint needs reduction, or to archive completed change records."
+
+sections:
+  - type: inline
+    content: |
+      # MVT Cleanup
+
+      ## Purpose
+
+      Clean up workspace artifacts, summarize completed changes, and maintain workspace health. Reduces token footprint by archiving old artifacts and removing stale data.
+
+  - type: shared
+    source: sections/role-header.md
+    params:
+      role: Conductor
+      role_desc: "a Workflow Coordinator"
+      decision_rules:
+        - rule: "No arguments -> Interactive cleanup (review items before action)"
+        - rule: "`--dry-run` flag -> Show what would be cleaned without taking action"
+        - rule: "Completed changes found -> Summarize and archive"
+        - rule: "Orphaned artifacts found -> List for user review"
+        - rule: "Stale session data found -> Summarize into single entry"
+      boundaries:
+        - scope: "analyze requirements"
+          skill: "/mvt-analyze"
+        - scope: "design architecture"
+          skill: "/mvt-design"
+        - scope: "write implementation code"
+          skill: "/mvt-implement"
+
+  - type: inline
+    content: |
+      ## Variants
+
+      | Variant | Description |
+      |---------|-------------|
+      | `/mvt-cleanup` | Interactive cleanup (review before action) |
+      | `/mvt-cleanup --dry-run` | Preview what would be cleaned |
+
+  - type: shared
+    source: sections/activation-load-context.md
+    params:
+      extended_context:
+        - "Scan all files under `.ai-agents/workspace/artifacts/` (all change-id directories)"
+
+  - 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: "project not initialized"
+          level: "REQUIRED"
+          message: "Project must be initialized (session.yaml exists)"
+
+  - type: inline
+    content: |
+      ## Cleanup Rules
+
+      | Category | Rule | Action |
+      |----------|------|--------|
+      | Completed changes | Change with `status: completed` older than current task | Summarize -> archive |
+      | Orphaned artifacts | Files in `artifacts/` not referenced by any active change | List for user review |
+      | Stale session data | Session history entries older than 5 phases ago | Summarize into single entry |
+
+  - type: file
+    source: ./business.md
+
+  - type: shared
+    source: sections/session-update.md
+
+  - type: shared
+    source: sections/footer-next-steps.md
+    params:
+      current_skill: mvt-cleanup

package/sources/skills/mvt-config/business.md

@@ -1,26 +1,94 @@
-## Execution Flow
-
-### Interactive Menu (Default)
-1. Read current settings from `config.yaml`
-2. Display configuration menu with categories and current values
-3. Wait for user to select a category (1-5)
-4. Show category detail view with editable settings
-5. Apply changes after user confirmation
-
-### Direct Set (`set {key} {value}`)
-1. Validate key exists -- if not, show available keys
-2. Validate value type -- if wrong, show expected type
-3. Preview the change (old -> new)
-4. Ask user to confirm
-5. Apply and write `config.yaml`
-
-### Guided Wizard (`wizard`)
-1. Step 1: Language Preference
-2. Step 2: Output Style (emojis, data format)
-3. Step 3: Architecture Pattern
-4. Summary Preview -> User confirms -> Apply all changes
-
-### Reset (`reset`)
-1. Show all settings that will be reset
-2. Ask user confirmation
-3. Write default values to `config.yaml`
+## Execution Flow
+
+### Step 1: Load Inputs
+- **Recommended**:
+  - `.ai-agents/knowledge/core/manifest.yaml` -- only when computing token estimates for shared knowledge view.
+- **Fallback**: if `config.yaml` is missing, surface the error and recommend `mvtt install` or `/mvt-init`. Do not silently create a fresh config from this skill.
+
+### Step 2: Dispatch by Mode
+- **What**: pick the operating mode from the user's invocation.
+- **How**:
+
+  | Invocation | Mode | Go to |
+  |------------|------|-------|
+  | `/mvt-config` (no args) | Interactive Menu | Step 3 |
+  | `/mvt-config show` | Show All | Step 4 |
+  | `/mvt-config set {key} {value}` | Direct Set | Step 5 |
+  | `/mvt-config wizard` | Guided Wizard | Step 6 |
+  | `/mvt-config reset` | Reset | Step 7 |
+  | Anything else | Refuse, print Variants table, stop | -- |
+
+### Step 3: Interactive Menu
+1. Read current `config.yaml` and render a numbered menu grouped by category (User Preferences, Knowledge Settings, etc.) with current values inline.
+2. Wait for user to select a category number (or `q` to quit).
+3. Show the category detail view: keys with current values, type, default, allowed values.
+4. Let user pick a key to edit; reuse Step 5 (Direct Set) sub-flow for validation, preview, confirmation, write.
+5. After write, return to the top-level menu until user quits.
+6. No write happens unless the Step 5 sub-flow confirms.
+
+### Step 4: Show All
+- Print every key with `current value | type | default`. Mark values that differ from default with a `*`.
+- Print the Configuration Keys reference table (provided in shared section above) below the values, for context.
+- No write.
+
+### Step 5: Direct Set (`set {key} {value}`)
+1. **Validate key exists**:
+   - The key must match one of the rows in the Configuration Keys table. If not, print "Unknown key: <name>", list available keys, exit without writing.
+2. **Validate value type and constraints**:
+
+   | Type | Validation |
+   |------|------------|
+   | `enum` | Value MUST be in the allowed list. Reject with the allowed list shown. For `language` enums (`en-US`, `zh-CN`), reject other locale strings -- ask user to pick from the allowed list (do not fuzzy-match) |
+   | `bool` | Accept exactly `true` / `false` (case-insensitive). Reject `yes`/`1`/`y` |
+   | `int` | Parse as integer; check range when range is documented (e.g., `relevance_threshold` must be 0-100) |
+   | `list` | Parse as comma-separated tokens; for `knowledge.shared`, every token must be a registered knowledge id |
+
+3. **Preview**: render `key: <current> -> <new>` on a single line.
+4. **Confirm**: prompt `Apply this change? (y/n)`. Skip the prompt only if invocation included an explicit non-interactive flag (none currently exists, so always prompt).
+5. **Write atomically**:
+   - Read the current file, mutate only the targeted key, preserve all other content and formatting (do NOT rewrite the whole file from a template -- the user may have comments).
+   - Write to a temp file in the same directory, then rename. On any error, do not touch the original.
+6. Report the new value and a one-line "what this affects" hint (e.g., "applies to subsequent skill invocations").
+
+### Step 6: Guided Wizard
+- Walk the user through these stages in order. Each stage uses the Step 5 validation rules. Defer the actual write to the end.
+
+  | Stage | Key | Notes |
+  |-------|-----|-------|
+  | 1 | `preferences.interaction_language` | Default `en-US`. Show allowed list |
+  | 2 | `preferences.document_output_language` | Default = whatever was just set in stage 1; user may override. Reuse stage-1 value when user accepts default |
+  | 3 | `preferences.output.no_emojis` | Default `true` |
+  | 4 | `preferences.output.data_format` | Default `yaml`; allowed: `yaml`, `json` |
+  | 5 | `preferences.context_routing.relevance_threshold` | Default `70`; allowed: 0-100 |
+
+- After all stages, render a Summary Preview table: `key | from | to`, then a single confirmation prompt to apply ALL changes atomically.
+- If the user aborts at the summary, discard all in-progress values; do not write anything.
+
+### Step 7: Reset
+1. Build the diff between current `config.yaml` and framework defaults: list every key that will revert.
+2. Render the diff as `key | current | will-become-default`.
+3. Require explicit confirmation: `Reset all settings to defaults? (y/n)`.
+4. Backup current `config.yaml` to `config.yaml.bak` before writing.
+5. Write defaults atomically.
+6. Report the keys that changed.
+- Do NOT reset `knowledge.shared` to defaults if the user has added entries via `/mvt-manage-context` -- preserve user-added knowledge ids; only reset preferences. Surface this exception in the diff.
+
+### Step 8: (session update handled by shared section)
+
+## Knowledge Inspection (sub-flow used by Interactive Menu and Show All)
+- **View**: list shared knowledge ids from `registry.yaml > knowledge.shared`, then per-skill knowledge ids grouped by skill (`registry.yaml > skills.*.knowledge`). Show token estimates from each entry's manifest if available.
+- **Modify**: this skill does NOT mutate knowledge settings; defer to `/mvt-manage-context`. Print the suggested command (`/mvt-manage-context move`, `/mvt-manage-context add`, etc.) instead of doing the work here.
+
+## Edge Cases & Errors
+
+| Case | Handling |
+|------|----------|
+| `config.yaml` missing | STOP; recommend `mvtt install` or `/mvt-init` |
+| `config.yaml` exists but unparseable YAML | Surface error with line number; refuse to write; recommend manual fix or `mvtt install --refresh` |
+| User runs `set` with a deprecated key (`preferences.language`) | Print migration hint: `Run mvtt update --migrate-config` to split into the two language fields. Do not mutate the deprecated key |
+| Wizard stage receives an empty value | Treat as "accept default for this stage", continue |
+| User aborts mid-wizard | No partial write; the temp values are discarded |
+| `.bak` from previous reset already exists | Overwrite (only the most recent backup is useful) |
+| Concurrent edit detected (mtime changed during preview->write) | Abort write, surface a message, ask user to re-run |
+| `set knowledge.shared <list>` includes unknown id | Reject with the list of valid ids from `registry.yaml` |
+| `reset` invoked but `config.yaml` already matches defaults | Report "nothing to reset", do not write |

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

@@ -3,7 +3,7 @@ output: .claude/skills/mvt-config/SKILL.md
 
 frontmatter:
   name: mvt-config
-  description: "Interactive configuration management for framework settings. Use when user wants to change language, output format, architecture pattern, or other framework settings."
+  description: "Manage MVTT framework configuration interactively. This skill should be used when user wants to change language, output format, or other framework settings."
 
 sections:
   - type: inline
@@ -12,7 +12,7 @@ sections:
 
       ## Purpose
 
-      Interactive configuration management for MVTT framework settings. Provides guided setup, direct key-value setting, and a setup wizard for common configurations.
+      Manage MVTT framework configuration interactively. Provide guided setup, direct key-value setting, and a setup wizard for common configurations.
 
   - type: shared
     source: sections/role-header.md
@@ -56,53 +56,41 @@ sections:
   - type: shared
     source: sections/activation-load-config.md
 
+  - type: shared
+    source: sections/output-language-constraint.md
+
   - type: inline
     content: |
       ### Step 3: Pre-flight Checks
       - No blocking checks required (config is always accessible)
 
-      ### Step 4: Execute
-      Proceed to Execution Flow below.
-
       ## Configuration Keys
 
       ### User Preferences
 
       | Key | Type | Default | Description |
       |-----|------|---------|-------------|
-      | `preferences.language` | enum | `en-US` | Output language for all responses and documents (en-US, zh-CN) |
+      | `preferences.interaction_language` | enum | `en-US` | Language for interactive output: chat replies, prompts, tables (en-US, zh-CN) |
+      | `preferences.document_output_language` | enum | `en-US` | Language for persisted documents: artifacts, project-context.md (falls back to interaction_language) |
       | `preferences.output.no_emojis` | bool | `true` | Disable emojis in output |
       | `preferences.output.data_format` | enum | `yaml` | Data output format (yaml, json) |
+      | `preferences.context_routing.relevance_threshold` | int | `70` | AI routing threshold for `/mvt-manage-context add` (0-100) |
 
-      ### Pattern Settings
+      ### Knowledge Settings
 
       | Key | Type | Default | Description |
       |-----|------|---------|-------------|
-      | `pattern.active` | enum | `` | Active architecture pattern |
-      | `pattern.selection.auto_detect` | bool | `true` | Auto-detect pattern on init |
-      | `pattern.selection.confirm_with_user` | bool | `true` | Confirm pattern with user |
+      | `knowledge.shared` | list | `[core, project-context]` | Shared knowledge entries in registry.yaml, loaded by all skills |
 
   - type: file
     source: ./business.md
 
-  - type: inline
-    content: |
-      ## Output Format
-
-      Read and use the output template from: `.ai-agents/skills/_templates/config-output.md`
-
-      If a custom version exists at `.ai-agents/skills/_templates/custom/config-output.md`, use the custom version instead.
-
-      Every response MUST end with a Suggested Next Steps section.
+  - type: shared
+    source: sections/session-update.md
+    params:
+      read_only: true
 
   - type: shared
     source: sections/footer-next-steps.md
     params:
-      next_primary: mvt-config
-      next_primary_desc: "`show` -- Verify changes"
-      next_alternatives:
-        - skill: mvt-init
-          when: "--refresh -- Re-analyze with new pattern"
-      always_show:
-        - skill: mvt-status
-          desc: "Check current project state"
+      current_skill: mvt-config