From 2e10c45780447c1dbc6132fac2125fcc758b64bb Mon Sep 17 00:00:00 2001 From: Ahmed Mahmud Date: Sat, 14 Nov 2026 13:56:03 +0100 Subject: [PATCH 1/4] docs(backlog): distinguish 100 new issues from historical open backlog --- docs/contributing/wave-backlog-plan.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/contributing/wave-backlog-plan.md b/docs/contributing/wave-backlog-plan.md index a4d7804..fd156f1 100644 --- a/docs/contributing/wave-backlog-plan.md +++ b/docs/contributing/wave-backlog-plan.md @@ -1,8 +1,8 @@ # StellarForge CLI — Stellar Wave Backlog Plan -**Active backlog target:** exactly 100 open GitHub issues per repository, with each contributor-facing issue independently actionable and evidence-backed. +**New-issue creation target:** 100 newly created, contributor-facing Stellar Wave issues for this backlog-generation effort. This is a cumulative creation target, not a cap on the repository's total open-issue count. Historical open issues remain separate and must not be deleted, closed, or counted toward the 100-new-issue target. As of 2026-11-14, 84 new issues (SW-121–SW-204; GitHub issues #302–#385) have been created, leaving 16 additional new issues to reach the target. The expected open-issue total may therefore exceed 100 when historical open issues are included. -The original SW-001–SW-120 catalogue is a candidate inventory, not a quota. Count only currently open issues toward the 100-issue target; exclude pull requests and closed issues. Reconcile every candidate against current `main`, open and merged pull requests, and existing contributor assignments before creating or counting it. Exclude maintainer-only and release-administration tasks from contributor backlog totals. Do not create duplicate, artificial, or already-completed work. Stellar Wave activation and Drips point allocation remain suspended until explicitly authorized. +Count only distinct, newly created issues toward the 100-new-issue target; exclude pull requests, closed issues, historical issues, maintainer-only/release-administration tasks, duplicates, artificial tasks, and work already completed on current `main`. Reconcile every candidate against current `main`, open and merged pull requests, existing contributor assignments, and the sibling `DigiNodes/StellarForge` repository before creation. Preserve all existing historical issues. Stellar Wave activation and Drips point allocation remain suspended until explicitly authorized. This plan defines the dependency graph and contributor taxonomy before GitHub issue creation. It is designed to maximize parallel contribution while preserving the frozen architecture in `docs/contributing/wave-architecture.md`. From ff43ad005965eb24fe96d830a2ffc0bf570bbb6e Mon Sep 17 00:00:00 2001 From: Ahmed Mahmud Date: Sat, 14 Nov 2026 15:12:34 +0100 Subject: [PATCH 2/4] docs(backlog): record completion of 100 new issue target --- docs/contributing/wave-backlog-plan.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/contributing/wave-backlog-plan.md b/docs/contributing/wave-backlog-plan.md index fd156f1..353422e 100644 --- a/docs/contributing/wave-backlog-plan.md +++ b/docs/contributing/wave-backlog-plan.md @@ -1,8 +1,8 @@ # StellarForge CLI — Stellar Wave Backlog Plan -**New-issue creation target:** 100 newly created, contributor-facing Stellar Wave issues for this backlog-generation effort. This is a cumulative creation target, not a cap on the repository's total open-issue count. Historical open issues remain separate and must not be deleted, closed, or counted toward the 100-new-issue target. As of 2026-11-14, 84 new issues (SW-121–SW-204; GitHub issues #302–#385) have been created, leaving 16 additional new issues to reach the target. The expected open-issue total may therefore exceed 100 when historical open issues are included. +**New-issue creation target:** 100 newly created, contributor-facing Stellar Wave issues for this backlog-generation effort. This is a cumulative creation target, not a cap on the repository's total open-issue count. Historical open issues remain separate and must not be deleted, closed, or counted toward the 100-new-issue target. As of 2026-11-14, the target is complete: 100 new issues, SW-121–SW-220 (GitHub issues #302–#402, excluding PR #386). The repository's total open-issue count therefore includes the separate historical backlog and may exceed 100. -Count only distinct, newly created issues toward the 100-new-issue target; exclude pull requests, closed issues, historical issues, maintainer-only/release-administration tasks, duplicates, artificial tasks, and work already completed on current `main`. Reconcile every candidate against current `main`, open and merged pull requests, existing contributor assignments, and the sibling `DigiNodes/StellarForge` repository before creation. Preserve all existing historical issues. Stellar Wave activation and Drips point allocation remain suspended until explicitly authorized. +Count only distinct, newly created issues toward the 100-new-issue target; exclude pull requests, closed issues, historical issues, maintainer-only/release-administration tasks, duplicates, artificial tasks, and work already completed on current `main`. Reconcile every candidate against current `main`, open and merged pull requests, existing contributor assignments, and the sibling `DigiNodes/StellarForge` repository before creation. Preserve all existing historical issues. The 16 additional issues SW-205–SW-220 were created as queued candidates after source review of dev/test process handling, package manifest validation, and project configuration parsing. Stellar Wave activation and Drips point allocation remain suspended until explicitly authorized. This plan defines the dependency graph and contributor taxonomy before GitHub issue creation. It is designed to maximize parallel contribution while preserving the frozen architecture in `docs/contributing/wave-architecture.md`. From 170d0b5fe2ff483a2caf75f467dc950d1c94eed9 Mon Sep 17 00:00:00 2001 From: Ahmed Mahmud Date: Sat, 14 Nov 2026 15:15:22 +0100 Subject: [PATCH 3/4] docs(backlog): clarify cumulative issue creation count --- docs/contributing/wave-backlog-plan.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/contributing/wave-backlog-plan.md b/docs/contributing/wave-backlog-plan.md index 353422e..aa86825 100644 --- a/docs/contributing/wave-backlog-plan.md +++ b/docs/contributing/wave-backlog-plan.md @@ -1,8 +1,8 @@ # StellarForge CLI — Stellar Wave Backlog Plan -**New-issue creation target:** 100 newly created, contributor-facing Stellar Wave issues for this backlog-generation effort. This is a cumulative creation target, not a cap on the repository's total open-issue count. Historical open issues remain separate and must not be deleted, closed, or counted toward the 100-new-issue target. As of 2026-11-14, the target is complete: 100 new issues, SW-121–SW-220 (GitHub issues #302–#402, excluding PR #386). The repository's total open-issue count therefore includes the separate historical backlog and may exceed 100. +**New-issue creation target:** 100 distinct, newly created, contributor-facing Stellar Wave issues for this backlog-generation effort. This is a cumulative creation target, not a cap on the repository's total open-issue count. Count each valid issue created for this effort even if it is later closed; exclude issues that predated this effort, duplicate records, maintainer-only/release-administration tasks, artificial tasks, and work already completed on current `main`. As of 2026-11-14, the target is complete: 100 new issues, SW-121–SW-220 (GitHub issues #302–#402, excluding PR #386). The repository's total open-issue count includes the separate historical backlog and may exceed 100. -Count only distinct, newly created issues toward the 100-new-issue target; exclude pull requests, closed issues, historical issues, maintainer-only/release-administration tasks, duplicates, artificial tasks, and work already completed on current `main`. Reconcile every candidate against current `main`, open and merged pull requests, existing contributor assignments, and the sibling `DigiNodes/StellarForge` repository before creation. Preserve all existing historical issues. The 16 additional issues SW-205–SW-220 were created as queued candidates after source review of dev/test process handling, package manifest validation, and project configuration parsing. Stellar Wave activation and Drips point allocation remain suspended until explicitly authorized. +Count only distinct, newly created issues that represented valid, independently actionable work when created. A later closure, completion, or superseding PR does not erase a valid issue from the cumulative creation count. Do not count pre-existing historical issues, duplicates, maintainer-only/release-administration tasks, artificial tasks, or work already completed on current `main`. Reconcile every candidate against current `main`, open and merged pull requests, existing contributor assignments, and the sibling `DigiNodes/StellarForge` repository before creation. Preserve all existing historical issues. The 16 additional issues SW-205–SW-220 were created as queued candidates after source review of dev/test process handling, package manifest validation, and project configuration parsing. Stellar Wave activation and Drips point allocation remain suspended until explicitly authorized. This plan defines the dependency graph and contributor taxonomy before GitHub issue creation. It is designed to maximize parallel contribution while preserving the frozen architecture in `docs/contributing/wave-architecture.md`. From e52f55f35b5f3668dee9dd269136827d4e51503e Mon Sep 17 00:00:00 2001 From: Ahmed Mahmud Date: Sat, 14 Nov 2026 15:35:52 +0100 Subject: [PATCH 4/4] docs(backlog): record historical and new open issue totals --- docs/contributing/wave-backlog-plan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/wave-backlog-plan.md b/docs/contributing/wave-backlog-plan.md index aa86825..1499710 100644 --- a/docs/contributing/wave-backlog-plan.md +++ b/docs/contributing/wave-backlog-plan.md @@ -1,6 +1,6 @@ # StellarForge CLI — Stellar Wave Backlog Plan -**New-issue creation target:** 100 distinct, newly created, contributor-facing Stellar Wave issues for this backlog-generation effort. This is a cumulative creation target, not a cap on the repository's total open-issue count. Count each valid issue created for this effort even if it is later closed; exclude issues that predated this effort, duplicate records, maintainer-only/release-administration tasks, artificial tasks, and work already completed on current `main`. As of 2026-11-14, the target is complete: 100 new issues, SW-121–SW-220 (GitHub issues #302–#402, excluding PR #386). The repository's total open-issue count includes the separate historical backlog and may exceed 100. +**New-issue creation target:** 100 distinct, newly created, contributor-facing Stellar Wave issues for this backlog-generation effort. This is a cumulative creation target, not a cap on the repository's total open-issue count. Count each valid issue created for this effort even if it is later closed; exclude issues that predated this effort, duplicate records, maintainer-only/release-administration tasks, artificial tasks, and work already completed on current `main`. As of 2026-11-14, the target is complete: 100 new issues, SW-121–SW-220 (GitHub issues #302–#402, excluding PR #386). The repository currently has 117 open issues: those 100 new issues plus 17 historical open issues that predate this effort. Count only distinct, newly created issues that represented valid, independently actionable work when created. A later closure, completion, or superseding PR does not erase a valid issue from the cumulative creation count. Do not count pre-existing historical issues, duplicates, maintainer-only/release-administration tasks, artificial tasks, or work already completed on current `main`. Reconcile every candidate against current `main`, open and merged pull requests, existing contributor assignments, and the sibling `DigiNodes/StellarForge` repository before creation. Preserve all existing historical issues. The 16 additional issues SW-205–SW-220 were created as queued candidates after source review of dev/test process handling, package manifest validation, and project configuration parsing. Stellar Wave activation and Drips point allocation remain suspended until explicitly authorized.