Skip to content

docs: update ROADMAP with completed phases and cross-cutting work - #76

Open
Mark7888 wants to merge 1 commit into
masterfrom
claude/dreamy-hawking-bnlkn2
Open

Mark7888 wants to merge 1 commit into
masterfrom
claude/dreamy-hawking-bnlkn2

Conversation

@Mark7888

Copy link
Copy Markdown
Owner

Updates docs/internal/ROADMAP.md to reflect the current state of the project after all numbered phases have landed and several cross-cutting features have shipped.

Summary

The roadmap is reorganized to document that all phases P0–P11 have now completed, with P8 (Release) marked as "mostly done" pending E2E drills and SECURITY.md. Work since P7 is now tracked as cross-cutting features in a new "Work beyond the phases" section, each with its own plan in docs/internal/plans/ and one PR per step.

Key changes

Notable details

  • Clarifies that P6 and P7 were the only phases allowed to run in parallel; everything else is strictly sequential
  • Explains the shift from one-phase-one-PR to cross-cutting features with their own plans and per-step PRs
  • Reorganizes P8 content to separate completed work from open items
  • Updates references to reflect that joiner-emitted pairing was the first such cross-cutting change, not the last
  • Adds context on smaller app work (file previews, share sheets, tray badges, first-run wizard, licensing) that landed without formal plans

The roadmap still showed P8 as next and P9 and P10 as in review, and
had no record of the work since P7. Checked against the merged PRs,
the release tags and the code:

- Mark P9 (#26) and P10 (#35, #36) done, add PR numbers to P3-P7 and
  the persistent store's follow-ups, and add the relay trust
  hardening work in review (#54, #55).
- Split P8 into what shipped (tagged releases since v1.0.0, the docs
  site, the interop and integration tests, CodeQL) and what is still
  open (a dedicated /e2e drill suite and SECURITY.md).
- Add a table of the cross-cutting features since P7 with their PRs
  and plans, and mark joiner-emitted pairing done (#11).
- Say in the backlog that the relay refuses ADMIN_PASSWORD_HASH and
  that the Linux desktop build is for development only.
- Set the status lines of the versioning and admin REST API plans,
  which still read "proposed" and "not started".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VGT5JCFgChDgMLGFSL2A4t

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants