specfact-cli 0.43.3__tar.gz → 0.45.1__tar.gz

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specfact-cli
-Version: 0.43.3
+Version: 0.45.1
 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
@@ -224,30 +224,28 @@ Classifier: Topic :: Software Development :: Testing
 Requires-Python: >=3.11
 Requires-Dist: azure-identity>=1.17.1
 Requires-Dist: beartype>=0.22.4
-Requires-Dist: cffi>=1.17.1
-Requires-Dist: crosshair-tool>=0.0.97
 Requires-Dist: cryptography>=43.0.0
 Requires-Dist: gitpython>=3.1.45
 Requires-Dist: graphviz>=0.20.1
-Requires-Dist: hypothesis>=6.142.4
 Requires-Dist: icontract>=2.7.1
 Requires-Dist: jinja2>=3.1.6
 Requires-Dist: jsonschema>=4.23.0
 Requires-Dist: networkx>=3.4.2
 Requires-Dist: opentelemetry-exporter-otlp-proto-http>=1.27.0
 Requires-Dist: opentelemetry-sdk>=1.27.0
+Requires-Dist: packaging>=24.0
 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
-Requires-Dist: ruff>=0.14.2
-Requires-Dist: typer>=0.20.0
+Requires-Dist: typer<0.24,>=0.20.0
 Requires-Dist: typing-extensions>=4.15.0
 Requires-Dist: watchdog>=6.0.0
+Provides-Extra: contracts
+Requires-Dist: crosshair-tool>=0.0.97; extra == 'contracts'
+Requires-Dist: hypothesis>=6.142.4; extra == 'contracts'
 Provides-Extra: dev
 Requires-Dist: basedpyright>=1.32.1; extra == 'dev'
 Requires-Dist: bearer>=3.1.0; extra == 'dev'
@@ -268,6 +266,7 @@ 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: setuptools>=69.0.0; extra == 'dev'
 Requires-Dist: tomlkit>=0.13.3; extra == 'dev'
 Requires-Dist: types-pyyaml>=6.0.12.20250516; extra == 'dev'
 Provides-Extra: enhanced-analysis
@@ -352,26 +351,40 @@ With SpecFact, you get:
 
 ## How do I get started?
 
-### Start Here (5 minutes)
+### Start Here (about 2 minutes): scored code review — no `pip install`
 
-### Install
+**Point SpecFact at your code.** From a **git repository** (any branch), run two commands:
 
 ```bash
-# Zero-install (recommended)
-uvx specfact-cli@latest
-
-# Or install globally
-pip install -U specfact-cli
+uvx specfact-cli init --profile solo-developer
+uvx specfact-cli code review run --path . --scope full
 ```
 
-### Bootstrap
+You should see a **Verdict** (PASS/FAIL), a **Score**, and categorized **findings** — the fastest way to see SpecFact on real code before you dive into backlog, specs, or CI.
+
+- **Command 1** installs the `solo-developer` bundles (including `specfact-codebase` and `specfact-code-review`) into your user module store so `code review` and related commands are available on the next invocation.
+- **Command 2** runs the clean-code review on the repo at `.`. Use **`--scope full`** on the first run so review does not depend on having local git changes.
+
+**Already installed the CLI?** Use the same flow with `specfact` instead of `uvx specfact-cli`:
 
 ```bash
-# Recommended first run
 specfact init --profile solo-developer
+specfact code review run --path . --scope full
 ```
 
