README has stale [planned] markers for shipped features

[frankbria]

Summary

The README still marks several shipped commands as `[planned]`, which is misleading for users and embarrassing at launch. These features are all fully implemented.

Stale Markers (line numbers in README.md)

Line	Command	Status
29	`cf prd stress-test`	✅ Shipped in #421
37	`cf proof run`	✅ Shipped in #422
38	`cf proof capture`	✅ Shipped in #422
121	`cf proof run` (diagram)	✅ Shipped in #422

Also Missing from README

• Kilocode engine — just added in feat(engines): add Kilocode engine adapter (#417) #451; README engine list shows Claude Code, Codex, OpenCode, or built-in but not Kilocode
• Replay/debug mode (cf work replay) — shipped in feat(replay): debug and replay mode (#315) #449
• TUI dashboard (cf tui) — shipped in feat(tui): terminal dashboard with Textual (#313) #448
• Dynamic config reload — shipped in feat(config): dynamic configuration reload during batch execution (#402) #450
• PROOF9 proof gate commands beyond run/capture (cf proof list, cf proof waive, cf proof status, cf proof show)

Acceptance Criteria

• Remove all [planned] markers for shipped features
• Add Kilocode to the engine list
• Add replay mode, TUI dashboard, and PROOF9 commands to feature table
• Update README status badge from "v2 Active Development" if launching

[coderabbitai]

🔗 Related PRs

#32 - Fix Key Features section formatting in README [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[traycerai]

Plan

Observations

The file:README.md has four concrete problems:

1. Three [planned] markers on lines 29, 37, 38, and 121 for features already shipped.
2. The engine list on line 22 omits Kilocode.
3. The CLI Reference → PROVE section (lines 204–210) is missing cf proof list, cf proof waive, cf proof status, cf proof show, cf work replay, and cf tui.
4. The Roadmap section (lines 240–267) still lists PROOF9 commands and cf prd stress-test as unshipped [ ] items, and the "What Works Today" section (line 227) is out of date.
5. The status badge on line 5 reads v2 Active Development, which may need updating at launch.

Approach

All changes are confined to file:README.md. Each fix is surgical and ordered top-to-bottom through the file to avoid merge conflicts and keep the diff reviewable.

---

Implementation Steps

1. Update the status badge (line 5)

Change the badge URL text from v2%20Active%20Development to an appropriate launched label (e.g., v2%20Released or v2%20Stable) to reflect that the product is no longer in active pre-launch development.

---

2. Remove [planned] from the THINK/BUILD/PROVE/SHIP code block (lines 26–50)

Line	Current text	Required change
29	cf prd stress-test … [planned]	Remove [planned]
37	cf proof run … [planned]	Remove [planned]
38	cf proof capture … [planned]	Remove [planned]

Preserve alignment/spacing of the surrounding block.

---

3. Add Kilocode to the engine description (line 22)

Change:

Claude Code, Codex, OpenCode, or CodeFRAME's built-in ReAct agent

To:

Claude Code, Codex, OpenCode, Kilocode, or CodeFRAME's built-in ReAct agent

---

4. Remove [planned] from the Architecture diagram (line 121)

Change:

|  cf proof run       9-gate quality system [planned]|

To:

|  cf proof run       9-gate quality system          |

---

5. Expand the CLI Reference → PROVE section (lines 204–210)

Add the missing shipped PROOF9 commands and the new top-level commands. The updated block should include:

cf proof run                          # Run all 9 proof gates
cf proof capture                      # Capture glitch as permanent requirement
cf proof list                         # List all proof obligations
cf proof status                       # Summary status across all gates
cf proof show <id>                    # Detail for a specific proof obligation
cf proof waive <id> "reason"          # Waive an obligation with justification
cf work replay <id>                   # Replay/debug a past execution
cf tui                                # Launch TUI dashboard
cf review                             # Run verification gates
cf checkpoint create "milestone"      # Snapshot project state
cf checkpoint list                    # List checkpoints
cf checkpoint restore <id>            # Roll back to checkpoint

---

6. Update the "What Works Today" section (lines 227–235)

Extend the PROVE bullet and add new items to reflect shipped features:

• PROVE: Add PROOF9 9-gate system, cf proof run/capture/list/status/show/waive.
• BUILD: Add cf work replay (replay/debug mode).
• Add a new TUI bullet: cf tui dashboard.
• Add Dynamic config reload to the relevant section.

Also update the phase label from v2 (Phase 2.5 complete) to the current phase.

---

7. Update the Roadmap section (lines 240–267)

Move shipped items from [ ] to [x] (or remove them from the roadmap entirely if they are fully done):

Section	Item	Action
THINK	cf prd stress-test	Mark [x]
PROVE	PROOF9 — 9-gate evidence-based quality system	Mark [x]
PROVE	cf proof capture	Mark [x]
BUILD	Agent adapter architecture (Claude Code, Codex, OpenCode, Kilocode)	Mark [x] if shipped

Add new [x] entries for:

• cf work replay — Replay/debug mode
• cf tui — TUI dashboard
• Dynamic config reload

Import In IDE

🤖 Prompt for AI Agents

## Observations

The `file:README.md` has four concrete problems:
1. Three `[planned]` markers on lines 29, 37, 38, and 121 for features already shipped.
2. The engine list on line 22 omits **Kilocode**.
3. The **CLI Reference → PROVE** section (lines 204–210) is missing `cf proof list`, `cf proof waive`, `cf proof status`, `cf proof show`, `cf work replay`, and `cf tui`.
4. The **Roadmap** section (lines 240–267) still lists PROOF9 commands and `cf prd stress-test` as unshipped `[ ]` items, and the **"What Works Today"** section (line 227) is out of date.
5. The status badge on line 5 reads `v2 Active Development`, which may need updating at launch.

## Approach

All changes are confined to `file:README.md`. Each fix is surgical and ordered top-to-bottom through the file to avoid merge conflicts and keep the diff reviewable.

---

## Implementation Steps

### 1. Update the status badge (line 5)

Change the badge URL text from `v2%20Active%20Development` to an appropriate launched label (e.g., `v2%20Released` or `v2%20Stable`) to reflect that the product is no longer in active pre-launch development.

---

### 2. Remove `[planned]` from the THINK/BUILD/PROVE/SHIP code block (lines 26–50)

| Line | Current text | Required change |
|------|-------------|-----------------|
| 29 | `cf prd stress-test … [planned]` | Remove `[planned]` |
| 37 | `cf proof run … [planned]` | Remove `[planned]` |
| 38 | `cf proof capture … [planned]` | Remove `[planned]` |

Preserve alignment/spacing of the surrounding block.

---

### 3. Add Kilocode to the engine description (line 22)

Change:
> `Claude Code, Codex, OpenCode, or CodeFRAME's built-in ReAct agent`

To:
> `Claude Code, Codex, OpenCode, Kilocode, or CodeFRAME's built-in ReAct agent`

---

### 4. Remove `[planned]` from the Architecture diagram (line 121)

Change:
```
|  cf proof run       9-gate quality system [planned]|
```
To:
```
|  cf proof run       9-gate quality system          |
```

---

### 5. Expand the CLI Reference → PROVE section (lines 204–210)

Add the missing shipped PROOF9 commands and the new top-level commands. The updated block should include:

```
cf proof run                          # Run all 9 proof gates
cf proof capture                      # Capture glitch as permanent requirement
cf proof list                         # List all proof obligations
cf proof status                       # Summary status across all gates
cf proof show <id>                    # Detail for a specific proof obligation
cf proof waive <id> "reason"          # Waive an obligation with justification
cf work replay <id>                   # Replay/debug a past execution
cf tui                                # Launch TUI dashboard
cf review                             # Run verification gates
cf checkpoint create "milestone"      # Snapshot project state
cf checkpoint list                    # List checkpoints
cf checkpoint restore <id>            # Roll back to checkpoint
```

---

### 6. Update the "What Works Today" section (lines 227–235)

Extend the **PROVE** bullet and add new items to reflect shipped features:

- **PROVE**: Add PROOF9 9-gate system, `cf proof run/capture/list/status/show/waive`.
- **BUILD**: Add `cf work replay` (replay/debug mode).
- Add a new **TUI** bullet: `cf tui` dashboard.
- Add **Dynamic config reload** to the relevant section.

Also update the phase label from `v2 (Phase 2.5 complete)` to the current phase.

---

### 7. Update the Roadmap section (lines 240–267)

Move shipped items from `[ ]` to `[x]` (or remove them from the roadmap entirely if they are fully done):

| Section | Item | Action |
|---------|------|--------|
| THINK | `cf prd stress-test` | Mark `[x]` |
| PROVE | `PROOF9 — 9-gate evidence-based quality system` | Mark `[x]` |
| PROVE | `cf proof capture` | Mark `[x]` |
| BUILD | Agent adapter architecture (Claude Code, Codex, OpenCode, Kilocode) | Mark `[x]` if shipped |

Add new `[x]` entries for:
- `cf work replay` — Replay/debug mode
- `cf tui` — TUI dashboard
- Dynamic config reload

---

Execution Information

Branch: main
Commit: 4308b0a

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.