[fpliger]

Stacked on #15189. Status and issue hygiene in Part B of the plan, from merged PRs only. No unit is marked done; acceptance is not recorded for any of them.

Changes (plans/kilo-v2-migration-plan.md)

Unit	Issue	Status	Evidence
U-L1-01	new → #15020	todo → active	Tooling #15026; syncs v2.0.27 #15029, v2.0.30 #15136. Deps narrowed: U-E0-04 is needed only for the dry-run workflow, the syncs already run without it
U-L3-01	#14381 (unchanged)	todo → active	Shared-file counter script/check-shared-patches.ts in #15026. #15026 states that the import metrics are not counted yet
U-E1-03	new → #14991	todo → active	#15111 (device login, teams), #15072 (account RPCs). Mapping from kilo-gateway-v2-plan.md ("Plan units")
U-E1-04	new → #14991	todo → active	#15111 (with #15065 catalog, #15067 headers and errors), #15116 (variants)
U-E1-05	new → #15108 (aliased models)	todo (unchanged)	#15108 covers only the aliased-model prompt overrides

• B14 mapping: new rows for Port Kilo Gateway, login and enterprise support to v2 as a Kilo-owned layer #14991 (Gateway tracker), Port the upstream merge tooling to v2 and sync from upstream/dev #15020 and Support backend opencode.family and prompt overrides for aliased Gateway models in v2 prompt selection (U-E1-05) #15108.
• B14 "Units that need a new issue": 78 → 75. U-L1-01, U-E1-03 and U-E1-04 are removed. U-E1-05 stays, because Support backend opencode.family and prompt overrides for aliased Gateway models in v2 prompt selection (U-E1-05) #15108 covers only part of it. The E0 row is stale (E0 has Kilo host and composition package #15172 to v1 reference fixtures for session runtime policy #15177). It is left for the E0 session, which owns E0 rows.

[github-actions]

➖ v2 migration progress: 0.1% → 0.1% (0 done, 0 total, 0 dropped; 12/9854 cells)

No change to the progress map.

Full map · how cells close

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

This is a documentation-only change to migration-tracking/plans/kilo-v2-migration-plan.md (11 insertions, 8 deletions). No code paths, so the memory-leak and image-format checks do not apply (no <img>/markdown images are introduced).

Checks performed against the changed lines:

• B14 "Units that need a new issue" count 78 → 75 is consistent with the row edits: E1 loses U-E1-03 and U-E1-04 (now #14991), L loses U-L1-01 (now #15020), and U-E1-05 stays as "beyond Support backend opencode.family and prompt overrides for aliased Gateway models in v2 prompt selection (U-E1-05) #15108" (partial coverage). The listed per-epic rows sum to 75.
• U-E1-03/U-E1-04 issue column now points at #14991, matching the new B14 mapping row.
• New B14 mapping rows #14991, #15020, #15108 match the changes to the unit rows and keep the table's 3-column shape.
• The A9 metrics rollup still reports 78 for "Need a new issue" but A9 is explicitly labeled "Counts at plan creation" (pre-existing, unchanged), so the snapshot is intentionally not restated — no contradiction with B14's live count.
• The PR description matches the diff (status transitions, issue assignments, the 78 → 75 count, and the narrowed U-L1-01 dependency on U-E0-04).

CI is the authority for the markdown-table and migration-progress guards; those were not re-run here.

Files Reviewed (1 file)

• migration-tracking/plans/kilo-v2-migration-plan.md

---

_{Reviewed by deepseek-v4.1-flash · Input: 50.2K · Output: 12.1K · Cached: 479.7K}

_{Review guidance: REVIEW.md from base branch docs-v2-reconcile}