viepilot 2.15.0 → 2.23.0

package/workflows/request.md

@@ -6,9 +6,10 @@ Create and manage project requests: bugs, features, enhancements, tech debt, and
 
 | Feature | Claude Code (terminal) | Cursor (Agent/Skills) | Codex CLI | Antigravity (native) |
 |---------|----------------------|-----------------------|-----------|----------------------|
-| Interactive prompts | ✅ `AskUserQuestion` tool | ❌ text fallback | ❌ text fallback | ❌ text fallback |
+| Interactive prompts | ✅ `AskUserQuestion` tool — **REQUIRED** | ❌ text fallback | ❌ text fallback | ❌ text fallback |
 
-When `AskUserQuestion` is not available, each prompt block falls back to the plain-text numbered list shown below it — no configuration needed.
+**Claude Code (terminal):** Always call `AskUserQuestion` first. Only fall back to the plain-text menu below if the tool returns an error or is unavailable.
+**Cursor / Codex CLI / Antigravity / other adapters:** `AskUserQuestion` not available — use text menus below.
 
 ## ViePilot Skill Scope Policy (BUG-004)
 
@@ -25,6 +26,8 @@ When `AskUserQuestion` is not available, each prompt block falls back to the pla
 
 <process>
 
+> **AUQ preload — Claude Code adapter (ENH-059):** At session start, before any interactive prompt, call `ToolSearch` with `query: "select:AskUserQuestion"` to load the deferred schema. Required on Claude Code (terminal). Skip only if `ToolSearch` returns an error → use text fallback for that session.
+
 <step name="init">
 ## 1. Initialize
 
@@ -63,12 +66,12 @@ Parse `{{VP_ARGS}}` for type flag:
 If no flag, ask user:
 
 > **Adapter-aware prompt:**
-> - **Claude Code (terminal):** use `AskUserQuestion` tool — spec:
+> **Claude Code (terminal) — REQUIRED:** Call `AskUserQuestion` tool. Only fall back to text menu if the tool errors or is unavailable. AUQ spec:
 >   - question: "What type of request would you like to create?"
 >   - header: "Request type"
 >   - options: [{ label: "🐛 Bug Report", description: "Something is broken — file a defect report" }, { label: "✨ Feature Request", description: "New functionality — add a capability that doesn't exist yet" }, { label: "🔧 Enhancement", description: "Improve existing feature — make something better" }, { label: "🧹 Technical Debt", description: "Code cleanup / refactor — no new behavior" }]
 >   - multiSelect: false
-> - **Cursor / Codex / Antigravity / other:** use text menu below (Brainstorm and List options remain text-only)
+> **Cursor / Codex / Antigravity / other:** use text menu below (Brainstorm and List options remain text-only)
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -86,6 +89,39 @@ What type of request?
 ```
 </step>
 
+<step name="feasibility_gate">
+## 2B. Feasibility Gate — research-agent (ENH-057)
+
+**Trigger**: auto-activate for **Feature** and **Enhancement** requests when any of:
+- User description mentions a new platform, IDE, API, protocol, or SDK
+- User asks "is this possible?", "how does X work?", "feasibility of X"
+- Request type = Feature AND subject is an external integration
+
+**Skip for**: Bug reports, internal refactors, Enhancement requests on known code.
+
+If triggered:
+
+**Claude Code (terminal) — invoke research-agent:**
+```
+Agent({
+  subagent_type: "general-purpose",
+  description: "research-agent: feasibility study for {topic}",
+  prompt: `
+    Load agents/research-agent.md for full spec.
+    Topic: {extracted from user description}
+    Questions: ["What SDK/API exists?", "What are integration points?", "What config dir/convention?", "Feasibility rating?"]
+    Return a ## Research Findings section + ## Sources.
+  `
+})
+```
+
+**Non-Claude Code**: if web search available, perform inline research. Otherwise note "manual research needed" and continue gathering details.
+
+**Output**: embed research-agent findings in the `## Research Findings` section of the request file.
+
+> This gate made FEAT-019 (Copilot adapter) research systematic — apply it to all future platform/API feature requests.
+</step>
+
 <step name="list_requests">
 ## 3. List Requests (if --list)
 
@@ -136,12 +172,12 @@ Options:
 6. Severity?
 
 > **Adapter-aware prompt:**
-> - **Claude Code (terminal):** use `AskUserQuestion` tool — spec:
+> **Claude Code (terminal) — REQUIRED:** Call `AskUserQuestion` tool. Only fall back to text menu if the tool errors or is unavailable. AUQ spec:
 >   - question: "What is the bug severity?"
 >   - header: "Severity"
 >   - options: [{ label: "Critical", description: "System down, data loss — needs immediate attention" }, { label: "High", description: "Major feature broken — significantly impacts users" }, { label: "Medium", description: "Feature impaired — workaround exists" }, { label: "Low", description: "Minor / cosmetic issue — no functional impact" }]
 >   - multiSelect: false
-> - **Cursor / Codex / Antigravity / other:** use text list below
+> **Cursor / Codex / Antigravity / other:** use text list below
 
    1. Critical - System down, data loss
    2. High - Major feature broken
@@ -219,12 +255,12 @@ Create `BUG-{N}.md`:
 5. Priority?
 
 > **Adapter-aware prompt:**
-> - **Claude Code (terminal):** use `AskUserQuestion` tool — spec:
+> **Claude Code (terminal) — REQUIRED:** Call `AskUserQuestion` tool. Only fall back to text menu if the tool errors or is unavailable. AUQ spec:
 >   - question: "What is the feature priority?"
 >   - header: "Priority"
 >   - options: [{ label: "Must-have", description: "Critical for release — cannot ship without it" }, { label: "Should-have", description: "Important but not blocking — include if capacity allows" }, { label: "Nice-to-have", description: "Quality-of-life improvement — can defer to next milestone" }]
 >   - multiSelect: false
