Skip to content

docs: record Continuum stack release roadmap#36

Merged
flyingrobots merged 1 commit into
mainfrom
docs/continuum-stack-release-roadmap
Jun 21, 2026
Merged

docs: record Continuum stack release roadmap#36
flyingrobots merged 1 commit into
mainfrom
docs/continuum-stack-release-roadmap

Conversation

@flyingrobots

@flyingrobots flyingrobots commented Jun 20, 2026

Copy link
Copy Markdown
Owner

Summary

  • adds docs/design/0036-continuum-stack-release-roadmap/README.md as the stable Continuum-owned release path for Echo 1.0 / stack convergence
  • records GP0-GP6, gate ownership, evidence requirements, closure rules, and the GP1 Echo durability handoff
  • updates the existing convergence packet so Project docs: document CodeRabbit unblock comment #15 is the release authority and the retired Echo-only Project is not
  • updates the changelog

Validation

  • npx prettier --check CHANGELOG.md docs/design/0035-continuum-stack-convergence/README.md docs/design/0036-continuum-stack-release-roadmap/README.md
  • npx markdownlint-cli2 CHANGELOG.md docs/design/0035-continuum-stack-convergence/README.md docs/design/0036-continuum-stack-release-roadmap/README.md
  • git diff --check

@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown

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 33 minutes and 37 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: 44264e6f-61ac-478d-989e-372aeee9d632

📥 Commits

Reviewing files that changed from the base of the PR and between ab5c87e and 6bc6f45.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • docs/design/0035-continuum-stack-convergence/README.md
  • docs/design/0036-continuum-stack-release-roadmap/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

Comment @coderabbitai help to get the list of available commands and usage tips.

@flyingrobots flyingrobots moved this from Todo to In Progress in Continuum Stack Convergence Jun 21, 2026
@flyingrobots flyingrobots merged commit 69c6d30 into main Jun 21, 2026
1 check passed
@flyingrobots flyingrobots deleted the docs/continuum-stack-release-roadmap branch June 21, 2026 00:01
@github-project-automation github-project-automation Bot moved this from In Progress to Done in Continuum Stack Convergence Jun 21, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6bc6f4572e

ℹ️ 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".

The roadmap in this packet is not a work queue. The live control surface is:

- Project: [Continuum Stack Convergence](https://github.com/users/flyingrobots/projects/15)
- Seed Project: [Continuum Stack Convergence Template](https://github.com/users/flyingrobots/projects/16)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Point the seed project at an accessible Project

When a maintainer or agent follows this live control surface, the Project #16 link currently returns a GitHub 404 while Project #15 is reachable, so the roadmap cannot use it as the copyable seed or as GP0 evidence. Either create/publish the seed Project or replace this link before making the roadmap canonical.

Useful? React with 👍 / 👎.

Comment on lines +166 to +167
- Echo's release contract points to the stack Project instead of maintaining a
live repository roadmap.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align Echo release authority before claiming GP0 evidence

The canonical Echo release bar linked in this packet still names the Echo 1.0 Convergence GitHub Project as the live roadmap authority and its exit criteria require active slices there, so this GP0 evidence is false unless echo#584 is updated. Agents following the new roadmap will otherwise see conflicting authorities between Continuum Project #15 and the Echo issue.

Useful? React with 👍 / 👎.

Comment on lines +193 to +194
- [echo#521](https://github.com/flyingrobots/echo/issues/521):
WAL/WSC Storage Relationship

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Put the GP1 umbrella in the live Project

When an agent starts GP1 from this primary issue family, echo#521 is the parent umbrella with the sub-issue progress but its GitHub metadata currently says No projects, while this packet says live status stays in Project #15. That leaves the advertised GP1 parent/status invisible from the live control surface unless #521 is added to Project #15 or documented as background-only.

Useful? React with 👍 / 👎.

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

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant