v0.43.1

Changed

• Packaging: Workflow slash-command prompts (specfact.*.md) are no longer duplicated in the core wheel; canonical copies live in specfact-cli-modules bundle packages under each bundle’s resources/prompts/. Install bundles (or use a dev repo checkout with resources/prompts/) for specfact init ide prompt export.
• IDE template drift checks on startup resolve source templates via the same installed-module discovery path as specfact init ide, not a single core resources/prompts directory inside the package.

v0.42.6

Fixed

• specfact init ide multi-source export writes prompts to a flat layout under the IDE export root (for example .github/prompts/ or .cursor/commands/) so editors and agents can discover specfact*.prompt.md (or equivalent) without per-source subfolders.
• Prompt catalog: core omits template basenames already provided by an installed module, avoiding duplicate exports when both ship the same filename.
• Re-export removes legacy per-source segment directories and prunes stale flat specfact* exports when the selected sources change.
• Tests: import pytest for MonkeyPatch annotations in init IDE prompt selection tests (Ruff F821).

v0.42.5

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.

v0.42.4

Fixed

• Hardened terminal output handling for non-UTF-8 environments so Rich output degrades safely on Windows, Linux, and macOS terminals that cannot render Unicode symbols or box drawing characters.
• Updated specfact init ide to discover prompt templates and backlog field mapping resources from installed module locations first, with path-based fallback behavior that remains compatible across different install methods such as Hatch, pip, pipx, and uv.
• Improved bundled module runtime compatibility failures to surface actionable interpreter and reinstall guidance instead of opaque import/load errors.

v0.42.3

Fixed

• Completed the dogfood code-review-zero-findings remediation so specfact code review run --scope full on this repository reports PASS with no findings (down from 2500+ baseline diagnostics across type safety, architecture, contracts, and clean-code categories).
• Type checking (basedpyright): eliminated blocking errors and drove high-volume warnings (including reportUnknownMemberType) to zero across src/specfact_cli, tools, scripts, and bundled modules; aligned pyproject.toml / extraPaths usage with review tooling limits.
• Radon: refactored hot paths to cyclomatic complexity ≤12 (no CC13–CC15 warnings) in adapters, sync/bridge, generators, importers, registry, CLI, utils, validators, tools, scripts, and bundled init / module_registry command surfaces.
• Lint / policy: addressed Ruff and Semgrep issues used by the review (for example SIM105 / SIM117, import ordering, contextlib.suppress where appropriate, and print_progress emitting via sys.stdout instead of print() to satisfy structured-output rules while keeping test-visible progress).
• Contracts: repaired icontract / @ensure wiring (for example vscode_settings_result_ok, save_bundle_with_progress preconditions versus on-disk creation) and bridge_sync_tasks_from_proposal checkbox helper typing so contract checks and tests stay consistent with the review gate.

v0.42.2

Fixed

• Corrected all authored docs (README.md, docs/) to use shipped command surfaces after the lean-core and modules split. Removed or replaced stale syntax families (project plan, project import from-bridge, backlog policy, spec contract, spec sdd, spec generate prompt subcommands) with current equivalents (code import from-bridge, backlog verify-readiness, spec validate, spec generate-tests, govern enforce sdd).
• Added docs parity tests that fail when removed syntax families reappear in authored docs, guarding against future regression.

v0.42.1

Added

• Integrated specfact code review run into this repository's pre-commit flow through a staged-file review gate and helper script, so blocking review verdicts fail commit validation while advisory verdicts remain green.

Changed

• Expanded docs/modules/code-review.md with repo-local pre-commit setup, portable adoption guidance for other projects, optional house_rules workflow guidance, and JSON-first reward-ledger documentation with optional backend persistence.

Fixed

• Declared radon in the runtime, dev, and Hatch default environments so specfact code review run can resolve its complexity runner consistently in fresh local bootstraps and worktrees.

v0.41.0

Added

• Added the nold-ai/specfact-code-review module scaffold (SP-001): structured ReviewFinding / ReviewReport models, review scoring helpers, and the specfact code review command surface documentation.

v0.40.4

Fixed

• Fixed Azure DevOps work item creation to use POST instead of PATCH API method, resolving 400 Bad Request errors when creating backlog items via specfact backlog add.
• Fixed category grouping registration to always mount category groups (code, backlog, project, spec, govern) even when category grouping is disabled, ensuring flat command availability.

v0.40.3

Changed

• Improved specfact module upgrade success output so multi-module upgrades print one module per line with explicit old -> new version transitions.
• Updated contributor/testing docs to document the command-package runtime audit procedure and the normal-output vs --debug diagnostics policy.

Fixed

• specfact backlog map-fields no longer blocks on non-mappable built-in required ADO hierarchy identifiers such as System.IterationId and System.AreaId.
• specfact backlog map-fields now reports incremental metadata-fetch progress after work item type selection instead of appearing stalled during follow-up field lookups.
• Shared bridge/registry logger diagnostics no longer leak raw log-formatted lines into normal console output when --debug is disabled.
• Successful bundled module upgrades no longer emit routine dependency already satisfied notices as warnings.