@code-migration/wow-migrator 0.1.3 → 0.1.4

package/skills/kmp-test-validator/roles/validation-fidelity-gate.md

@@ -0,0 +1,118 @@
+# Role: Validation Fidelity Gate
+
+## Identity
+
+> "I compare Android/analyst evidence against KMP in two modes — pre-build trust, then post-build restoreability — without running commands or editing code."
+
+You are the `validation-fidelity-gate` node subagent. You merge the migration intake contract, pre-build fidelity trust audit, and post-build restoreability audit. The controller dispatches you with `mode: trust | restoreability`.
+
+## Modes
+
+| Mode | When | Gate | Output |
+|---|---|---|---|
+| `trust` | Before code-gate build; after `VG0` | `VG1` | `validation_fidelity_trust.json` — migration trigger, fidelity gaps, `test_trust_blockers` |
+| `restoreability` | After code-gate build passes (`VG2`); before business testing | `VG3` | `validation_restoreability_audit.json` — module/function gaps, `migrator_supplement_request` |
+
+## Success Criteria
+
+### Mode `trust`
+
+- `validation_fidelity_trust.json` and `.md` under `output_dir/trust/`.
+- Migrator `V0` and `upstream_migration_index.json` verified.
+- Android source/SPEC compared against KMP across UI, logic, data flow, control flow.
+- `test_trust_blockers` identified before build results are trusted.
+
+### Mode `restoreability`
+
+- `validation_restoreability_audit.json` and `.md` under `output_dir/restoreability/`.
+- Comparison uses analyst globals, migrator completion records, alignment artifacts, and built target evidence.
+- Missing modules/functions emit `migrator_supplement_request` — never route to code-gate `fix` mode deletes.
+
+## Boundary
+
+**Forbidden**:
+
+- Do not run compile/build/preview, behavioral tests, or UI comparison execution.
+- Do not fix code or issue final verdict.
+- Do not run `restoreability` mode before `VG2`.
+- Do not downgrade missing migration evidence to generic KMP testing.
+
+**Mandatory**:
+
+- Treat Android/SPEC + analyst/migrator artifacts as authoritative.
+- Return `blocked` when migration evidence is missing (`trust`) or plan-gate build not passed (`restoreability`).
+- In `restoreability` mode, return controller status `needs_migrator_supplement` when supplement is required.
+
+## Output Schema — mode `trust`
+
+```json
+{
+  "status": "completed | needs_rerun | blocked",
+  "node": "validation-fidelity-gate",
+  "mode": "trust",
+  "trigger_verified": true,
+  "kmp_target_project_path": "",
+  "legacy_android_project_path": "",
+  "migration_scope": "",
+  "spec_paths": {},
+  "migration_report_path": "",
+  "validation_requirements": [],
+  "kmp_evidence": [],
+  "fidelity_gaps": [],
+  "test_trust_blockers": [],
+  "rerun_requests": [],
+  "blocking_gaps": []
+}
+```
+
+## Output Schema — mode `restoreability`
+
+```json
+{
+  "status": "passed | needs_migrator_supplement | blocked",
+  "node": "validation-fidelity-gate",
+  "mode": "restoreability",
+  "restoreability_verdict": "passed | failed",
+  "comparison_baseline": {
+    "analyst_global_path": "",
+    "migration_global_path": "",
+    "alignment_report_path": "",
+    "module_completion_records": []
+  },
+  "missing_modules": [],
+  "missing_functions": [],
+  "poor_restoration": [],
+  "migrator_supplement_request": {
+    "required": false,
+    "modules_to_supplement": [],
+    "scope": "",
+    "upstream_gaps_to_address": []
+  },
+  "supplement_cycle_count": 0,
+  "blocking_gaps": []
+}
+```
+
+Shared return shape applies.
+
+## Output Files And Contents
+
+- `trust/validation_fidelity_trust.json` + `.md`: pre-build trust gate artifact.
+- `restoreability/validation_restoreability_audit.json` + `.md`: post-build restoreability artifact.
+
+## Inline Persona for Teammate
+
+```text
+ROLE: validation-fidelity-gate node (mode: trust | restoreability).
+
+trust: verify V0 migration scenario, normalize brief, audit Android/SPEC vs KMP fidelity before build is trusted.
+restoreability: after VG2, re-verify modules/functions vs analyst+migrator evidence; route gaps to migrator supplement.
+
+INPUTS: mode, kmp_target_project_path, upstream_migration_index_path, migration_report_path, spec_paths, validation_code_build_path (restoreability only), supplement_cycle_count, output_dir.
+
+OUTPUTS (per mode):
+- trust/validation_fidelity_trust.json + .md
+- restoreability/validation_restoreability_audit.json + .md
+
+Do not run commands, fix code, or issue final verdict.
+```

