projecta-rrr 1.16.4 → 1.16.5

package/CHANGELOG.md

@@ -4,40 +4,22 @@ All notable changes to RRR will be documented in this file.
 
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
-## [1.16.4] - 2026-01-27
+## [1.16.5] - 2026-01-27
 
 ### Fixed
-- **Playwright MCP Detection** - Enhanced detection logic now checks multiple locations:
-  - `~/.claude/mcp.json` (primary)
-  - `~/.claude/settings.json` (alternate)
-  - `playwright-mcp` command availability
-  - Running processes via `ps`
-- **QA Engineer Mode Auto-Detection** - UAT now auto-detects test type from SUMMARY.md:
-  - Web UI tests → Recommend AI QA Engineer (Playwright + MiniMax)
-  - API/Backend tests → Recommend Zeroshot
-  - Mixed tests → Offer both options with clear recommendations
-
-### Added
-- **Intuitive Mode Selection** - Testing mode selection now shows:
-  - Auto-detected test type (e.g., "Web UI tests")
-  - Clear explanation of each mode's strengths
-  - Recommended option highlighted
-  - Cost estimates for AI-powered modes
-
-- **run_qa_engineer_batch Step** - New workflow step for AI QA Engineer mode:
-  - Combines Playwright MCP (browser control) + MiniMax (visual AI)
-  - Tests edge cases automatically
-  - Explores navigation paths beyond happy path
-  - ~$0.001 per test (MiniMax vision is 50-100x cheaper than Anthropic API)
+- **Verify-Work UAT Workflow Path** - Fixed workflow file loading for UAT mode:
+  - Changed from relative path (`rrr/workflows/verify-work.md`) to `@` reference (`@rrr/workflows/verify-work.md`)
+  - Workflow now loads correctly from RRR framework (`~/.claude/rrr/workflows/verify-work.md`)
+- **Milestone-Level UAT Support** - Added comprehensive milestone support:
+  - Detects milestone targets (`v1.2`, `v2.0`) and finds all phases in that milestone
+  - Creates UAT file at `.planning/milestones/{milestone}/phases/{milestone}-UAT.md`
+  - Updates frontmatter with `target_type` (phase/milestone) and `target`
+  - Fixed commit message generation for milestone-level UAT
+- **PHASE_ARG Variable Propagation** - Added export of `PHASE_ARG` for workflow consumption
+- **SUMMARY Path Detection** - Fixed test type detection to search both old and new directory structures
+- **UAT File Discovery** - Updated active session detection to search `.planning/` recursively for both phase and milestone UAT files
 
-- **run_playwright_batch Step** - New workflow step for Playwright-only mode:
-  - Browser automation without visual AI validation
-  - Fallback when MiniMax API key not available
-
-### Changed
-- **Improved Mode Routing** - create_uat_file step now routes to 4 modes:
-  - `qa-engineer` → run_qa_engineer_batch
-  - `zeroshot` → run_zeroshot_batch
+## [1.16.4] - 2026-01-27
   - `playwright` → run_playwright_batch
   - `manual` → present_test
 

package/commands/rrr/verify-work.md

@@ -86,6 +86,14 @@ Validate built features through **audit mode by default**, or interactive UAT wi
 hasAuditFlag = $ARGUMENTS contains "--audit"
 hasUatFlag = $ARGUMENTS contains "--uat"
 target = $ARGUMENTS with flags removed (e.g., "05", "v1.9", or empty)
+
+# Set PHASE_ARG for workflow consumption (UAT mode needs this)
+if [ -n "$target" ]; then
+  PHASE_ARG="$target"
+else
+  PHASE_ARG=""
+fi
+export PHASE_ARG
 ```
 
 **Step 2: Route and explain selection**
@@ -98,6 +106,7 @@ target = $ARGUMENTS with flags removed (e.g., "05", "v1.9", or empty)
 **If --uat is present:**
 1. Execute the `<uat_mode>` section below
 2. This loads the workflow file which runs component tests then UAT
+3. The workflow uses `$PHASE_ARG` to find summaries
 
 **If --audit is present OR no flags:**
 1. Execute the `<audit_mode>` section below (DEFAULT)
@@ -331,9 +340,9 @@ Purpose: Component tests → Zeroshot/Manual user acceptance testing
 For quick evidence check, use: /rrr:verify-work --audit
 ```
 
