[fpliger]

Bring the migration docs in line with the current state of origin/v2. Docs only.

This PR now carries the whole stack: #15190, #15191 and #15192 were merged into docs-v2-reconcile, so the diff against v2 is their union. The one change to a recorded decision is D1, the sync source: upstream/dev instead of upstream/v2. The skill, #15020, the merged tooling (#15026) and the syncs (#15029, #15136) already assume it. The same change states the moving-base strategy explicitly.

Files (7, +160 / −203)

File	Change
plans/migration-context.md	State, pinned refs, repositories, D1, Decision 7, bootstrap status
plans/kilo-v2-migration-plan.md	Part A facts and strategy; Part B unit status and issue mapping; appendices
plans/v2-plan-delta-2026-10-13.md	Deleted; folded into the plan, the context and the fork conventions
technical-notes/baseline/pinned-v2-baseline.md	New capture at v2.0.30; the 2026-10-11 capture kept
technical-notes/v2-fork-conventions.md	Banner corrected; new "Areas expected to need rung 3 or 4"
.kilo/skills/v2-migration/SKILL.md	Sources of truth, moving base, baseline policy
.kilo/skills/kilocode-merge-minimizer/SKILL.md	Delta section 3 reference repointed

Docs location and state (#15189)

• migration-context.md: the current working base is origin/v2 (docs landed 2026-10-13, docs(migration): land the bootstrap, discovery and plan docs on v2 #15038). Status says L1 is running (feat(upstream): port the upstream merge tooling to the v2 line #15026, chore(upstream): sync v2.0.27 (4d9678a79d6) #15029, chore(upstream): sync v2.0.30 (775d1d0d713) #15136) and that no Part B unit is marked done.
• SKILL.md: the docs are on v2; the git show origin/kilo-v2-clean-bootstrap:<path> instruction is removed.

Upstream source and moving base (#15189)

• Repositories: upstream's v2 line is upstream/dev since 2026-10-10 (5caf1f9). The name-collision note adds that upstream/v2 is frozen (tip 4617210822b) and never merged.
• D1 is "New base, kept current": every upstream release is merged into origin/v2, at least weekly, in its own PR, with a merge commit. Several pending releases may go in one sync when the PR says why (as chore(upstream): sync v2.0.30 (775d1d0d713) #15136 did).
• Plan A1: the target is upstream v2 at its latest synced release. A4: a new "Moving upstream base" paragraph with the why and the rules (BASE means the current base; each sync is its own PR; open PRs merge after a sync; known failures are compared against origin/v2).
• Plan A3 D1 row, A6 L1 lane, A8 upstream risk and a new "sync breaks a seam or an in-flight unit" risk, A9 lag metric in releases and days, U-L1-01 title and acceptance.
• Appendix B: upstream/dev row; upstream/v2 marked frozen; BASE now moves; new Sync term.
• Pinned refs: "Initial upstream base" (5e73d5cb) and a new "Current upstream base", derived from the newest sync merge via pinned() (script/upstream/utils/upstream.ts); v2.0.30 on 2026-10-16.

Delta fold and deletion (#15191)

Folded v2-plan-delta-2026-10-13.md into its homes, then deleted it:

• Decision 7: upstream's desktop app, web app and hosted platform packages are not shipped (removed 2026-10-16).
• A10: Q-PROD-01 now covers pairing only. Adds D-1 (package names), D-3 (owners) and D-4 (identity and branding split), keeping the delta's IDs because script/upstream/* cites D-1. Its D-2 (cadence) is decided by D1.
• A8 shared-patch risk now points to the rung table.
• B0 mechanism paragraph: how a Kilo plugin registers until the host (U-E0-01) lands.
• U-L3-01 acceptance defines the counted metrics. U-E9-15 is active (removal chore: remove upstream desktop, web app and hosted platform packages #15151; hiding /pair still open). U-E3-07 acceptance includes deciding the removal of services/, nix/, install and github/.
• Fork conventions: new "Areas expected to need rung 3 or 4" subsection.
• Follow-up commit: Part A had picked up issue IDs (#15151, #15021), which Decision 10 forbids in Part A. Part A is issue-free again and links to Decision 7 instead.

Baseline re-measure (#15192)

New capture at origin/v2 98ead1f27e (upstream v2.0.30): typecheck 27/27; lint (oxlint only) pass; check:generated pass in packages/client, services/www and packages/protocol (protocol was stale at the initial base); CLI build and service smoke pass; both Kilo packages pass.

• turbo test: @opencode/core 37, @opencode/cli 1, @opencode/tui 1 fail. 30 are the same macOS host cases (bash 3.2, no rg); 9 are load flakes that pass in an isolated re-run.
• Fork CI verified; the check.yml PR-trigger description was corrected after the review bot flagged it.

Unit status and issue mapping (#15190)

Unit	Before	After	Evidence
U-L1-01	new / todo	#15020 / active	#15026, #15029, #15136; dep narrowed to U-E0-04 (dry-run workflow only)
U-L3-01	todo	active	shared-file counter in #15026; import metrics not counted yet
U-E1-03	new / todo	#14991 / active	#15111, #15072
U-E1-04	new / todo	#14991 / active	#15111 (with #15065, #15067), #15116
U-E1-05	new	#15108 (aliased models only)	still todo

B14 gains rows for #14991, #15020 and #15108. "Units that need a new issue" drops from 78 to 75. No unit is marked done and no acceptance is recorded.

Still open (not in this PR)

• U-E0-04 still says "neutralize … hosted web properties"; E0 rows are owned by the E0 session.
• U-E9-14 (embedded web UI decision) is unresolved.
• v2-fork-conventions.md body, root AGENTS.md and technical-notes/script/v2-baseline.ts still assume the old base; U-E0-03 owns all three.
• script/check-workflows.ts:7 still says the line merges upstream/v2 (code comment; next sync PR).
• Whether each gate requires the newest release to be synced before go/no-go (needs a decision).
• Node build and smoke not run (host Node 24.13.0; CI pins 26.4.0).

Checks

typecheck, unit (linux), unit (windows), migration progress map, shared upstream patches, upstream sync tooling tests and workflow allowlist pass. e2e is skipped on the fork. bun script/upstream/progress.ts --check: up to date.

The Vercel "docs" check fails because the project builds packages/kilo-docs, which does not exist on v2; it also fails on docs-* branches elsewhere (#15169). It is not a required check.

[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: 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/migration-context.md	35	PR body "Unsure" section says D1/L1 state no cadence and no one-PR-per-sync, but D1 now reads "in its own PR … at least weekly" (and the plan L1 row mirrors it). The body text no longer matches the code.

The incremented docs are otherwise internally consistent and the factual claims match the sources: pinned() exists at script/upstream/utils/upstream.ts:59, the sync merge chore(upstream): sync v2.0.30 (775d1d0d713) (#15136) is present on origin/v2, and the "about five releases a week / 16 of 21 seam patches" figures match plans/v2-plan-delta-2026-10-13.md:37. No inline comments: the only finding is a PR-body/code mismatch, which is summary-only.

Files Reviewed (3 files)

• .kilo/skills/v2-migration/SKILL.md
• migration-tracking/plans/kilo-v2-migration-plan.md
• migration-tracking/plans/migration-context.md

Fix these issues in Kilo Cloud

Previous Review Summary (commit 9f865c2)

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

Previous review (commit 9f865c2)

Status: No Issues Found | Recommendation: Merge

Docs-only reconciliation of the v2 migration plan, context, skill, and fork-convention banner. The upstream/dev sync source, frozen upstream/v2 wording, and dropped kilo-v2-clean-bootstrap references are applied consistently across all four files, and the changed lines match the facts stated in the PR body.

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/v2-fork-conventions.md

---

_{Reviewed by deepseek-v4.1-flash · Input: 42.4K · Output: 9.2K · Cached: 429.3K}

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs (docs-staging)	Error		Oct 18, 2026 1:29am UTC