@code-migration/wow-migrator 0.2.4 → 0.2.6

package/skills/android-to-kmp-migrator/roles/global-migration-phase.md

@@ -28,12 +28,14 @@ You are the `global-migration-phase` node subagent. Your job is **target KMP pro
 **Integrate mode**:
 - Target KMP glue files edited/created to wire `ui_transition_edges`, `control_logic_handoffs`, `data_call_edges` from analyst cross-module globals and per-module migration representations.
 - **Entry point wiring complete**: KMP app shell, launcher/root navigation, startup graph, deep-link handlers, and platform entry wrappers match Legacy Android entry evidence from analyst `presentation_resource` `entry_points[]`, manifest launcher intent, and TPA `entry_point_anchors[]`.
+- **Analytics SDK wiring complete** when analyst evidence shows analytics dependencies: global analytics init, DI bindings, and shared track/report facade wired in target glue (`analytics_sdk_wiring[]`).
 - `global_system_integration.json` / `.md` with `kmp_target_project_path`, `integration_changed_files`, `target_edit_summary`, wired edges, `entry_point_wiring[]`, shared contracts applied, evidence paths, blockers.
 - `integration_changed_files` limited to glue under `kmp_target_project_path`; module body gaps routed via `rerun_requests` to `module-implementation` or `migration-prep`.
 
 **Align mode**:
 - True comparison: analyst artifacts vs **migrated target KMP files** on disk; `alignment_verdict` explicit.
 - **Entry point alignment verified**: each Legacy Android entry point has a resolved KMP counterpart; launch flow, root/start destination, deep links, and Application/startup hooks are compared with `entry_point_alignment_results[]` and folded into `global_alignment_results.entry_points`.
+- **Analytics alignment verified**: global analytics SDK init, DI, and shared track/report facade compared with legacy `project_architecture` analytics deps and per-module `analytics_restoration_summary`; results in `analytics_alignment_results[]` and `global_alignment_results.analytics`.
 - `comparison_evidence[]` pairs analyst claim paths with resolved target file paths under `kmp_target_project_path`.
 - Entry point mismatches → `rerun_global_integration: true` (integrate must rewire app shell); module-scoped entry screens → `rerun_modules[]`.
 - `rerun_modules[]` and `rerun_global_integration` when omissions found.
@@ -91,6 +93,17 @@ You are the `global-migration-phase` node subagent. Your job is **target KMP pro
       "evidence_paths": []
     }
   ],
+  "analytics_sdk_wiring": [
+    {
+      "legacy_sdk": "",
+      "legacy_init_path": "",
+      "target_init_path": "",
+      "target_facade_symbol": "",
+      "di_binding_path": "",
+      "status": "wired | partial | deferred | not_applicable",
+      "evidence_paths": []
+    }
+  ],
   "integration_changed_files": [],
   "rerun_requests": [],
   "blocking_gaps": []
@@ -116,6 +129,13 @@ You are the `global-migration-phase` node subagent. Your job is **target KMP pro
       "aligned_count": 0,
       "total_count": 0,
       "gaps": []
+    },
+    "analytics": {
+      "verdict": "passed | passed_with_assumptions | failed | not_applicable",
+      "restored_event_count": 0,
+      "total_event_count": 0,
+      "sdk_wired": true,
+      "gaps": []
     }
   },
   "entry_point_alignment_results": [
@@ -134,6 +154,20 @@ You are the `global-migration-phase` node subagent. Your job is **target KMP pro
       "gap": ""
     }
   ],
+  "analytics_alignment_results": [
+    {
+      "event_id": "",
+      "event_name": "",
+      "legacy_source_path": "",
+      "migration_module_id": "",
+      "target_path": "",
+      "target_symbol": "",
+      "alignment_status": "aligned | partial | missing",
+      "params_match": true,
+      "evidence_paths": [],
+      "gap": ""
+    }
+  ],
   "omissions": [],
   "poor_restoration": [],
   "rerun_modules": [],
@@ -168,6 +202,9 @@ Edit only integration glue in the KMP target:
   - Deep links / intent filters / notification taps → KMP deep-link handlers and route arguments.
   - Cross-platform entry: common `App()` composable and platform wrappers must route to the same logical entry as Android.
   - Consume TPA `entry_point_anchors[]` and per-module `presentation_resource` `entry_points[]`; record every wired pair in `entry_point_wiring[]`.
+- **Analytics SDK / global 埋点 glue (when analyst shows analytics deps)**:
+  - Wire shared analytics init (Application/startup), DI module bindings, and common `track`/`report` facade used by module implementations.
+  - Record every wired SDK/init/facade pair in `analytics_sdk_wiring[]`.
 
 Do **not** edit module-internal screens, repositories, or ViewModels — those are `module-implementation` scope. If a handoff requires module body changes, emit `rerun_requests` for the owning `migration_module_id`.
 
@@ -185,6 +222,21 @@ Read-only verification after integrate. For each Legacy Android entry in analyst
    - `failed` — any required launcher/root/deep-link mismatch; set `rerun_global_integration: true`.
 6. Entry point failures block package **M6** until integrate rewires app shell.
 
+## Analytics Alignment Rules (align mode)
+
+Read-only verification after integrate. Aggregate per-module `migration_verification` → `analytics_restoration_summary` and legacy analyst analytics evidence:
+
+1. Resolve legacy 埋点 inventory from `behavior_logic` side_effects and `project_architecture` analytics dependencies.
+2. Resolve KMP track/report calls and `analytics_sdk_wiring[]` from integrate output and module `analytics_coverage[]`.
+3. Compare event name, trigger, param keys, and SDK init path for each event.
+4. Record `analytics_alignment_results[]` with `alignment_status` and evidence path pairs in `comparison_evidence[]`.
+5. Set `global_alignment_results.analytics.verdict`:
+   - `not_applicable` — no analytics in migration scope with evidence.
+   - `passed` — all required events restored and SDK wired.
+   - `passed_with_assumptions` — documented deferrals only.
+   - `failed` — missing events or SDK wiring; add to `poor_restoration[]` and route `rerun_modules[]` or `rerun_global_integration`.
+6. Analytics failures block package **M6** when legacy scope had analytics and restoration is incomplete.
+
 ## Inline Persona for Teammate
 
 ```text
@@ -198,6 +250,7 @@ hooks in androidMain/iosMain). Do NOT mix patterns.
 INTEGRATE — EDIT THE TARGET KMP PROJECT:
 - Wire cross-module UI transitions, control logic handoffs, and data calls inside kmp_target_project_path.
 - Wire entry points: Android launcher/Application/root nav/deep links → KMP app shell (entry_point_wiring[]).
+- Wire analytics SDK/init/DI/facade when legacy uses analytics (analytics_sdk_wiring[]).
 - integration_changed_files = every target glue file you created or modified.
 - Glue only: nav, DI, shared contracts, app shell, entry wiring. No module body reimplementation.
 - Legacy Android and analyst artifacts are read-only evidence.
@@ -205,6 +258,7 @@ INTEGRATE — EDIT THE TARGET KMP PROJECT:
 ALIGN — READ-ONLY:
 - Compare analyst evidence vs migrated target KMP files on disk.
 - Verify entry_point_alignment_results[] vs Android entry_points + manifest + entry_point_wiring[].
+- Verify analytics_alignment_results[] vs per-module analytics_restoration_summary + analytics_sdk_wiring[].
 - Write post_integration_alignment.* and alignment_report under report_dir.
 - Entry point mismatch → rerun_global_integration. NO target edits. NO full project build.
 

package/skills/android-to-kmp-migrator/roles/migration-prep.md

@@ -10,7 +10,7 @@ You are the `migration-prep` node subagent. You merge **presentation integration
 
 - `migration_prep.json` and `migration_prep.md` written under `output_dir`.
 - **Presentation section**: token mappings, resource mapping, route mapping, UI handoff, presentation gaps.
-- **State/data section**: state mappings, model mappings, API contract expectations, logic handoff. State holder expectations MUST follow the run's `design_mode` (default `mvi`): `mvi` → sealed `State`/`Action` + state-machine handoff (`references/kmp-mvi-flowredux.md`); `mvvm` → immutable `UiState` + `ViewModel` event-method handoff (`references/kmp-mvvm.md`). All scaffold and contracts target a KMP project per `references/kmp-expert.md` base conventions — place shared tokens/resources/models/routes in `commonMain`, reserve `androidMain`/`iosMain` for platform actuals, and prefer the multiplatform stack (Ktor, kotlinx-serialization, kotlinx-datetime) over Android-only types.
+- **State/data section**: state mappings, model mappings, API contract expectations, logic handoff, `analytics_expectations[]`. State holder expectations MUST follow the run's `design_mode` (default `mvi`): `mvi` → sealed `State`/`Action` + state-machine handoff (`references/kmp-mvi-flowredux.md`); `mvvm` → immutable `UiState` + `ViewModel` event-method handoff (`references/kmp-mvvm.md`). All scaffold and contracts target a KMP project per `references/kmp-expert.md` base conventions — place shared tokens/resources/models/routes in `commonMain`, reserve `androidMain`/`iosMain` for platform actuals, and prefer the multiplatform stack (Ktor, kotlinx-serialization, kotlinx-datetime) over Android-only types.
 - Changed files recorded; cross-module impacts noted.
 - No full UI layouts or repository/API behavior.
 
@@ -53,7 +53,18 @@ When planning allows prep-time file changes, you MAY create or update target sca
     "state_mappings": [],
     "model_mappings": [],
     "api_contract_expectations": [],
-    "logic_handoff": []
+    "logic_handoff": [],
+    "analytics_expectations": [
+      {
+        "event_id": "",
+        "event_name": "",
+        "trigger": "",
+        "params": [],
+        "legacy_source_path": "",
+        "expected_placement": "onActionEffect | viewModel_side_effect | composable_launchedEffect | screen_enter | lifecycle | global_sdk_init",
+        "sdk_hint": ""
+      }
+    ]
   },
   "changed_files": [],
   "blocking_gaps": []
@@ -70,7 +81,8 @@ See [output-contract.md](../output-contract.md). Artifact basename: `migration_p
 ROLE: migration-prep node. Merge presentation + state/data prep in ONE invocation.
 
 PRESENTATION: tokens, resources, media, routes, UI handoff.
