specfact-cli 0.7.0__tar.gz → 0.9.0__tar.gz

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specfact-cli
-Version: 0.7.0
+Version: 0.9.0
 Summary: Brownfield-first CLI: Reverse engineer legacy Python → specs → enforced contracts. Automate legacy code documentation and prevent modernization regressions.
 Project-URL: Homepage, https://github.com/nold-ai/specfact-cli
 Project-URL: Repository, https://github.com/nold-ai/specfact-cli.git
@@ -317,6 +317,23 @@ A brownfield-first CLI that **reverse engineers your legacy code** into document
 - ✅ **Runtime contract enforcement** → Prevent regressions during modernization
 - ✅ **Symbolic execution** → Discover hidden edge cases with CrossHair
 - ✅ **Works offline** → No cloud required, fully local
+- ✅ **CLI integrations** → Works seamlessly with VS Code, Cursor, GitHub Actions, and any agentic workflow
+
+---
+
+## 🔌 CLI Integrations
+
+SpecFact CLI works with your existing tools—no new platform to learn. See real bugs that were caught and fixed through different integrations:
+
+- ✅ **VS Code** - Catch async bugs before you commit
+- ✅ **Cursor** - Prevent regressions during AI-assisted refactoring
+- ✅ **GitHub Actions** - Block bad code from merging
+- ✅ **Pre-commit Hooks** - Validate code locally before pushing
+- ✅ **AI Assistants** - Find edge cases AI might miss
+
+👉 **[Integration Showcases](docs/examples/integration-showcases/)** - Real examples of bugs fixed via CLI integrations
+
+**Core USP**: Pure CLI-first approach—works offline, no account required, zero vendor lock-in. Regularly showcases successful integrations that fix bugs not detected by other tools.
 
 ---
 
@@ -326,7 +343,7 @@ A brownfield-first CLI that **reverse engineers your legacy code** into document
 
 ```bash
 # Zero-install (just run it)
-uvx --from specfact-cli specfact --help
+uvx specfact-cli@latest --help
 
 # Or install with pip
 pip install specfact-cli
@@ -353,13 +370,13 @@ That's it! 🎉
 
 ## See It In Action
 
-We ran SpecFact CLI **on itself** to prove it works:
+We ran SpecFact CLI **on itself** to prove it works with legacy code:
 
-- ⚡ Analyzed 32 Python files → Discovered **32 features** and **81 stories** in **3 seconds**
+- ⚡ Analyzed 32 legacy Python files → Discovered **32 features** and **81 stories** in **3 seconds**
 - 🚫 Set enforcement to "balanced" → **Blocked 2 HIGH violations** (as configured)
 - 📊 Compared manual vs auto-derived plans → Found **24 deviations** in **5 seconds**
 
-**Total time**: < 10 seconds | **Total value**: Found real naming inconsistencies and undocumented features
+**Total time**: < 10 seconds | **Total value**: Found real naming inconsistencies and undocumented features in legacy codebase
 
 👉 **[Read the complete example](docs/examples/dogfooding-specfact-cli.md)** with actual commands and outputs
 
@@ -369,6 +386,8 @@ We ran SpecFact CLI **on itself** to prove it works:
 
 **New to SpecFact?** Start with the [Getting Started Guide](docs/getting-started/README.md)
 
+**Want to see integrations?** Check out [Integration Showcases](docs/examples/integration-showcases/) - Real bugs fixed via VS Code, Cursor, GitHub Actions
+
 **Tried Spec-Kit?** See [How SpecFact Compares to Spec-Kit](docs/guides/speckit-comparison.md) and [The Journey: From Spec-Kit to SpecFact](docs/guides/speckit-journey.md)
 
 **Need help?** Browse the [Documentation Hub](docs/README.md)

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/README.md

@@ -51,6 +51,23 @@ A brownfield-first CLI that **reverse engineers your legacy code** into document
 - ✅ **Runtime contract enforcement** → Prevent regressions during modernization
 - ✅ **Symbolic execution** → Discover hidden edge cases with CrossHair
 - ✅ **Works offline** → No cloud required, fully local
+- ✅ **CLI integrations** → Works seamlessly with VS Code, Cursor, GitHub Actions, and any agentic workflow
+
+---
+
+## 🔌 CLI Integrations
+
+SpecFact CLI works with your existing tools—no new platform to learn. See real bugs that were caught and fixed through different integrations:
+
+- ✅ **VS Code** - Catch async bugs before you commit
+- ✅ **Cursor** - Prevent regressions during AI-assisted refactoring
+- ✅ **GitHub Actions** - Block bad code from merging
+- ✅ **Pre-commit Hooks** - Validate code locally before pushing
+- ✅ **AI Assistants** - Find edge cases AI might miss
+
+👉 **[Integration Showcases](docs/examples/integration-showcases/)** - Real examples of bugs fixed via CLI integrations
+
+**Core USP**: Pure CLI-first approach—works offline, no account required, zero vendor lock-in. Regularly showcases successful integrations that fix bugs not detected by other tools.
 
 ---
 
@@ -60,7 +77,7 @@ A brownfield-first CLI that **reverse engineers your legacy code** into document
 
 ```bash
 # Zero-install (just run it)
-uvx --from specfact-cli specfact --help
+uvx specfact-cli@latest --help
 
 # Or install with pip
 pip install specfact-cli
@@ -87,13 +104,13 @@ That's it! 🎉
 
 ## See It In Action
 
-We ran SpecFact CLI **on itself** to prove it works:
+We ran SpecFact CLI **on itself** to prove it works with legacy code:
 
-- ⚡ Analyzed 32 Python files → Discovered **32 features** and **81 stories** in **3 seconds**
+- ⚡ Analyzed 32 legacy Python files → Discovered **32 features** and **81 stories** in **3 seconds**
 - 🚫 Set enforcement to "balanced" → **Blocked 2 HIGH violations** (as configured)
 - 📊 Compared manual vs auto-derived plans → Found **24 deviations** in **5 seconds**
 
-**Total time**: < 10 seconds | **Total value**: Found real naming inconsistencies and undocumented features
+**Total time**: < 10 seconds | **Total value**: Found real naming inconsistencies and undocumented features in legacy codebase
 
 👉 **[Read the complete example](docs/examples/dogfooding-specfact-cli.md)** with actual commands and outputs
 
@@ -103,6 +120,8 @@ We ran SpecFact CLI **on itself** to prove it works:
 
 **New to SpecFact?** Start with the [Getting Started Guide](docs/getting-started/README.md)
 
+**Want to see integrations?** Check out [Integration Showcases](docs/examples/integration-showcases/) - Real bugs fixed via VS Code, Cursor, GitHub Actions
+
 **Tried Spec-Kit?** See [How SpecFact Compares to Spec-Kit](docs/guides/speckit-comparison.md) and [The Journey: From Spec-Kit to SpecFact](docs/guides/speckit-journey.md)
 
 **Need help?** Browse the [Documentation Hub](docs/README.md)

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "specfact-cli"
-version = "0.7.0"
+version = "0.9.0"
 description = "Brownfield-first CLI: Reverse engineer legacy Python → specs → enforced contracts. Automate legacy code documentation and prevent modernization regressions."
 readme = "README.md"
 requires-python = ">=3.11"

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/src/__init__.py

@@ -3,4 +3,4 @@ SpecFact CLI - Spec→Contract→Sentinel tool for contract-driven development.
 """
 
 # Define the package version (kept in sync with pyproject.toml and setup.py)
-__version__ = "0.7.0"
+__version__ = "0.9.0"

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/src/specfact_cli/__init__.py

@@ -9,6 +9,6 @@ This package provides command-line tools for:
 - Validating reproducibility
 """
 
-__version__ = "0.7.0"
+__version__ = "0.9.0"
 
 __all__ = ["__version__"]

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/src/specfact_cli/analyzers/ambiguity_scanner.py

@@ -197,7 +197,7 @@ class AmbiguityScanner:
                         description=f"Feature {feature.key} has no outcomes specified",
                         impact=0.6,
                         uncertainty=0.5,
-                        question=f"What are the expected outcomes for feature {feature.key}?",
+                        question=f"What are the expected outcomes for feature {feature.key} ({feature.title})?",
                         related_sections=[f"features.{feature.key}.outcomes"],
                     )
                 )
@@ -228,7 +228,7 @@ class AmbiguityScanner:
                         description=f"Feature {feature.key} mentions data but has no constraints",
                         impact=0.5,
                         uncertainty=0.6,
-                        question=f"What are the data model constraints for feature {feature.key}?",
+                        question=f"What are the data model constraints for feature {feature.key} ({feature.title})?",
                         related_sections=[f"features.{feature.key}.constraints"],
                     )
                 )
@@ -262,7 +262,7 @@ class AmbiguityScanner:
                                 description=f"Story {story.key} mentions UX but lacks error handling",
                                 impact=0.5,
                                 uncertainty=0.4,
