chore: wish housekeeping — mark 14 shipped, 3 obsolete - #1076
Conversation
Audit all 80+ wishes against dev codebase. 17 had stale statuses: SHIPPED (14): - unified-omni-bridge (PRs #1063, #1065) - fix-omni-bridge-hardening (PR #1065) - unified-executor-layer (PR #1062) - auto-orchestrate, fix-depends-parser, parallel-execution - task-projects, test-pg-ram-isolation, task-auto-close-on-merge - worktree-out-of-repo, docs-overhaul, genie-hacks-community-docs - multi-agent-session-isolation, session-auto-create OBSOLETE (3): - genie-omni-marriage (superseded by smaller wishes) - fix-session-uuid-resume (replaced by --continue by name) - qa-dev-to-main (time-bound QA from March 20)
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5e66cee764
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # Wish: Documentation & Prompt Overhaul | ||
|
|
||
| **Status:** DRAFT | ||
| **Status:** SHIPPED |
There was a problem hiding this comment.
syncWishes() derives status via parseWishStatus() (src/lib/wish-sync.ts), which only matches table rows like | **Status** | ... | and otherwise falls back to DRAFT. This change switches the wish to **Status:** SHIPPED, so the sync path will continue storing this wish as DRAFT, making backlog/status queries inaccurate even after this housekeeping update.
Useful? React with 👍 / 👎.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the status of numerous wish documents, transitioning them from states such as DRAFT or APPROVED to SHIPPED or OBSOLETE. The review feedback highlights an inconsistency in how metadata is formatted across these files, which currently use a mix of Markdown tables, bolded key-value pairs, and YAML frontmatter. It is suggested to standardize these files using YAML frontmatter to improve consistency and support automated parsing.
| # Wish: Documentation & Prompt Overhaul | ||
|
|
||
| **Status:** DRAFT | ||
| **Status:** SHIPPED |
There was a problem hiding this comment.
While this PR does a great job of updating the status of many wishes, I've noticed that the format for wish metadata (like Status, Slug, Created) is inconsistent across the different WISH.md files. Some use YAML frontmatter, some use markdown tables, and others (like this one) use bolded key-value pairs.
To improve consistency and make these files easier to parse automatically, it would be beneficial to standardize on a single format. YAML frontmatter seems like a good choice as it's already used in some wishes (e.g., genie-hacks-community-docs) and is highly machine-readable.
For example, this file's metadata block could be converted to YAML frontmatter:
---
status: SHIPPED
slug: docs-overhaul
created: 2026-03-16
---
# Wish: Documentation & Prompt OverhaulSince this PR is already focused on housekeeping and touches many wish files, it could be a good opportunity to apply this standardization across all of them for better maintainability.
1 participant
Summary
SHIPPED (14)
unified-omni-bridge(PRs feat: unified omni bridge — one lane for all agents #1063, fix(omni): bridge hardening — lifecycle, PG degraded mode, liveness #1065)fix-omni-bridge-hardening(PR fix(omni): bridge hardening — lifecycle, PG degraded mode, liveness #1065)unified-executor-layer(PR feat(omni): unified executor layer — merge World B into World A #1062)auto-orchestrate,fix-depends-parser,parallel-executiontask-projects,test-pg-ram-isolation,task-auto-close-on-mergeworktree-out-of-repo,docs-overhaul,genie-hacks-community-docsmulti-agent-session-isolation,session-auto-createOBSOLETE (3)
genie-omni-marriage— superseded by individual smaller wishesfix-session-uuid-resume— UUID approach replaced by--continueby session nameqa-dev-to-main— time-bound QA wish from March 20Remaining actionable wishes
After this cleanup, the backlog is:
Test plan
bun test— 2163 pass, 0 fail.genie/wishes/*/WISH.mdstatus fields changed — no code changes