-STATE/DATA: state holders, models, mappers, API expectations, logic handoff.
+STATE/DATA: state holders, models, mappers, API expectations, logic handoff, analytics_expectations
+(legacy 埋点 inventory from behavior_logic side_effects + project_architecture analytics deps).
 State holder shape follows design_mode (default mvi): mvi → sealed State/Action + state machine
 (references/kmp-mvi-flowredux.md); mvvm → UiState + ViewModel methods (references/kmp-mvvm.md).
 Target is a KMP project per references/kmp-expert.md: scaffold in commonMain, platform actuals only in

package/skills/android-to-kmp-migrator/roles/migration-verification.md

@@ -15,6 +15,7 @@ You are the `migration-verification` node subagent. You verify one `migration_mo
 - `ui_render`
 - `ui_restoration`
 - `logic_restoration`
+- `analytics_restoration`
 
 ## Forbidden Check IDs
 
@@ -29,6 +30,7 @@ If a dispatch contract includes forbidden check ids, return `blocked` and cite [
 - `migration_verification.json` and `migration_verification.md` written under `output_dir`.
 - Every required `check_id` has `passed | failed | blocked`.
 - `ui_restoration` and `logic_restoration` cite upstream analyst paths and list gaps explicitly.
+- `analytics_restoration` inventories Legacy Android 埋点 from upstream `behavior_logic` (user-action/lifecycle `side_effects`, screen-exposure hooks) and `project_architecture` (`analytics` dependencies), compares each event to migrated KMP track/report calls in target files, and records missing or mismatched events in `analytics_restoration_summary`.
 - `syntax_check` validates changed Kotlin/files statically without assembling the whole project.
 - `target_files_exist` confirms every aggregated module `changed_files[]` path exists on disk under `kmp_target_project_path`.
 - Failures route to owning roles per `SKILL.md`; Leader writes `module_completion_record.json` only when all checks pass.
@@ -58,7 +60,7 @@ If a dispatch contract includes forbidden check ids, return `blocked` and cite [
   "upstream_module_representation_path": "",
   "check_results": [
     {
-      "check_id": "target_files_exist | source_set | syntax_check | api_contract | ui_render | ui_restoration | logic_restoration",
+      "check_id": "target_files_exist | source_set | syntax_check | api_contract | ui_render | ui_restoration | logic_restoration | analytics_restoration",
       "status": "passed | failed | blocked",
       "evidence": [],
       "failures": [],
@@ -68,6 +70,28 @@ If a dispatch contract includes forbidden check ids, return `blocked` and cite [
   ],
   "ui_restoration_summary": { "status": "passed | failed", "gaps": [] },
   "logic_restoration_summary": { "status": "passed | failed", "gaps": [] },
+  "analytics_restoration_summary": {
+    "status": "passed | failed | skipped",
+    "legacy_event_count": 0,
+    "restored_count": 0,
+    "partial_count": 0,
+    "missing_count": 0,
+    "events": [
+      {
+        "event_id": "",
+        "event_name": "",
+        "trigger": "",
+        "legacy_source_path": "",
+        "target_path": "",
+        "target_symbol": "",
+        "params_match": true,
+        "status": "restored | partial | missing | unknown",
+        "gap": ""
+      }
+    ],
+    "sdk_wiring": { "legacy_sdk": "", "target_sdk_path": "", "status": "wired | partial | missing | not_applicable" },
+    "gaps": []
+  },
   "log_files": [],
   "blocking_gaps": []
 }
@@ -79,8 +103,8 @@ Write only under `output_dir = <output_root>/modules/<migration_module_id>/node-
 
 ## Output Files And Contents
 
-- `migration_verification.json`: check results, restoration summaries, routing, log paths.
-- `migration_verification.md`: agent-readable verification handoff; must state build is deferred to kmp-test-validator.
+- `migration_verification.json`: check results, restoration summaries, analytics inventory parity, routing, log paths.
+- `migration_verification.md`: agent-readable verification handoff; must state build and runtime analytics reporting are deferred to kmp-test-validator.
 - Optional static analysis logs under `output_dir/logs/` (listed in `log_files`).
 
 ## Inline Persona for Teammate
