docs: retire 0.9-era plans from command to history

Hmbown · Hmbown · commit 17bde5e33463 · 2026-07-12T14:04:15.000-07:00
A full audit of every document claiming to define 0.9.0 or the next major found that most of the old cutover plan already shipped in v0.8.68 under a different route, while several committed documents still presented stale obligations as binding — including a tracker asserting unshipped Multitask work as Done and a handoff instructing removal of todo_* aliases that #4132 deliberately kept. Give every roadmap-era document an explicit status: the workrooms RFC is a future RFC with Phase 1 shipped; the external-memory cutline is marked principle-only with its aspirational layer rows called out; the harness cutline records its shipped schema/resolver lane; the file-decomposition RFC is re-scoped honestly (config.rs was overtaken by ProviderLake while ui.rs and main.rs grew); the 0.8.68 playbook, tracker, and completion handoff are stamped Historical with their live residuals (#4175/#4177/#4178/#4179) and their false-Done rows named. TOOL_SURFACE gets its version stamp and the alias paragraph corrected to shipped-in-0.8.68; ARCHITECTURE gains the workflow/workflow-js/lane crates; LOCALIZATION states its website-only scope next to the TUI packs; REBRAND's product framing is neutralized to every-provider-first-class per stewardship policy. The present-day description of what a next-major release would actually mean now lives in docs/AGENT_RUNTIME.md — scope, not a version promise — and the six-module do-not-delete guardrail is salvaged from the handoff into AGENTS.md where agents will see it.
diff --git a/AGENTS.md b/AGENTS.md
@@ -47,6 +47,13 @@
   injection were all removed. `constitution.md` is the sole base prompt.
 - Configurable sub-agent depth stays. Add a new limit only when it's clearly
   needed, and explain why.
+- **Do-not-delete guardrail** (salvaged from the 0.8.68 handoff; these were
+  repeatedly misflagged as dead code and deleting them broke the build):
+  `tui/src/memory.rs`, `tui/src/context_budget.rs`,
+  `tui/src/model_registry.rs`, `tui/src/prompt_zones.rs`,
+  `tui/src/tools/remember.rs`, and the entire `config/src/route/` directory
+  are all actively imported. Verify consumers with `rg` before believing any
+  dead-code audit.
 - The sub-agent **TUI freeze reported in older handoffs is resolved** by the
   v0.8.61 cutover (cap-20, persist-debounce, AgentProgress redraw throttle,
   ListSubAgents coalescing, input-pump-off-render-thread). The leading
diff --git a/CODEWHALE_0_8_68_TRACKER.md b/CODEWHALE_0_8_68_TRACKER.md
@@ -1,5 +1,13 @@
 # CodeWhale 0.8.68 — Workflow + Stability Patch Release
 
+> **Status (2026-07-12): Historical.** v0.8.68 shipped on 2026-07-10; this
+> tracker is superseded by the shipped release. Caution for readers: the
+> Wave-7 "Multitask" rows below are marked Done but describe work that was
+> **rolled back before ship** — Multitask never shipped and leftover settings
+> normalize to Operate (`crates/tui/src/tui/app.rs`, mode picker). The
+> "deferred to 0.9.0" lists remain useful as a raw next-major backlog feed;
+> the release label itself is a maintainer decision.
+>
 > **What this is.** Local tracker + handoff for the CodeWhale 0.8.68 release
 > candidate. It documents what's in scope, what's deferred to 0.9.0, and the
 > current verification state.
diff --git a/HANDOFF_v0.8.68_completion.md b/HANDOFF_v0.8.68_completion.md
@@ -1,9 +1,17 @@
 # CodeWhale 0.8.68 Handoff — Finish the Landing
 
