Repository navigation
docs(migration): land the bootstrap, discovery and plan docs on v2 - #15038
Conversation
… and deferred channel naming
chore(dev): run bun dev in an isolated v2 profile
Upstream OpenCode workflows that publish, deploy, post, label or close things do not belong in Kilo CI. Remove them, and remove the pure check workflows that never trigger on Kilo branches. Keep test.yml as the test gate and run check.yml on every pull request, so v2 PRs get `bun run check`. Add script/check-workflows.ts, modeled on the v1 guard, and run it from the new kilo-v2.yml so an upstream merge cannot bring a workflow back without review.
Port the v1 merge tooling `skipFiles` behavior for workflows: `bun script/check-workflows.ts --fix` runs `git rm -f` on the upstream workflows that Kilo removed, which also resolves their modify/delete conflicts. A new upstream workflow still fails the check for review. Add the step to the v2 upstream merge procedure in the fork conventions.
docs(migration): new v2 migration plan
docs: add v2 migration skill with TUI self-test recipe
chore(ci): remove upstream workflows and guard the workflow list
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| Account Pooler access. Owned processes and disposable profile/workspace/socket | ||
| artifacts were cleaned up; the existing user window/stores were untouched. | ||
|
|
||
| Sanitized evidence: [model groups](/Users/johnnyamancio/.bb/thread-storage/thr_7bdux6wma9/v1-selftest-model-picker.png), |
There was a problem hiding this comment.
WARNING: Leaked personal absolute filesystem paths
These five evidence links (lines 107-111), plus the framework path on line 81, commit the author's home directory (/Users/johnnyamancio/.bb/thread-storage/... and /Users/johnnyamancio/.config/...) into the repository. That exposes a personal username and internal thread-storage IDs, and none of the links can resolve for other readers. Consider moving the evidence images under migration-tracking/assets/ and referencing them relatively, or redacting the paths.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| mode-0700 private thread-storage directory, with the database file mode 0600. | ||
| The backup passed `PRAGMA quick_check` and contained the expected 60 records. | ||
|
|
||
| Backup: `/Users/johnnyamancio/.bb/thread-storage/thr_qr9z7p3cqc/credential-recovery-20rbKX/before-cleanup.db`. |
There was a problem hiding this comment.
WARNING: Leaked personal path to a credential backup
This line commits /Users/johnnyamancio/.bb/thread-storage/thr_qr9z7p3cqc/credential-recovery-20rbKX/before-cleanup.db, a personal home-directory path that points at a credential backup database, while the next line says the backup must not be published. Consider redacting the path.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| | Item | Value | | ||
| |---|---| | ||
| | Date | 2026-10-07 (amended; first pass 2026-10-05) | | ||
| | Cloud repo | `Kilo-Org/cloud` at `3de933dd85070e9d15c41d8ff3af6c91ca856fd4` (read-only clone `/Users/fpliger/dev/kiloverse/cloud`) | |
There was a problem hiding this comment.
WARNING: Leaked personal absolute paths
Lines 11 and 14 (/Users/fpliger/dev/kiloverse/cloud and /Users/fpliger/dev/opencode) expose personal home-directory paths. Consider redacting or removing them.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| installs, fetches, credentials, or live relay/share traffic. Sources, all read | ||
| locally: this checkout (`kilo-v2` at `61a8707c03` plus the frozen dirty batch), | ||
| Kilo v1 pinned `ecccd1f54b62f9bb16e53a2a58b32bb6d98d0fd7` (`git show`), and the | ||
| sibling cloud checkout `/Users/johnnyamancio/Workspace/kilo_workspace/cloud` |
There was a problem hiding this comment.
WARNING: Leaked personal absolute path
/Users/johnnyamancio/Workspace/kilo_workspace/cloud exposes a personal home directory. Consider redacting it.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
|
|
||
| ## Exact source and runtime | ||
|
|
||
| The source checkout is `/Users/johnnyamancio/Workspace/kilo_workspace/kilocode` |
There was a problem hiding this comment.
WARNING: Leaked personal absolute paths
Lines 11 and 102 commit /Users/johnnyamancio/Workspace/kilo_workspace/kilocode. Consider redacting the path, for example by using a placeholder checkout variable.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| delta closes the leak without a protocol/auth/reasoning regression. The stable | ||
| snapshot passed the full CLI fresh-artifact wrapper: **443 pass / 0 fail, | ||
| 2,741 assertions across 77 files** (359.21s, bundled Bun 1.4). Log: | ||
| `/Users/johnnyamancio/.bb/thread-storage/thr_qr9z7p3cqc/native-route-full-cli.log`. |
There was a problem hiding this comment.
WARNING: Leaked personal absolute path
/Users/johnnyamancio/.bb/thread-storage/thr_qr9z7p3cqc/native-route-full-cli.log exposes a personal home directory and internal thread-storage ID. Consider redacting the path.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| 4. **Staleness gate.** For each feature, diff the v1 files it touches between the assessment snapshot and the v1 target. Empty delta: the donor is likely faithful. Non-empty: re-derive behavior from v1 and keep only the donor's v2 mapping. | ||
| 5. **Staged cutover.** G1 CLI/TUI → G2 VS Code → G3 JetBrains, each with its own go/no-go. G2 and G3 are independent client-surface tracks that run in parallel with G1 once their prerequisites land. Until their gate, the IDEs stay on v1: VS Code bundles the CLI from the same `main` build (no version pin); JetBrains pins a CLI version. | ||
| 6. **Storage.** A separate customer v2 data store. v1 files are never touched while any v1 surface ships. Import is opt-in and re-runnable. Path consolidation only after G3. | ||
| 7. **Scope.** Post-cutover (non-gating): voice, image generation, team and incremental sharing, legacy TUI extras, and features behind experimental flags on v1 that are off by default, unless explicitly made a gate. Features named experimental but on by default on v1 (for example background subagents and the shared agent board) are in scope like any shipped feature. KiloClaw is not needed. Hard gates: FIM/next-edit (G2, G3). Cloud agents and Anaconda Desktop gate whichever surface they consume. |
There was a problem hiding this comment.
SUGGESTION: Internal contradiction on the FIM/next-edit gate
This decision states FIM/next-edit is a hard gate for (G2, G3), but the deferred-decision table in the same file (line 52) lists "whether FIM/next-edit gates G3" as still open, and the plan agrees (kilo-v2-migration-plan.md:199 "whether FIM gates G3 is still open"; kilo-v2-migration-plan.md:348 Q-G3-01). Consider reconciling the parenthetical with the deferred table.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge All findings from the previous review at
No new issues were introduced by the incremental changes. The two known follow-ups stated in the PR description (folding the plan delta, and the pre-existing broken seeded-doc links) remain out of scope for this PR. Files Reviewed (8 files)
Previous Review Summary (commit a5e0423)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit a5e0423)Status: 8 Issues Found | Recommendation: Address before merge Overview
The PR is described and documented as a docs-only change into the integration branch The six WARNING findings are all the same class: personal absolute filesystem paths committed into the new docs. The one SUGGESTION is an internal contradiction in the canonical brief. Also noted, not counted: the description itself lists "fix the broken links in the seeded docs" as a deliberate follow-up, and the diff contains many broken relative links (e.g. the superseded Issue Details (click to expand)CRITICAL
WARNING
SUGGESTION
Files Reviewed (93 files)All 93 added files fall under
Reviewed by deepseek-v4.1-flash · Input: 37.3K · Output: 5.2K · Cached: 234.1K |
Issue
Part of #13750
Supersedes #15014
Exception to "Fixes": #13750 is the migration epic and must stay open. This PR lands its planning docs; it does not complete it.
Context
The migration docs live only on
kilo-v2-clean-bootstrap. Agents and reviewers onv2cannot read them, and the v2 migration skill already points to them. #15016 landed the code from the bootstrap branch (CI lane, isolatedbun dev, migration skill) and left the docs for this merge, as its description says.This PR merges
kilo-v2-clean-bootstrapintov2. It brings three reviewed phases:migration-tracking/reference docs and the canonical briefplans/migration-context.md(pinned refs, decisions, working model, conventions).discovery/(feature inventory, epic taxonomy, unit register, doc inventory) and the refreshedtechnical-notes/baseline/pinned-v2-baseline.md.plans/kilo-v2-migration-plan.md(docs(migration): new v2 migration plan #14987), with superseded banners on the previous plans.It also includes the doc updates for the rename of
kilo-v2-cleantov2, and theorigin/v2vsupstream/v2notes.Implementation
v2was merged intokilo-v2-clean-bootstrapfirst. Conflicts came from chore(ci): remove upstream workflows and guard the workflow list #14996, chore(dev): run bun dev in an isolated v2 profile #14989 and docs: add v2 migration skill with TUI self-test recipe #14994: they were merged into the bootstrap branch and also cherry-picked intov2by chore(v2): land CI lane, isolated bun dev and migration skill #15016. Every conflict outsidemigration-tracking/was resolved tov2's version, which is the newer, reviewed copy.v2is documentation only (93 files, all undermigration-tracking/).v2.Known follow-ups, deliberately not in this PR:
plans/v2-plan-delta-2026-10-13.md(docs(v2): plugin-first policy and upstream/dev sync plan #15021) into the plan and the context (action item A8). This changes D1 to syncing fromupstream/devrelease by release, records thatupstream/v2is frozen, and adds the plugin-first rung table and the Gateway epic (Port Kilo Gateway, login and enterprise support to v2 as a Kilo-owned layer #14991). It makes the current "mergeupstream/v2" wording inmigration-context.mdcorrect again.Screenshots / Video
N/A (documentation only)
How to Test
Manual/local verification
gh api repos/Kilo-Org/kilocode/compare/v2...kilo-v2-clean-bootstrapreports 22 commits ahead and 0 behind, 93 changed files, and no file outsidemigration-tracking/.origin/v2intokilo-v2-clean-bootstrap, resolved the conflicts tov2's versions, ranbun install, then pushed. The push passed the pre-push hook (bun run check, including the package typechecks).Reviewer test steps
migration-tracking/.migration-tracking/plans/migration-context.md, then Part A ofmigration-tracking/plans/kilo-v2-migration-plan.md.git diff origin/v2...origin/kilo-v2-clean-bootstrap --statand confirm the output is the same.Blocked checks and substitute verification