-                                question=f"What error/empty states should be handled for story {story.key}?",
+                                question=f"What error/empty states should be handled for story {story.key} ({story.title})?",
                                 related_sections=[f"features.{feature.key}.stories.{story.key}.acceptance"],
                             )
                         )
@@ -321,7 +321,7 @@ class AmbiguityScanner:
                         description=f"Feature {feature.key} mentions integration but has no constraints",
                         impact=0.6,
                         uncertainty=0.5,
-                        question=f"What are the external dependency constraints and failure modes for feature {feature.key}?",
+                        question=f"What are the external dependency constraints and failure modes for feature {feature.key} ({feature.title})?",
                         related_sections=[f"features.{feature.key}.constraints"],
                     )
                 )
@@ -354,7 +354,7 @@ class AmbiguityScanner:
                             description=f"Story {story.key} has limited acceptance criteria, may be missing edge cases",
                             impact=0.4,
                             uncertainty=0.5,
-                            question=f"What edge cases or negative scenarios should be handled for story {story.key}?",
+                            question=f"What edge cases or negative scenarios should be handled for story {story.key} ({story.title})?",
                             related_sections=[f"features.{feature.key}.stories.{story.key}.acceptance"],
                         )
                     )
@@ -424,7 +424,7 @@ class AmbiguityScanner:
                             description=f"Story {story.key} has no acceptance criteria",
                             impact=0.8,
                             uncertainty=0.7,
-                            question=f"What are the testable acceptance criteria for story {story.key}?",
+                            question=f"What are the testable acceptance criteria for story {story.key} ({story.title})?",
                             related_sections=[f"features.{feature.key}.stories.{story.key}.acceptance"],
                         )
                     )
@@ -459,7 +459,7 @@ class AmbiguityScanner:
                                 description=f"Story {story.key} has vague acceptance criteria: {', '.join(vague_criteria[:2])}",
                                 impact=0.7,
                                 uncertainty=0.6,
-                                question=f"Story {story.key} has vague acceptance criteria. Should these be converted to testable Given/When/Then format?",
+                                question=f"Story {story.key} ({story.title}) has vague acceptance criteria. Should these be converted to testable Given/When/Then format?",
                                 related_sections=[f"features.{feature.key}.stories.{story.key}.acceptance"],
                             )
                         )
@@ -486,7 +486,7 @@ class AmbiguityScanner:
                                 description=f"Story {story.key} acceptance criteria may not be testable",
                                 impact=0.5,
                                 uncertainty=0.4,
-                                question=f"Are the acceptance criteria for story {story.key} measurable and testable?",
+                                question=f"Are the acceptance criteria for story {story.key} ({story.title}) measurable and testable?",
                                 related_sections=[f"features.{feature.key}.stories.{story.key}.acceptance"],
                             )
                         )
@@ -508,7 +508,7 @@ class AmbiguityScanner:
                         description=f"Feature {feature.key} has no stories",
                         impact=0.9,
                         uncertainty=0.8,
-                        question=f"What user stories are needed for feature {feature.key}?",
+                        question=f"What user stories are needed for feature {feature.key} ({feature.title})?",
                         related_sections=[f"features.{feature.key}.stories"],
                     )
                 )
@@ -522,7 +522,7 @@ class AmbiguityScanner:
                         description=f"Feature {feature.key} has no acceptance criteria",
                         impact=0.7,
                         uncertainty=0.6,
-                        question=f"What are the acceptance criteria for feature {feature.key}?",
+                        question=f"What are the acceptance criteria for feature {feature.key} ({feature.title})?",
                         related_sections=[f"features.{feature.key}.acceptance"],
                     )
                 )
@@ -558,7 +558,7 @@ class AmbiguityScanner:
                                     description=f"Feature {feature.key} has incomplete requirement: '{outcome}' (missing verb/action)",
                                     impact=0.6,
                                     uncertainty=0.5,
-                                    question=f"Feature {feature.key} requirement '{outcome}' appears incomplete. What should the system do?",
+                                    question=f"Feature {feature.key} ({feature.title}) requirement '{outcome}' appears incomplete. What should the system do?",
                                     related_sections=[f"features.{feature.key}.outcomes"],
                                 )
                             )
@@ -593,7 +593,7 @@ class AmbiguityScanner:
                                 description=f"Story {story.key} has generic tasks without implementation details: {', '.join(generic_tasks[:2])}",
                                 impact=0.4,
                                 uncertainty=0.3,