-> - **Cursor / Codex / Antigravity / other:** use text list below
+> **Cursor / Codex / Antigravity / other:** use text list below
 
    1. Must-have - Critical for release
    2. Should-have - Important but not blocking
@@ -256,6 +292,9 @@ Create `FEAT-{N}.md`:
 ## Summary
 {TITLE}
 
+## Research Findings
+{Populated by research-agent if feasibility gate triggered (Step 2B); omit section if not applicable}
+
 ## Problem Statement
 {PROBLEM}
 
@@ -544,6 +583,8 @@ git push
 <step name="confirm">
 ## 7. Confirm
 
+Output the request summary banner:
+
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  VIEPILOT ► REQUEST CREATED ✓
@@ -558,15 +599,33 @@ git push
  File: .viepilot/requests/{TYPE}-{N}.md
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- Next Steps
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
 
- /vp-request --list    View all requests
- /vp-evolve            ROADMAP + phase/tasks (before code)
- /vp-auto              Implement theo task plan (sau evolve)
- /vp-request           Create another request
- /vp-status            See overall progress
+Then — **Claude Code adapter (terminal): use AskUserQuestion**:
 
+```
+question: "Request {TYPE}-{N} logged. What would you like to do next?"
+options:
+  - label: "Plan phase + tasks → /vp-evolve"
+    description: "Create ROADMAP entry, phase dir, and task files now (Recommended)"
+  - label: "Create another request → /vp-request"
+    description: "Log more requests before planning"
+  - label: "Done for now"
+    description: "Exit — request is saved in backlog"
+```
+
+**On selection:**
+- "Plan phase + tasks → /vp-evolve": invoke `/vp-evolve` skill
+- "Create another request → /vp-request": invoke `/vp-request` skill
+- "Done for now": print brief confirmation and exit
+
+**Text fallback (Cursor, Codex, Copilot, Antigravity — AUQ not available):**
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ Next:
+ - /vp-evolve            Plan phase/tasks + ROADMAP
+ - /vp-request           Create another request
+ - /vp-request --list    View all requests
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 </step>

package/workflows/rollback.md

@@ -8,7 +8,8 @@ Safe rollback to any ViePilot checkpoint with backup and state preservation.
 ## 1. List Available Checkpoints
 
 ```bash
-git tag --sort=-creatordate | rg "(^vp-p|^-*vp-backup|^[a-z0-9-]+-vp-p|^[a-z0-9-]+-vp-backup)" | head -20
+git tag --sort=-creatordate | rg "(^vp-p|^-*vp-backup|^[a-z0-9._-]+-vp-p|^[a-z0-9._-]+-vp-backup)" | head -20
+# [a-z0-9._-]+ matches both legacy and enriched (prefix-branch-version-vp-p*) formats (ENH-050)
 ```
 
 For each tag, get info:
@@ -127,13 +128,44 @@ git log -1 --oneline
 <step name="update_state">
 ## 7. Update State Files
 
-Parse tag to determine phase/task (support both legacy and project-scoped):
-- `vp-p{N}-t{M}` or `{project}-vp-p{N}-t{M}` → Phase N, Task M, status: in_progress
-- `vp-p{N}-t{M}-done` or `{project}-vp-p{N}-t{M}-done` → Phase N, Task M+1, status: not_started
-- `vp-p{N}-complete` or `{project}-vp-p{N}-complete` → Phase N+1, Task 1, status: not_started
+Parse tag to determine phase/task — 3 supported formats (ENH-050):
 
-Update HANDOFF.json accordingly.
-Update TRACKER.md progress.
+- **Format A** (legacy): `vp-p{N}-t{M}[-done]` or `vp-p{N}-complete`
+- **Format B** (project-scoped): `{project}-vp-p{N}-t{M}[-done]` or `{project}-vp-p{N}-complete`
+- **Format C** (enriched): `{project}-{branch}-{version}-vp-p{N}-t{M}[-done|-complete]`
+
+For all formats, extract N and M by matching the terminal segments:
+
+```bash
+TAG="{selected_tag}"
+
+# Extract phase number — works for all 3 formats
+PHASE_NUM=$(echo "$TAG" | grep -oE 'vp-p[0-9]+' | grep -oE '[0-9]+$')
+
+# Extract task number if present
+TASK_NUM=$(echo "$TAG" | grep -oE '\-t[0-9]+' | tail -1 | grep -oE '[0-9]+$')
+
+# Determine restore intent
+if echo "$TAG" | grep -q '\-complete$'; then
+  # Phase complete tag → restore to start of next phase
+  RESTORE_PHASE=$((PHASE_NUM + 1))
+  RESTORE_TASK=1
+  RESTORE_STATUS="not_started"
+elif echo "$TAG" | grep -q '\-done$'; then
+  # Task done tag → restore to start of next task
+  RESTORE_PHASE=$PHASE_NUM
+  RESTORE_TASK=$((TASK_NUM + 1))
+  RESTORE_STATUS="not_started"
+else
+  # Task start tag → restore to in-progress state
+  RESTORE_PHASE=$PHASE_NUM
+  RESTORE_TASK=${TASK_NUM:-1}
+  RESTORE_STATUS="in_progress"
+fi
+```
+
+Update HANDOFF.json with `RESTORE_PHASE`, `RESTORE_TASK`, `RESTORE_STATUS`.
+Update TRACKER.md progress accordingly.
 </step>
 
 <step name="confirm_success">