-### Get First Value
+**Read the canonical walkthrough:** **[Documentation — Quickstart](https://docs.specfact.io/getting-started/quickstart/)** · **[Installation](https://docs.specfact.io/getting-started/installation/)** (uvx-first, then persistent install).
+
+### Install (persistent CLI for daily use)
+
+```bash
+pip install -U specfact-cli
+```
+
+You can still use **`uvx specfact-cli@latest ...`** anytime without installing; it always fetches the latest published CLI.
+
+### After the wow path: deeper workflows
+
+When you want analysis, snapshots, or sidecar validation on top of the review layer:
 
 ```bash
 # Analyze a codebase you care about
@@ -385,10 +398,7 @@ specfact code validate sidecar init my-project /path/to/repo
 specfact code validate sidecar run my-project /path/to/repo
 ```
 
-That path gives you a concrete first win: SpecFact understands your project context and gives you a
-validated starting point instead of jumping straight into blind change work.
-
-### AI IDE Setup
+### AI IDE setup
 
 ```bash
 specfact init ide
@@ -406,7 +416,7 @@ your IDE. If module prompt payloads are not installed yet, the CLI uses packaged
 Use SpecFact as the validation layer around fast-moving implementation work.
 
 Start with:
-- `specfact init --profile solo-developer`
+- `uvx specfact-cli init --profile solo-developer` then `uvx specfact-cli code review run --path . --scope full` (see **Start Here** above)
 - `specfact code validate sidecar init <bundle> /path/to/repo`
 - `specfact code validate sidecar run <bundle> /path/to/repo`
 
@@ -584,10 +594,11 @@ Use `https://modules.specfact.io/` for the in-depth backlog, project, spec, gove
 
 ## How It Works (High Level)
 
-1. **Bootstrap**: install the CLI and initialize the official bundles you need.
-2. **Analyze or sync**: import code, connect backlog systems, or sync external artifacts into project bundles.
-3. **Validate**: run spec, governance, and sidecar validation flows before implementation or release.
-4. **Iterate safely**: use module-provided workflows while the core runtime keeps command mounting, trust, and lifecycle consistent.
+1. **Bootstrap**: use **uvx** or **pip**, then `init --profile` to install the bundles you need (for example `solo-developer` for a scored **code review** first).
+2. **Review or analyze**: run **`code review run`** on a repo, or import code and snapshot state for deeper workflows.
+3. **Sync**: connect backlog systems or sync external artifacts into project bundles when you are ready.
+4. **Validate**: run spec, governance, and sidecar validation flows before implementation or release.
+5. **Iterate safely**: use module-provided workflows while the core runtime keeps command mounting, trust, and lifecycle consistent.
 
 ## Where SpecFact Fits
 

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/README.md

@@ -71,26 +71,40 @@ With SpecFact, you get:
 
 ## How do I get started?
 
-### Start Here (5 minutes)
+### Start Here (about 2 minutes): scored code review — no `pip install`
 
-### Install
+**Point SpecFact at your code.** From a **git repository** (any branch), run two commands:
 
 ```bash
-# Zero-install (recommended)
-uvx specfact-cli@latest
-
-# Or install globally
-pip install -U specfact-cli
+uvx specfact-cli init --profile solo-developer
+uvx specfact-cli code review run --path . --scope full
 ```
 
-### Bootstrap
+You should see a **Verdict** (PASS/FAIL), a **Score**, and categorized **findings** — the fastest way to see SpecFact on real code before you dive into backlog, specs, or CI.
+
+- **Command 1** installs the `solo-developer` bundles (including `specfact-codebase` and `specfact-code-review`) into your user module store so `code review` and related commands are available on the next invocation.
+- **Command 2** runs the clean-code review on the repo at `.`. Use **`--scope full`** on the first run so review does not depend on having local git changes.
+
+**Already installed the CLI?** Use the same flow with `specfact` instead of `uvx specfact-cli`:
 
 ```bash
-# Recommended first run
 specfact init --profile solo-developer
+specfact code review run --path . --scope full
 ```
 
-### Get First Value
+**Read the canonical walkthrough:** **[Documentation — Quickstart](https://docs.specfact.io/getting-started/quickstart/)** · **[Installation](https://docs.specfact.io/getting-started/installation/)** (uvx-first, then persistent install).
+
+### Install (persistent CLI for daily use)
+
+```bash
+pip install -U specfact-cli
+```
+
+You can still use **`uvx specfact-cli@latest ...`** anytime without installing; it always fetches the latest published CLI.
+
+### After the wow path: deeper workflows
+
+When you want analysis, snapshots, or sidecar validation on top of the review layer:
 
 ```bash
 # Analyze a codebase you care about
@@ -104,10 +118,7 @@ specfact code validate sidecar init my-project /path/to/repo
 specfact code validate sidecar run my-project /path/to/repo
 ```
 
-That path gives you a concrete first win: SpecFact understands your project context and gives you a
-validated starting point instead of jumping straight into blind change work.
-
-### AI IDE Setup
+### AI IDE setup
 
 ```bash
 specfact init ide
@@ -125,7 +136,7 @@ your IDE. If module prompt payloads are not installed yet, the CLI uses packaged
 Use SpecFact as the validation layer around fast-moving implementation work.
 
 Start with:
-- `specfact init --profile solo-developer`
+- `uvx specfact-cli init --profile solo-developer` then `uvx specfact-cli code review run --path . --scope full` (see **Start Here** above)
 - `specfact code validate sidecar init <bundle> /path/to/repo`
 - `specfact code validate sidecar run <bundle> /path/to/repo`
 
@@ -303,10 +314,11 @@ Use `https://modules.specfact.io/` for the in-depth backlog, project, spec, gove
 
 ## How It Works (High Level)
 
-1. **Bootstrap**: install the CLI and initialize the official bundles you need.
-2. **Analyze or sync**: import code, connect backlog systems, or sync external artifacts into project bundles.
-3. **Validate**: run spec, governance, and sidecar validation flows before implementation or release.
-4. **Iterate safely**: use module-provided workflows while the core runtime keeps command mounting, trust, and lifecycle consistent.
+1. **Bootstrap**: use **uvx** or **pip**, then `init --profile` to install the bundles you need (for example `solo-developer` for a scored **code review** first).
+2. **Review or analyze**: run **`code review run`** on a repo, or import code and snapshot state for deeper workflows.
+3. **Sync**: connect backlog systems or sync external artifacts into project bundles when you are ready.
+4. **Validate**: run spec, governance, and sidecar validation flows before implementation or release.
+5. **Iterate safely**: use module-provided workflows while the core runtime keeps command mounting, trust, and lifecycle consistent.
 
 ## Where SpecFact Fits
 

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "specfact-cli"
-version = "0.43.3"
+version = "0.45.1"
 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"
@@ -36,6 +36,10 @@ keywords = [
     "cli",
     "specfact",
 ]
+# Install profiles (PEP 621 extras):
+# - `pip install specfact-cli` — minimal runtime (CLI, registry, contracts via icontract/beartype, no CrossHair/Hypothesis wheels).
+# - `pip install specfact-cli[contracts]` — add CrossHair + Hypothesis for contract exploration / property tooling.
+# - `pip install specfact-cli[dev]` — contributors: pytest, linters, and same contract tools as [contracts] (see dev list).
 classifiers = [
     "Development Status :: 4 - Beta",
     "Intended Audience :: Developers",
@@ -51,16 +55,17 @@ classifiers = [
 dependencies = [
     # Core dependencies
     "pydantic>=2.12.3",
-    "python-dotenv>=1.2.1",
     "typing-extensions>=4.15.0",
     "PyYAML>=6.0.3",
     "requests>=2.32.3",
     "azure-identity>=1.17.1",
     "cryptography>=43.0.0",
-    "cffi>=1.17.1",
-    
+    "packaging>=24.0",
+    # PEP 440 / markers for module installer and registry (do not rely on transitive pins only)
+
     # CLI framework
-    "typer>=0.20.0",
+    # Typer 0.24+ requires click>=8.2.1 (generic Choice[...]); dev semgrep pins click~=8.1.8 — cap Typer.
+    "typer>=0.20.0,<0.24",
     "rich>=13.5.2,<13.6.0",  # Compatible with semgrep (requires rich~=13.5.2)
     "questionary>=2.0.1",  # Interactive prompts with arrow key navigation
     
@@ -80,16 +85,10 @@ dependencies = [
     # Schema validation
     "jsonschema>=4.23.0",
     
-    # Contract-First Development Dependencies
+    # Contract-First (runtime decorators; exploration tools are optional extra `contracts`)
     "icontract>=2.7.1",  # Design-by-contract decorators
     "beartype>=0.22.4",  # Runtime type checking
-    "crosshair-tool>=0.0.97",  # Contract exploration and counterexample discovery
-    "hypothesis>=6.142.4",  # Property-based testing
-    
-    # Code analysis
-    "ruff>=0.14.2",
-    "radon>=6.0.1",
-    
+
     # File system watching
     "watchdog>=6.0.0",
 
@@ -99,7 +98,13 @@ dependencies = [
 ]
 
 [project.optional-dependencies]
+contracts = [
+    "crosshair-tool>=0.0.97",
+    "hypothesis>=6.142.4",
+]
+
 dev = [
+    "setuptools>=69.0.0",
     "pytest>=8.4.2",
     "pytest-cov>=7.0.0",
     "pytest-mock>=3.15.1",
@@ -114,12 +119,14 @@ dev = [
     "types-PyYAML>=6.0.12.20250516",
     "pip-tools>=7.5.1",
     "semgrep>=1.144.0",  # Latest version compatible with rich~=13.5.2
-    
-    # Contract-First Development Dependencies (dev)
-    "icontract>=2.7.1",
-    "beartype>=0.22.4", 
+
+    # Same contract exploration stack as [contracts] (extras cannot self-reference)
     "crosshair-tool>=0.0.97",
     "hypothesis>=6.142.4",
+
+    # Contract-First Development Dependencies (dev)
+    "icontract>=2.7.1",
+    "beartype>=0.22.4",
     
     # Enhanced Analysis Tools (for local development)
     # Note: syft excluded from dev/test due to rich version conflict with semgrep
@@ -165,12 +172,13 @@ specfact-cli = "specfact_cli.cli:cli_main"  # Alias for uvx compatibility
 [tool.hatch.envs.default]
 python = "3.12"
 dependencies = [
+    # Semgrep pulls opentelemetry; some versions import pkg_resources (setuptools)
+    "setuptools>=69.0.0",
     "pip-tools",
     "pytest",
     "pytest-cov",
     "pytest-mock",
     "pytest-xdist",
-    "python-dotenv",
     "pre-commit",
     # Ensure format/lint tools are available in the hatch env
     "isort>=7.0.0",
@@ -204,6 +212,9 @@ governance = "pylint src tests tools --reports=y --output-format=parseable"
 format = "ruff check . --fix && ruff format ."
 
 # Code scanning (Semgrep)
+# Semgrep 1.38+ deprecated implicit .semgrep.yml discovery; always pass --config explicitly.
+# Script must not be named `semgrep` (Hatch treats that as circular expansion with the semgrep CLI).
+semgrep-full = "semgrep --config tools/semgrep {args}"
 scan = "semgrep --config tools/semgrep/async.yml {args}"
 scan-all = "semgrep --config tools/semgrep/async.yml ."
 scan-json = "semgrep --config tools/semgrep/async.yml --json . > logs/semgrep-results.json"

specfact_cli-0.45.1/resources/templates/github-action.yml.j2

@@ -0,0 +1,200 @@
+# yaml-language-server: $schema=https://json.schemastore.org/github-workflow.json
+# yamllint disable rule:line-length rule:truthy
+# Generated workflow — aligns with current SpecFact CLI: non-interactive CI must run
+# `specfact init --profile …` (or `specfact module install …`) before `specfact code …` commands.
+name: SpecFact CLI Validation
+
+on:
+  pull_request:
+    branches: [main, dev]
+    paths-ignore:
+      - "docs/**"
+      - "**.md"
+      - "**.mdc"
+  push:
+    branches: [main, dev]
+    paths-ignore:
+      - "docs/**"
+      - "**.md"
+      - "**.mdc"
+  workflow_dispatch:
+    inputs:
+      budget:
+        description: "Time budget in seconds for code repro"
+        required: false
+        default: "{{ budget }}"
+        type: string
+      mode:
+        description: "Enforcement mode (block, warn, log)"
+        required: false
+        default: "block"
+        type: choice
+        options:
+          - block
+          - warn
+          - log
+      version_check_mode:
+        description: "Project bundle version check (info, warn, block; skipped if no .specfact/projects)"
+        required: false
+        default: "info"
+        type: choice
+        options:
+          - info
+          - warn
+          - block
+      bundle_name:
+        description: "Project bundle name for `specfact project version check` (under .specfact/projects/)"
+        required: false
+        default: "{{ bundle_name }}"
+        type: string
+
+jobs:
+  specfact-validation:
+    name: Contract Validation
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      pull-requests: write
+      checks: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "{{ python_version }}"
+          cache: "pip"
+
+      - name: Install SpecFact CLI
+        run: |
+          python -m pip install --upgrade pip
+          echo "📦 Installing SpecFact CLI..."
+          pip install specfact-cli
+
+      - name: Bootstrap SpecFact (CI — required for workflow commands)
+        run: |
+          # Non-interactive CI must pass --profile or --install (see `specfact init --help`).
+          specfact init --profile solo-developer --repo .
+
+      - name: Set validation parameters
+        id: validation
+        run: |
+          BUDGET="{% raw %}${{ github.event.inputs.budget || '{% endraw %}{{ budget }}{% raw %}' }}{% endraw %}"
+          MODE="{% raw %}${{ github.event.inputs.mode || 'block' }}{% endraw %}"
+          VERSION_CHECK_MODE="{% raw %}${{ github.event.inputs.version_check_mode || 'info' }}{% endraw %}"
+          BUNDLE_NAME="{% raw %}${{ github.event.inputs.bundle_name || '{% endraw %}{{ bundle_name }}{% raw %}' }}{% endraw %}"
+          echo "budget=$BUDGET" >> "$GITHUB_OUTPUT"
+          echo "mode=$MODE" >> "$GITHUB_OUTPUT"
+          echo "version_check_mode=$VERSION_CHECK_MODE" >> "$GITHUB_OUTPUT"
+          echo "bundle_name=$BUNDLE_NAME" >> "$GITHUB_OUTPUT"
+          echo "SPECFACT_BUDGET=$BUDGET" >> "$GITHUB_ENV"
+          echo "SPECFACT_MODE=$MODE" >> "$GITHUB_ENV"
+          echo "SPECFACT_VERSION_CHECK_MODE=$VERSION_CHECK_MODE" >> "$GITHUB_ENV"
+          echo "BUNDLE_NAME=$BUNDLE_NAME" >> "$GITHUB_ENV"
+
+      - name: Optional — CrossHair / repro tooling setup
+        continue-on-error: true
+        run: specfact code repro setup
+
+      - name: Run contract validation (code repro)
+        id: repro
+        continue-on-error: true
+        run: |
+          set +e
+          specfact code repro --verbose --budget "{% raw %}${{ steps.validation.outputs.budget }}{% endraw %}"
+          ec=$?
+          set -e
+          echo "exit_code=$ec" >> "$GITHUB_OUTPUT"
+
+      - name: Project bundle version check (optional)
+        id: version_check
+        continue-on-error: true
+        run: |
+          VERSION_CHECK_MODE="{% raw %}${{ steps.validation.outputs.version_check_mode }}{% endraw %}"
+          BUNDLE_NAME="{% raw %}${{ steps.validation.outputs.bundle_name }}{% endraw %}"
+          echo "📌 Bundle version check (mode: $VERSION_CHECK_MODE, bundle: $BUNDLE_NAME)..."
+          if [ ! -d .specfact/projects ]; then
+            echo "No .specfact/projects — skipping project version check."
+            echo "version_check_passed=skipped" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+          if ! find .specfact/projects -mindepth 1 -maxdepth 1 -type d 2>/dev/null | grep -q .; then
+            echo "No project bundles under .specfact/projects — skipping."
+            echo "version_check_passed=skipped" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+          if specfact project version check --repo . --bundle "$BUNDLE_NAME"; then
+            echo "version_check_passed=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "version_check_passed=false" >> "$GITHUB_OUTPUT"
+            if [ "$VERSION_CHECK_MODE" = "warn" ]; then
+              echo "⚠️ Version check did not pass (warn mode — continuing)"
+            elif [ "$VERSION_CHECK_MODE" = "block" ]; then
+              echo "❌ Version check failed (block mode)"
+              exit 1
+            else
+              echo "ℹ️ Version check finished (info mode — continuing)"
+            fi
+          fi
+
+      - name: Find latest repro report
+        id: report
+        if: always()
+        run: |
+          REPORT_DIR=".specfact/reports/enforcement"
+          if [ -d "$REPORT_DIR" ]; then
+            LATEST_REPORT=$(find "$REPORT_DIR" -name "report-*.yaml" -type f -printf "%T@ %p\n" | sort -n | tail -1 | cut -d' ' -f2-)
+            if [ -n "$LATEST_REPORT" ]; then
+              echo "path=$LATEST_REPORT" >> "$GITHUB_OUTPUT"
+              echo "SPECFACT_REPORT_PATH=$LATEST_REPORT" >> "$GITHUB_ENV"
+            fi
+          fi
+
+      - name: Create GitHub annotations
+        id: annotations
+        if: {% raw %}${{ always() && steps.report.outputs.path != '' }}{% endraw %}
+        run: |
+          python -m specfact_cli.utils.github_annotations || true
+
+      - name: Generate PR comment
+        id: pr-comment
+        if: {% raw %}${{ always() && github.event_name == 'pull_request' && steps.report.outputs.path != '' }}{% endraw %}
+        run: |
+          python -m specfact_cli.utils.github_annotations
+          if [ -f ".specfact/pr-comment.md" ]; then
+            echo "comment_path=.specfact/pr-comment.md" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Post PR comment
+        if: {% raw %}${{ always() && github.event_name == 'pull_request' && steps.pr-comment.outputs.comment_path != '' }}{% endraw %}
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const fs = require('fs');
+            const commentPath = '{% raw %}${{ steps.pr-comment.outputs.comment_path }}{% endraw %}';
+            if (fs.existsSync(commentPath)) {
+              const comment = fs.readFileSync(commentPath, 'utf8');
+              github.rest.issues.createComment({
+                issue_number: context.issue.number,
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                body: comment
+              });
+            }
+
+      - name: Upload validation report
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: specfact-report
+          path: |
+            .specfact/reports/enforcement/*.yaml
+            .specfact/pr-comment.md
+          if-no-files-found: ignore
+
+      - name: Fail workflow if validation failed
+        if: {% raw %}${{ steps.repro.outputs.exit_code != '0' && steps.validation.outputs.mode == 'block' }}{% endraw %}
+        run: |
+          echo "❌ Validation failed. Exiting with error code."
+          exit 1

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/resources/templates/pr-template.md.j2

@@ -14,6 +14,15 @@
 
 ## ✅ Validation
 
+**CI / local prerequisites (SpecFact v0.40+):**
+
+- Install: `pip install specfact-cli` (or `uvx specfact-cli@latest` for one-off runs).
+- **Non-interactive / CI** must bootstrap workflow bundles before `specfact code …` or `specfact project …`:
+  - `specfact init --profile solo-developer --repo .` (or another profile / `specfact init --install …`), **or**
+  - `specfact module install nold-ai/specfact-codebase` (and other bundles as needed).
+- Contract repro in CI uses **`specfact code repro`** (not `specfact repro`). Optional: `specfact code repro setup` for CrossHair config.
+- Optional `specfact project version check` needs a project under `.specfact/projects/<bundle>/` and `--bundle <name>`.
+
 **SpecFact CLI Validation Results:**
 
 {% if validation_passed %}

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/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.43.3"
+__version__ = "0.45.1"

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/src/specfact_cli/__init__.py

@@ -45,6 +45,6 @@ def _bootstrap_bundle_paths() -> None:
 
 _bootstrap_bundle_paths()
 
-__version__ = "0.43.3"
+__version__ = "0.45.1"
 
 __all__ = ["__version__"]

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/src/specfact_cli/adapters/speckit.py

@@ -426,7 +426,7 @@ class SpecKitAdapter(BridgeAdapter):
                 )
                 if title_match:
                     feature_title = title_match.group(1).strip()
-            except Exception:
+            except (OSError, UnicodeDecodeError):
                 pass
         if not feature_title or feature_title.strip() == "":
             return "Unknown Feature"

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/src/specfact_cli/agents/analyze_agent.py

@@ -262,7 +262,7 @@ Focus on semantic understanding, not just structural parsing. Generate the plan
                 try:
                     content = dep_file.read_text(encoding="utf-8")[:500]
                     dependencies.append(f"{dep_file.name}: {content[:100]}...")
-                except Exception:
+                except (OSError, UnicodeDecodeError):
                     pass
         return dependencies
 

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/src/specfact_cli/analyzers/ambiguity_scanner.py

@@ -772,7 +772,7 @@ class AmbiguityScanner:
                     continue
                 if user_clean and len(user_clean) > 2 and user_lower not in excluded and len(user_clean.split()) <= 3:
                     result.add(user_clean.title())
-        except Exception:
+        except (OSError, UnicodeDecodeError, re.error):
             pass
         return result
 
@@ -898,9 +898,9 @@ class AmbiguityScanner:
                         continue
                     try:
                         self._personas_from_py_file(py_file, result, excluded)
-                    except Exception:
+                    except (OSError, UnicodeDecodeError, re.error):
                         continue
-        except Exception:
+        except (OSError, UnicodeDecodeError, re.error):
             pass
         return result
 

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/src/specfact_cli/analyzers/code_analyzer.py

@@ -1794,14 +1794,14 @@ class CodeAnalyzer:
             for commit in commits:
                 try:
                     self._process_commit_for_feature_bounds(commit)
-                except Exception:
+                except (OSError, ValueError):
                     # Skip individual commits that fail (corrupted, etc.)
                     continue
 
         except ImportError:
             # GitPython not available, skip
             pass
-        except Exception:
+        except OSError:
             # Git operations failed, skip gracefully
             pass
 

{specfact_cli-0.43.3 → specfact_cli-0.45.1}/src/specfact_cli/analyzers/contract_extractor.py

@@ -240,7 +240,7 @@ class ContractExtractor:
         if hasattr(ast, "unparse"):
             try:
                 return ast.unparse(node)
-            except Exception:
+            except (ValueError, TypeError):
                 pass
 
         # Fallback: manual conversion
@@ -282,7 +282,7 @@ class ContractExtractor:
         if hasattr(ast, "unparse"):
             try:
                 return ast.unparse(node)
-            except Exception:
+            except (ValueError, TypeError):
                 pass
 
         return "..."
@@ -295,7 +295,7 @@ class ContractExtractor:
         if hasattr(ast, "unparse"):
             try:
                 return ast.unparse(node)
-            except Exception:
+            except (ValueError, TypeError):
                 pass
 
         # Fallback: basic conversion