@code-migration/wow-migrator 0.2.4 → 0.2.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@code-migration/wow-migrator",
-  "version": "0.2.4",
+  "version": "0.2.6",
   "description": "Install KMP migration skills into Claude Code, Codex, Cursor, Gemini, OpenCode, OpenClaw, and JiuwenSwarm via npm install.",
   "keywords": [
     "android",

package/skills/android-project-analyst/SKILL.md

@@ -11,27 +11,27 @@ roles:
   - id: analysis-workspace-state
     kind: ai_agent
     purpose: Analysis ledger — module status, node output inventory, stale inputs, rerun/blocker history, artifact readiness, and next actions. No source analysis or SPEC writing.
-    skills: []
+    skills: [operating-instructions]
     tools: [git]
   - id: presentation-resource
     kind: ai_agent
     purpose: Presentation and resource owner — screens, UI technologies, navigation, UI modules, local/remote image and media resources, safe downloads, and UI/resource migration implications.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg, curl]
   - id: project-architecture
     kind: ai_agent
     purpose: Project architecture owner — Gradle/module topology, architecture style, layer roles, dependency ecosystem, Jetpack/DI/platform services, generated tooling, and Android-only constraints.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg]
   - id: data-contract-flow
     kind: ai_agent
     purpose: Data contract and flow owner — network/local data contracts, models, consumers, repositories, streams, transformations, cache/error/pagination, write-back, and UI state propagation.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg]
   - id: behavior-logic
     kind: ai_agent
     purpose: Behavior and control-flow owner — user actions, lifecycle, state holders, business rules, side effects, state machines, navigation effects, gates, and cross-module interactions.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg]
 ---
 
@@ -41,6 +41,8 @@ This is the agent-facing registry and team definition for the `android-project-a
 
 **Canonical file recording system**: [output-contract.md](output-contract.md) defines every output path, required content, write order, and downstream **handoff package gates** (`P0`–`P6`). Downstream handlers (`migration-task-adapter`, `android-to-kmp-migrator`, `kmp-test-validator`) trigger only when the declared package artifacts exist, are non-empty, in-path, and not stale. The Leader MUST read `output-contract.md` before the first dispatch and MUST NOT claim completion without updating `handoff_gates` in the workspace ledger and `SPEC/verification.md`.
 
+**Baseline operating instructions**: [../operating-instructions/SKILL.md](../operating-instructions/SKILL.md) is the shared conduct layer for this skill and every dispatched analyst role. The Leader MUST read it before pre-flight/module partitioning and include it in each role dispatch as baseline instructions; role files, workflow gates, and output contracts add to it, not replace it.
+
 The team is **module-first Mixed B+C with a workspace-state ledger**: the Leader partitions the project into `analysis_modules`, writes index artifacts and one `modules/<module_id>/` folder per module, maintains `analysis-workspace-state` before downstream consumption, runs three foundation nodes in **parallel** (B) inside each module, then a final **gated specialization** node (C) synthesizes module behavior from verified upstream outputs. The Leader writes a module representation per module, records cross-module architecture and data/logic separately under `global/`, then combines everything into `global_representation.*` and SPEC. The controller owns routing, strict output-path enforcement, reconciliation, workspace-state refreshes, and SPEC integration; nodes own bounded module analysis only.
 
 ## Module Partitioning Model

package/skills/android-project-analyst/bind.md

@@ -22,7 +22,7 @@ Team-level rules — distinct from each role's own `## Boundary`.
 - **Foundation slices, dispatch-time fixed (B-pattern, Stage A)**: each foundation node works ONLY on its assigned slice. Slices are fixed at dispatch and are not renegotiated between nodes; nodes do not see each other's working state during Stage A.
 - **Gated handoff, no upstream mutation (C-pattern, Stage B)**: `behavior-logic` references upstream node outputs (by path) and enriches only where behavior analysis requires; it MUST NOT rebuild or overwrite an upstream node's catalog. If upstream data is missing/stale, it returns `needs_rerun`/`blocked` rather than reconstructing it.
 - **Mandatory contract enforcement**: every node is dispatched with a complete module-scoped contract (`source_project_path`, `module_id`, `module_scope`, `module_brief_path`, required upstream artifacts, `analysis_scope`, `skill_spec_path`, exact `output_dir`). The Leader rejects any return that lacks required JSON/MD artifacts, omits produced files from `output_files`, writes outside the assigned path, or claims `completed`/`ready_*` without proven output storage.
-- **Role-output content discipline**: required artifacts must contain the content owned by their role, not just the correct filename. For example, `presentation_resource.*` must contain screens/resources/navigation/UI-tree evidence with `tree_text` in Required Markdown shape (`tree_text_format: required-markdown-v1`) for every checked screen; `module_representation.json` must promote those trees verbatim into `presentation_slice.ui_layout_view_trees[]`; `module_ui_representation.md` must contain the same trees as the standalone UI handoff; `project_architecture.*` must contain topology/build/dependency/platform evidence, `data_contract_flow.*` must contain APIs/data-source/model/flow evidence, and `behavior_logic.*` must contain action/lifecycle/rule/control-flow evidence. If content belongs to another role, rerun or route rather than accepting it.
+- **Role-output content discipline**: required artifacts must contain the content owned by their role, not just the correct filename. For example, `presentation_resource.*` must contain screens/resources/navigation/UI-tree evidence with `tree_text` in Required Markdown shape (`tree_text_format: required-markdown-v1`) for every checked screen; `module_representation.json` must promote those trees verbatim into `presentation_slice.ui_layout_view_trees[]`; `module_ui_representation.md` must contain the same trees as the standalone UI handoff; `project_architecture.*` must contain topology/build/dependency/platform evidence; `data_contract_flow.*` must contain APIs/data-source/model/flow evidence; `data_flow_tracker_report.*` must record handler-step coverage, follow-ups, and links to `data_contract_flow.*`; and `behavior_logic.*` must contain action/lifecycle/rule/control-flow evidence. If content belongs to another role, rerun or route rather than accepting it.
 - **Conflict handling**: when nodes disagree on a fact affecting architecture, data flow, resources, ecosystem constraints, behavior, or migration, the Leader surfaces it verbatim as `Needs confirmation` in `verification.md`. The Leader does NOT silently pick a winner or average findings.
 - **No source modification**: no node and not the Leader may edit the analyzed Android project. `presentation-resource` writes downloads only under `<output_dir>/node-results/presentation-resource/downloaded_resources/` and never stores secrets/cookies/tokens.
 - **Agent-only artifacts**: node outputs and SPEC files are structured for downstream agents/controllers, not human presentation; any user-facing summary is produced only after durable artifacts exist.

