Repository navigation
docs: add v1 implementation roadmap - #16
Merged
Merged
Conversation
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
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
Adds
docs/roadmap.mdas the implementation-order source of truth for the frozen cpp_request v1 requirements.Roadmap structure
Captured gaps
The roadmap explicitly records remaining frozen-requirement work that was easy to overlook while implementing feature PRs, including:
Result<T>hardeningScope control
The document also restates the frozen v1 exclusions and defines a roadmap-maintenance rule so future scope/order changes are reflected explicitly.
This PR is documentation-only and is intentionally separate from the open Client core PR.