chore(roadmap): publish the local board and retire stale planning cards

[automagik-genie]

Why

genie task sync has reported "both the local board and roadmap.json changed" on every hook run since 2026-08-30, and the committed .genie/roadmap.json has been stale since 2026-08-13.

Root cause: the 2026-08-29 export of the local board only reached the unmerged branch recovery/orca-drain/genie-main-20260830 (efc5ff0fa). The 2026-08-30 Orca-drain reset reverted the working-tree file to the committed content, but the gitignored sync baseline .genie/roadmap-sync still held that export's hash. Verified by hashing with the sync's own canonical algorithm: the baseline matches the recovery-branch file exactly and neither side today. Since then the file side read as "changed" and the db side kept accumulating cards, so the three-way sync refused to touch anything and the fail-open hooks never re-exported.

What

Two commits, deliberately separate so the prune is a one-command revert:

1. Publish the local board untouched (84 cards). The local db was a strict superset of the committed snapshot apart from the six khal-rebrand cards, which INDEX.md records as relocated to the desktop repo. No shared card differed.
2. Retire 21 stale ready cards whose own records say the plan is dead (relocated khal-native-theme, retired ui-bridge and desktop live-dev-loop, the never-executed July jar-triage plan, the unrun roadmap-truth follow-up, and the delegate-bridge wave superseded by Orca owning dispatch), and mark the shipped skills-everywhere umbrella card done. Done cards stay as history.

Resulting board: 63 cards, 61 done, 1 ready (Genie cleanup release), 1 in progress (DSH board G3).

Revert the prune

git show <commit-1>:.genie/roadmap.json > .genie/roadmap.json
genie task import --replace

🤖 Generated with Claude Code

https://claude.ai/code/session_012RU32tvczV84Ys9kHVtEQD

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 718fc89a-5293-441b-be39-fce278ca8412

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6f857410a6

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Preserve the pre-prune board in a separate commit

When an operator needs to undo the pruning, this reviewed commit provides no recoverable pre-prune revision: it has only parent e5cac71, whose stale snapshot contains 59 tasks, while this combined revision both publishes 31 newer tasks and removes 21 stale cards. Consequently, following the advertised rollback by restoring the parent would discard the newly published tasks and their history rather than merely undoing the prune. Split the 84-card publication and the pruning into consecutive commits so the prune's parent is the complete pre-prune snapshot.

Useful? React with 👍 / 👎.