@wazir-dev/cli 1.1.0 → 1.3.0

package/wazir.manifest.yaml

@@ -47,20 +47,31 @@ workflows:
   - prepare_next
   - run_audit
 phases:
-  - clarify
-  - discover
-  - specify
-  - spec_challenge
-  - author
-  - design
-  - design_review
-  - plan
-  - plan_review
-  - execute
-  - verify
-  - review
-  - learn
-  - prepare_next
+  - init
+  - clarifier
+  - executor
+  - final_review
+phase_prerequisites:
+  init: {}
+  clarifier: {}
+  executor:
+    required_artifacts:
+      - clarified/clarification.md
+      - clarified/spec-hardened.md
+      - clarified/design.md
+      - clarified/execution-plan.md
+    required_phase_exits:
+      - clarifier
+  final_review:
+    required_artifacts:
+      - clarified/clarification.md
+      - clarified/spec-hardened.md
+      - clarified/design.md
+      - clarified/execution-plan.md
+      - artifacts/verification-proof.md
+    required_phase_exits:
+      - clarifier
+      - executor
 roles:
   - clarifier
   - researcher
@@ -85,6 +96,7 @@ required_hooks:
   - stop_handoff_harvest
   - protected_path_write_guard
   - loop_cap_guard
+  - context_mode_router
 protected_paths:
   - input
   - roles

package/workflows/plan-review.md

@@ -39,7 +39,9 @@ On completing this phase, run:
 
 ## Loop Structure
 
-Follows the review loop pattern in `docs/reference/review-loop-pattern.md` with plan dimensions. The planner role resolves findings. Pass count determined by depth. No extension.
+Follows the review loop pattern in `docs/reference/review-loop-pattern.md` with 8 plan dimensions (including Input Coverage). The planner role resolves findings. Pass count determined by depth. No extension.
+
+**Input Coverage dimension:** The reviewer reads the original input/briefing, counts distinct items, and compares against tasks in the plan. If `tasks_in_plan < items_in_input`, this is a HIGH finding listing the missing items. This prevents silent scope reduction where 21 input items become 5 tasks.
 
 ## Failure Conditions
 

package/workflows/verify.md

@@ -14,6 +14,16 @@ On entering this phase, run:
 - changed files
 - claimed outcomes
 - acceptance criteria
+- project type (detected via `detectRunnableType(projectRoot)` → web | api | cli | library, from `tooling/src/verify/proof-collector.js`)
+
+## Process
+
+1. **Detect project type:** Run `detectRunnableType(projectRoot)` to determine verification strategy
+2. **Collect evidence:** Run `collectProof(taskSpec, runConfig)` with the detected type
+3. **For runnable output (web/api/cli):** Run the application and capture runtime evidence (build output, screenshots, curl responses, CLI output)
+4. **For non-runnable output (library/config/skills):** Run lint, format check, type check, and tests — all must pass
+5. **Save evidence:** Write to `.wazir/runs/<id>/artifacts/proof-<task>.json`
+6. **Validate:** Ensure every acceptance criterion has at least one evidence item mapped to it
 
 ## Primary Role
 
@@ -21,7 +31,11 @@ On entering this phase, run:
 
 ## Outputs
 
-- verification proof artifact
+- verification proof artifact (produced by `collectProof` from `tooling/src/verify/proof-collector.js`)
+
+## Proof Collection
+
+Use `detectRunnableType` to classify the project, then `collectProof` to gather evidence. The proof-collector runs type-appropriate commands (build, test, lint, type-check) using `execFileSync` and returns structured `{ type, evidence }`.
 
 ## Approval Gate
 
@@ -32,6 +46,19 @@ On entering this phase, run:
 On completing this phase, run:
 `wazir capture event --run <run-id> --event phase_exit --phase <phase-name> --status completed`
 
+## Proof of Implementation
+
+The verifier detects whether the project output is runnable and collects appropriate evidence:
+
+| Project Type | Detection | Evidence Collected |
+|-------------|-----------|-------------------|
+| `web` | next/vite/react-scripts in deps | Build output, Playwright screenshot (if available), curl response |
+| `api` | express/fastify/hono in deps | curl endpoint responses with status codes |
+| `cli` | `bin` field in package.json | `--help` output, test run with sample args |
+| `library` | default (no runnable markers) | npm test, tsc, eslint, prettier — all must pass |
+
+Evidence is saved to `.wazir/runs/<id>/artifacts/proof-<task>.json` using `collectProof()` from `tooling/src/verify/proof-collector.js`.
+
 ## Relationship to Review Loops
 
 Verification is invoked per-task during execution, not as a review loop. It produces deterministic proof, not adversarial findings.
@@ -39,3 +66,5 @@ Verification is invoked per-task during execution, not as a review loop. It prod
 ## Failure Conditions
 
 - stale or partial verification
+- proof-collector reports `status: "fail"` for any evidence item
+- runnable type detected but no evidence collected