specfact-cli 0.41.0__tar.gz → 0.42.2__tar.gz

{specfact_cli-0.41.0 → specfact_cli-0.42.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specfact-cli
-Version: 0.41.0
+Version: 0.42.2
 Summary: The swiss knife CLI for agile DevOps teams. Keep backlog, specs, tests, and code in sync with validation and contract enforcement for new projects and long-lived codebases.
 Project-URL: Homepage, https://github.com/nold-ai/specfact-cli
 Project-URL: Repository, https://github.com/nold-ai/specfact-cli.git
@@ -240,6 +240,7 @@ Requires-Dist: pydantic>=2.12.3
 Requires-Dist: python-dotenv>=1.2.1
 Requires-Dist: pyyaml>=6.0.3
 Requires-Dist: questionary>=2.0.1
+Requires-Dist: radon>=6.0.1
 Requires-Dist: requests>=2.32.3
 Requires-Dist: rich<13.6.0,>=13.5.2
 Requires-Dist: ruamel-yaml>=0.18.16
@@ -264,6 +265,7 @@ Requires-Dist: pytest-cov>=7.0.0; extra == 'dev'
 Requires-Dist: pytest-mock>=3.15.1; extra == 'dev'
 Requires-Dist: pytest-xdist>=3.8.0; extra == 'dev'
 Requires-Dist: pytest>=8.4.2; extra == 'dev'
+Requires-Dist: radon>=6.0.1; extra == 'dev'
 Requires-Dist: ruff>=0.14.2; extra == 'dev'
 Requires-Dist: semgrep>=1.144.0; extra == 'dev'
 Requires-Dist: tomlkit>=0.13.3; extra == 'dev'
@@ -298,6 +300,19 @@ Description-Content-Type: text/markdown
 
 ---
 
+## Documentation Topology
+
+`docs.specfact.io` is the canonical docs entry point for SpecFact.
+
+- Core CLI/runtime/platform documentation remains owned by `specfact-cli`.
+- Module-specific deep docs are canonically owned by `specfact-cli-modules`.
+- The live modules docs site is currently published at `https://modules.specfact.io/`.
+
+Use this repository's docs for core runtime, lifecycle, registry, trust, and architecture guidance. Use the modules docs site for bundle-specific workflow and module-authoring deep dives.
+In short, module-specific deep docs are canonically owned by `specfact-cli-modules`.
+
+---
+
 ## Start Here (60 seconds)
 
 ### Install
@@ -346,9 +361,9 @@ specfact code validate sidecar run my-project /path/to/repo
 
 As of `0.40.0`, flat root commands are removed. Use grouped commands:
 
-- `specfact validate ...` -> `specfact code validate ...`
-- `specfact plan ...` -> `specfact project plan ...`
-- `specfact policy ...` -> `specfact backlog policy ...`
+- `specfact validate ...` → `specfact code validate ...`
+- `specfact plan ...` → removed; use `specfact project devops-flow` or `specfact project snapshot`
+- `specfact policy ...` → removed; use `specfact backlog verify-readiness`
 
 ### Backlog Bridge (60 seconds)
 
@@ -366,7 +381,7 @@ specfact backlog daily ado --ado-org <org> --ado-project "<project>" --state any
 specfact backlog refine ado --ado-org <org> --ado-project "<project>" --id <work-item-id> --preview
 
 # 3) Keep backlog + spec intent aligned (avoid silent drift)
-specfact backlog policy validate --group-by-item
+specfact backlog verify-readiness --bundle <bundle-name>
 ```
 
 For GitHub, replace adapter/org/project with:
@@ -434,18 +449,18 @@ Most tools help **either** coders **or** agile teams. SpecFact does both:
 Recommended command entrypoints:
 - `specfact backlog ceremony standup ...`
 - `specfact backlog ceremony refinement ...`
-- `specfact backlog policy validate ...`
-- `specfact backlog policy suggest ...`
+- `specfact backlog verify-readiness --bundle <bundle-name>`
+- `specfact backlog analyze-deps --bundle <bundle-name>`
 
-What the Policy Engine does in practice:
+What the backlog readiness and ceremony commands do in practice:
 - Turns team agreements (DoR, DoD, flow checks) into executable checks against your real backlog data.
 - Shows exactly what is missing per item (for example missing acceptance criteria or definition of done).
-- Generates patch-ready suggestions so teams can fix policy gaps quickly without guessing.
+- Run structured ceremony workflows (standup, refinement, retrospective) directly from the CLI.
 
 Start with:
-- `specfact backlog policy init --template scrum`
-- `specfact backlog policy validate --group-by-item`
-- `specfact backlog policy suggest --group-by-item --limit 5`
+- `specfact backlog ceremony standup --help`
+- `specfact backlog verify-readiness --bundle <bundle-name>`
+- `specfact backlog refine --help`
 
 **Try it now**
 
@@ -484,9 +499,10 @@ For technical architecture details (module lifecycle, registry internals, adapte
 
 SpecFact ships official bundle packages via the dedicated marketplace registry repository
 `nold-ai/specfact-cli-modules`.
-Bundle-specific docs are still temporarily hosted in this docs set while the long-term
-bundle docs home is prepared in the modules repository docs site:
-`https://nold-ai.github.io/specfact-cli-modules/`.
+
+This core docs set remains the canonical docs entry point and release-line overview for marketplace concepts.
+Bundle-specific deep docs are canonically owned by `specfact-cli-modules` and are currently published at:
+`https://modules.specfact.io/`.
 
 Install examples:
 
@@ -511,9 +527,8 @@ auto-install dependencies:
 - `nold-ai/specfact-spec` pulls `nold-ai/specfact-project`
 - `nold-ai/specfact-govern` pulls `nold-ai/specfact-project`
 
-Use this repo's docs for the current CLI/runtime release branch. Module-specific guides
-will move to `specfact-cli-modules` so future bundle-only changes do not require ongoing
-docs maintenance in long-lived `specfact-cli` release branches.
+Use this repo's docs for the current CLI/runtime release branch and for marketplace lifecycle overview content.
+Use the modules docs site for bundle-specific deep guidance so bundle-only changes can ship without rebuilding the core docs release branch.
 
 ---
 

{specfact_cli-0.41.0 → specfact_cli-0.42.2}/README.md

@@ -19,6 +19,19 @@
 
 ---
 
+## Documentation Topology
+
+`docs.specfact.io` is the canonical docs entry point for SpecFact.
+
+- Core CLI/runtime/platform documentation remains owned by `specfact-cli`.
+- Module-specific deep docs are canonically owned by `specfact-cli-modules`.
+- The live modules docs site is currently published at `https://modules.specfact.io/`.
+
+Use this repository's docs for core runtime, lifecycle, registry, trust, and architecture guidance. Use the modules docs site for bundle-specific workflow and module-authoring deep dives.
+In short, module-specific deep docs are canonically owned by `specfact-cli-modules`.
+
+---
+
 ## Start Here (60 seconds)
 
 ### Install
@@ -67,9 +80,9 @@ specfact code validate sidecar run my-project /path/to/repo
 
 As of `0.40.0`, flat root commands are removed. Use grouped commands:
 
-- `specfact validate ...` -> `specfact code validate ...`
-- `specfact plan ...` -> `specfact project plan ...`
-- `specfact policy ...` -> `specfact backlog policy ...`
+- `specfact validate ...` → `specfact code validate ...`
+- `specfact plan ...` → removed; use `specfact project devops-flow` or `specfact project snapshot`
+- `specfact policy ...` → removed; use `specfact backlog verify-readiness`
 
 ### Backlog Bridge (60 seconds)
 
@@ -87,7 +100,7 @@ specfact backlog daily ado --ado-org <org> --ado-project "<project>" --state any
 specfact backlog refine ado --ado-org <org> --ado-project "<project>" --id <work-item-id> --preview
 
 # 3) Keep backlog + spec intent aligned (avoid silent drift)
-specfact backlog policy validate --group-by-item
+specfact backlog verify-readiness --bundle <bundle-name>
 ```
 
 For GitHub, replace adapter/org/project with:
@@ -155,18 +168,18 @@ Most tools help **either** coders **or** agile teams. SpecFact does both:
 Recommended command entrypoints:
 - `specfact backlog ceremony standup ...`
 - `specfact backlog ceremony refinement ...`
-- `specfact backlog policy validate ...`
-- `specfact backlog policy suggest ...`
+- `specfact backlog verify-readiness --bundle <bundle-name>`
+- `specfact backlog analyze-deps --bundle <bundle-name>`
 
-What the Policy Engine does in practice:
+What the backlog readiness and ceremony commands do in practice:
 - Turns team agreements (DoR, DoD, flow checks) into executable checks against your real backlog data.
 - Shows exactly what is missing per item (for example missing acceptance criteria or definition of done).
-- Generates patch-ready suggestions so teams can fix policy gaps quickly without guessing.
+- Run structured ceremony workflows (standup, refinement, retrospective) directly from the CLI.
 
 Start with:
-- `specfact backlog policy init --template scrum`
-- `specfact backlog policy validate --group-by-item`
-- `specfact backlog policy suggest --group-by-item --limit 5`
+- `specfact backlog ceremony standup --help`
+- `specfact backlog verify-readiness --bundle <bundle-name>`
+- `specfact backlog refine --help`
 
 **Try it now**
 
@@ -205,9 +218,10 @@ For technical architecture details (module lifecycle, registry internals, adapte
 
 SpecFact ships official bundle packages via the dedicated marketplace registry repository
 `nold-ai/specfact-cli-modules`.
-Bundle-specific docs are still temporarily hosted in this docs set while the long-term
-bundle docs home is prepared in the modules repository docs site:
-`https://nold-ai.github.io/specfact-cli-modules/`.
+
+This core docs set remains the canonical docs entry point and release-line overview for marketplace concepts.
+Bundle-specific deep docs are canonically owned by `specfact-cli-modules` and are currently published at:
+`https://modules.specfact.io/`.
 
 Install examples:
 
@@ -232,9 +246,8 @@ auto-install dependencies:
 - `nold-ai/specfact-spec` pulls `nold-ai/specfact-project`
 - `nold-ai/specfact-govern` pulls `nold-ai/specfact-project`
 
-Use this repo's docs for the current CLI/runtime release branch. Module-specific guides
-will move to `specfact-cli-modules` so future bundle-only changes do not require ongoing
-docs maintenance in long-lived `specfact-cli` release branches.
+Use this repo's docs for the current CLI/runtime release branch and for marketplace lifecycle overview content.
+Use the modules docs site for bundle-specific deep guidance so bundle-only changes can ship without rebuilding the core docs release branch.
 
 ---
 

{specfact_cli-0.41.0 → specfact_cli-0.42.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "specfact-cli"
-version = "0.41.0"
+version = "0.42.2"
 description = "The swiss knife CLI for agile DevOps teams. Keep backlog, specs, tests, and code in sync with validation and contract enforcement for new projects and long-lived codebases."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -88,6 +88,7 @@ dependencies = [
     
     # Code analysis
     "ruff>=0.14.2",
+    "radon>=6.0.1",
     
     # File system watching
     "watchdog>=6.0.0",
@@ -108,6 +109,7 @@ dev = [
     "isort>=7.0.0",
     "pylint>=4.0.2",
     "ruff>=0.14.2",
+    "radon>=6.0.1",
     "tomlkit>=0.13.3",  # Style-preserving TOML library (recommended successor to pytoml)
     "types-PyYAML>=6.0.12.20250516",
     "pip-tools>=7.5.1",
@@ -175,6 +177,7 @@ dependencies = [
     "basedpyright>=1.32.1",
     "pylint>=4.0.2",
     "ruff>=0.14.2",
+    "radon>=6.0.1",
     "yamllint>=1.37.1",
     "semgrep>=1.144.0",  # Latest version compatible with rich~=13.5.2
     # Contract-First Development Dependencies

{specfact_cli-0.41.0 → specfact_cli-0.42.2}/src/__init__.py

@@ -3,4 +3,4 @@ SpecFact CLI - Spec→Contract→Sentinel tool for contract-driven development.
 """
 
 # Package version: keep in sync with pyproject.toml, setup.py, src/specfact_cli/__init__.py
-__version__ = "0.41.0"
+__version__ = "0.42.1"

{specfact_cli-0.41.0 → specfact_cli-0.42.2}/src/specfact_cli/__init__.py

@@ -42,6 +42,6 @@ def _bootstrap_bundle_paths() -> None:
 
 _bootstrap_bundle_paths()
 
-__version__ = "0.41.0"
+__version__ = "0.42.2"
 
 __all__ = ["__version__"]