docs(issues): add specification for #2107 - #2108
Merged
josecelano merged 3 commits intoAug 28, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds the approved issue specification for #2107 (persistence-free v3 runtime composition) and updates the configuration-overhaul EPIC (#1978) documentation to include and sequence the new subissue after #999 and #1980.
Changes:
- Add new open-issue spec document for #2107, including scope, acceptance criteria, verification plan, and progress tracking.
- Update EPIC #1978 subissue table and delivery graph to include #2107 and mark #1980 as DONE after PR #2103 merged.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/issues/open/2107-1978-activate-persistence-free-v3-runtime-composition.md | New specification for #2107, detailing persistence-free runtime composition requirements and verification. |
| docs/issues/open/1978-configuration-overhaul-epic/EPIC.md | Adds #2107 to EPIC links/table/graph and updates #1980 status; needs small consistency fixes in remaining narrative/log text. |
Suppressed comments (1)
docs/issues/open/1978-configuration-overhaul-epic/EPIC.md:306
- This progress-log entry hardcodes #2067 as the “thirteenth” native sub-issue, but after adding #2107 the table now numbers #2067 as subissue #15. To avoid future renumbering drift, prefer wording that doesn’t encode the ordinal position.
- 2026-08-28 00:00 UTC - GitHub Copilot/User - Created approved feature subissue #2107 for
persistence-free v3 runtime activation and linked it natively to this EPIC. It follows #999 and
#1980, preserves REST API availability, and makes disabled whitelist/key routes return controlled
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Member
Author
|
ACK f33706b |
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
Scope
Documentation only: the implementation of persistence-free composition, capability-aware REST API responses, and container behavior is intentionally not included.
Validation
cargo machete --with-metadata,cargo deny check bans,linter all, andcargo test --doc --workspacegit diff --checkRelated to #2107