-> **Companion document:** [`opportunities.md`](../../opportunities.md) — the
-> verified cleanup & optimization catalog. Every item below cross-references
-> it. Read both together; this file is the *what to do next*, opportunities.md
-> is the *what's real*.
+> **Status (2026-07-12): Historical / completed.** Every actionable item below
+> either landed by v0.8.68 (multipart/brotli removal, palette migration,
+> allowed_tools deletion, tools_file/removed_messages cleanup, double-Enter
+> steer) or was deliberately superseded — item 7's "remove `todo_*` aliases at
+> 0.9.0" went the other way: #4132 keeps `todo_*`/`checklist_*` as hidden
+> replay aliases, so do not execute it. The DO-NOT-DELETE module table below
+> remains a standing guardrail. The companion `opportunities.md` was never
+> committed; its link is dangling by design.
+>
+> ~~**Companion document:** [`opportunities.md`](../../opportunities.md)~~ (not
+> in the repository) — this file was the *what to do next*; the catalog behind
+> it stayed private.
 
 ## Branch & Location
 - **Worktree:** `/Users/hunter/Desktop/Harnesses/CW/.cw-worktrees/v0867-pr4047`
diff --git a/docs/AGENT_RUNTIME.md b/docs/AGENT_RUNTIME.md
@@ -150,3 +150,37 @@ CodeWhale should converge with Claude Code on **shape**, not on branding:
 
 The litmus test for any new agent surface: *does it launch and observe the one
 runtime, or does it invent a second one?* Only the former is allowed.