package/skills/android-project-analyst/dependencies.yaml

@@ -5,7 +5,17 @@
 # Android Studio MCP is optional auxiliary evidence for the Legacy Android source project —
 # it never replaces durable node artifacts or handoff package gates (P0–P6).
 
-skills: []   # No local domain-specific skill packages required for active roles.
+skills:
+  - name: operating-instructions
+    required: true
+    used_by:
+      - Leader
+      - analysis-workspace-state
+      - presentation-resource
+      - project-architecture
+      - data-contract-flow
+      - behavior-logic
+    purpose: Shared baseline conduct layer loaded before analyst pre-flight, module partitioning, node dispatch, evidence synthesis, and final handoff work.
 
 optional_mcp:
   - server: jetbrains

package/skills/android-project-analyst/output-contract.md

@@ -33,6 +33,8 @@ output_root = <output_dir or ~/.a2c_agents/understand>/android-project-analyst
 │       │   │   ├── project_architecture.json
 │       │   │   └── project_architecture.md
 │       │   ├── data-contract-flow/
+│       │   │   ├── data_flow_tracker_report.json
+│       │   │   ├── data_flow_tracker_report.md
 │       │   │   ├── data_contract_flow.json
 │       │   │   └── data_contract_flow.md
 │       │   └── behavior-logic/
@@ -162,6 +164,8 @@ Artifacts MUST be produced in this order. Skipping a layer invalidates downstrea
 | `modules/<module_id>/node-results/presentation-resource/presentation_resource.json` | `presentation-resource` | `module_id`, `screen_inventory`, `ui_layout_view_trees[]` (each with non-empty `tree_text` in `tree_text_format: required-markdown-v1` when `representation_promotion_ready: true`), `navigation_edges`, `cross_module_references[]`, `resource_usage_map`, `representation_promotion`, `evidence_paths` | UI understanding, resource migration, navigation handoff, representation promotion |
 | `modules/<module_id>/node-results/project-architecture/project_architecture.json` | `project-architecture` | `module_id`, `module_topology`, `detected_patterns`, `layer_roles`, `cross_module_dependencies[]`, `migration_constraints`, `evidence_paths` | Architecture migration, dependency/platform gate |
 | `modules/<module_id>/node-results/data-contract-flow/data_contract_flow.json` | `data-contract-flow` | `module_id`, API/model contracts, `end_to_end_flows`, `cross_module_data_links[]`, `evidence_paths` | Data/API migration, repository mapping |
+| `modules/<module_id>/node-results/data-contract-flow/data_flow_tracker_report.json` | `data-contract-flow` | `module_id`, `handler_steps[]`, `coverage_summary`, `follow_ups[]`, `blocking_gaps`, `linked_artifacts` | Investigation coverage gate, workspace ledger, rerun routing |
+| `modules/<module_id>/node-results/data-contract-flow/data_flow_tracker_report.md` | `data-contract-flow` | Step coverage table, coverage summary, open follow-ups, blockers | Agent-readable investigation handoff |
 | `modules/<module_id>/node-results/behavior-logic/behavior_logic.json` | `behavior-logic` | `module_id`, `screen_logic`, `control_flows`, `cross_module_interactions[]`, upstream alignment refs | Behavior/test planning, control-flow migration |
 | `modules/<module_id>/dimension_index.json` | Leader | `module_id`, `dimensions{}` with four entries, each with `node_id`, `output_dir`, `json_path`, `md_path`, `status` | **Per-module completeness gate** — handlers verify all four dimensions before consuming representation |
 | `modules/<module_id>/representation/module_representation.json` | Leader | `module_id`, `ui_representation_md_path`, `dimension_traceability[]`, `presentation_slice.ui_layout_view_trees[]` (verbatim `tree_text` from `presentation_resource.json`), synthesized slices per dimension, `intra_module_gaps`, `readiness` | **Module-level handoff** — migrator loads this for a scoped `module_id` |
@@ -277,14 +281,23 @@ Rules:
       "evidence_count": 0
     },
     "project-architecture": { },
-    "data-contract-flow": { },
+    "data-contract-flow": {
+      "node_id": "data-contract-flow",
+      "output_dir": "",
+      "json_path": "",
+      "md_path": "",
+      "tracker_json_path": "",
+      "tracker_md_path": "",
+      "status": "completed | blocked | missing",
+      "evidence_count": 0
+    },
     "behavior-logic": { }
   },
   "representation_ready": false
 }
 ```
 
-Each dimension entry MUST have resolvable `json_path` and `md_path` before `representation_ready` is true.
+Each dimension entry MUST have resolvable `json_path` and `md_path` before `representation_ready` is true. The `data-contract-flow` entry MUST also have resolvable `tracker_json_path` and `tracker_md_path`.
 
 ### Cross-module global records (migration assembly basis)
 
@@ -364,8 +377,9 @@ Downstream handlers MUST NOT start unless the declared package gate passes. A ga
 | `modules/<module_id>/module_brief.json` |
 | `modules/<module_id>/dimension_index.json` (all four dimensions `status: completed`) |
 | all four dimension JSON+MD pairs under `node-results/<dimension>/` |
+| `modules/<module_id>/node-results/data-contract-flow/data_flow_tracker_report.json` and `.md` |
 
-**Fail closed when**: any dimension is `missing`, `blocked`, or paths in `dimension_index.json` do not resolve.
+**Fail closed when**: any dimension is `missing`, `blocked`, or paths in `dimension_index.json` do not resolve; `data-contract-flow` tracker report is missing, empty, or `handler_steps` do not cover all eleven investigation steps.
 
 ### Package `P3` — Module representation handoff
 
@@ -440,6 +454,7 @@ Every node MUST:
 - Use exact filenames from this contract (JSON snake_case basename, dimension folder kebab-case).
 - Include `module_id` in every dimension JSON artifact.
 - Populate cross-module pointer arrays (`cross_module_references`, `cross_module_dependencies`, `cross_module_data_links`, `cross_module_interactions`) with `target_module_id` and `source_paths` so the Leader can build Package `P4` without re-reading source.
+- `data-contract-flow` MUST write and maintain `data_flow_tracker_report.*` during investigation and list all four output files in `output_files`.
 
 ## Invalid Artifact Handling (downstream uniform rule)
 

package/skills/android-project-analyst/roles/analysis-workspace-state.md

@@ -10,7 +10,7 @@ You are the `analysis-workspace-state` node subagent dispatched by the `android-
 
 - `analysis_workspace_state.json` and `analysis_workspace_state.md` written under `output_dir`, both non-empty.
 - Every known analysis module and node output is normalized into one ledger.
