nold-ai · djm81 · Mar 25, 2026 · Feb 6, 2026 · Feb 6, 2026 · Feb 6, 2026
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -7,6 +7,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.42.5] - 2026-03-25
+
+### Added
+
+- `specfact init ide` builds a prompt-source catalog from **core** (bundled or repo `resources/prompts`) plus installed modules across builtin, project, user, and marketplace roots; defaults to exporting all sources; supports `--prompts` for non-interactive selection (`all`, `core`, comma-separated module ids) and an interactive multi-select when multiple sources exist.
+- IDE prompt exports are written under per-source subfolders (for example `.cursor/commands/core/`, `.cursor/commands/<owner>__<module>/`) so filenames stay collision-safe.
+- Startup IDE template drift checks resolve exports under the namespaced layout (flat or nested).
+
+### Fixed
+
+- VS Code / Copilot: `chat.promptFilesRecommendations` lists only prompt sources actually exported by `init ide`; selective `--prompts` no longer leaves stale `.github/prompts/...` entries from unexported modules.
+- Integration tests: restore module discovery / installer paths after the command-audit temp-home scenario so later unit tests do not observe leaked marketplace module roots.
 
 ---
 
@@ -391,27 +405,14 @@ All notable changes to this project will be documented in this file.
   - Unit test and TDD evidence for CrossHair per-path timeout passthrough.
 - **Init module discovery alignment** (backlog-core-01): `specfact init` now uses the same module discovery roots as command registration (`discover_all_package_metadata()`), so `--list-modules`, `--enable-module`, and `--disable-module` operate on all discovered modules including workspace-level ones (e.g. `modules/backlog-core/`). Closes [#116](https://github.com/nold-ai/specfact-cli/issues/116) scope for init-module-discovery-alignment.
 - **Patch mode module** (patch-mode-01, [#177](https://github.com/nold-ai/specfact-cli/issues/177)): `specfact patch apply <patchfile>` for local apply with preflight; `specfact patch apply --write --yes` for explicit upstream write orchestration and idempotency (`check_idempotent` / `mark_applied`).
-
-### Changed
-
-- `specfact init` module state and validation now build from `discover_all_package_metadata()` instead of `discover_package_metadata(get_modules_root())`, aligning enable/disable and list-modules with runtime command discovery.
-
-### Fixed
-
-- `specfact repro --crosshair-per-path-timeout 0` (or negative) now fails with a clear error instead of being silently ignored; CLI rejects non-positive CrossHair per-path timeout values.
-
----
-## [Unreleased]
-
-### Added
-
 - Architecture documentation remediation for OpenSpec change `arch-08-documentation-discrepancies-remediation`:
   - New architecture implementation status page: `docs/architecture/implementation-status.md`.
   - New ADR set with template and initial ADR: `docs/architecture/adr/`.
   - New module development guide: `docs/guides/module-development.md`.
 
 ### Changed
 
+- `specfact init` module state and validation now build from `discover_all_package_metadata()` instead of `discover_package_metadata(get_modules_root())`, aligning enable/disable and list-modules with runtime command discovery.
 - Reworked architecture references to align with implemented behavior:
   - `docs/reference/architecture.md`
   - `docs/architecture/README.md`
@@ -428,6 +429,8 @@ All notable changes to this project will be documented in this file.
 
 ### Fixed
 
+- `specfact repro --crosshair-per-path-timeout 0` (or negative) now fails with a clear error instead of being silently ignored; CLI rejects non-positive CrossHair per-path timeout values.
+
 ---
 
 ## [0.33.0] - 2026-02-17

diff --git a/docs/core-cli/init.md b/docs/core-cli/init.md
@@ -46,21 +46,31 @@ specfact init --install backlog,code-review
 
 ## IDE Setup
 
-The `init ide` subcommand generates IDE-specific prompt templates and settings:
+The `init ide` subcommand discovers prompt templates from **core** (bundled `specfact_cli` resources or your repo checkout) and from **installed modules** under the effective module roots (builtin, project `.specfact/modules`, user `~/.specfact/modules`, marketplace, and `SPECFACT_MODULES_ROOTS`). It is a **re-sync** command: it only copies what is already installed; it does not download or extract modules. If prompts are missing, install or seed modules first (for example `specfact module init --scope project` or `specfact module install --scope user`).
 
 ```bash
-# Initialize Cursor IDE integration
+# Initialize Cursor IDE integration (interactive: pick IDE, then prompt sources)
 specfact init ide --ide cursor
 
+# Non-interactive: export all discovered sources (default)
+specfact init ide --ide cursor --repo .
+
+# Non-interactive: only core, or a comma-separated list of module ids
+specfact init ide --ide cursor --prompts core
+specfact init ide --ide cursor --prompts all
+specfact init ide --ide cursor --prompts "core,nold-ai/specfact-backlog"
+
 # Initialize with dependency installation
 specfact init ide --install-deps
 ```
 
-This creates:
+Exported IDE files are placed under **per-source subfolders** (for example `.cursor/commands/core/`, `.cursor/commands/nold-ai__specfact-backlog/`) so names collide deterministically and provenance stays visible.
+
+This creates or refreshes:
 
 - `.specfact/` directory structure
-- `.specfact/templates/backlog/field_mappings/` with default field mapping templates
-- IDE-specific command files for your AI assistant
+- `.specfact/templates/backlog/field_mappings/` with default field mapping templates when available
+- IDE-specific command files under the IDE export directory, namespaced by prompt source
 
 ## Dependency Installation
 

diff --git a/docs/core-cli/module.md b/docs/core-cli/module.md
@@ -9,6 +9,8 @@ description: Reference for the specfact module command group - install, manage,
 
 Manage marketplace modules: install, uninstall, search, upgrade, and configure registries.
 
+Use `specfact module init --scope user|project` to seed bundled module trees and `specfact module install --scope user|project` to add or refresh modules. After modules are present, `specfact init ide` discovers their prompt resources from those roots and exports IDE-facing files; it does not download modules itself.
+
 ## Usage
 
 ```bash

diff --git a/openspec/CHANGE_ORDER.md b/openspec/CHANGE_ORDER.md
@@ -149,7 +149,7 @@ Cross-repo dependency: `docs-07-core-handoff-conversion` depends on `specfact-cl
 | module-migration | 09 | backlog-module-ownership-cleanup | TBD | module-migration-06; backlog-core-07; cli-val-07 findings |
 | module-migration | 10 | module-migration-10-bundle-command-surface-alignment | [#385](https://github.com/nold-ai/specfact-cli/issues/385) | module-migration-02 ✅; module-migration-06/07 baseline; cli-val-07 findings |
 | module-migration | 11 | module-migration-11-project-codebase-ownership-realignment | [#408](https://github.com/nold-ai/specfact-cli/issues/408) | module-migration-06 baseline; backlog-module-ownership-cleanup precedent; blocks final canonical import-path decisions in module-migration-10 |
-| init-ide | 01 | init-ide-prompt-source-selection | TBD | backlog-module-ownership-cleanup |
+| init-ide | 01 | init-ide-prompt-source-selection | [#382](https://github.com/nold-ai/specfact-cli/issues/382) | backlog-module-ownership-cleanup; packaging-02-cross-platform-runtime-and-module-resources; modules-repo/packaging-01-bundle-resource-payloads (#101); module-migration-11 command-ownership alignment |
 | backlog-auth | 01 | backlog-auth-01-backlog-auth-commands | TBD | module-migration-03 (central auth interface in core; auth removed from core) |
 
 ### Cross-cutting foundations (no hard dependencies — implement early)

diff --git a/openspec/changes/init-ide-prompt-source-selection/CHANGE_VALIDATION.md b/openspec/changes/init-ide-prompt-source-selection/CHANGE_VALIDATION.md
@@ -0,0 +1,23 @@
+# Change Validation: init-ide-prompt-source-selection
+
+- Date: 2026-03-25
+- Command: `openspec validate init-ide-prompt-source-selection --strict`
+- Result: `Change 'init-ide-prompt-source-selection' is valid`
+
+## Scope Review
+
+- The change was narrowed to `specfact-cli` orchestration only.
+- Bundle-owned prompt/template payload migration remains in `specfact-cli-modules` change `packaging-01-bundle-resource-payloads` (`nold-ai/specfact-cli-modules#101`).
+- Installed-resource discovery mechanics remain owned by `packaging-02-cross-platform-runtime-and-module-resources` in `specfact-cli`.
+
+## Dependency Review
+
+- `backlog-module-ownership-cleanup` remains a prerequisite so backlog prompt ownership is no longer split across core and bundle code.
+- `specfact-cli-modules#101` is now treated as the paired payload provider for bundle-owned prompt/template resources.
+- `module-migration-11-project-codebase-ownership-realignment` is treated as command-surface alignment context so exported prompts do not reassert obsolete ownership or grouped command paths.
+
+## Behavioral Boundaries Confirmed
+
+- `specfact init ide` is an anytime re-sync/export command.
+- `specfact init ide` discovers installed resources from effective module roots; it does not download or install module archives.
+- Install/bootstrap guidance continues to belong to `specfact module init` and `specfact module install` with user/project scope selection.
diff --git a/openspec/changes/init-ide-prompt-source-selection/TDD_EVIDENCE.md b/openspec/changes/init-ide-prompt-source-selection/TDD_EVIDENCE.md
@@ -0,0 +1,12 @@
+# TDD evidence: init-ide-prompt-source-selection
+
+## Pre-implementation (failing tests)
+
+- Command: `hatch run pytest tests/unit/modules/init/test_init_ide_prompt_selection.py -v`
+- Timestamp: 2026-03-25 (session; tests added before implementation in worktree `feature/init-ide-prompt-source-selection`)
+- Note: New tests were introduced to lock catalog export, `--prompts` parsing, and CLI failure on invalid tokens; implementation followed in the same change.
+
+## Post-implementation (passing)
+
+- Command: `hatch run pytest tests/unit/modules/init/test_init_ide_prompt_selection.py tests/unit/utils/test_ide_setup.py tests/e2e/test_init_command.py -q`
+- Status: green after `ide_setup` catalog + namespaced copy, `init ide` wiring, startup_checks rglob, and e2e path updates.
diff --git a/openspec/changes/init-ide-prompt-source-selection/design.md b/openspec/changes/init-ide-prompt-source-selection/design.md
@@ -1,28 +1,59 @@
 ## Context
 
-Today `init ide` is effectively designed around core-owned prompt resources. That breaks down once backlog and other domain prompt assets are properly owned by modules. The export flow needs a source-aware model that works for both interactive and automation-friendly use.
+`packaging-02-cross-platform-runtime-and-module-resources` moved `specfact-cli` toward installed-resource discovery, but it explicitly left the prompt-selection UX and source-targeting behavior for this follow-up change.
+
+That follow-up now has to cover more than a selector:
+
+- bundle-owned prompt/template payloads are being moved into `specfact-cli-modules`
+- modules can be present in multiple roots depending on how the user bootstrapped or installed them
+- `specfact init ide` can be run at any time and therefore must discover the currently effective installed roots instead of assuming a one-time bootstrap copy from core-owned resources
+- `specfact init ide` must not start performing marketplace download/extract work, because installation remains owned by `specfact module init` and `specfact module install`
+
+The prompt/export flow therefore needs a source-aware and scope-aware orchestration model, not just a new option flag.
 
 ## Decision
 
 - Define prompt sources as:
   - `core`
   - installed/enabled module ids, for example `nold-ai/specfact-backlog`
+- Resolve available sources from effective module roots in repository context:
+  - built-in core module root
+  - project module root at `<repo>/.specfact/modules` when present
+  - nearest workspace module root discovered from the repo path
+  - user module root at `~/.specfact/modules`
+  - optional custom roots from `SPECFACT_MODULES_ROOTS`
 - Default export behavior to `all` sources.
 - In interactive mode, show a multi-select picker over the available prompt sources.
 - In non-interactive mode, use a comma-separated `--prompts` selector that accepts:
   - `all`
   - `core`
   - full installed module ids
   - mixed values such as `core,nold-ai/specfact-backlog`
+- Keep installation responsibilities separate:
+  - `specfact module init --scope user|project` seeds bundled module artifacts/resources into the selected root
+  - `specfact module install --scope user|project --source <auto|bundled|marketplace>` downloads and extracts bundles into the selected root
+  - `specfact init ide` only discovers already-installed resources and copies/refreshes the IDE-facing output for the current repository
 
 ## Rules
 
 - unknown or not-installed module ids fail with actionable guidance
 - exported prompt resources remain namespaced by source to avoid collisions
 - `all` includes `core` plus all installed/enabled modules that contribute prompts
+- root precedence and duplicate handling must remain deterministic across user/project/custom roots
+- missing module-owned prompt/resources must report the owning module, the root that was inspected, and the install/bootstrap command that can satisfy the missing payload
+- prompt ownership must respect active command-surface migration decisions and must not reassert obsolete import/project command paths in exported prompts or recommendations
+
+## Non-Goals
+
+- downloading marketplace artifacts during `specfact init ide`
+- extracting archives directly from `specfact-cli-modules` source trees at runtime when the owning bundle is not installed
+- reintroducing bundle-owned prompt/template payloads into the core package
+- replacing `packaging-02` as the owner of low-level installed-resource discovery logic
 
 ## Validation
 
 - add tests for default `all` behavior
+- add tests for root-aware source discovery across built-in, user, project, and custom roots
 - add tests for interactive picker source lists
 - add tests for non-interactive parsing and validation of `--prompts`
+- add tests that `init ide` surfaces scope-aware install guidance instead of downloading/installing missing modules
diff --git a/openspec/changes/init-ide-prompt-source-selection/proposal.md b/openspec/changes/init-ide-prompt-source-selection/proposal.md
@@ -2,32 +2,43 @@
 
 ## Why
 
+`specfact init ide` is now downstream of two separate realities:
 
-`specfact init ide` needs a stable prompt-source model once backlog prompts/templates move into modules. Users should get all relevant prompts by default, and they need both interactive selection and non-interactive source targeting when they only want core prompts or a subset of installed module prompts.
+- official bundle-owned prompts and templates are being moved into `specfact-cli-modules`
+- users can install modules into different runtime roots (`~/.specfact/modules`, `<repo>/.specfact/modules`, built-in core package roots, and optional custom roots)
 
-## What Changes
+The original proposal treated this as only a simple prompt selector. That is no longer sufficient. The remaining core-side work is to make prompt and resource export aware of installation scope, ownership, and provenance without reintroducing payload ownership into `specfact-cli`.
 
+## What Changes
 
-- Redesign prompt export in `specfact init ide` around prompt sources rather than assuming prompts are core-owned.
-- Default to exporting all prompt sources.
-- Add interactive multi-select for installed prompt sources and non-interactive `--prompts` selection with `all`, `core`, and full module ids.
-- Keep exported prompt resources namespaced by source so module prompt collisions remain deterministic and readable.
+- MODIFY: Narrow this change to `specfact-cli` orchestration only. Prompt/template payload migration stays in `specfact-cli-modules` change `packaging-01-bundle-resource-payloads` (`nold-ai/specfact-cli-modules#101`).
+- EXTEND: Build an installation-aware prompt/resource catalog for `specfact init ide` from core built-ins plus discovered installed modules across user, project, and configured custom module roots.
+- ADD: Default `specfact init ide` behavior exports all discovered prompt sources, while interactive and non-interactive selection can target `core` and specific installed module ids.
+- ADD: Exported prompt files remain attributable to their owning source so collisions are deterministic and later ownership changes do not silently overwrite unrelated prompts.
+- ADD: `specfact init ide` remains an anytime re-sync command. It discovers and copies installed resources; it does not download, install, or extract module archives itself.
+- ADD: When selected resources are missing, the command reports the missing owner/root and points users to the relevant core install/bootstrap flows such as `specfact module init --scope <user|project>` and `specfact module install --scope <user|project>`.
 
 ## Capabilities
 ### New Capabilities
 
 - `init-ide-prompt-selection`: `specfact init ide` can export prompts from core and selected installed modules with consistent interactive and non-interactive behavior.
+- `init-ide-installed-resource-orchestration`: `specfact init ide` can discover installed prompt/resource payloads from the effective module roots and direct users to the correct install/bootstrap command when those payloads are absent.
 
 ## Acceptance Criteria
-- `specfact init ide` exports all available prompt sources by default.
-- Interactive mode shows a multi-select picker containing `core` plus installed module ids.
+- `specfact init ide` builds its prompt-source catalog from the effective installed module roots for the current repository context, including user scope, project scope, built-in core modules, and configured custom roots.
+- Default execution exports all discovered prompt sources by default rather than only the first matching root.
+- Interactive mode shows a source picker containing `core` plus installed module ids that actually contribute prompt resources.
 - Non-interactive mode accepts `--prompts all`, `--prompts core`, and comma-separated full module ids.
-- The command fails clearly when a requested module id is not installed or does not expose prompt resources.
-- Exported prompt files are grouped by source so prompt provenance remains visible.
+- The command does not download or install module archives. Missing sources produce actionable guidance to run the correct core install/bootstrap command for the relevant scope.
+- Exported prompt files are grouped or namespaced by source so prompt provenance remains visible and collisions stay deterministic.
+- The scope respects canonical command ownership from active migration changes and must not reintroduce obsolete command paths into prompt export or recommendations.
 
 ## Dependencies
 - `backlog-module-ownership-cleanup` must land first so backlog prompt ownership is no longer split across core and module.
-- Existing `init ide` resource-copy logic in `specfact-cli` provides the base export path that this change extends.
+- `packaging-02-cross-platform-runtime-and-module-resources` provides the installed-resource discovery foundation in `specfact-cli` and must stay the owner of payload discovery mechanics.
+- `specfact-cli-modules/packaging-01-bundle-resource-payloads` (`nold-ai/specfact-cli-modules#101`) must provide the bundle-owned prompt/template payloads that this change selects and exports.
+- `module-migration-11-project-codebase-ownership-realignment` must be treated as command-surface alignment context so exported prompts do not preserve obsolete grouped command ownership.
+- Existing `specfact module init` and `specfact module install` commands in `specfact-cli` remain the install/bootstrap path for user/project module roots; `init ide` extends only the post-install discovery/export path.
 
 
 ---
@@ -39,4 +50,4 @@
 - **Issue URL**: <https://github.com/nold-ai/specfact-cli/issues/382>
 - **Last Synced Status**: proposed
 - **Sanitized**: false
-<!-- content_hash: fc82ab6be9832592 -->
+<!-- content_hash: fc82ab6be9832592 -->
-Original file line number
+Diff line change
@@ Expand Up @@
     Manage marketplace modules: install, uninstall, search, upgrade, and configure registries.
+    Use `specfact module init --scope user|project` to seed bundled module trees and `specfact module install --scope user|project` to add or refresh modules. After modules are present, `specfact init ide` discovers their prompt resources from those roots and exports IDE-facing files; it does not download modules itself.
     ## Usage
     ```bash
@@ Expand Down @@