@@ -89,9 +113,20 @@ Write only under `output_dir = <output_root>/modules/<migration_module_id>/node-
 ROLE: migration-verification node.
 
 Run module-scoped checks ONLY: target_files_exist, source_set, syntax_check, api_contract,
-ui_render, ui_restoration, logic_restoration. Compare UI/logic to upstream analyst module_representation.
-
-DO NOT run incremental_build or full project compile — kmp-test-validator owns that.
+ui_render, ui_restoration, logic_restoration, analytics_restoration. Compare UI/logic/埋点 to
+upstream analyst module_representation, behavior_logic, and project_architecture analytics deps.
+
+ANALYTICS_RESTORATION:
+1. Build legacy 埋点 inventory from behavior_logic user_actions/lifecycle side_effects and
+   project_architecture analytics SDK dependencies.
+2. For each legacy event, locate equivalent KMP track/report call in module_implementation_logic
+   changed_files or shared analytics wrapper under kmp_target_project_path.
+3. Compare event name, trigger point, and param keys; mark restored | partial | missing.
+4. Record sdk_wiring when global analytics init/DI is required.
+5. status skipped only when inventory is empty with evidence (no analytics in module scope).
+
+DO NOT run incremental_build or full project compile — kmp-test-validator owns build and
+runtime analytics reporting verification.
 
 INPUTS: migration_module_id, changed_files, planning/TPA/UI/logic outputs,
 upstream_module_representation_path, analyst dimension paths, target path, output_dir.

package/skills/android-to-kmp-migrator/roles/module-implementation.md

@@ -44,8 +44,8 @@ Both modes follow `references/kmp-expert.md` for base KMP/CMP conventions. If `d
 - UI binds to TPA anchors and planning `source_to_target_map`; no business logic beyond compile-safe UI state shells.
 
 **Logic mode**:
-- Target KMP files edited/created for repositories, use cases, ViewModels/state holders, mappers, API clients, and platform `expect`/`actual` boundaries.
-- `module_implementation_logic.json` / `.md` with `kmp_target_project_path`, `changed_files`, `target_edit_summary`, data flows, API integrations, logic coverage, platform boundaries.
+- Target KMP files edited/created for repositories, use cases, ViewModels/state holders, mappers, API clients, platform `expect`/`actual` boundaries, and **analytics/埋点 side effects** (track/report calls, screen-exposure hooks) mapped from upstream `behavior_logic`.
+- `module_implementation_logic.json` / `.md` with `kmp_target_project_path`, `changed_files`, `target_edit_summary`, data flows, API integrations, logic coverage, `analytics_coverage[]` (legacy event → target track call), platform boundaries.
 - Binds to approved UI binding surfaces from UI mode; no Android-only APIs in `commonMain`.
 - No TODO placeholders in production paths.
 
