-
Notifications
You must be signed in to change notification settings - Fork 0
[Stage 2.1] Add issue dependency map to contributor backlog #78
Copy link
Copy link
Closed
Labels
agent-friendlyarea: docsgood first contributionEntry-level contribution with clear scope and low project-context costEntry-level contribution with clear scope and low project-context costoss first friendlyFriendly for first open source contributions and automated contributorsFriendly for first open source contributions and automated contributorsstage: 2.1MVP hardening and validation work before Stage 3MVP hardening and validation work before Stage 3status: readyReady for contributors to pick upReady for contributors to pick up
Metadata
Metadata
Assignees
Labels
agent-friendlyarea: docsgood first contributionEntry-level contribution with clear scope and low project-context costEntry-level contribution with clear scope and low project-context costoss first friendlyFriendly for first open source contributions and automated contributorsFriendly for first open source contributions and automated contributorsstage: 2.1MVP hardening and validation work before Stage 3MVP hardening and validation work before Stage 3status: readyReady for contributors to pick upReady for contributors to pick up
Type
Fields
Give feedbackNo fields configured for issues without a type.
Goal: add a contributor-facing issue dependency map to the backlog documentation.
Related plan: #65.
Acceptance criteria:
- Update .github/backlog/ISSUES.md with a Stage 2.1 section.
- Include issue numbers, dependency notes, and suggested merge order.
- Keep Stage 3 dependencies clear without over-constraining contributors.
- Ensure every listed issue has labels.