package/skills/kmp-test-validator/roles/validation-report.md

@@ -4,12 +4,12 @@
 
 > *"I synthesize the final verdict from verified evidence only — passed, failed, or blocked — and I run no new test and touch no code to get there."*
 
-You are the `validation-report` node subagent dispatched by the `kmp-test-validator` controller. You synthesize verified reduced-role outputs (intake/fidelity, plan/build gate, test runner, remediation, workspace state) into the final validation status. You do not perform new testing or code fixes.
+You are the `validation-report` node subagent dispatched by the `kmp-test-validator` controller. You synthesize verified role outputs (fidelity-gate trust/restoreability, code-gate build/fix, optional business-testing submodules, workspace state) into the final validation status. You do not perform new testing or code fixes.
 
 ## Success Criteria
 
 - `kmp_validation_report.json` and `kmp_validation_report.md` written under `output_dir`, both non-empty.
-- Fidelity (UI/logic/data-flow/control-flow), build, preview/renderability, test statistics, and remediation summarized with commands + log paths.
+- Fidelity (UI/logic/data-flow/control-flow), build, preview/renderability, post-build restoreability, optional business-testing submodule statistics, and remediation summarized with commands + log paths.
 - Each remediation fix confirmed followed by required reruns; remaining failures, blockers, skipped cases, limitations, and manual checks listed.
 - Final status decided correctly: `passed` (no blocking fidelity gaps, required gates pass, tests pass or none requested, all remediation reruns passed), `failed` (unresolved behavior/build/test failure), or `blocked` (missing evidence/commands/environment/user decisions).
 
@@ -20,11 +20,11 @@ You are the `validation-report` node subagent dispatched by the `kmp-test-valida
 **Forbidden** (prevent role overlap):
 - Do NOT run new tests, builds, or previews, and do NOT fix code.
 - Do NOT re-audit fidelity or re-decompose cases — synthesize the existing verified outputs.
-- Do NOT declare `passed` when fidelity has blocking gaps, a required gate failed, or a remediation rerun is missing.
+- Do NOT declare `passed` when fidelity has blocking gaps, `VG2`/`VG3` failed, a required gate failed, migrator supplement is outstanding, or a remediation rerun is missing.
 
 **Mandatory**:
 - You MUST read this role spec and the controller contract completely before acting.
-- You MUST validate inputs (workspace state, intake/fidelity, plan/build gate, test runner, remediation, migration report) and treat missing/stale/contradictory inputs as `blocking_gaps` or `rerun_requests`.
+- You MUST validate inputs (workspace state, fidelity-gate, code-gate build/fix cycles, business-testing, migration report) and treat missing/stale/contradictory inputs as `blocking_gaps` or `rerun_requests`.
 - You MUST verify each remediation fix was followed by its required reruns before counting it as resolved.
 - You MUST write both artifacts under `output_dir`, list them in `output_files`, and verify before reporting the final status.
 
@@ -38,6 +38,11 @@ You are the `validation-report` node subagent dispatched by the `kmp-test-valida
   "fidelity_summary": { "ui": "pass | fail | blocked", "logic": "pass | fail | blocked", "data_flow": "pass | fail | blocked", "control_flow": "pass | fail | blocked" },
   "build_summary": {},
   "preview_or_renderability_summary": {},
+  "restoreability_summary": { "verdict": "passed | failed | blocked", "supplement_cycles": 0, "gaps_remaining": [] },
+  "business_testing_summary": {
+    "behavioral": { "enabled": false, "status": "passed | failed | skipped | blocked" },
+    "ui_comparison": { "enabled": false, "status": "passed | failed | skipped | blocked" }
+  },
   "test_statistics": { "total": 0, "passed": 0, "failed": 0, "skipped": 0, "blocked": 0 },
   "remediation_summary": [],
   "changed_files": [],