-- Stale inputs are flagged when module briefs, node outputs, module representations, global representation, SPEC paths, source roots, or analysis requirements changed since a dependent artifact was produced.
+- Stale inputs are flagged when module briefs, node outputs, data-flow investigation tracker reports, module representations, global representation, SPEC paths, source roots, or analysis requirements changed since a dependent artifact was produced.
 - Rerun and blocker history are recorded without hiding repeated failures.
 - Next safe controller actions are listed.
 - `handoff_gates` for packages `P0`–`P6` per [output-contract.md](../output-contract.md) are evaluated with `ready` flags and `missing_paths[]`.
@@ -70,7 +70,7 @@ Write only under `output_dir = <output_root>/workspace-state/`. Evaluate handoff
 ## Output Files And Contents
 
 - `analysis_workspace_state.json`: machine-routable ledger of run mode, current controller step, module statuses, node output statuses, artifact inventory, stale upstream inputs, rerun history, blocking gaps, `handoff_gates` (`P0`–`P6` per [output-contract.md](../output-contract.md)), and next safe actions. It must not include UI, architecture, data-flow, or behavior analysis.
-- `analysis_workspace_state.md`: agent-readable ledger handoff with module status table, dimension output inventory per `module_id`, `modules_index.json` and `dimension_index.json` readiness, cross-module global record status, artifact readiness table, stale-input table, rerun/blocker history, and next controller action. It must preserve exact artifact paths and owner nodes.
+- `analysis_workspace_state.md`: agent-readable ledger handoff with module status table, dimension output inventory per `module_id`, data-flow investigation tracker status per module, `modules_index.json` and `dimension_index.json` readiness, cross-module global record status, artifact readiness table, stale-input table, rerun/blocker history, and next controller action. It must preserve exact artifact paths and owner nodes.
 
 ## Inline Persona for Teammate
 
@@ -114,13 +114,17 @@ INPUTS YOU WILL RECEIVE:
 HANDLER (how you process):
 1. Normalize module status and node output status for every known analysis module.
 2. Track artifact inventory for run manifest, module inventory, modules_index.json, module briefs,
-   dimension outputs, dimension_index.json, module representations, cross-module global records,
+   dimension outputs (including `data-contract-flow` → `data_flow_tracker_report.*` plus
+   `data_contract_flow.*`), dimension_index.json, module representations, cross-module global records,
    global representation, and SPEC outputs.
-3. Detect stale upstream inputs when source roots, module briefs, node outputs, representations, or
+3. For each `data-contract-flow` module output, record tracker report paths, `handler_steps`
+   completion summary, open `follow_ups`, and `blocking_gaps`; flag stale when tracker and
+   `data_contract_flow.*` are out of sync or tracker is missing.
+4. Detect stale upstream inputs when source roots, module briefs, node outputs, representations, or
    SPEC inputs changed after dependent artifacts were produced.
-4. Record rerun and blocker history without hiding repeated failures.
-5. Evaluate handoff packages P0–P6 from output-contract.md; set ready flags and missing_paths.
-6. Identify the next safe controller action.
+5. Record rerun and blocker history without hiding repeated failures.
+6. Evaluate handoff packages P0–P6 from output-contract.md; set ready flags and missing_paths.
+7. Identify the next safe controller action.
 
 OUTPUTS (write under output_dir, exact names):
 - analysis_workspace_state.json (machine ledger: module/node/artifact status, stale inputs, reruns, blockers, next actions)

package/skills/android-project-analyst/roles/data-contract-flow.md

@@ -8,7 +8,8 @@ You are the `data-contract-flow` node subagent and data contract/flow owner disp
 
 ## Success Criteria
 
-- `data_contract_flow.json` and `data_contract_flow.md` written under the assigned module-scoped `output_dir`, both non-empty.
+- `data_contract_flow.json`, `data_contract_flow.md`, `data_flow_tracker_report.json`, and `data_flow_tracker_report.md` written under the assigned module-scoped `output_dir`, all non-empty.
+- `data_flow_tracker_report.*` records investigation-step coverage, follow-ups, and links to the final flow artifacts.
 - The output includes the exact `module_id` and stays within `module_scope`.
 - Every API entry has a service class/function or is listed as dynamic/unknown.
 - Every API entry and major data-source claim has at least one source path.
@@ -33,7 +34,8 @@ You are the `data-contract-flow` node subagent and data contract/flow owner disp
 - You MUST validate inputs and scope before work (`module_id` present, `module_scope` in-bounds, and `module_brief_path` exists); on missing/stale/contradictory/out-of-scope inputs, stop and return `blocked` or `needs_rerun` with precise `blocking_gaps`.
 - You MUST attach a source path to every endpoint, major data source, repository flow, transformation, and end-to-end flow.
 - You MUST record dynamic/generated/unavailable APIs in `dynamic_or_unknown_apis` instead of guessing.