@@ -99,6 +99,19 @@ Both modes follow `references/kmp-expert.md` for base KMP/CMP conventions. If `d
   "data_flows": [],
   "api_integrations": [],
   "logic_coverage": [],
+  "analytics_coverage": [
+    {
+      "legacy_event_id": "",
+      "event_name": "",
+      "trigger": "",
+      "legacy_source_path": "",
+      "target_path": "",
+      "target_symbol": "",
+      "params_mapped": [],
+      "placement": "onActionEffect | viewModel_side_effect | composable_launchedEffect | screen_enter | lifecycle | other",
+      "status": "restored | partial | deferred"
+    }
+  ],
   "diagnostics": [],
   "blocking_gaps": []
 }
@@ -113,8 +126,8 @@ Populate UI fields in `ui` mode; logic fields in `logic` mode. `changed_files` a
 - `module_implementation_ui.md` — agent-readable UI migration handoff: legacy screen/section → target composable/resource path table, edited files list, binding surfaces, known fidelity gaps, next logic dependencies.
 
 **Logic mode** under `<module_root>/node-results/module-implementation/logic/`:
-- `module_implementation_logic.json` — machine implementation record: `kmp_target_project_path`, `target_edit_summary`, `changed_files` with logic placement, data flows, API integrations, logic coverage vs upstream `behavior_logic`, platform boundary decisions, blockers.
-- `module_implementation_logic.md` — agent-readable logic migration handoff: legacy behavior/use-case → target repository/ViewModel/state path table, edited files list, platform splits, unresolved gaps.
+- `module_implementation_logic.json` — machine implementation record: `kmp_target_project_path`, `target_edit_summary`, `changed_files` with logic placement, data flows, API integrations, logic coverage vs upstream `behavior_logic`, `analytics_coverage[]` vs legacy 埋点, platform boundary decisions, blockers.
+- `module_implementation_logic.md` — agent-readable logic migration handoff: legacy behavior/use-case → target repository/ViewModel/state path table, **legacy 埋点 → target track/report table**, edited files list, platform splits, unresolved gaps.
 
 ## Target Edit Rules By Mode
 
@@ -130,6 +143,7 @@ Populate UI fields in `ui` mode; logic fields in `logic` mode. `changed_files` a
 - ViewModels, presenters, or state holders bound to approved UI surfaces.
 - Repositories, data sources, mappers, DTO/domain models.
 - API client integrations and error/loading state propagation.
+- **Analytics/埋点**: restore legacy track/report calls at the same behavioral trigger points — e.g. MVI `onActionEffect` / `onEnter`, MVVM ViewModel side-effect methods after state transitions, screen-enter `LaunchedEffect`, lifecycle hooks. Reuse shared analytics wrapper from prep when present.
 - `expect`/`actual` declarations and platform-specific implementations in `androidMain`/`iosMain` when required.
 
 ## Inline Persona for Teammate
@@ -152,6 +166,7 @@ UI MODE:
 
 LOGIC MODE:
 - Port behavior from upstream behavior_logic evidence into target repositories/ViewModels/state/platform code.
+- Restore legacy 埋点 at matching triggers; record every event in analytics_coverage[].
 - Bind only to approved UI binding surfaces from prior UI mode output.
 - changed_files = every target file you created or modified.
 

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

@@ -94,11 +94,11 @@ graph TD
 |---|---|---|
 | 5a | TPA `module_anchors` | Package **M2** per module |
 | 5b | `migration-planning-gate` | Planning + dep/platform in one pass |
-| 5c | `migration-prep` | Presentation + state/data in one pass |
+| 5c | `migration-prep` | Presentation + state/data + `analytics_expectations[]` |
 | 5d | `module-node-review-fix` | After prep if file-changing |
 | 5e | `module-implementation` `ui` | Edit/create target KMP UI files; then review/fix |
-| 5f | `module-implementation` `logic` | Edit/create target KMP logic files after UI approved; then review/fix |
-| 5g | `migration-verification` | Static + restoration; **no full build** |
+| 5f | `module-implementation` `logic` | Edit/create target KMP logic + **埋点** restoration; then review/fix |
+| 5g | `migration-verification` | Static + restoration incl. **analytics_restoration** (埋点 parity); **no full build** |
 | 5h | Leader | `module_completion_record.json` |
 | 5i | `completion-report` `readiness` + module representation | Package **M3** |
 
@@ -109,16 +109,16 @@ Repeat until package **M4**.
 ### 6a Integrate
 
 - **Role**: `global-migration-phase` `mode: integrate`
-- **Action**: edit target KMP cross-module glue (nav, DI, shared contracts) and **wire app-shell entry points** (launcher, Application/startup, root NavHost start destination, deep links) under `kmp_target_project_path`, using TPA `entry_point_anchors[]` and analyst `presentation_resource` `entry_points[]`
-- **Output**: `global-migration-phase/integrate/global_system_integration.*` with `integration_changed_files[]` and `entry_point_wiring[]`
+- **Action**: edit target KMP cross-module glue (nav, DI, shared contracts), **wire app-shell entry points** (launcher, Application/startup, root NavHost start destination, deep links), and **analytics SDK/init/facade** when legacy uses analytics, under `kmp_target_project_path`, using TPA `entry_point_anchors[]` and analyst `presentation_resource` `entry_points[]`
+- **Output**: `global-migration-phase/integrate/global_system_integration.*` with `integration_changed_files[]`, `entry_point_wiring[]`, and `analytics_sdk_wiring[]`
 - **Gate**: package **M5**
 
 ### 6b Align
 
 - **Role**: `global-migration-phase` `mode: align`
-- **Action**: read-only comparison including **entry point alignment** — verify each Android entry resolves to the correct KMP shell path, launch flow, and deep-link route
-- **Output**: `global-migration-phase/align/post_integration_alignment.*` with `entry_point_alignment_results[]` and `global_alignment_results.entry_points`, plus `report/alignment_report.*`
-- **Gate**: package **M6**; entry point or cross-module mismatch → `rerun_global_integration` or module loop
+- **Action**: read-only comparison including **entry point alignment** and **analytics alignment** — verify each Android entry resolves to the correct KMP shell path; verify legacy 埋点 inventory matches migrated track/report calls and global analytics SDK wiring
+- **Output**: `global-migration-phase/align/post_integration_alignment.*` with `entry_point_alignment_results[]`, `analytics_alignment_results[]`, `global_alignment_results.entry_points`, `global_alignment_results.analytics`, plus `report/alignment_report.*`
+- **Gate**: package **M6**; entry point, analytics SDK, or cross-module mismatch → `rerun_global_integration` or module loop
 
 ## Step 7 — Report + mandatory validator handoff (MG17)
 
@@ -140,4 +140,5 @@ Any target question → TPA `mode: consult` (append `consultation_log`).
 - Dispatch only role IDs from `SKILL.md`.
 - Mode rules: `ui` before `logic`; `integrate` before `align`; `review`/`fix` separate.
 - `migration-verification` never runs `incremental_build`.
+- Per-module and global **analytics_restoration** (埋点) parity verified before **M3** / **M6**; runtime analytics **reporting** deferred to `kmp-test-validator`.
 - `handoff_gates` match output-contract.

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

@@ -11,27 +11,27 @@ roles:
   - id: validation-workspace-state
     kind: ai_agent
     purpose: Validation ledger — node status, handoff gates VG0–VG5, supplement/remediation cycle counts, stale inputs, blockers. No audit, build, fix, or verdict.
-    skills: []
+    skills: [operating-instructions]
     tools: [git]
   - id: validation-fidelity-gate
     kind: ai_agent
     purpose: Fidelity gate — mode trust (pre-build Android/SPEC vs KMP) or restoreability (post-build module/function audit, migrator supplement routing). Read-only.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg, git]
   - id: validation-code-gate
     kind: ai_agent
     purpose: Code gate — mode build (3-scenario compile/preview) or fix (edit target KMP project to resolve build/preview failures). Only fix mode edits production code.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg, git]
   - id: validation-business-testing
     kind: ai_agent
     purpose: Optional business testing — behavioral submodule (user test cases) and ui_comparison submodule (Figma) after VG3.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg, git]
   - id: validation-report
     kind: ai_agent
     purpose: Final verdict synthesis — passed/failed/blocked from verified fidelity, code-gate, business-testing, and fix evidence.
-    skills: []
+    skills: [operating-instructions]
     tools: [git]
 ---
 
@@ -43,6 +43,8 @@ The team is a **serial pipeline with two controller loops**: code-gate fix remed
 
 **Canonical file recording system**: [output-contract.md](output-contract.md) defines paths, migrator `V0` inputs, handoff gates `VG0`–`VG5`, and mode contracts. The Leader MUST read `output-contract.md` before the first dispatch.
 
+**Baseline operating instructions**: [../operating-instructions/SKILL.md](../operating-instructions/SKILL.md) is the shared conduct layer for this skill and every dispatched validator role. The Leader MUST read it before pre-flight and include it in each role dispatch as baseline instructions; role files, workflow gates, and output contracts add to it, not replace it.
+
 ## Protocol Summary
 
 0. **Pre-flight** — [dependencies.yaml](dependencies.yaml); verify migrator `V0`; lock output root.

package/skills/kmp-test-validator/dependencies.yaml

@@ -3,6 +3,16 @@
 # Leader reads this in Workflow Step 0 → run_manifest.json dependency_preflight.
 
 skills:
+  - name: operating-instructions
+    required: true
+    used_by:
+      - Leader
+      - validation-workspace-state
+      - validation-fidelity-gate
+      - validation-code-gate
+      - validation-business-testing
+      - validation-report
+    purpose: Shared baseline conduct layer loaded before validator pre-flight, fidelity/code gates, optional business testing, remediation, and final reporting work.
   - name: ui-reconstruction-score
     required: false
     used_by:

package/skills/kmp-test-validator/output-contract.md

@@ -116,8 +116,8 @@ output_root = <output_dir or ~/.a2c_agents/validation>/kmp-test-validator
 | `VG0` | Migrator `V0` verified; `upstream_migration_index.json` written |
 | `VG1` | `fidelity-gate/trust/validation_fidelity_trust.json` — no unresolved `test_trust_blockers` |
 | `VG2` | `code-gate/build/validation_code_build.json` — `build.status: passed`; preview passed or justified `skipped` |
-| `VG3` | `fidelity-gate/restoreability/validation_restoreability_audit.json` — `restoreability_verdict: passed` |
-| `VG4` | `business-testing/validation_business_testing.json` — submodule outcomes or explicit `skipped` |
+| `VG3` | `fidelity-gate/restoreability/validation_restoreability_audit.json` — `restoreability_verdict: passed`; when `analytics_reporting_required`, `analytics_reporting_summary.verdict: passed | not_applicable` |
+| `VG4` | `business-testing/validation_business_testing.json` — submodule outcomes or explicit `skipped`; `analytics_reporting` MUST run when migrator requires it |
 | `VG5` | `report/kmp_validation_report.json` issued |
 
 **Fail closed**: `passed` requires `VG2` + `VG3`; enabled `VG4` submodules must have no unresolved failures.
@@ -216,7 +216,7 @@ The validator maintains a durable bug-fix experience ledger for compile/preview
 
 ### `validation_restoreability_audit.json` (mode `restoreability`)
 
-`migrator_supplement_request` when new migration work required. Controller invokes `android-to-kmp-migrator` — not code-gate `fix`.
+`migrator_supplement_request` when new migration work required. When `migration_report.validation_inputs.analytics_reporting_required`, MUST include `analytics_reporting_results[]` and `analytics_reporting_summary` — failed analytics reporting blocks `restoreability_verdict: passed`. Controller invokes `android-to-kmp-migrator` — not code-gate `fix`.
 
 ### `validation_business_testing.json`
 
@@ -224,11 +224,14 @@ The validator maintains a durable bug-fix experience ledger for compile/preview
 {
   "submodules": {
     "behavioral": { "enabled": false, "status": "passed | failed | skipped | blocked" },
-    "ui_comparison": { "enabled": false, "status": "passed | failed | skipped | blocked" }
+    "ui_comparison": { "enabled": false, "status": "passed | failed | skipped | blocked" },
+    "analytics_reporting": { "enabled": false, "status": "passed | failed | skipped | blocked" }
   }
 }
 ```
 
