refactor: remove backlog ownership from core cli

CHANGELOG.md

@@ -8,6 +8,20 @@ All notable changes to this project will be documented in this file.
 **Important:** Changes need to be documented below this block as this is the header section. Each section should be separated by a horizontal rule. Newer changelog entries need to be added on top of prior ones to keep the history chronological with most recent changes first.
 
 
+---
+
+## [0.40.2] - 2026-03-06
+
+### Changed
+
+- Finished the backlog ownership cleanup in core: built-in backlog command shims, bundled backlog prompts/templates, and the `backlog-core` package were removed so backlog functionality is owned by the marketplace module instead of `specfact-cli`.
+- Replaced backlog-specific command-group wiring with generic member-group registration so installed modules provide `backlog` and `policy` surfaces without core overlap rules.
+
+### Fixed
+
+- Removed the root cause of duplicate backlog command registration at startup by eliminating the split core-plus-module backlog ownership model.
+- Updated core validation and IDE prompt export expectations so backlog prompt assets are no longer treated as built-in core resources.
+
 ---
 
 ## [0.40.1] - 2026-03-06

README.md

@@ -74,6 +74,8 @@ As of `0.40.0`, flat root commands are removed. Use grouped commands:
 ### Backlog Bridge (60 seconds)
 
 SpecFact's USP is closing the drift gap between **backlog -> specs -> code**.
+These commands require the backlog bundle to be installed first, for example via
+`specfact init --profile backlog-team` or `specfact init --install backlog`.
 
 ```bash
 # 1) Initialize backlog config + field mapping

docs/getting-started/installation.md

@@ -191,7 +191,6 @@ uvx specfact-cli@latest import from-code my-project --repo .
 Fresh install exposes only core commands:
 
 - `specfact init`
-- `specfact backlog auth`
 - `specfact module`
 - `specfact upgrade`
 
@@ -203,6 +202,9 @@ Category groups appear after bundle installation:
 - `specfact spec ...`
 - `specfact govern ...`
 
+Backlog authentication commands such as `specfact backlog auth ...` are provided by the
+installed backlog bundle, not by the permanent core command surface.
+
 Profile outcomes:
 
 | Profile | Installed bundles | Available groups |

docs/getting-started/tutorial-backlog-refine-ai-ide.md

@@ -76,6 +76,8 @@ In Cursor, VS Code, or your IDE:
 2. Pass the same arguments you would use in the CLI, for example:
    - `/specfact.backlog-refine --adapter github --repo-owner OWNER --repo-name NAME --labels feature --limit 5`
 
+These slash prompts are provided by the installed backlog bundle, not by the permanent core CLI package.
+
 The AI will use the **SpecFact Backlog Refinement** prompt, which includes:
 
 - Template-driven refinement (user story, defect, spike, enabler)

docs/getting-started/tutorial-daily-standup-sprint-review.md

@@ -35,6 +35,7 @@ Preferred command path is `specfact backlog ceremony standup ...`. The legacy `s
   The prompt content is always **normalized to Markdown-only text** (no raw HTML tags or HTML entities) so
   ADO-style HTML descriptions/comments and GitHub/Markdown content render consistently.
 - Use the **`specfact.backlog-daily`** (or `specfact.daily`) slash prompt for interactive walkthrough with the DevOps team story-by-story (focus, issues, open questions, discussion notes as comments)
+- The daily standup slash prompt is provided by the installed backlog bundle rather than the permanent core CLI package
 - Filter by **`--assignee`**, **`--sprint`** / **`--iteration`**, **`--search`**, **`--release`**, **`--id`**, **`--first-issues`** / **`--last-issues`**, **`--blockers-first`**, and optional **`--suggest-next`**
 
 ---
@@ -162,7 +163,8 @@ The output includes an instruction to generate a standup summary, the applied fi
 state, sprint, assignee, limit), and the same per-item data as `--copilot-export`. With
 `--comments`/`--annotations`, the prompt includes normalized descriptions and comment annotations when
 supported. Use it with the **`specfact.backlog-daily`** slash prompt for interactive team walkthrough
-(story-by-story, current focus, issues/open questions, discussion notes as comments).
+(story-by-story, current focus, issues/open questions, discussion notes as comments). The slash prompt
+itself is provided by the installed backlog bundle.
 
 ---
 

docs/guides/agile-scrum-workflows.md

@@ -176,6 +176,7 @@ scope: **state=open**, **limit=20**; configure via `SPECFACT_STANDUP_*` or `.spe
 `--copilot-export <path>`, `--summarize`, `--summarize-to <path>`, `--comments`/`--annotations`, and optional
 `--first-comments`/`--last-comments` plus `--first-issues`/`--last-issues` as well as global filters
 `--search`, `--release`, and `--id` to narrow scope consistently with backlog ceremony refinement.
+The slash prompt itself is provided by the installed backlog bundle rather than the permanent core CLI package.
 See [Tutorial: Daily Standup and Sprint Review](../getting-started/tutorial-daily-standup-sprint-review.md)
 for the full walkthrough.
 

docs/guides/ai-ide-workflow.md

@@ -76,7 +76,7 @@ Once initialized, the following slash commands are available in your IDE:
 |---------------|---------|------------------------|
 | `/specfact.compare` | Compare plans | `specfact project plan compare` |
 | `/specfact.validate` | Validation suite | `specfact code repro` |
-| `/specfact.backlog-refine` | Backlog refinement (AI IDE interactive loop) | `specfact backlog refine github \| ado` |
+| `/specfact.backlog-refine` | Backlog refinement (AI IDE interactive loop, provided by the backlog bundle) | `specfact backlog refine github \| ado` |
 
 For an end-to-end tutorial on backlog refine with your AI IDE (story quality, underspecification, DoR, custom templates), see **[Tutorial: Backlog Refine with AI IDE](../getting-started/tutorial-backlog-refine-ai-ide.md)**.
 

docs/guides/devops-adapter-integration.md

@@ -61,7 +61,7 @@ SpecFact CLI supports **bidirectional synchronization** between OpenSpec change
   (instruction + filter context + standup data) for slash command or Copilot to generate a standup summary.
   **Slash prompt** `specfact.backlog-daily` (or `specfact.daily`): use with IDE/Copilot for interactive
   team walkthrough story-by-story (current focus, issues/open questions, discussion notes as comments);
-  prompt file at `resources/prompts/specfact.backlog-daily.md`. **Sprint goal** is stored in your
+  the prompt is provided by the installed backlog bundle rather than the permanent core package. **Sprint goal** is stored in your
   board/sprint settings and is not displayed or edited by the CLI.
 - **Content Sanitization**: Protect internal information when syncing to public repositories
 - **Separate Repository Support**: Handle cases where OpenSpec proposals and source code are in different repositories

docs/index.md

@@ -43,6 +43,8 @@ Recommended command entrypoints:
 ### Backlog Bridge in 60 Seconds
 
 SpecFact closes the drift gap between **backlog -> specs -> code**.
+These commands require the backlog bundle to be installed first, for example via
+`specfact init --profile backlog-team` or `specfact init --install backlog`.
 
 ```bash
 # 1) Initialize backlog config + field mapping