-                                question=f"Story {story.key} has generic tasks. Should these include file paths, method names, or component references?",
+                                question=f"Story {story.key} ({story.title}) has generic tasks. Should these include file paths, method names, or component references?",
                                 related_sections=[f"features.{feature.key}.stories.{story.key}.tasks"],
                             )
                         )

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/src/specfact_cli/analyzers/constitution_evidence_extractor.py

@@ -62,7 +62,10 @@ class ConstitutionEvidenceExtractor:
         self.repo_path = Path(repo_path)
 
     @beartype
-    @require(lambda repo_path: repo_path is None or repo_path.exists(), "Repository path must exist if provided")
+    @require(
+        lambda repo_path: repo_path is None or (isinstance(repo_path, Path) and repo_path.exists()),
+        "Repository path must exist if provided",
+    )
     @ensure(lambda result: isinstance(result, dict), "Must return dict")
     def extract_article_vii_evidence(self, repo_path: Path | None = None) -> dict[str, Any]:
         """
@@ -145,7 +148,7 @@ class ConstitutionEvidenceExtractor:
             )
         else:
             status = "FAIL"
-            issues = []
+            issues: list[str] = []
             if not depth_pass:
                 issues.append(
                     f"deep directory structure (max depth: {max_depth}, threshold: {self.MAX_DIRECTORY_DEPTH})"
@@ -167,7 +170,10 @@ class ConstitutionEvidenceExtractor:
         }
 
     @beartype
-    @require(lambda repo_path: repo_path is None or repo_path.exists(), "Repository path must exist if provided")
+    @require(
+        lambda repo_path: repo_path is None or (isinstance(repo_path, Path) and repo_path.exists()),
+        "Repository path must exist if provided",
+    )
     @ensure(lambda result: isinstance(result, dict), "Must return dict")
     def extract_article_viii_evidence(self, repo_path: Path | None = None) -> dict[str, Any]:
         """
@@ -252,7 +258,7 @@ class ConstitutionEvidenceExtractor:
             rationale = "No framework abstractions detected (direct library usage)"
         else:
             status = "FAIL"
-            issues = []
+            issues: list[str] = []
             if frameworks_detected:
                 issues.append(f"framework abstractions detected ({', '.join(frameworks_detected)})")
             if abstraction_layers > self.MAX_ABSTRACTION_LAYERS:
@@ -271,7 +277,10 @@ class ConstitutionEvidenceExtractor:
         }
 
     @beartype
-    @require(lambda repo_path: repo_path is None or repo_path.exists(), "Repository path must exist if provided")
+    @require(
+        lambda repo_path: repo_path is None or (isinstance(repo_path, Path) and repo_path.exists()),
+        "Repository path must exist if provided",
+    )
     @ensure(lambda result: isinstance(result, dict), "Must return dict")
     def extract_article_ix_evidence(self, repo_path: Path | None = None) -> dict[str, Any]:
         """

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/src/specfact_cli/analyzers/contract_extractor.py

@@ -303,7 +303,7 @@ class ContractExtractor:
     @ensure(lambda result: isinstance(result, str), "Must return string")
     def _op_to_string(self, op: ast.cmpop) -> str:
         """Convert AST comparison operator to string."""
-        op_map = {
+        op_map: dict[type[Any], str] = {
             ast.Eq: "==",
             ast.NotEq: "!=",
             ast.Lt: "<",

{specfact_cli-0.7.0 → specfact_cli-0.9.0}/src/specfact_cli/cli.py

@@ -53,7 +53,7 @@ from rich.panel import Panel
 from specfact_cli import __version__, runtime
 
 # Import command modules
-from specfact_cli.commands import constitution, enforce, import_cmd, init, plan, repro, sync
+from specfact_cli.commands import constitution, enforce, generate, import_cmd, init, plan, repro, sync
 from specfact_cli.modes import OperationalMode, detect_mode
 from specfact_cli.utils.structured_io import StructuredFormat
 
@@ -291,8 +291,9 @@ app.add_typer(
     name="constitution",
     help="Manage project constitutions (Spec-Kit compatibility layer)",
 )
-app.add_typer(import_cmd.app, name="import", help="Import codebases and Spec-Kit projects")
+app.add_typer(import_cmd.app, name="import", help="Import codebases and external tool projects (e.g., Spec-Kit, Linear, Jira)")
 app.add_typer(plan.app, name="plan", help="Manage development plans")
+app.add_typer(generate.app, name="generate", help="Generate artifacts from SDD and plans")
 app.add_typer(enforce.app, name="enforce", help="Configure quality gates")
 app.add_typer(repro.app, name="repro", help="Run validation suite")
 app.add_typer(sync.app, name="sync", help="Synchronize Spec-Kit artifacts and repository changes")