diff --git a/ROADMAP.md b/ROADMAP.md index c419d4c..176ef6f 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -25,16 +25,17 @@ - The drawing's link (0.1.26): How we work and Kai tell a session that every message showing or changing a drawing gives the page's link with the picture, as a clickable `file:///` link, without being asked. Until then a drawing lane could send only pictures. - The model and effort follow the job (0.1.27): a plan row's Who names a job word (design, build, edit, review, write), and the job, not the persona, sets the stage's model and effort, from one line each in `tiers.conf`: design is Opus 5.5 at high, build, review and write Opus 5.5 at medium, edit Sonnet 5.5 at medium. A row can pin any other point; Fable is pinned only after Opus at high fell short, or for security or concurrency code. Stage chips carry the model and the effort, the stage checks both, and `/ck:cost history` shows cost by model and effort. - Two endings (0.1.28): How we work tells a session that every message to the User ends with what is left in the session, in order, and the words for the first step ("Say merge 95"), or with "This session can be closed." It never says "nothing is needed". Until then the template itself told sessions to say so, and d20mob and hireling sessions said it while a merge, a "log it" and a branch deletion were still waiting. -- Main is at 0.1.28. Each release is a branch from main, a pull request into main, a tag on main, and a GitHub release. The tests run on every pull request. -- Two channels: stable (the `code-katz` marketplace) and ck-next (a local marketplace, used by d20mob, hireling and the ck folder), both on `v0.1.28` since 2026-11-06. Rollback in a project is two commands. +- Every page names its project (0.1.29): review pages, gallery pages and `/ck:do` mockups carry the project's name in their title and banner line, found from the git repository's main checkout, so a d20mob page can be told apart in the artifact list. Until then the banner said "Code Katz · review page", and a d20mob staged plan was titled "Phase 9, the ten: staged plan". +- Main is at 0.1.29. Each release is a branch from main, a pull request into main, a tag on main, and a GitHub release. The tests run on every pull request. +- Two channels: stable (the `code-katz` marketplace) and ck-next (a local marketplace, used by d20mob, hireling and the ck folder), stable on `v0.1.28` since 2026-11-06 and ck-next on `v0.1.29` since 2026-11-07. Rollback in a project is two commands. **What's missing or fragile:** - The memory gate has not yet been tried in an interactive session. - 0.1.20 to 0.1.28 have not been checked in a real d20mob session, and stable serves them. d20mob, hireling and ck have no team file yet, so each gets only the eight core seats, and d20mob's plan rows owned by Reiner, Tracy, Travolta or Piper get no card until they are invited. - How the desktop app shows the cost line after a merge has not been seen; a test hook did not fire. - A change to ck's "How we work" template reaches no project on its own. The question rule (0.1.14) and the finishing rule (0.1.24) were each copied into d20mob and hireling by hand. The stage's model rule (0.1.25) and the drawing's link rule (0.1.26) went in the same way on 2026-11-05 ([d6veteran/d20mob#400](https://github.com/d6veteran/d20mob/pull/400), [d6veteran/hireling#65](https://github.com/d6veteran/hireling/pull/65)), and How we work 0.1.28, with 0.1.27's model and effort, on 2026-11-06 ([d6veteran/d20mob#427](https://github.com/d6veteran/d20mob/pull/427), [d6veteran/hireling#104](https://github.com/d6veteran/hireling/pull/104)). -- `claude plugin update` in a repository with worktree installs can update the wrong one; from 2026-11-03 to 2026-11-06 the d20mob and hireling main installs were set by hand, to 0.1.24, 0.1.25, 0.1.26, 0.1.27 and then 0.1.28. Each time it updated the main ck folder correctly, but moved an old worktree install in d20mob and in hireling instead of their main folders. -- Auto mode sometimes refuses to push a tag or create a GitHub release; then you run that step by hand, as for `v0.1.27`. It allowed both for `v0.1.28`. +- `claude plugin update` in a repository with worktree installs can update the wrong one; from 2026-11-03 to 2026-11-07 the d20mob and hireling main installs were set by hand, to 0.1.24, 0.1.25, 0.1.26, 0.1.27, 0.1.28 and then 0.1.29. Each time it updated the main ck folder correctly, but moved an old worktree install in d20mob and in hireling instead of their main folders. +- Auto mode sometimes refuses to push a tag or create a GitHub release; then you run that step by hand, as for `v0.1.27`. It allowed both for `v0.1.28` and `v0.1.29`. - ck2 is abandoned. Anything from it is rebuilt from scratch, if at all. --- @@ -72,7 +73,8 @@ ck reaches projects from two places. **Stable** is the `code-katz` marketplace o | 0.1.25 | 2026-11-04 | The stage's model: a stage session on the wrong model stops and waits, whoever wrote its brief; How we work 0.1.25 | Tag `v0.1.25` | | 0.1.26 | 2026-11-05 | The drawing's link: every message that shows or changes a drawing gives the page's link with the picture; How we work 0.1.26 | Tag `v0.1.26` | | 0.1.27 | 2026-11-05 | The model and effort follow the job: five job words in Who, each a model and an effort in `tiers.conf`, pins for any other point, chips with both, cost by model and effort; How we work 0.1.27 | Tag `v0.1.27` | -| 0.1.28 | 2026-11-06 | Two endings: every message ends with what is left in the session or "This session can be closed.", never "nothing is needed"; How we work 0.1.28 | Tag `v0.1.28`; **stable** and **ck-next** | +| 0.1.28 | 2026-11-06 | Two endings: every message ends with what is left in the session or "This session can be closed.", never "nothing is needed"; How we work 0.1.28 | Tag `v0.1.28`; **stable** | +| 0.1.29 | 2026-11-07 | Every page names its project: review pages, galleries and `/ck:do` mockups carry the project's name in their title and banner line, from the git repository's main checkout; `--project` overrides it | Tag `v0.1.29`; **ck-next** | --- @@ -110,7 +112,7 @@ Dropped with ck2: its 0.2.0 release plan, which would have replaced ck in the `c | # | Opportunity | Why Now | Success Signal | |---|---|---|---| -| 1 | **Try 0.1.19 to 0.1.28 in d20mob** (in progress since 2026-11-07) | Stable moved from `v0.1.19` to `v0.1.28` on 2026-11-06 ([code-katz/claude-plugins#11](https://github.com/code-katz/claude-plugins/pull/11)), at your word, before any of 0.1.19 to 0.1.28 was tried by hand in a d20mob session | In d20mob: a memory save shows the proposal and then the approval prompt, `/ck:do` runs, `/ck:cost` prints a real table, the four checks in [code-katz/ck#51](https://github.com/code-katz/ck/pull/51) pass, a merge prints one cost line for the right pull request, a lane that runs a gate skill ends with only its finished sentence, a phase's stages open on their job word's model and effort with no ruling in the row, with `/ck:cost history` showing the cost of each, and no session says "nothing is needed" with work waiting; if one fails, it is fixed in the next release, or stable goes back to `v0.1.19` | +| 1 | **Try 0.1.19 to 0.1.28 in d20mob** (in progress since 2026-11-07) | Stable moved from `v0.1.19` to `v0.1.28` on 2026-11-06 ([code-katz/claude-plugins#11](https://github.com/code-katz/claude-plugins/pull/11)), at your word, before any of 0.1.19 to 0.1.28 was tried by hand in a d20mob session | In d20mob: a memory save shows the proposal and then the approval prompt, `/ck:do` runs, `/ck:cost` prints a real table, the four checks in [code-katz/ck#51](https://github.com/code-katz/ck/pull/51) pass, a merge prints one cost line for the right pull request, a lane that runs a gate skill ends with only its finished sentence, a phase's stages open on their job word's model and effort with no ruling in the row, with `/ck:cost history` showing the cost of each, no session says "nothing is needed" with work waiting, and each page ck publishes names d20mob (0.1.29, on ck-next); if one fails, it is fixed in the next release, or stable goes back to `v0.1.19` | | 2 | **Measure d20mob's 400K auto-compact test** (in progress since 2026-11-07) | The compaction evaluation chose this over a ck feature. The setting went into d20mob's local settings on 2026-10-30, and the baseline is saved | On 2026-11-06, a pass or fail against the baseline; the prediction is $116 to $154 a week saved, in API-equivalent dollars | ### Tier 2: High Value, Plan for Next Sprint @@ -119,7 +121,7 @@ Dropped with ck2: its 0.2.0 release plan, which would have replaced ck in the `c |---|---|---|---| | 1 | **The lean review's remaining recommendations** ([ck: is it lean?](https://claude.ai/artifact/PKCgiGsjZroKmLVXXEjuuB)); R1 and R3 shipped in 0.1.21 | Fewer tokens per session and per command | Each one is weighed on its own, by tokens saved per week | | 2 | **Template changes reach projects** | A rule fixed in ck's "How we work" template is missing from every project until someone copies it by hand; d20mob's questions came as chips because of this | A changed sentence can go into a reviewed section as a one-line edit, with no redraft; `scripts/claude-md.py status` already reports "behind: yes" | -| 3 | **A release in one command** | About eight hand steps per release (tag, GitHub release, ck-next's four fields, the installs), seven releases since 2026-10-28, and `claude plugin update` moving the wrong install three days running | One script can tag, release, pin ck-next and set each main install from the DEVLOG entry; it is next after the d20mob trial on the releases page, now as 0.1.29, with its own plan | +| 3 | **A release in one command** | About eight hand steps per release (tag, GitHub release, ck-next's four fields, the installs), seven releases since 2026-10-28, and `claude plugin update` moving the wrong install three days running | One script can tag, release, pin ck-next and set each main install from the DEVLOG entry; it is next after the d20mob trial on the releases page, now as 0.1.30, with its own plan | | 4 | **A code-quality review command** | One ck command reviews a project's code, or one area of it, for quality: patterns and practices, duplication, complexity to simplify, dead code, dependency versions, and overall maintainability, and ends in a page of findings you comment on. Today nothing covers dead code, dependency versions or a whole project; ck2's `/ck:lean` and the outcome loop were not planned | It can reuse Claude Code's own `/simplify` (reuse, simplification, efficiency) and `/code-review` (bugs) instead of rebuilding them; findings ranked by upkeep saved are worth the tokens a run costs. A design session investigates first, then you choose | ### Tier 3: Strategic / Longer Horizon @@ -134,8 +136,8 @@ Dropped with ck2: its 0.2.0 release plan, which would have replaced ck in the `c ## Recommended Sequencing ``` -Now: a d20mob phase on 0.1.28 (stable and ck-next), checking 0.1.19 to 0.1.28; measuring d20mob's 400K auto-compact test (both in progress) -Next: 0.1.29, a release in one command, with its own plan; the code-quality review command's design +Now: a d20mob phase on ck-next 0.1.29 (stable on 0.1.28), checking 0.1.19 to 0.1.29; measuring d20mob's 400K auto-compact test (both in progress) +Next: 0.1.30, a release in one command, with its own plan; the code-quality review command's design Later: the code-quality review command; template changes reach projects; the lean review's remaining recommendations ``` @@ -162,6 +164,24 @@ Later: the code-quality review command; template changes reach projects; the lea ## Revision History +## [2026-11-07] 0.1.29 shipped: every page names its project; ck-next on 0.1.29 + +**Change Type:** `complete` +**Triggered by:** `delivery` +**Items Affected:** Snapshot; What's missing or fragile; Releases; Tier 1 item 1; Tier 2 item 3; Recommended Sequencing + +### What Changed +Releases gains 0.1.29 (every page names its project, [code-katz/ck#68](https://github.com/code-katz/ck/pull/68)), tagged `v0.1.29`, and ck-next serves it. Stable stays on 0.1.28. The main ck, d20mob and hireling installs run 0.1.29. The d20mob trial now runs on ck-next 0.1.29 and checks that each page names d20mob. A release in one command moves to 0.1.30. + +### Why +A d20mob staged plan was published as "Phase 9, the ten: staged plan" under "Code Katz · review page", so nothing on it said d20mob. `claude plugin update` updated the main ck folder; the d20mob and hireling main installs were set by hand again. + +### Open Questions Resolved / Added +- Resolved: none. +- Added: none. + +--- + ## [2026-11-07] Tier 1 in progress; a code-quality review command in Tier 2 **Change Type:** `add`