+`analytics_reporting` is **enabled** when migrator `validation_inputs.analytics_reporting_required` is true — not optional skip when legacy scope had 埋点.
+
 ---
 
 ## Leader Obligations

package/skills/kmp-test-validator/roles/validation-business-testing.md

@@ -12,14 +12,15 @@ You are the `validation-business-testing` node subagent. You own optional post-`
 |---|---|---|
 | `behavioral` | `validation_requirements`, test cases, acceptance criteria | Decompose Android-anchored cases; execute via trusted test commands |
 | `ui_comparison` | `figma_refs` (file key, node IDs, or exported assets) | Compare implementation screenshots vs design (e.g. `ui-reconstruction-score` when available) |
+| `analytics_reporting` | `migration_report.json` → `validation_inputs.analytics_reporting_required: true` | Verify legacy 埋点 events fire and reach SDK/report pipeline on key user flows post-build |
 
-When neither input exists: both submodules `enabled: false`, `status: skipped`, reason `no_business_testing_inputs`.
+When neither behavioral/ui_comparison inputs exist and analytics_reporting is not required: all submodules `enabled: false`, `status: skipped`, reason `no_business_testing_inputs`.
 
 ## Success Criteria
 
 - `validation_business_testing.json` and `.md` under `output_dir`.
 - Submodules run only after `VG2` and `VG3` are true.
-- Behavioral expectations anchored to Android/SPEC; UI comparison anchored to Figma refs.
+- Behavioral expectations anchored to Android/SPEC; UI comparison anchored to Figma refs; **analytics_reporting** anchored to `migration_report.json` → `analytics_restoration_summary.event_catalog`.
 - Failures routed to `validation-code-gate` mode `fix` when target-code fixable.
 - Logs under `logs_dir/business-testing/` and `logs_dir/ui-comparison/` when run.
 
@@ -58,6 +59,14 @@ When neither input exists: both submodules `enabled: false`, `status: skipped`,
       "comparison_results": [],
       "score_report_path": "",
       "log_files": []
+    },
+    "analytics_reporting": {
+      "enabled": false,
+      "status": "passed | failed | skipped | blocked",
+      "event_catalog_ref": "",
+      "flow_results": [],
+      "reporting_log_path": "",
+      "log_files": []
     }
   },
   "changed_files": [],
@@ -73,7 +82,10 @@ Shared return shape applies. `changed_files` lists only test files created in ta
 ```text
 ROLE: validation-business-testing node.
 