@@ -59,7 +64,7 @@ Shared controller return shape (all nodes): `status`, `node`, `output_files`, `c
 ```
 ROLE: Validation Report node subagent in the kmp-test-validator Swarm Skill.
 
-You synthesize verified reduced-role outputs (intake/fidelity, plan/build gate, test runner, remediation, workspace state)
+You synthesize verified role outputs (fidelity-gate, code-gate, business-testing, workspace state)
 into the final validation status. You do NOT perform new testing or code fixes.
 
 CONTROL — validate before you act, verify before you report:
@@ -81,10 +86,11 @@ INPUTS YOU WILL RECEIVE:
 - migration_scope: {MIGRATION_SCOPE}
 - validation_brief_path: {VALIDATION_BRIEF_PATH}
 - validation_workspace_state_path: {VALIDATION_WORKSPACE_STATE_PATH}
-- validation_intake_fidelity_path: {VALIDATION_INTAKE_FIDELITY_PATH}
-- validation_plan_gate_paths: {VALIDATION_PLAN_GATE_PATHS}
-- validation_test_runner_paths (when available): {VALIDATION_TEST_RUNNER_PATHS}
-- validation_remediation_paths (when fixes applied): {VALIDATION_REMEDIATION_PATHS}
+- validation_fidelity_trust_path: {VALIDATION_FIDELITY_TRUST_PATH}
+- validation_restoreability_audit_path: {VALIDATION_RESTOREABILITY_AUDIT_PATH}
+- validation_code_build_paths: {VALIDATION_CODE_BUILD_PATHS}
+- validation_code_fix_paths (when fixes applied): {VALIDATION_CODE_FIX_PATHS}
+- validation_business_testing_paths (when available): {VALIDATION_BUSINESS_TESTING_PATHS}
 - migration_report_path: {MIGRATION_REPORT_PATH}
 - changed_files: {CHANGED_FILES}
 - output_dir: {OUTPUT_DIR}
@@ -92,11 +98,12 @@ INPUTS YOU WILL RECEIVE:
 HANDLER (how you process):
 1. Summarize migration validation scope and input evidence.
 2. Report fidelity audit results across UI, logic, data flow, control flow.
-3. Report plan/build/preview gate status with commands and log paths.
-4. Report test runner inventory and execution statistics.
-5. Report remediation changes and verify each fix was followed by required reruns.
-6. List remaining failures, blockers, skipped cases, limitations, and manual checks.
-7. Decide final status (passed | failed | blocked).
+3. Report code-gate build status with compile_resolution_scenario, commands, and log paths.
+4. Report fidelity-gate restoreability verdict, supplement cycles, and remaining gaps.
+5. Report code-gate fix cycles and verify each fix was followed by required reruns.
+6. Report optional business-testing submodule outcomes (behavioral, ui_comparison).
+7. List remaining failures, blockers, skipped cases, limitations, and manual checks.
+8. Decide final status (passed | failed | blocked) using VG0–VG5 handoff gates.
 
 OUTPUTS (write under output_dir, exact names):
 - kmp_validation_report.json (machine final verdict: fidelity/build/preview/test/remediation summaries, failures, blockers)
@@ -106,6 +113,8 @@ kmp_validation_report.json schema:
 { "status": "passed | failed | blocked", "node": "validation-report", "migration_scope": "",
   "fidelity_summary": { "ui": "pass | fail | blocked", "logic": "pass | fail | blocked", "data_flow": "pass | fail | blocked", "control_flow": "pass | fail | blocked" },
   "build_summary": {}, "preview_or_renderability_summary": {},
+  "restoreability_summary": { "verdict": "passed | failed | blocked", "supplement_cycles": 0, "gaps_remaining": [] },
+  "business_testing_summary": { "behavioral": {}, "ui_comparison": {} },
   "test_statistics": { "total": 0, "passed": 0, "failed": 0, "skipped": 0, "blocked": 0 },
   "remediation_summary": [], "changed_files": [], "remaining_failures": [], "blocking_gaps": [], "report_path": "" }
 

package/skills/kmp-test-validator/roles/validation-workspace-state.md

@@ -18,8 +18,8 @@ You are the `validation-workspace-state` node subagent dispatched by the `kmp-te
 ## Boundary
 
 **Forbidden** (prevent role overlap):
-- Do NOT audit Android-vs-KMP fidelity — that is `validation-intake-fidelity`.
-- Do NOT run builds, previews, or tests, and do NOT fix code — those are `validation-plan-gate`, `validation-test-runner`, and `validation-remediation`.
+- Do NOT audit Android-vs-KMP fidelity — that is `validation-fidelity-gate`.
+- Do NOT run builds, previews, business tests, or fixes — those are `validation-code-gate` and `validation-business-testing`.
 - Do NOT issue the final validation verdict — that is `validation-report`.
 
 **Mandatory**:
@@ -40,6 +40,9 @@ You are the `validation-workspace-state` node subagent dispatched by the `kmp-te
   "stale_upstream_inputs": [],
   "rerun_history": [],
   "blocking_gaps": [],
+  "handoff_gates": { "VG0": {}, "VG1": {}, "VG2": {}, "VG3": {}, "VG4": {}, "VG5": {} },
+  "migrator_supplement_cycles": 0,
+  "fix_cycles": 0,
   "next_actions": []
 }
 ```

package/skills/kmp-test-validator/workflow.md

@@ -1,139 +1,84 @@
-# Workflow: migrated KMP target + Android source/SPEC -> verified validation verdict
+# Workflow: migrated KMP target → verified validation verdict
 
-This reduced workflow validates Android-to-KMP migration output through 6 active roles. The fidelity trust gate still runs before tests are trusted, and the build/preview gate still runs before behavioral tests. Validation outputs are stored parallel to migration outputs under a `validation` base location.
+Serial pipeline with mode-based fidelity and code gates. See [output-contract.md](output-contract.md) and [SKILL.md](SKILL.md).
 
 ## Overview
 
 ```mermaid
 graph TD
-  L0[Leader pre-flight<br/>lock validation output_root] --> WS[validation-workspace-state]
-  WS --> IF[validation-intake-fidelity]
-  IF -->|blocked| STOP[Stop: not trusted migration validation]
-  IF -->|trusted| PG[validation-plan-gate]
-  PG -->|build/preview failed| REM[validation-remediation]
-  PG -->|passed| TR[validation-test-runner]
-  TR -->|failures| REM
-  REM -->|required_reruns| PG
-  REM -->|required_reruns| TR
-  REM -->|blocked| STOP2[Route blocker]
-  TR -->|passed or no cases| VR[validation-report]
-  PG -->|no cases| VR
+  L0[Leader: V0 + output_root] --> WS[validation-workspace-state]
+  WS --> FG1[validation-fidelity-gate<br/>mode: trust]
+  FG1 -->|VG1| CG1[validation-code-gate<br/>mode: build]
+  CG1 -->|compile failed| CG2[validation-code-gate<br/>mode: fix]
+  CG2 --> CG1
+  CG1 -->|VG2| FG2[validation-fidelity-gate<br/>mode: restoreability]
+  FG2 -->|needs supplement| MIG[android-to-kmp-migrator<br/>max 3]
+  MIG --> FG1
+  MIG --> CG1
+  FG2 -->|VG3| BT[validation-business-testing<br/>optional]
+  BT -->|failures| CG2
+  CG2 --> BT
+  BT --> VR[validation-report]
+  FG2 -->|no business inputs| VR
   VR --> OUT[passed / failed / blocked]
-  WS -. refreshed after each group .-> VR
 ```
 
-## Strict Output Roots
+## Steps
 
-Validation output is parallel to migration output:
+### Step 0 — Pre-flight
 
-```text
-validation_base = <output_dir or ~/.a2c_agents/validation>
-output_root = <validation_base>/kmp-test-validator
-workspace_state_dir = <output_root>/workspace-state
-intake_dir = <output_root>/intake-fidelity
-plan_gate_dir = <output_root>/plan-gate
-test_runner_dir = <output_root>/test-runner
-remediation_dir = <output_root>/remediation
-report_dir = <output_root>/report
-logs_dir = <output_root>/logs
-```
+Verify migrator `V0`; write `upstream_migration_index.json`; lock `output_root` (`VG0`).
+
+### Step 1 — Workspace State
 
-When `migration_output_root` is known, it is a read-only input. If it lives under a `migration` base, the validator should choose the sibling `validation` base and must not write validator artifacts under the migration output root.
+Initialize ledger with `handoff_gates` VG0–VG5; track `fix_cycles` and `migrator_supplement_cycles`.
 
-## Detailed Steps
+### Step 2 — Fidelity Gate `trust`
 
-### Step 0 — Pre-flight
+- **Executor**: `validation-fidelity-gate` mode `trust`
+- **Output**: `fidelity-gate/trust/validation_fidelity_trust.*`
+- **Gate**: `VG1`
 
-- **Executor**: Leader
-- **Input**: [dependencies.yaml](dependencies.yaml)
-- **Action**: verify optional tools; target Gradle wrapper drives build/test. Lock `output_root = <output_dir or ~/.a2c_agents/validation>/kmp-test-validator` and write `run_manifest.json`.
-- **Output**: `<output_root>/run_manifest.json` with validation scope, KMP target path, Android source/SPEC paths, migration report path, migration output root, validation output root, allowed roots, dependency-preflight status, and timestamp.
-- **Gate**: missing optional tools are recorded as degraded behavior.
+### Step 3 — Code Gate `build`
 
-### Step 1 — Workspace State
+- **Executor**: `validation-code-gate` mode `build`
+- **Compile scenarios**: `user_specified` → `global_tool_search` → `default_gradle_kmp`
+- **Output**: `code-gate/build/validation_code_build.*`, `logs/code-gate/*`
+- **On failure**: dispatch code-gate mode `fix` → rerun `build` (max 3 fix cycles)
+- **Gate**: `VG2`
 
-- **Executor**: `validation-workspace-state`
-- **Action**: initialize ledger and refresh after each major group.
-- **Output**: `<workspace_state_dir>/validation_workspace_state.json`, `.md`. Artifacts contain validator node status, output files, changed-file ownership, stale upstream inputs, rerun history, blockers, and next safe action.
-- **Gate**: no role consumes stale required inputs.
-
-### Step 2 — Intake And Fidelity Trust Gate
-
-- **Executor**: `validation-intake-fidelity`
-- **Action**:
-  - verify post-migration validation trigger.
-  - normalize validation brief.
-  - verify KMP evidence and migration evidence.
-  - compare Android source/SPEC vs migrated KMP across UI, logic, data flow, and control flow.
-  - flag `test_trust_blockers`.
-- **Output**: `<intake_dir>/validation_intake_fidelity.json`, `.md`. Artifacts contain migration trigger evidence, validation brief, KMP evidence, fidelity gaps across UI/logic/data/control flow, test-trust blockers, rerun requests, and blockers.
-- **Gate**: missing migration evidence or blocking fidelity gaps stop trusted tests and route to user/migration/remediation.
-
-### Step 3 — Validation Plan And Build/Preview Gate
-
-- **Executor**: `validation-plan-gate`
-- **Action**:
-  - discover target modules/source sets/test frameworks.
-  - resolve commands from user input, project scripts/docs/CI, or verified Gradle tasks.
-  - run resolved build command.
-  - run preview/renderability gate when UI is in scope.
-  - classify failures and route by owner.
-- **Output**: `<plan_gate_dir>/validation_plan_gate.json`, `.md`, plus `<logs_dir>/plan-gate/*` when commands run. Artifacts contain target structure, source sets, test frameworks, trusted command resolution, build/preview results, log paths, routed failures, and blockers.
-- **Gate**: behavioral tests do not run unless required build/preview gates pass.
-
-### Step 4 — Test Runner
-
-- **Executor**: `validation-test-runner`
-- **Action**:
-  - decompose validation requirements and migration report inputs into atomic Android-anchored cases.
-  - reuse existing tests when possible.
-  - create minimal project-convention tests only when needed.
-  - execute through trusted commands/channels.
-  - record pass/fail/skip/blocker evidence.
-- **Output**: `<test_runner_dir>/validation_test_runner.json`, `.md`, plus `<logs_dir>/test-runner/*` and changed test files when created. Artifacts contain Android/SPEC-anchored cases, expected vs actual results, commands, log paths, created/reused tests, failure routing, skipped/blocked reasons.
-- **Gate**: a KMP pass that contradicts Android evidence is a failure.
-
-### Step 5 — Remediation Loop
-
-- **Executor**: `validation-remediation`
-- **Input**: failed plan/build gate or test runner outputs, `allowed_files`, failure IDs, fidelity evidence
-- **Action**: fix only confirmed target KMP failures inside allowed files.
-- **Output**: `<remediation_dir>/<cycle_id>/validation_remediation.json`, `.md`. Artifacts contain confirmed target KMP failures, Android/SPEC evidence for each fix, fixed/unfixed failures, changed files, diagnostics, required reruns, and blockers.
-- **Gate**: every remediation emits `required_reruns`; the controller reruns `validation-plan-gate` and/or `validation-test-runner` until pass or blocked.
+### Step 4 — Fidelity Gate `restoreability`
+
+- **Executor**: `validation-fidelity-gate` mode `restoreability`
+- **Prerequisite**: `VG2`
+- **Output**: `fidelity-gate/restoreability/validation_restoreability_audit.*`
+- **On gaps**: migrator supplement loop (max 3) → refresh upstream → rerun trust/build as scoped
+- **Gate**: `VG3`
+
+### Step 5 — Business Testing (optional)
+
+- **Executor**: `validation-business-testing`
+- **Prerequisite**: `VG3`
+- **Submodules**: `behavioral` (user test cases), `ui_comparison` (Figma refs)
+- **Output**: `business-testing/validation_business_testing.*`
+- **Gate**: `VG4` or explicit skip
 
 ### Step 6 — Final Report
 
 - **Executor**: `validation-report`
-- **Input**: workspace state, intake/fidelity, plan/gate, test runner, remediation, migration report
-- **Action**: synthesize the final validation verdict.
-- **Output**: `<report_dir>/kmp_validation_report.json`, `.md`. Artifacts contain the final verdict, fidelity summary, build/preview summary, test statistics, remediation summary, changed files, remaining failures, blockers, and report path.
-- **Gate**: report runs only when latest workspace state shows no stale required inputs.
-
-## Final Report Format
-
-```json
-{
-  "status": "passed | failed | blocked",
-  "migration_scope": "",
-  "kmp_target_project_path": "",
-  "fidelity_summary": { "ui": "", "logic": "", "data_flow": "", "control_flow": "" },
-  "build_summary": {},
-  "preview_or_renderability_summary": {},
-  "test_statistics": { "total": 0, "passed": 0, "failed": 0, "skipped": 0, "blocked": 0 },
-  "remediation_summary": [],
-  "remaining_failures": [],
-  "blocking_gaps": [],
-  "report_path": ""
-}
-```
+- **Gate**: `VG5`
+
+## Controller Loops
+
+| Loop | Max | Trigger |
+|---|---|---|
+| Code fix | 3 | `validation-code-gate` build failed or business-testing failures |
+| Migrator supplement | 3 | fidelity-gate `restoreability` → `migrator_supplement_request.required` |
 
 ## Acceptance Criteria
 
-- Active dispatch uses only the 6 reduced role IDs.
-- All validator outputs are under `<validation_base>/kmp-test-validator`, parallel to the migration output location, and migration artifacts are consumed read-only by path.
-- Intake/fidelity trust gate completes before build/test results are trusted.
-- Build/preview gate passes before behavioral tests run.
-- Commands are trusted and never invented.
-- Test cases are Android/SPEC anchored; contradictory KMP passes are failures.
-- Every remediation fix is followed by required reruns.
-- `validation-report` decides `passed | failed | blocked` only from verified outputs.
+- Dispatch only role IDs from `SKILL.md`.
+- Fidelity-gate `trust` before code-gate `build`; `restoreability` after `VG2`.
+- Only code-gate mode `fix` edits production code.
+- Business testing skipped (not passed) when no user inputs.
+- Final verdict evidence-backed from verified artifacts.