docs: add Continuum stack roadmap projection

[flyingrobots]

Summary

• Add the Continuum Stack Project Slice Plan packet as a versioned projection of GitHub Project docs: document CodeRabbit unblock comment #15.
• Record the roadmap goalpost by goalpost and repository, with GitHub issue and PR coordinates.
• Preserve Project docs: document CodeRabbit unblock comment #15 as one umbrella Project while documenting distinct lanes:
  • Target: 1.0 for the hard Echo 1.0 / Continuum stack release lane.
  • Target: Launchpad for the Continuum website/browser-replay demo lane.
• Add Mermaid Gantt zoom layers for milestones, goalposts, and slices.
• Add project-update guidance for when to post status updates and what each update should say.
• Clarify that GitHub Project docs: document CodeRabbit unblock comment #15 and the linked GitHub issue graph are the operational roadmap authority.

Project repair

Project #15 was repaired in place rather than split into separate Projects:

• Added Target: Launchpad.
• Added Track: Durability.
• Added Track: Bijou.
• Reclassified Launchpad/browser-replay rows out of Target: 1.0 and into Target: Launchpad.
• Reclassified Echo WAL/WSC rows under Track: Durability.
• Filled missing Target, Track, and Goalpost fields on broad release rows.

The current Project split is:

• Target: 1.0: 53 rows.
• Target: Launchpad: 31 rows.

Roadmap authority

This document is not the live tracker. Project #15 and the GitHub issue graph remain authoritative for status, dependencies, assignees, proof state, blockers, and release readiness. If this packet disagrees with GitHub live state, GitHub wins.

Validation

• npx prettier --check CHANGELOG.md docs/design/0037-continuum-stack-project-slice-plan/README.md
• npx markdownlint-cli2 CHANGELOG.md docs/design/0037-continuum-stack-project-slice-plan/README.md
• git diff --check origin/main...HEAD

[coderabbitai]

Warning

Review limit reached

@flyingrobots, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 48 minutes and 29 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 02c04360-c49d-4e13-a471-ae630888c8c9

📥 Commits

Reviewing files that changed from the base of the PR and between 69c6d30 and 5958afb.

📒 Files selected for processing (2)

• CHANGELOG.md
• docs/design/0037-continuum-stack-project-slice-plan/README.md

---

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 and usage tips.}

[flyingrobots]

Scope correction before merge:

This PR currently reflects Project #15 as it stands, but Project #15 appears to be carrying two different planning surfaces in one place:

• broad Continuum Stack Convergence / Echo 1.0 release work
• narrower Launchpad/browser-replay website work powered by Echo + WARP TTD

The broad Project identity still looks correct, but the Target: 1.0 item set includes Launchpad-specific rows that should probably live in a separate Project or be explicitly marked as a demo/deferred track instead of release-critical Continuum launch work.

Please do not merge this projection until the Project scope is corrected and this packet is revised to match the intended authority.

[flyingrobots]

Scope correction completed.

Project #15 was repaired in place as one umbrella Project with lanes rather than being split:

• Added Target: Launchpad.
• Added Track: Durability.
• Added Track: Bijou.
• Reclassified Launchpad/browser-replay rows to Target: Launchpad.
• Reclassified Echo WAL/WSC rows to Track: Durability.
• Filled missing Target, Track, and Goalpost fields on broad release rows.

Current Project lane split:

Target	Rows	Meaning
1.0	53	hard Echo 1.0 / Continuum stack release lane
Launchpad	31	Continuum website/browser-replay demo lane

PR branch was updated in 5958afb so the packet now documents the single-Project multi-lane model instead of treating Launchpad rows as hard 1.0 release work.