-- You MUST write `data_contract_flow.json` and `data_contract_flow.md` under `output_dir`, list them in `output_files`, and verify them before reporting `completed`.
+- You MUST maintain `data_flow_tracker_report.json` and `data_flow_tracker_report.md` throughout investigation — update step coverage and follow-ups as you work, then finalize before completion.
+- You MUST write all four artifacts under `output_dir`, list them in `output_files`, and verify they exist and are non-empty before reporting `completed`.
 
 ## Output Schema
 
@@ -88,6 +90,54 @@ You are the `data-contract-flow` node subagent and data contract/flow owner disp
 }
 ```
 
+#### `data_flow_tracker_report.json` (investigation tracker — write/update during analysis)
+
+Machine-routable progress ledger for the data-flow investigation. Update as handler steps complete; finalize when `data_contract_flow.*` is written.
+
+```json
+{
+  "status": "in_progress | completed | blocked",
+  "node": "data-contract-flow",
+  "module_id": "",
+  "investigation_started_at": "",
+  "investigation_completed_at": "",
+  "linked_artifacts": {
+    "data_contract_flow_json": "data_contract_flow.json",
+    "data_contract_flow_md": "data_contract_flow.md"
+  },
+  "handler_steps": [
+    {
+      "step_id": "scope_and_cross_module_links | network_stack | api_declarations | api_consumers | local_data_sources | models_and_mappings | repository_layers | reactive_propagation | transformations_writeback | loading_error_empty | record_unknowns",
+      "step_number": 0,
+      "status": "pending | in_progress | completed | partial | blocked | skipped",
+      "items_investigated": 0,
+      "items_pending": 0,
+      "follow_ups": [],
+      "evidence_paths": []
+    }
+  ],
+  "coverage_summary": {
+    "apis": { "total": 0, "investigated": 0, "unknown": 0 },
+    "data_sources": { "total": 0, "investigated": 0, "unknown": 0 },
+    "repository_flows": { "total": 0, "investigated": 0, "unknown": 0 },
+    "reactive_streams": { "total": 0, "investigated": 0, "unknown": 0 },
+    "end_to_end_flows": { "total": 0, "investigated": 0, "unknown": 0 }
+  },
+  "follow_ups": [
+    {
+      "id": "",
+      "area": "",
+      "description": "",
+      "reason": "",
+      "blocking": false,
+      "owner": "data-contract-flow | behavior-logic | Leader",
+      "source_paths": []
+    }
+  ],
+  "blocking_gaps": []
+}
+```
+
 ## Output Path Contract
 
 Write only under `output_dir = <output_root>/modules/<module_id>/node-results/data-contract-flow/`. Exact filenames and downstream trigger role: [output-contract.md](../output-contract.md) § Per-module dispatch and dimensions. Out-of-path artifacts invalidate package `P2`.
@@ -96,6 +146,8 @@ Write only under `output_dir = <output_root>/modules/<module_id>/node-results/da
 
 - `data_contract_flow.json`: machine-routable data contract/flow artifact containing network stack, API declarations, request/response/model contracts, local/generated/platform data sources, model mappings, repository flows, reactive streams, transformations, end-to-end flows, dynamic/unknown APIs, cross-module data links, gaps, assumptions, and evidence paths.
 - `data_contract_flow.md`: agent-readable data handoff containing network stack overview, API endpoint table, consumer mapping table, local/generated/platform data-source inventory, model mapping notes, repository & mapper flow tables, reactive stream summary, end-to-end Mermaid flow diagrams when evidence allows, loading/error/empty handling summary, dynamic or unknown API gaps, gaps, and assumptions.
+- `data_flow_tracker_report.json`: machine-routable investigation tracker — handler-step status, coverage counts, follow-ups, blocking gaps, and links to `data_contract_flow.*`.
+- `data_flow_tracker_report.md`: agent-readable investigation handoff — step coverage table, coverage summary, open follow-ups, and blockers. Update during analysis; finalize when flow artifacts are complete.
 
 ## Inline Persona for Teammate
 
@@ -113,7 +165,9 @@ CONTROL — validate before you act, verify before you report:
   and module_brief_path exists. On missing / stale / contradictory / out-of-scope inputs, STOP
   and return status "blocked" or "needs_rerun" with precise blocking_gaps. Do not guess or
   broaden scope.
-- Write outputs ONLY under output_dir; do not report "completed" until both files exist,
+- Initialize data_flow_tracker_report.* at investigation start; refresh step coverage and
+  follow_ups as handler steps complete.
+- Write outputs ONLY under output_dir; do not report "completed" until all four files exist,
   are non-empty, and are verified.
 
 You MUST attach a source path to every endpoint, data source, repository flow, transformation,
@@ -137,28 +191,41 @@ INPUTS YOU WILL RECEIVE:
 - optional jetbrains MCP context (indexed search / symbol info): {MCP_CONTEXT}
 
 HANDLER (how you process):
+0. Create data_flow_tracker_report.json and .md with status in_progress, module_id,
+   investigation_started_at, empty handler_steps aligned to steps 1–11 below, and
+   coverage_summary initialized to zero.
 1. Stay inside module_scope; record cross-module data dependencies as cross_module_data_links with target_module_id and source_paths — these feed global/cross_module_data_logic.* during Leader integration
-   without analyzing target modules here.
+   without analyzing target modules here. Update tracker step scope_and_cross_module_links.
 2. Identify network stack (Retrofit/OkHttp/Ktor/Volley/GraphQL/custom/generated clients).
+   Update tracker step network_stack.
 3. Catalog API service declarations (path, method, function, service class, request/response
-   types, annotations).
+   types, annotations). Update tracker step api_declarations and coverage_summary.apis.
 4. Catalog API and data consumers (repositories, data sources, use cases, ViewModels, presenters,
-   loaders, workers).
+   loaders, workers). Update tracker step api_consumers.
 5. Catalog local/generated/platform data sources (Room/SQLite/DataStore/SharedPreferences/files/
-   ContentProvider/in-memory caches/Worker outputs/generated API or DB code).
+   ContentProvider/in-memory caches/Worker outputs/generated API or DB code). Update tracker step
+   local_data_sources and coverage_summary.data_sources.
 6. Catalog models and mappings (request/response DTOs, entities, domain models, UI state models,
-   pagination/error wrappers).
+   pagination/error wrappers). Update tracker step models_and_mappings.
 7. Trace repository & data-source layers (interfaces, implementations, mappers, cache policies,
-   paging sources, loaders, data managers).
+   paging sources, loaders, data managers). Update tracker step repository_layers and
+   coverage_summary.repository_flows.
 8. Trace reactive propagation (LiveData/StateFlow/Flow/Rx/callbacks/event-bus/observable fields/
-   Compose state).
+   Compose state). Update tracker step reactive_propagation and coverage_summary.reactive_streams.
 9. Trace transformations and write-back paths (action→validation→repo/API/local write→cache
-   invalidation→UI update).
+   invalidation→UI update). Update tracker step transformations_writeback.
 10. Identify loading/error/empty paths, retry/refresh, cache invalidation, pagination, and gaps.
+    Update tracker step loading_error_empty.
 11. Record unknowns (dynamic endpoint construction, generated code absent, remote schema
-   unavailable, unclear consumers).
+    unavailable, unclear consumers). Update tracker step record_unknowns; add non-blocking items to
+    follow_ups and blocking items to blocking_gaps.
+12. Write data_contract_flow.json and .md from verified findings; finalize tracker with status
+    completed, investigation_completed_at, linked_artifacts paths, and reconciled coverage_summary
+    counts vs data_contract_flow.json.
 
 OUTPUTS (write under output_dir, exact names):
+- data_flow_tracker_report.json (investigation tracker: handler-step coverage, follow-ups, blockers)
+- data_flow_tracker_report.md (agent handoff: step table, coverage summary, follow-ups, blockers)
 - data_contract_flow.json (machine artifact: APIs, data sources, models, mappings, repository/reactive/end-to-end flows, gaps, evidence)
 - data_contract_flow.md (agent handoff: endpoint/source/consumer tables, flow diagrams, loading/error/empty behavior, unknowns)
 
@@ -167,7 +234,7 @@ RETURN TO CONTROLLER (exactly this shape, no preamble):
   "status": "completed",
   "node": "data-contract-flow",
   "summary": "short summary",
-  "output_files": ["data_contract_flow.json", "data_contract_flow.md"],
+  "output_files": ["data_flow_tracker_report.json", "data_flow_tracker_report.md", "data_contract_flow.json", "data_contract_flow.md"],
   "key_findings": [],
   "blocking_gaps": []
 }

package/skills/android-project-analyst/workflow.md

@@ -126,8 +126,9 @@ No node may choose its own output path. `presentation-resource` may write downlo
   - `presentation_resource.json`, `presentation_resource.md`: UI entry points, screen inventory, checked UI layout/view trees (`tree_text` in Required Markdown shape, `representation_promotion_ready`), navigation, presentation modules, resources, safe downloads, usage map, migration implications, gaps.
   - `project_architecture.json`, `project_architecture.md`: build/SDK config, topology, architecture patterns, layer roles, dependencies, Jetpack/DI/platform/generated usage, boundary risks, migration constraints.
   - `data_contract_flow.json`, `data_contract_flow.md`: network/local data contracts, APIs, models, data sources, mappings, repository/reactive/end-to-end flows, loading/error/empty behavior, dynamic API gaps.
+  - `data_flow_tracker_report.json`, `data_flow_tracker_report.md`: investigation-step coverage, coverage counts, follow-ups, blockers, and links to the flow artifacts above.
 - **Serial / Parallel**: parallel within one module — all three run together for the same `module_id`. Do not start the next module until the current module representation is written unless the user explicitly allows concurrent modules.
-- **Quality gate**: each return must be `status: "completed"` with `output_files` that exist and are non-empty. Refresh `analysis-workspace-state` after the group; on missing/empty/non-`completed`/stale output → re-dispatch that node with the same contract plus the failure reason (retry policy in [bind.md](bind.md) § Failure Handling). Do NOT synthesize around a failed node.
+- **Quality gate**: each return must be `status: "completed"` with `output_files` that exist and are non-empty. For `data-contract-flow`, require `data_flow_tracker_report.*` in addition to `data_contract_flow.*`. Refresh `analysis-workspace-state` after the group; on missing/empty/non-`completed`/stale output → re-dispatch that node with the same contract plus the failure reason (retry policy in [bind.md](bind.md) § Failure Handling). Do NOT synthesize around a failed node.
 
 ### Step 5 — Stage B per module: dispatch behavior logic node (gated handoff, C-pattern)
 
@@ -142,7 +143,7 @@ No node may choose its own output path. `presentation-resource` may write downlo
 
 - **Executor**: Leader
 - **Input**: verified dimension JSON/MD outputs for one `module_id`
