Skip to content

Milestones

Wijanarko Putra Rajeb edited this page Nov 21, 2026 · 3 revisions

Milestones

The record of every piece of work Kabmo has planned, shipped, or turned down: one page in docs/milestones/ per milestone, numbered, with the measurements that decided it. The index is docs/README.md.

The point of keeping them is not history. Each page names the bug its rule prevents and how the number was measured, which is the part a reader re-breaks when it is missing — a decision without its measurement gets relitigated in the next session.

The list

# Milestone What it delivered Status
01 Unified realtime transport one WebSocket per tab, per-topic subscriptions, polling and per-session SSE gone done
02 omp engine adoption the RPC and settings audit from 18.8 through 18.10, and the schema it adopted done
03 Browser end-to-end testing the Playwright layer: temp-root harness, fake omp, a data-testid contract partial
04 Plugin platform a plugin's server half, keyed slots, storage, the test harness and the CLI done
05 Plugin platform, wave 2 participant hooks (useComposer, useRpc, useRealtime) and four conversation slots done
06 Tool renderer audit four tool-card defects measured at omp 18.10.3, and their fixes done
07 Stats plugin the CPU/RAM panel and the server-side sampler behind it done
08 Git panel merge and conflict resolution, branch rename, the branch manager, fetch and amend done
09 Command Runner plugin a repo's command sources as rows, run in the foreground or the background done
10 Packaging and shells five native shells released as artifacts; the bundled-server sidecar is not built partial
11 Worktree sessions a chat born in its own git worktree, chosen before the first send done
12 CodeMirror 6 editor the hand-built code surface replaced end to end, diff view included partial
13 Shell transport and QR pairing the measured case for TLS trust and pairing between a shell and a server partial
14 Editor panel gaps external-change guard, indentation, tab management, Save As, split editor done
15 Composer styles five selectable composer styles, each with a desktop and a phone form done
16 Multi-harness research the measured ACP/RPC capability matrix for nine agent harnesses done
17 Multi-harness design one transport per harness: per-harness tabs, the sidebar mark, per-harness settings done
18 Centre terminal xterm versus Ghostty, measured, for a terminal beside the timeline planned
19 Threads, forks and orchestration a reference implementation measured, then the session tree, spawn, fork, child outcomes and the sidebar separation done
20 Cross-harness orchestration five references compared, then the shipped @harness mention grammar: default-model delegation, prompt contract, worker preamble partial
21 Terminal emulator migration the right-panel terminal moved from xterm.js to ghostty-web, with the theme, cell-box, fit and grid workarounds it needed partial
22 Session MCP server the typed control plane over the session tree: the tree-scoped agent token shipped, with the four tools and the stdio injection path specified partial
23 Change journal a Kabmo-owned JSONL journal for every mutation, including the bash writes omp never records: the writer, reader, classifier, git scan pass and tests partial
24 GitHub Actions viewer the Actions panel plugin — list, run drill with jobs and steps, job logs, cancel/re-run, header readout — over measured payloads and a free conditional poll partial

Still owed

# Owed Why it is not done
03 P5: firefox, webkit and a macOS leg the firefox build will not launch on this machine, and an unverified leg must not gate main
10 P0–P3: a desktop shell that bundles and spawns its own server the shells shipped as thin webview hosts first; the sidecar needs the packaged-server layout measured in that page
12 Phase 4's device run: soft keyboard, IME composition, selection handles, both mobile WebViews a viewport emulation has none of them
13 the TLS half the QR pairing shipped; no shell trusts a certificate, and the pinning tiers remain unbuilt
18 all of it research only: no centre-stage terminal view exists
20 composer-side direct spawn, model autocomplete, roles, MCP injection, Run/fleet UI the mention grammar and defaults shipped; the MCP half is specified in M22, the rest needs the Run work
21 the phone/WebView run, the hidden-terminal memory number, and upstream theme/scrollback/reset fixes the renderer swap, its workarounds and the paint benchmark shipped; the device run and the upstream fixes remain
22 kabmo mcp serve, ACP injection, the adapter matrix the tree-scoped token rule shipped; the MCP server and its injection are specified, not implemented
23 the parity test on a real session, the blob prune, apply_patch/MCP write adapters the writer, reader, classifier, scan pass and run separation shipped; the remaining items are listed in §10.4
24 the shared-core extraction (P0/D1) and the run-level log archive (P7) the plugin, its 51 tests and the browser smoke shipped; the extraction and the archive did not

Turned down on the record, not left open: plugin-platform P6 (a component registry, declined in M04 and re-declined in M05 once twelve slots had shipped without needing one) and the editor's format-on-save (M14).

How the numbering works

  • M<NN>-<slug>.md, two digits, contiguous from 01.
  • NN is when the work started, not when it finished. M18 and M24 are planned and carry numbers before their turn for that reason; renumbering on each ship would move every later file and make the number mean nothing.
  • No version and no date in the filename. 18.8 and 2026-10-13 drift the moment a pin moves or the page is revisited; both live in the header instead.
  • One milestone, one page. Two documents written together that decide different things stay two milestones, in order — M16 measures nine harnesses, M17 designs the UI over those measurements.

Status tokens

Every milestone states its status once, in the header block — after the title, before the first ## section — as Status: **<token>** — <one clause> (YYYY-MM-DD, \commit`)`.

Token Means
done every planned item landed, or was declined with the reason in the page
partial something is still owed and is named in the clause and in Still owed
planned nothing is implemented; the page is research or design only
declined considered, measured, and not built, with the reason
blocked owed, and blocked by something outside this repository

docs/reference/ carries no status: the plugin SDK and the built-in panel table are living contracts, and a contract that is over is not a contract.

Why this is enforced by a test

tests/docs-milestones.test.ts pins the naming, the status line, the index rows and every docs/… path named from the README, the packages, CI and the pages themselves.

Two failures earned it, and both were silent — no build, no lint, no test noticed either:

  • A page outliving its own conclusion. The git panel page said "research only, nothing implemented" for fifteen days after merge, branch rename and the branch manager had shipped; the packaging page said "nothing implemented" with five shells published. A reader trusts the header.
  • A link to a page that never existed. The worktree page cited docs/omp-worktree-research for the three omp bugs that motivated the design. The measurements were real; the page was not.

Neither is catchable by reading the code, and neither surfaces until someone follows the link.

Clone this wiki locally