-**Load the workflow to run UAT:**
+**Load the UAT workflow:**
 
-Read the file at: `rrr/workflows/verify-work.md`
+@rrr/workflows/verify-work.md
 
 The workflow contains the full UAT process including:
 1. **Component tests** — Runs vitest --browser if configured

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projecta-rrr",
-  "version": "1.16.4",
+  "version": "1.16.5",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by Projecta.ai",
   "bin": {
     "projecta-rrr": "bin/install.js"

package/rrr/workflows/verify-work.md

@@ -237,7 +237,8 @@ Based on what's available, calculate the recommended mode:
 
 ```bash
 # Check SUMMARY.md content to determine test type
-SUMMARY_CONTENT=$(cat .planning/phases/*/phases/*-SUMMARY.md 2>/dev/null | head -100)
+# Search in both old (.planning/phases/*/) and new (.planning/milestones/*/phases/*/) structures
+SUMMARY_CONTENT=$(cat .planning/phases/*/*-SUMMARY.md .planning/milestones/*/phases/*/*-SUMMARY.md 2>/dev/null | head -100)
 
 if echo "$SUMMARY_CONTENT" | grep -qiE "(ui|page|screen|button|form|input|click|navigation|redirect|layout|visual|interface)"; then
   TEST_TYPE="WEB_UI"
@@ -306,34 +307,35 @@ Proceed to `check_active_session`.
 **First: Check for active UAT sessions**
 
 ```bash
-find .planning/phases -name "*-UAT.md" -type f 2>/dev/null | head -5
+# Search for UAT files in both old (.planning/phases/) and new (.planning/milestones/*/phases/) structures
+UAT_FILES=$(find .planning -name "*-UAT.md" -type f 2>/dev/null | head -10)
 ```
 
 **If active sessions exist AND no $ARGUMENTS provided:**
 
-Read each file's frontmatter (status, phase) and Current Test section.
+Read each file's frontmatter (status, target, target_type) and Current Test section.
 
 Display inline:
 
 ```
 ## Active UAT Sessions
 
-| # | Phase | Status | Current Test | Progress |
-|---|-------|--------|--------------|----------|
-| 1 | 04-comments | testing | 3. Reply to Comment | 2/6 |
-| 2 | 05-auth | testing | 1. Login Form | 0/4 |
+| # | Target | Type | Status | Current Test | Progress |
+|---|--------|------|--------|--------------|----------|
+| 1 | 04-comments | phase | testing | 3. Reply to Comment | 2/6 |
+| 2 | v1.2 | milestone | testing | 1. Login Form | 0/4 |
 
-Reply with a number to resume, or provide a phase number to start new.
+Reply with a number to resume, or provide a target to start new.
 ```
 
 Wait for user response.
 
 - If user replies with number (1, 2) → Load that file, go to `resume_from_file`
-- If user replies with phase number → Treat as new session, go to `create_uat_file`
+- If user replies with phase number or milestone → Treat as new session, go to `create_uat_file`
 
 **If active sessions exist AND $ARGUMENTS provided:**
 
-Check if session exists for that phase. If yes, offer to resume or restart.
+Check if session exists for that target (phase or milestone). If yes, offer to resume or restart.
 If no, continue to `create_uat_file`.
 
 **If no active sessions AND no $ARGUMENTS:**
@@ -341,7 +343,7 @@ If no, continue to `create_uat_file`.
 ```
 No active UAT sessions.
 
-Provide a phase number to start testing (e.g., /rrr:verify-work 4)
+Provide a phase number (e.g., 4) or milestone (e.g., v1.2) to start testing:
 ```
 
 **If no active sessions AND $ARGUMENTS provided:**
@@ -352,15 +354,32 @@ Continue to `create_uat_file`.
 <step name="find_summaries">
 **Find what to test:**
 
-Parse $ARGUMENTS as phase number (e.g., "4") or plan number (e.g., "04-02").
+Parse $ARGUMENTS to determine scope:
 
-```bash
-# Find phase directory
-# Find phase directory using phase-paths library (handles milestone-aware structure)
-PHASE_DIR=$(find_phase_dir "${PHASE_ARG}")
+- **Phase number** (e.g., `4`, `05`, `05-auth`): Test that phase only
+- **Milestone** (e.g., `v1.9`, `v2.0`): Test all phases in that milestone
+- **Empty**: Use current milestone from ROADMAP.md
 
-# Find SUMMARY files
-ls "$PHASE_DIR"/*-SUMMARY.md 2>/dev/null
+```bash
+# Determine if target is a milestone (starts with 'v' followed by digits)
+if [[ "$PHASE_ARG" =~ ^v[0-9]+\.[0-9]+$ ]]; then
+  # Milestone target - find all SUMMARY files in that milestone's phases
+  MILESTONE="$PHASE_ARG"
+  MILESTONE_DIR=".planning/milestones/${MILESTONE}/phases"
+  if [ -d "$MILESTONE_DIR" ]; then
+    find "$MILESTONE_DIR" -maxdepth 2 -name "*-SUMMARY.md" 2>/dev/null | sort
+  else
+    echo "ERROR: Milestone directory not found: $MILESTONE_DIR" >&2
+  fi
+else
+  # Phase target - use find_phase_dir
+  PHASE_DIR=$(find_phase_dir "${PHASE_ARG}")
+  if [ -n "$PHASE_DIR" ]; then
+    ls "$PHASE_DIR"/*-SUMMARY.md 2>/dev/null
+  else
+    echo "ERROR: Phase directory not found for: $PHASE_ARG" >&2
+  fi
+fi
 ```
 
 Read each SUMMARY.md to extract testable deliverables.
@@ -391,7 +410,21 @@ Skip internal/non-observable items (refactors, type changes, etc.).
 **Create UAT file with all tests:**
 
 ```bash
-mkdir -p "$PHASE_DIR"
+# Determine if milestone target and set up output location
+if [[ "$PHASE_ARG" =~ ^v[0-9]+\.[0-9]+$ ]]; then
+  # Milestone-level UAT - create in milestone's phases directory
+  MILESTONE="$PHASE_ARG"
+  MILESTONE_DIR=".planning/milestones/${MILESTONE}/phases"
+  mkdir -p "$MILESTONE_DIR"
+  UAT_FILE="$MILESTONE_DIR/${MILESTONE}-UAT.md"
+  TARGET_TYPE="milestone"
+else
+  # Phase-level UAT - use existing phase directory
+  mkdir -p "$PHASE_DIR"
+  PHASE_NAME=$(basename "$PHASE_DIR")
+  UAT_FILE="$PHASE_DIR/${PHASE_NAME}-UAT.md"
+  TARGET_TYPE="phase"
+fi
 ```
 
 Build test list from extracted deliverables.
@@ -401,7 +434,8 @@ Create file:
 ```markdown
 ---
 status: testing
-phase: XX-name
+target_type: {TARGET_TYPE}
+target: {PHASE_ARG}
 source: [list of SUMMARY.md files]
 started: [ISO timestamp]
 updated: [ISO timestamp]
@@ -441,7 +475,7 @@ skipped: 0
 [none yet]
 ```
 
-Write to `{phase_dir}/{phase}-UAT.md` (where phase_dir is from get_phase_dir)
+Write to `$UAT_FILE`
 
 **Route based on testing mode:**
 - If `TESTING_MODE=qa-engineer` → Go to `run_qa_engineer_batch`
@@ -782,13 +816,19 @@ Clear Current Test section:
 
 Commit the UAT file:
 ```bash
-git add "{phase_dir}/{phase}-UAT.md"
-git commit -m "test({phase}): complete UAT - {passed} passed, {issues} issues"
+# Use target from frontmatter (phase or milestone)
+if [ "$TARGET_TYPE" = "milestone" ]; then
+  git add "$UAT_FILE"
+  git commit -m "test(${TARGET}): complete UAT - ${passed} passed, ${issues} issues"
+else
+  git add "$UAT_FILE"
+  git commit -m "test(${TARGET}): complete UAT - ${passed} passed, ${issues} issues"
+fi
 ```
 
 Present summary:
 ```
-## UAT Complete: Phase {phase}
+## UAT Complete: {TARGET_TYPE} {TARGET}
 
 | Result | Count |
 |--------|-------|