docs: triage M4 pending todos and scope closeout phases 74-79#605
Merged
Conversation
…very, annotate 68.2 backlog Retire to completed/ with resolution notes: - web-e2e-flaky-cascade-abort — resolved by PR #593 (file-level parallelism) - rotation-hardening-followups-from-pr-review — all 6 closed by Phase 70 + 70.1 - add-permanent-delete-confirmation-dialog — ConfirmDialog gates delete (D-02 per-mode wording caveat noted) - shared-write-base-aware-merge-parity — NOT APPLICABLE: shared-write.ts has no CAS-409 merge path (strict publishOrThrow), so the resurrection vector cannot occur Merge duplicate recovery-v3 todos: fold 2026-06-29-recovery-html-vault-v3-migration into the fuller 2026-07-03-port-recovery-tool-to-v3-vault-format (supersedes + vault-v3-blob.json note). Annotate 68.2 CodeRabbit backlog after re-verifying against HEAD/#603: mark item 1 RESOLVED (72-06 listingCache.delete), item 4 RESOLVED (73-05, ROT-07 residual deferred), item 7 PARTIAL (generation assertion done; fail-closed + selectEncryptionMode still open); 8 items remain open. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Z3zThQZPm6bVk2476WURL Entire-Checkpoint: 22aff8d89af6
Add five closeout phases to the active v2.0 milestone (Phases 61-78) with goals, success criteria, dependencies, and per-phase source-todo lists: - Phase 74: Rust/FUSE Rotation-Revocation Soundness (3 todos) - Phase 75: Cross-Language IPNS/Node-Codec Verification Parity (4 todos) - Phase 76: FUSE Durability + TEE Write-Path Hardening (4 todos) - Phase 77: Crypto Hygiene + Terminology Canonicalization (12 todos) - Phase 78: Recovery Tool v3 + Web UX + CI Guards (5 todos) Stamp resolves_phase on all 28 M4 closeout todos; the 10 non-M4 todos (M5 features, infra/ops, tech-debt, parked FUSE-T) are left unstamped. Retire confirm-no-legacy-v1-v2-vault-blobs (WON'T DO — user: no migration, all legacy vaults deprecated; the deserializeVaultBlobV3 hard-cut stands as the D-05 guard). Update ROADMAP milestone header/checklist and STATE roadmap-evolution + phase count (16 -> 21). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Z3zThQZPm6bVk2476WURL Entire-Checkpoint: 07289de753be
…deferred test revival Triaging the 83 TODO(phase 63/65) markers found ~40 that are not stale: the web listing UI never got routed through ResolvedChild.kind (added in 68.2), so folders-first sort, drag-and-drop, and kind-aware dialog labels never returned after the Phase 62 cutover, createdAt is still stubbed in details panes, and four test suites remain describe.skip'd. - Add Phase 79 to the active v2.0 milestone (now Phases 61-79) with grouped scope, success criteria, and the full still-valid marker inventory - Add consolidating pending todo (resolves_phase: 79) - Update ROADMAP header/checklist and STATE roadmap-evolution (phase count -> 22) The 43 stale markers (63/65 shipped, code migrated) are removed separately as a pure comment cleanup on a code branch. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Z3zThQZPm6bVk2476WURL Entire-Checkpoint: ab67c91ff365
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (43)
✨ 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 |
Contributor
Release PreviewNo version bumps detected. All changes are in unversioned paths or use exempt commit types. |
Greptile SummaryThis PR reorganizes the M4 closeout planning backlog. The main changes are:
Confidence Score: 4/5The planning state cursor needs a fix before merging.
.planning/STATE.md Important Files Changed
Reviews (1): Last reviewed commit: "docs(roadmap): add Phase 79 for web kind..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Comment on lines
5
to
17
| current_phase: 73 | ||
| status: executing | ||
| stopped_at: Completed 72-10-PLAN.md | ||
| last_updated: "2026-07-10T20:34:21.059Z" | ||
| last_updated: "2026-07-10T23:36:09.597Z" | ||
| last_activity: 2026-07-10 | ||
| last_activity_desc: Phase 73 complete | ||
| progress: | ||
| total_phases: 16 | ||
| total_phases: 22 | ||
| completed_phases: 15 | ||
| total_plans: 189 | ||
| completed_plans: 188 | ||
| percent: 94 | ||
| percent: 68 | ||
| current_phase_name: shared-write-navigation-correctness-web |
There was a problem hiding this comment.
When the next planning command resumes from this state, it still sees Phase 73 as the executing phase even though this PR marks Phase 73 complete and adds Phases 74–79 as the open closeout work. The stale current_phase, current_phase_name, and stopped_at values can send follow-up plans back through the shipped Phase 73/old Phase 72 boundary instead of starting Phase 74.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Triage of the
.planning/todos/pending/backlog and the repo-wideTODO(phase 63/65)code markers, scoping the remaining M4 (v2.0 Metadata and Sharing Refactor) closeout work into phases. Planning-only — no code changes (the marker code cleanup is a separate PR).Todo bookkeeping
Retired to
completed/with resolution notes:web-e2e-flaky-cascade-abort— resolved by#593(file-level parallelism)rotation-hardening-followups-from-pr-review— all 6 closed by Phase 70 + 70.1add-permanent-delete-confirmation-dialog—ConfirmDialoggates delete (D-02 per-mode wording caveat noted)shared-write-base-aware-merge-parity— NOT APPLICABLE:shared-write.tshas no CAS-409 merge path, so the resurrection vector cannot occurconfirm-no-legacy-v1-v2-vault-blobs— WON'T DO (no migration; legacy vaults deprecated; the v3 hard-cut stands as the D-05 guard)Merged the two duplicate recovery-v3 todos into one; annotated the 68.2 CodeRabbit backlog after re-verifying against HEAD (2 resolved, 1 partial, 8 open).
New closeout phases (61–79 milestone)
28 M4 todos stamped with
resolves_phase; the 10 non-M4 todos (M5 features, infra/ops, tech-debt, parked FUSE-T) are left unstamped. ROADMAP header/checklist + STATE roadmap-evolution updated (22 phases).Phase 79 was surfaced by triaging the 84
TODO(phase 63/65)markers: ~40 are still-valid and describe a real shipped gap (the web listing UI never got routed throughResolvedChild.kind).🤖 Generated with Claude Code
https://claude.ai/code/session_012Z3zThQZPm6bVk2476WURL