+
+## What a next-major ("0.9-level") release would mean today
+
+Refreshed 2026-07-12 from a full audit of the 0.9-era documents. The release
+label is a maintainer decision; this section describes scope, not a version
+promise. Most of what the old cutover plan called "0.9.0" already shipped in
+v0.8.68 (Plan/Act/Operate + posture cycle, the wired Workflow engine with a
+durable run journal, the Lane CLI/runtime, the setup wizard with
+`operate_ready`, the constitution rebalance, ProviderLake/Models.dev). What
+genuinely remains:
+
+1. **Rebrand completion** — the only hard-dated obligations: remove the
+   `deepseek`/`deepseek-tui` binary shims and shim release assets; finish the
+   Homebrew `codewhale` formula rollout (`docs/REBRAND.md`).
+2. **Operate as a value stream** — a control-board surface over the underwater
+   shell (WIP, queue age, bottleneck); model-visible Work state (#3983); phase
+   ledger (#4039); Workrooms Phase 2 (#3209/#3210) as the inbox substrate;
+   receipt reconciliation.
+3. **Flow control** — real WIP limits and visible queues (#4015, #4016),
+   reconciled with the shipped 16-concurrent/1k-run access model (#4292).
+4. **Fleet/Workflow convergence residuals** — live tmux/verifier-gate dogfood
+   closing #4175/#4177/#4178/#4179; Fleet consuming canonical AgentProfiles;
+   Conductor/topology (#4010, #4012) as stretch.
+5. **TTC_DESIGN implementation** — approved and now unblocked post-0.8.68.
+6. **HarnessProfile completion** — the status/UX display lane
+   (`docs/rfcs/HARNESS_PROFILE_CUTLINE.md`).
+7. **File decomposition, re-scoped** — `ui.rs` (~13.6k lines) and `main.rs`
+   (~12.1k) are the current offenders (`docs/rfcs/FILE_DECOMPOSITION_0_9_0.md`).
+
+Explicitly deferred by their own documents: external workflow memory (boundary
+only), automatic harness evolution, hosted workrooms, `constitution_modules`
+(needs sign-off), permission profiles (#3211, needs design), and plan-ceiling
+probing (needs a product decision).
+
diff --git a/docs/AGENT_WORKFLOWS_0868.md b/docs/AGENT_WORKFLOWS_0868.md
@@ -1,5 +1,13 @@
 # CodeWhale v0.8.68 — Agent Workflow Playbook
 
+> **Status (2026-07-12): Historical.** v0.8.68 shipped on 2026-07-10; this
+> playbook's waves are complete. Two things in it remain live and should be
+> carried forward, not re-derived: the settled product vocabulary
+> (**Fleet = who · Workflow = what order · Lane = running instance ·
+> Runtime = where/how**) and the still-open dogfood residuals
+> (#4175, #4177, #4178, #4179 — blocked on a completed live tmux stopship run
+> with child receipts and a verifier gate).
+
 This document tells autonomous agents how to systematically complete the v0.8.68
 release. It pairs with:
 
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md
@@ -2,7 +2,7 @@
 
 This document provides an overview of the codewhale architecture for developers and contributors.
 
-Current boundary note (v0.8.67):
+Current boundary note (v0.8.68):
 - `crates/tui` is still the live end-user runtime for the TUI, runtime API, task manager, and tool execution loop.
 - Other workspace crates are being split out incrementally, but they are not yet the sole runtime source of truth.
 - The LSP subsystem (`crates/tui/src/lsp/`) is fully wired into the engine's post-tool-execution path
@@ -97,6 +97,12 @@ Current boundary note (v0.8.67):
 - **`crates/protocol`** - Request/response framing and protocol types.
 - **`crates/secrets`** - OS keyring integration for API key storage.
 - **`crates/state`** - SQLite thread/session persistence layer.
+- **`crates/workflow`** / **`crates/workflow-js`** - Workflow engine and its
+  QuickJS scripting layer (renamed from the whaleflow crates).
+- **`crates/lane`** - Lane runtime: durable, attachable running instances of
+  Fleet/Workflow work (`codewhale lane list/status/attach/logs/stop`).
+- **`crates/release`** / **`crates/build-support`** - Release checks and build
+  plumbing.
 
 ### LLM Integration
 
diff --git a/docs/LOCALIZATION.md b/docs/LOCALIZATION.md
@@ -3,7 +3,14 @@
 Canonical tracking document for every locale CodeWhale ships, is actively
 building, is planning, or has explicitly deferred.
 
-Last updated: 2026-06-29.
+> **Scope note (2026-07-12):** this matrix tracks the website/README surface.
+> The TUI ships its own locale packs under `crates/tui/locales/`
+> (en, es-419, ja, ko, pt-BR, vi, zh-Hans complete; zh-Hant intentionally
+> partial per #4057), guarded by raw key-parity tests in
+> `crates/tui/src/localization.rs`. Keep the two surfaces distinct when
+> updating status here.
+
+Last updated: 2026-07-12.
 Source-of-truth README: `README.md` (English, post-#3087).
 
 ## Status legend
diff --git a/docs/REBRAND.md b/docs/REBRAND.md
@@ -205,8 +205,9 @@ doctor`, `codewhale sessions`, and your expected skills all show the same state.
 ## Why the name change
 
 CodeWhale is a shorter, terminal-friendlier handle for the same terminal
-coding agent and the longer-term product direction: a DeepSeek-first agentic
-terminal for open source and open-weight coding models. The project name,
+coding agent and the longer-term product direction: an agentic terminal for
+open source and open-weight coding models, with DeepSeek — the provider the
+project started with — remaining first-class alongside every other provider. The project name,
 command names, package names, release assets, Docker image, and CNB mirror move
 to CodeWhale; the official DeepSeek provider, model IDs, env vars, and
 `~/.deepseek/` config surface remain first-class.
diff --git a/docs/TOOL_SURFACE.md b/docs/TOOL_SURFACE.md
@@ -15,7 +15,7 @@ chosen over the available shell equivalent. Companion to `crates/tui/src/prompts
   for the same backing operation are a model trap — the LLM will alternate
   between them and the cache hit rate suffers.
 
-## Current surface (v0.8.49)
+## Current surface (v0.8.68)
 
 ### File operations
 
@@ -316,7 +316,10 @@ guidance.
 The old one-shot `rlm` model-facing tool is also replaced by persistent
 `rlm_open` / `rlm_eval` / `rlm_configure` / `rlm_close` sessions.
 
-v0.9.0 adds the following hidden-compat aliases (#2682, #2683):
+v0.8.68 ships the following hidden-compat aliases (#2682, #2683, #4132) —
+they are deliberately retained for transcript replay, not scheduled for
+removal (the earlier plan to drop `todo_*` at the next major was
+superseded by #4132):
 
 | Hidden alias | Canonical replacement | Status |
 |---|---|---|
diff --git a/docs/rfcs/3209-workrooms.md b/docs/rfcs/3209-workrooms.md
@@ -1,11 +1,14 @@
 # RFC: CodeWhale Workrooms — Chat-native Threaded Agent Work
 
 **Issue:** #3209
-**Status:** Draft
-**Date:** 2026-06-17
-**Target:** v0.9.0
-
-This document is design scaffolding. The v0.8.62 branch currently carries the
+**Status:** Future RFC — Phase 1 shipped (protocol types + link parser in
+`crates/protocol/src/workroom.rs`); Phase 2 (store, app-server endpoints,
+`resolve_workroom_link` tool, TUI inbox) not started
+**Date:** 2026-06-17 (status refreshed 2026-07-12)
+**Target:** next-major release (previously written as "v0.9.0"; the release
+label is a maintainer decision, not part of this design)
+
+This document is design scaffolding. As of v0.8.68 the tree carries the
 shared protocol types and link parser only; runtime endpoints, mobile UI
 integration, persistent state, and model-visible tools remain follow-up work.
 
diff --git a/docs/rfcs/FILE_DECOMPOSITION_0_9_0.md b/docs/rfcs/FILE_DECOMPOSITION_0_9_0.md
@@ -1,12 +1,22 @@
 # RFC: File Decomposition for v0.9.0
 
+**Status (2026-07-12): still valuable, needs redesign.** The original
+`config.rs` plan was overtaken by events: `config.rs` shrank to ~7.0k lines via
+a different module split (`crates/tui/src/config/`), and the provider-churn
+problem it targeted was mostly solved by the Models.dev catalog + ProviderLake
+(#4184–#4188) rather than by file moves. Meanwhile the render/CLI monoliths
+grew — `ui.rs` 9.4k → 13.6k, `main.rs` 8.0k → 12.1k — so any revival of this
+RFC should re-scope around `ui.rs` and `main.rs`. The migration method
+(§"Migration strategy": git mv + re-exports, no functional changes) remains
+the right approach.
+
 ## Problem
 
 Six files exceed 5,000 lines. The worst offenders accumulate provider-specific
 logic, test code, and UI rendering in single translation units. This makes
 provider additions touch 15+ files and makes code review fragile.
 
-### Current state (lines)
+### Current state (lines, v0.8.6x era — see status note for v0.8.68 numbers)
 
 | File | Lines | Contents |
 |------|-------|----------|
diff --git a/docs/rfcs/HARNESS_PROFILE_CUTLINE.md b/docs/rfcs/HARNESS_PROFILE_CUTLINE.md
@@ -1,6 +1,11 @@
 # Harness Profile Cutline
 
-This note defines the v0.9.0 order for HarnessProfile work. The automatic
+**Status (2026-07-12): Current cutline.** The schema/resolver lane is
+implemented (`crates/config/src/harness.rs`: `HarnessPostureKind`,
+`HarnessProfile`, seed profiles); the status/UX display and runtime use remain
+deferred, and automatic profile evolution stays future work.
+
+This note defines the next-major order for HarnessProfile work. The automatic
 Harness Creator must not run before the profile schema, resolver, seed
 profiles, and user-visible status surfaces are explicit and tested.
 
@@ -71,7 +76,7 @@ and pure resolver checks, the acceptance matrix should record evidence for:
 - a generic/HF/local model resolving to a lean or standard profile;
 - the TUI or runtime status surface showing provider, model, profile, and repo
   constitution separately;
-- no automatic profile mutation during normal Agent or WhaleFlow runs.
+- no automatic profile mutation during normal Agent or Workflow runs.
 
 For v0.9.0, pure resolver tests may satisfy the profile-selection evidence, but
 status display and runtime use remain deferred until separate PRs wire those
diff --git a/docs/rfcs/WORKFLOW_EXTERNAL_MEMORY.md b/docs/rfcs/WORKFLOW_EXTERNAL_MEMORY.md
@@ -1,6 +1,11 @@
 # Workflow External Memory Cutline
 
-This note resolves the v0.9.0 cutline for Aleph-style external memory in
+**Status (2026-07-12): Principle-only cutline — current.** The boundary below
+still holds at v0.8.68. Note the layer table names machinery (TraceStore, the
+ARMH/RLM memo store, the cached-main overlay) that is proposed, not in the
+tree; only user memory (`/memory`, `remember`) and RLM sessions exist today.
+
+This note resolves the next-major cutline for Aleph-style external memory in
 Workflow. It is a design boundary, not a runtime implementation.
 
 ## Decision
