[fpliger]

Stacked on #15190, which is stacked on #15189. This folds plans/v2-plan-delta-2026-10-13.md into the plan, the context and the fork conventions, then deletes it, as its own status line asked ("when the bootstrap docs land on v2, fold … then delete it"). The deleted text stays readable in #15021 and in git history.

Where each delta section went

Delta section	Destination
§1 Facts	Sync facts: plan A4 "Moving upstream base" (#15189) and #15020. Plugin-first facts: new subsection "Areas expected to need rung 3 or 4" in v2-fork-conventions.md
§2 Upstream sync	D1, the L1 lane, U-L1-01 and A4 (#15189). The tooling and first-sync steps are done (#15026, #15029, #15136)
§3 Plugin first	The rung table was already in the fork conventions and B0 (#15178). The "Areas that will need rung 3 or 4" list is now in v2-fork-conventions.md. A8 "Shared-patch growth" now points to the rung table. U-L3-01 acceptance defines the counted metrics and the rung field per shared file. The two import metrics stay, because #15026 lists them as not yet counted
§4 Host package	Already in the U-E0-01 row (#15178). Its reference "(delta §4)" now points to #15021. The rule "until the host lands, register with one marked line; in-flight PRs do not wait" is in the B0 Mechanism paragraph
§5 Doc changes	All applied by this stack and #15178. The Gateway epic (#14991) is mapped in B14 (#15190)
§6 Decisions	D-1 (package names), D-3 (owners) and D-4 (identity and branding split) are A10 rows. They keep their IDs because script/upstream/* cites D-1. D-2 (cadence) is decided by D1
§7 Removed upstream product areas	Decision 7 in migration-context.md. A10 Q-PROD-01 now covers pairing only. U-E9-15 is active: removal in #15151, hiding /pair still open. U-E3-07 acceptance now includes the removal decision for services/, nix/, install and github/

Other changes

• .kilo/skills/v2-migration/SKILL.md: removed the delta pointer.
• .kilo/skills/kilocode-merge-minimizer/SKILL.md: its delta §3 reference now points to the fork conventions.

Not changed

• The U-E0-04 row still says "neutralize … hosted web properties". chore: remove upstream desktop, web app and hosted platform packages #15151 removed them, but E0 rows belong to the E0 session.
• U-E9-14 (embedded web UI decision). §7 says the CLI embeds no web UI today, but it does not decide between kilo-web-ui and upstream packages/app.

Follow-up commit after the review bot: Part A §A10 cited #15151 and #15021, which Decision 10 forbids in Part A. The Q-PROD-01 row now links to migration-context.md Decision 7 (which cites #15151), and the D-1/D-3/D-4 note drops the PR number (Part B's U-E0-01 row still cites #15021). Part A has no issue IDs again.

bun script/upstream/progress.ts --check: up to date.

[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]

SUGGESTION: Part A now carries issue IDs.

migration-context.md decision 10 states "Issue IDs only in Part B and the register", and §A10 (Part A) had no issue IDs before this PR. This row adds #15151, and the new note at line 371 adds #15021. If Part A is meant to stay free of issue IDs (the pattern the rest of §A10 follows), consider moving these citations into the Part B rows or dropping them. Advisory only.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (4 files)

• .kilo/skills/v2-migration/SKILL.md
• migration-tracking/plans/kilo-v2-migration-plan.md
• migration-tracking/plans/migration-context.md
• migration-tracking/technical-notes/baseline/pinned-v2-baseline.md

Verified against current HEAD (13d764aa41):

• Plan Part A (§A10) carries no issue IDs again; the Q-PROD-01 row now cites migration-context.md Decision 7 and the D-1/D-3/D-4 note drops #15021. The prior SUGGESTION is resolved and its comment is now outdated.
• Baseline claims that are checkable in-repo hold: skipFiles exists in script/upstream/utils/config.ts; script/check-shared-patches.ts exists and shared-patches.json defines files: 14; test.yml has the affected job at if: false with push branches dev/v2 and an unfiltered pull_request; check.yml:5-7 matches the described trigger; packages/cli/package.json is 2.0.29; and @kilocode/gateway-core/@kilocode/kilo-plugin match the "Kilo packages" table. Referenced paths (migration-tracking/technical-notes/script/v2-baseline.ts, migration-tracking/discovery/doc-inventory.md) exist.
• Docs-only change. The custom image/<img> rule does not apply (no image tags in changed files) and there is no runtime code, so the memory-leak check does not apply.

Gaps: timing numbers, CI run statuses, and historical run claims in pinned-v2-baseline.md are not locally verifiable and were not re-measured.

Previous Review Summary (commit c8aa7ab)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit c8aa7ab)

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	0
SUGGESTION	1

Issue Details (click to expand)

SUGGESTION

File	Line	Issue
migration-tracking/plans/kilo-v2-migration-plan.md	358	Part A §A10 now carries issue IDs (#15151 here, #15021 at line 371), which migration-context.md decision 10 restricts to Part B and the register

Notes: this is a docs-only fold of v2-plan-delta-2026-10-13.md. I verified the factual claims that are checkable in-repo and they hold: skipFiles exists in script/upstream/utils/config.ts and matches the removed product areas; the removal commit is dated 2026-10-16 as claimed; the TUI /pair slash command exists (packages/tui/src/app.tsx); the referenced packages/core/src/plugin/internal.ts/provider.ts exist; shared-patches.json has rung/seam fields; the deleted file is no longer referenced anywhere in the repo; and the D-1 package-name references match script/upstream. The custom instruction about images/HTML <img> and memory leaks does not apply (no image tags in changed files; no runtime code changed).

Fix these issues in Kilo Cloud

Files Reviewed (6 files)

• .kilo/skills/kilocode-merge-minimizer/SKILL.md - 0 issues
• .kilo/skills/v2-migration/SKILL.md - 0 issues
• migration-tracking/plans/kilo-v2-migration-plan.md - 1 issue
• migration-tracking/plans/migration-context.md - 0 issues
• migration-tracking/plans/v2-plan-delta-2026-10-13.md (deleted) - 0 issues
• migration-tracking/technical-notes/v2-fork-conventions.md - 0 issues

---

_{Reviewed by deepseek-v4.1-flash · Input: 63.9K · Output: 17K · Cached: 755.5K}

_{Review guidance: REVIEW.md from base branch coord-status-units}