-- **Action**: write `dimension_index.json` mapping the four analysis dimensions to their verified artifact paths and status. Then integrate ONLY from verified dimension outputs for that module. Write a module representation that covers both UI and logic when present: module purpose, UI surface, resources, architecture/ecosystem, data contracts/flows, behavior logic, dimension traceability index, intra-module dependencies, risks, gaps, evidence index, and readiness. **Promote presentation UI trees**: copy every `presentation_resource.json` → `ui_layout_view_trees[]` item with `representation_promotion_ready: true` verbatim into `module_representation.json` → `presentation_slice.ui_layout_view_trees[]` (`tree_text`, `tree_text_format: required-markdown-v1`, screen/section metadata, `dimension_source_path`); write the same trees into independent `module_ui_representation.md` under `## UI Layout Trees` (Required Markdown shape in ` ```text ` fences per screen/section). Set `ui_representation_md_path` in JSON; `module_representation.md` links to the UI file — no duplicate tree blocks. Record cross-module references as pointers only; do not synthesize full inter-module graphs here.
+- **Action**: write `dimension_index.json` mapping the four analysis dimensions to their verified artifact paths and status. For `data-contract-flow`, include `tracker_json_path` and `tracker_md_path` pointing at `data_flow_tracker_report.*`. Then integrate ONLY from verified dimension outputs for that module. Write a module representation that covers both UI and logic when present: module purpose, UI surface, resources, architecture/ecosystem, data contracts/flows, behavior logic, dimension traceability index, intra-module dependencies, risks, gaps, evidence index, and readiness. **Promote presentation UI trees**: copy every `presentation_resource.json` → `ui_layout_view_trees[]` item with `representation_promotion_ready: true` verbatim into `module_representation.json` → `presentation_slice.ui_layout_view_trees[]` (`tree_text`, `tree_text_format: required-markdown-v1`, screen/section metadata, `dimension_source_path`); write the same trees into independent `module_ui_representation.md` under `## UI Layout Trees` (Required Markdown shape in ` ```text ` fences per screen/section). Set `ui_representation_md_path` in JSON; `module_representation.md` links to the UI file — no duplicate tree blocks. Record cross-module references as pointers only; do not synthesize full inter-module graphs here.
 - **Output**: `dimension_index.json`, `module_representation.json`, `module_representation.md`, `module_ui_representation.md`. `dimension_index.json` is the per-module dimension lookup. Module representation JSON is the module-level synthesis and traceability index; `module_ui_representation.md` is the standalone UI handoff; `module_representation.md` is the full-module agent-readable summary. All must cite verified dimension artifacts and source evidence; presentation trees MUST use Required Markdown shape from [roles/presentation-resource.md](roles/presentation-resource.md).
 - **Serial / Parallel**: serial
 - **Quality gate**: `dimension_index.json` lists all four dimensions with resolvable paths; no unknowns hidden; every module representation points to its dimension artifacts and source evidence; every `representation_promotion_ready: true` UI tree from `presentation_resource.json` appears verbatim in `presentation_slice.ui_layout_view_trees[]` and in `module_ui_representation.md`. Refresh workspace state after writing. Do not proceed to cross-module global records until every scheduled module is represented or explicitly marked blocked/out of scope.

package/skills/android-to-kmp-migrator/SKILL.md

@@ -11,47 +11,47 @@ roles:
   - id: migration-workspace-state
     kind: ai_agent
     purpose: Migration ledger — handoff gates M0–V0, plan-vs-code gaps, stale outputs, rerun hooks. No code edits.
-    skills: []
+    skills: [operating-instructions]
     tools: [git]
   - id: target-project-assistant
     kind: ai_agent
     purpose: Target KMP owner — global baseline, per-module anchors, alignment revision, consult log.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg]
   - id: migration-planning-gate
     kind: ai_agent
     purpose: Planning and dependency/platform gate — SPEC deltas, source-to-target map, capability map, ready_for_implementation.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg]
   - id: migration-prep
     kind: ai_agent
     purpose: Presentation and state/data prep — tokens, resources, routes, state/models/API expectations.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg, curl]
   - id: module-implementation
     kind: ai_agent
     purpose: Target KMP module implementation by mode — edit/create KMP UI files first, then logic after UI approval.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg]
   - id: module-node-review-fix
     kind: ai_agent
     purpose: Review or scoped fix by mode; fresh re-review after every fix.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg, git]
   - id: migration-verification
     kind: ai_agent
-    purpose: Module static checks + UI/logic restoration vs analyst — no full project build.
-    skills: []
+    purpose: Module static checks + UI/logic/analytics (埋点) restoration vs analyst — no full project build.
+    skills: [operating-instructions]
     tools: [rg, git]
   - id: global-migration-phase
     kind: ai_agent
     purpose: Target KMP global integrate (edit cross-module glue + entry point wiring) then align (read-only analyst vs target comparison incl. entry points) by mode.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg]
   - id: completion-report
     kind: ai_agent
     purpose: Readiness and migration_report modes; validation handoff to kmp-test-validator.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg, git]
 ---
 
@@ -61,6 +61,8 @@ Module-first migrator for Legacy Android → KMP target assembly. **Upstream ana
 
 **Canonical contract**: [output-contract.md](output-contract.md)
 
+**Baseline operating instructions**: [../operating-instructions/SKILL.md](../operating-instructions/SKILL.md) is the shared conduct layer for this skill and every dispatched migrator role. The Leader MUST read it before pre-flight and include it in each role dispatch as baseline instructions; role files, architecture references, workflow gates, and output contracts add to it, not replace it.
+
 ## Protocol Summary
 
 0. Pre-flight — [dependencies.yaml](dependencies.yaml): `rg` / `git` / `curl`, optional `jetbrains` MCP (`optional_mcp`), upstream analyst **P6** (`upstream_inputs`); **identify `design_mode` from user input (default `mvi`)**; record `dependency_preflight` and `design_mode` in `run_manifest.json`.
@@ -68,8 +70,8 @@ Module-first migrator for Legacy Android → KMP target assembly. **Upstream ana
 2. Migration inventory + `modules_migration_index.json`.
 3. Workspace state init.
 4. TPA `global_baseline`.
-5. **Per module** (assembly_order): TPA `module_anchors` → **planning-gate** → **prep** → review/fix → **implementation `ui`** → review/fix → **implementation `logic`** → review/fix → verification → completion record → readiness → module representation.
-6. **Global phase `integrate`** (cross-module glue + **entry point wiring**) → **`align`** (incl. **entry point alignment** vs Android) + alignment report.
+5. **Per module** (assembly_order): TPA `module_anchors` → **planning-gate** → **prep** (incl. analytics_expectations) → review/fix → **implementation `ui`** → review/fix → **implementation `logic`** (incl. 埋点 restoration) → review/fix → verification (incl. analytics_restoration) → completion record → readiness → module representation.
+6. **Global phase `integrate`** (cross-module glue + **entry point wiring** + **analytics SDK wiring**) → **`align`** (incl. **entry point** and **analytics alignment** vs Android) + alignment report.
 7. Global representation + completion-report `report` mode.
 8. **kmp-test-validator** — **mandatory** when **V0** ready (MG17).
 

package/skills/android-to-kmp-migrator/bind.md

@@ -51,6 +51,7 @@
 | `ui` and `logic` combined | Reject invocation |
 | `integrate` and `align` combined | Reject invocation |
 | Verification restoration failed | Rerun `module-implementation` or `migration-prep`; no completion record |
+| Analytics restoration failed (`analytics_restoration` check or `global_alignment_results.analytics` failed) | Rerun `module-implementation` `logic` for missing 埋点; rerun `global-migration-phase integrate` for SDK wiring gaps |
 | Align omissions | Rerun `rerun_modules` or `global-migration-phase integrate` |
 | Entry point alignment failed | `rerun_global_integration` — rewire KMP app shell in integrate mode |
 | Build requested in migrator | Block; route to kmp-test-validator |

package/skills/android-to-kmp-migrator/dependencies.yaml

@@ -8,6 +8,20 @@
 
 # Skill chain (mandatory — Leader enforces at Step 0 and MG17)
 skills:
+  - name: operating-instructions
+    required: true
+    used_by:
+      - Leader
+      - migration-workspace-state
+      - target-project-assistant
+      - migration-planning-gate
+      - migration-prep
+      - module-implementation
+      - module-node-review-fix
+      - migration-verification
+      - global-migration-phase
+      - completion-report
+    purpose: Shared baseline conduct layer loaded before migrator pre-flight, planning, implementation, review/fix, verification, integration, and reporting work.
   - name: android-project-analyst
     required: true
     phase: prerequisite

package/skills/android-to-kmp-migrator/output-contract.md

@@ -198,8 +198,8 @@ output_root = <output_dir or ~/.a2c_agents/migration>/android-to-kmp-migrator
 | `migration-prep/migration_prep.json` |
 | `module-implementation/ui/module_implementation_ui.json`, `module-implementation/logic/module_implementation_logic.json` + approved reviews |
 | **Target edits**: when planning tasks require file changes, both UI and logic implementation artifacts MUST have non-empty `changed_files[]` under `kmp_target_project_path` |
-| `migration_verification.json` with all required `check_ids` passed (including `target_files_exist` when `changed_files` non-empty) |
-| `module_completion_record.json` with `ui_restoration` and `logic_restoration` passed and `target_changed_files[]` listing module target paths |
+| `migration_verification.json` with all required `check_ids` passed (including `target_files_exist` when `changed_files` non-empty, and `analytics_restoration` passed or `skipped` with evidence) |
+| `module_completion_record.json` with `ui_restoration`, `logic_restoration`, and `analytics_restoration` passed (or analytics `skipped` with evidence) and `target_changed_files[]` listing module target paths |
 
 ### Package `M4` — All modules migrated
 
@@ -221,7 +221,7 @@ output_root = <output_dir or ~/.a2c_agents/migration>/android-to-kmp-migrator
 | Required paths |
 |---|
 | Package `M5` |
-| `global/node-results/global-migration-phase/align/post_integration_alignment.json` with `alignment_verdict: passed \| passed_with_assumptions` and `global_alignment_results.entry_points.verdict: passed \| passed_with_assumptions` |
+| `global/node-results/global-migration-phase/align/post_integration_alignment.json` with `alignment_verdict: passed \| passed_with_assumptions` and `global_alignment_results.entry_points.verdict: passed \| passed_with_assumptions` and `global_alignment_results.analytics.verdict: passed \| passed_with_assumptions \| not_applicable` |
 | `report/alignment_report.json` (includes entry point alignment verdict) |
 
 ### Package `V0` — kmp-test-validator entry (downstream)
@@ -306,6 +306,7 @@ Machine lookup: `migration_module_id` → `legacy_module_id`, `module_output_roo
   "target_changed_files": [{ "path": "", "owning_role": "migration-prep | module-implementation | module-node-review-fix", "mode": "ui | logic | fix | null" }],
   "ui_restoration": { "status": "passed | failed", "gaps": [] },
   "logic_restoration": { "status": "passed | failed", "gaps": [] },
+  "analytics_restoration": { "status": "passed | failed | skipped", "restored_count": 0, "total_count": 0, "gaps": [] },
   "upstream_match": { "module_representation_path": "", "matched_claims": [], "missing_claims": [] },
   "rerun_required": false,
   "evidence_paths": []
@@ -321,16 +322,19 @@ Machine lookup: `migration_module_id` → `legacy_module_id`, `module_output_roo
 - `ui_render` — static UI surface check (Compose structure/resources; no full render pipeline build)
 - `ui_restoration` — migrated UI coverage vs upstream `presentation_resource` + module representation
 - `logic_restoration` — migrated logic coverage vs upstream `behavior_logic` + module representation
+- `analytics_restoration` — legacy 埋点 inventory vs migrated KMP track/report calls and params; `skipped` only when module scope has no analytics with evidence
 
 **Forbidden**: `incremental_build`, `full_project_compile`, `gradle_assemble`.
 
+Runtime analytics **reporting** verification (event actually reaches SDK/report pipeline after build) is delegated to **`kmp-test-validator`** restoreability / business-testing — migrator performs static parity only.
+
 ### `global_system_integration.json`
 
-`kmp_target_project_path`, `target_edit_summary`, `assembly_order`, `ui_transition_edges[]`, `control_logic_handoffs[]`, `data_call_edges[]`, `entry_point_wiring[]` (Android entry → KMP shell wiring with `wiring_kind` and `status`), `shared_contracts_applied[]`, `integration_changed_files[]` (target glue paths only), evidence paths from analyst cross-module globals and per-module `presentation_resource` `entry_points[]`. Integrate mode MUST edit the target KMP project and wire app-shell entry points; module body changes belong in `module-implementation`.
+`kmp_target_project_path`, `target_edit_summary`, `assembly_order`, `ui_transition_edges[]`, `control_logic_handoffs[]`, `data_call_edges[]`, `entry_point_wiring[]` (Android entry → KMP shell wiring with `wiring_kind` and `status`), `analytics_sdk_wiring[]` (legacy analytics SDK/init → KMP facade/DI with `status`), `shared_contracts_applied[]`, `integration_changed_files[]` (target glue paths only), evidence paths from analyst cross-module globals and per-module `presentation_resource` `entry_points[]`. Integrate mode MUST edit the target KMP project and wire app-shell entry points and global analytics glue when required; module body changes belong in `module-implementation`.
 
 ### `post_integration_alignment.json` (analysis only — no target edits)
 