-Optional business verification after VG3. Enable behavioral when user test cases exist. Enable ui_comparison when Figma refs exist. Route failures to validation-code-gate fix mode.
+Optional business verification after VG3. Enable behavioral when user test cases exist.
+Enable ui_comparison when Figma refs exist. Enable analytics_reporting when migrator sets
+analytics_reporting_required — exercise key flows and confirm 埋点 reach SDK/report pipeline.
+Route failures to validation-code-gate fix mode.
 
 INPUTS: kmp_target_project_path, validation_fidelity_trust_path, validation_code_build_path, validation_restoreability_audit_path, validation_requirements, figma_refs, migration_report_path, output_dir, logs_dir.
 

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

@@ -25,7 +25,8 @@ You are the `validation-fidelity-gate` node subagent. You merge the migration in
 ### 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.
+- Comparison uses analyst globals, migrator completion records, alignment artifacts, built target evidence, and **`migration_report.json` → `analytics_restoration_summary`** when `validation_inputs.analytics_reporting_required` is true.
+- **Analytics reporting verification**: for each event in `event_catalog`, confirm KMP target wires track/report at the documented trigger and SDK init path is reachable post-build; record `analytics_reporting_results[]` with `report_path_reachable` and `flow_verified` status.
 - Missing modules/functions emit `migrator_supplement_request` — never route to code-gate `fix` mode deletes.
 
 ## Boundary
@@ -82,6 +83,27 @@ You are the `validation-fidelity-gate` node subagent. You merge the migration in
   "missing_modules": [],
   "missing_functions": [],
   "poor_restoration": [],
+  "analytics_reporting_results": [
+    {
+      "event_id": "",
+      "event_name": "",
+      "migration_module_id": "",
+      "legacy_source_path": "",
+      "target_path": "",
+      "static_restored": true,
+      "report_path_reachable": true,
+      "flow_verified": true,
+      "status": "passed | failed | blocked",
+      "gap": ""
+    }
+  ],
+  "analytics_reporting_summary": {
+    "required": false,
+    "total_events": 0,
+    "passed_count": 0,
+    "failed_count": 0,
+    "verdict": "passed | failed | not_applicable"
+  },
   "migrator_supplement_request": {
     "required": false,
     "modules_to_supplement": [],
@@ -106,7 +128,10 @@ Shared return shape applies.
 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.
+restoreability: after VG2, re-verify modules/functions vs analyst+migrator evidence; when
+migration_report.validation_inputs.analytics_reporting_required, verify each 埋点 in event_catalog
+reaches the analytics SDK/report pipeline post-build (analytics_reporting_results[]); 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.
 

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

@@ -52,7 +52,7 @@ Initialize ledger with `handoff_gates` VG0–VG5; track `fix_cycles` and `migrat
 
 - **Executor**: `validation-fidelity-gate` mode `restoreability`
 - **Prerequisite**: `VG2`
-- **Output**: `fidelity-gate/restoreability/validation_restoreability_audit.*`
+- **Output**: `fidelity-gate/restoreability/validation_restoreability_audit.*` (incl. `analytics_reporting_results[]` when migrator requires analytics reporting)
 - **On gaps**: migrator supplement loop (max 3) → refresh upstream → rerun trust/build as scoped
 - **Gate**: `VG3`
 
@@ -60,7 +60,7 @@ Initialize ledger with `handoff_gates` VG0–VG5; track `fix_cycles` and `migrat
 
 - **Executor**: `validation-business-testing`
 - **Prerequisite**: `VG3`
-- **Submodules**: `behavioral` (user test cases), `ui_comparison` (Figma refs)
+- **Submodules**: `behavioral` (user test cases), `ui_comparison` (Figma refs), `analytics_reporting` (migrator `analytics_reporting_required` — verify 埋点 reporting on key flows)
 - **Output**: `business-testing/validation_business_testing.*`
 - **Gate**: `VG4` or explicit skip
 

package/skills/migration-task-adapter/SKILL.md

@@ -11,17 +11,17 @@ roles:
   - id: task-route-orchestrator
     kind: ai_agent
     purpose: Task route and orchestration — mode route (classify intent, paths, downstream sequence) or orchestrate (dispatch contracts, observed downstream outputs). No downstream role work.
-    skills: []
+    skills: [operating-instructions]
     tools: [rg, git]
   - id: adapter-workspace-state
     kind: ai_agent
     purpose: Workspace ledger — stage inspections, intermediate asset records, path compliance, freshness, reruns. No routing, orchestration, or final verdict.
-    skills: []
+    skills: [operating-instructions]
     tools: [git]
   - id: adapter-report
     kind: ai_agent
     purpose: Final adapter report from verified route, orchestration, workspace, stage, and downstream evidence. No new routing or workflow execution.
-    skills: []
+    skills: [operating-instructions]
     tools: [git]
 ---
 
@@ -31,6 +31,8 @@ Front-door adapter for the KMP Migration Toolkit. It does not replace `android-p
 
 **Canonical file recording system**: [output-contract.md](output-contract.md) defines every adapter output path, required content, write order, and **handoff package gates** (`A0`–`A6`). The Leader MUST read `output-contract.md` before the first dispatch and MUST NOT claim completion without updating `handoff_gates` in `adapter_workspace_state.json`.
 
+**Baseline operating instructions**: [../operating-instructions/SKILL.md](../operating-instructions/SKILL.md) is the shared conduct layer for this skill and every dispatched adapter role. The Leader MUST read it before route/pre-flight work and include it in each role dispatch as baseline instructions; role files and output contracts add to it, not replace it.
+
 ## Task Routes
 
 | Route | Downstream |

package/skills/migration-task-adapter/dependencies.yaml

@@ -1,6 +1,13 @@
 # dependencies.yaml — migration-task-adapter startup check
 
 skills:
+  - name: operating-instructions
+    required: true
+    used_by:
+      - task-route-orchestrator
+      - adapter-workspace-state
+      - adapter-report
+    purpose: Shared baseline conduct layer loaded before adapter routing, workspace-state, orchestration, and reporting work.
   - name: android-project-analyst
     required: false
     used_by: