✨ docs(v0.2): add milestone and issue scoping plan with gh creation script#24
Merged
Conversation
Scopes the v0.2 GitHub milestone and its 10 issues (5 security-hardening SEC-1..5 plus 5 backlog BL-1..5, and an optional SEC-0 tracking epic), folding the agent blast-radius remediation lists into the existing v0.2 backlog. Includes EARS bodies, acceptance criteria, cross-references, and a re-runnable gh milestone/label/issue creation script. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Merge the v0.2 requirements, the sourcebooks MCP design review, and the OCR/licensing follow-ups (formerly specs_v0.2.md) into the single v0.2-milestone-plan.md: the forward backlog stays as the BL-1..5 issues; the detailed design review and the R-1..R-5 record (incl. R-1E kreuzberg evidence) move to appendices B and C. Delete specs_v0.2.md and repoint its live references (README, THIRD_PARTY_NOTICES, dependabot.yml, create-issues.sh) to the merged doc; CHANGELOG history left as-is. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Reconcile four drifts between the issue-creation script and the plan doc: adopt the richer milestone description in all copies; comment out the unused priority labels in Appendix A to match the script; correct the issue count (ten -> eleven, SEC-0..5 + BL-1..5) in both the Contents summary and the verification step; standardize the SEC-0 title tag on [epic]. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Scopes the v0.2 GitHub milestone and its 10 issues (5 security-hardening SEC-1..5 plus 5 backlog BL-1..5, and an optional SEC-0 tracking epic), folding the agent blast-radius remediation lists into the existing v0.2 backlog. Includes EARS bodies, acceptance criteria, cross-references, and a re-runnable gh milestone/label/issue creation script.
Summary
re-runnable
ghcreation script (specs/v0.2/create-issues.sh).Folds the agent blast-radius security remediation into the existing v0.2 backlog under one
v0.2milestone: 5 security issues (SEC-1..5) plus an optional tracking epic (SEC-0), and5 backlog issues (BL-1..5) from
specs_v0.2.md.Key decisions captured:
:rostatic PDFs, narrow RW vault + code), chosen overvolume-clone after a data-classification and Linux-host review.
Each issue has an EARS body, acceptance criteria, and cross-refs to
specs_v0.2.md/SecurityReview.md.Notes
specs/v0.2/); no code or CI touched.create-issues.shis idempotent (labels via--force, issues skipped if the title exists)and requires
gh auth login.tracked by the issues.