-`alignment_verdict`, `module_alignment_results[]`, `global_alignment_results` (including `entry_points.verdict`), `entry_point_alignment_results[]`, `omissions[]`, `poor_restoration[]`, `rerun_modules[]`, `rerun_global_integration` (true when entry point alignment fails), `comparison_evidence[]` (analyst path vs target path pairs). Entry point alignment MUST pass (`global_alignment_results.entry_points.verdict: passed | passed_with_assumptions`) for package **M6**.
+`alignment_verdict`, `module_alignment_results[]`, `global_alignment_results` (including `entry_points.verdict` and `analytics.verdict`), `entry_point_alignment_results[]`, `analytics_alignment_results[]`, `omissions[]`, `poor_restoration[]`, `rerun_modules[]`, `rerun_global_integration` (true when entry point or analytics SDK alignment fails), `comparison_evidence[]` (analyst path vs target path pairs). Entry point alignment MUST pass (`global_alignment_results.entry_points.verdict: passed | passed_with_assumptions`) and analytics alignment MUST pass or be `not_applicable` for package **M6**.
 
 ### `migration_planning_gate.json`
 
@@ -338,15 +342,56 @@ Combined `planning` (spec deltas, source-to-target map, tasks) and `dependency_p
 
 ### `migration_prep.json`
 
-Combined `presentation` (tokens, resources, routes) and `state_data` (state/models/API expectations) sections.
+Combined `presentation` (tokens, resources, routes) and `state_data` (state/models/API expectations, `analytics_expectations[]`) sections.
 
 ### `module_implementation_ui.json` / `module_implementation_logic.json`
 
-UI mode and logic mode outputs under `module-implementation/ui/` and `module-implementation/logic/` respectively. Each MUST record `kmp_target_project_path`, `target_edit_summary`, and `changed_files[]` listing every target KMP path created or modified in that invocation. Legacy Android paths are evidence only — implementation edits occur under `kmp_target_project_path`.
+UI mode and logic mode outputs under `module-implementation/ui/` and `module-implementation/logic/` respectively. Each MUST record `kmp_target_project_path`, `target_edit_summary`, and `changed_files[]` listing every target KMP path created or modified in that invocation. Logic mode MUST include `analytics_coverage[]` when legacy scope contains 埋点. Legacy Android paths are evidence only — implementation edits occur under `kmp_target_project_path`.
 
 ### `alignment_report.json`
 
-Human/agent-readable synthesis of align mode; includes `entry_point_alignment_results` summary; routes reruns to `migration_module_id` or `global-migration-phase integrate` when entry points or cross-module glue fail.
+Human/agent-readable synthesis of align mode; includes `entry_point_alignment_results` summary and `analytics_alignment_results` / `global_alignment_results.analytics` summary; routes reruns to `migration_module_id` or `global-migration-phase integrate` when entry points, analytics SDK, or cross-module glue fail.
+
+### `migration_report.json` — analytics handoff (for kmp-test-validator)
+
+When migration scope includes analytics, `migration_report.json` MUST aggregate:
+
+```json
+{
+  "analytics_restoration_summary": {
+    "total_legacy_events": 0,
+    "restored_events": 0,
+    "partial_events": 0,
+    "missing_events": 0,
+    "global_analytics_verdict": "passed | passed_with_assumptions | failed | not_applicable",
+    "per_module": [
+      {
+        "migration_module_id": "",
+        "verification_ref": "",
+        "status": "passed | failed | skipped",
+        "event_count": 0
+      }
+    ],
+    "event_catalog": [
+      {
+        "event_id": "",
+        "event_name": "",
+        "trigger": "",
+        "legacy_source_path": "",
+        "target_path": "",
+        "migration_module_id": "",
+        "status": "restored | partial | missing"
+      }
+    ]
+  },
+  "validation_inputs": {
+    "analytics_reporting_required": true,
+    "analytics_event_catalog_path": "report/migration_report.json#analytics_restoration_summary.event_catalog"
+  }
+}
+```
+
+`validation_inputs.analytics_reporting_required` is `true` when `total_legacy_events > 0`; `kmp-test-validator` MUST run analytics reporting verification during restoreability / business-testing.
 
 ---
 

package/skills/android-to-kmp-migrator/roles/completion-report.md

@@ -61,7 +61,7 @@ Shared return shape applies.
 
 - `completion_readiness.json`: machine-routable readiness artifact containing requirement coverage, migration invariants, module/global representation references when applicable, verification/review status, validation inputs readiness, rerun requests, and blockers.
 - `completion_readiness.md`: agent-readable readiness handoff containing coverage tables, invariant checks, incomplete markers, rerun routing, blockers, and whether representation/report gates may proceed.
-- `migration_report.json`: machine-routable final migration handoff containing migration scope, source/target paths, analyst_output_root, upstream_analyst_index, `handoff_gates` (`M0`–`M6`, `V0`), `handoff_package: V0`, module representations, global representation, `alignment_report` path, `global_system_integration` path, `target_changed_files[]` (deduplicated union of all module and global integrate target paths with `owning_role`), changed files by role, coverage summary, validation inputs for kmp-test-validator, `validation_deferred_to: kmp-test-validator`, limitations, blockers.
+- `migration_report.json`: machine-routable final migration handoff containing migration scope, source/target paths, analyst_output_root, upstream_analyst_index, `handoff_gates` (`M0`–`M6`, `V0`), `handoff_package: V0`, module representations, global representation, `alignment_report` path, `global_system_integration` path, `target_changed_files[]` (deduplicated union of all module and global integrate target paths with `owning_role`), `analytics_restoration_summary` (aggregated 埋点 catalog for validator), changed files by role, coverage summary, validation inputs for kmp-test-validator (incl. `analytics_reporting_required`), `validation_deferred_to: kmp-test-validator`, limitations, blockers.
 - `migration_report.md`: agent-readable final migration report for `kmp-test-validator` and follow-up agents, preserving exact artifact paths, changed-file ownership, validation handoff context, limitations, and blockers.
 - Report mode success signals Leader to **mandatorily invoke** `kmp-test-validator` — migration is incomplete without validator dispatch.