specfact-cli 0.26.17__tar.gz → 0.28.0__tar.gz

{specfact_cli-0.26.17 → specfact_cli-0.28.0}/.gitignore

@@ -95,15 +95,21 @@ docs/internal/
 
 # Ignore .specify artifacts
 .specify/
-.cursor/commands/speckit.*
+.cursor/commands/speckit.*.md
 /specs/
 
-# Include openspec/specs/ directory
-!openspec/
-
 # Ignore specfact-cli prompt templates
-.cursor/commands/specfact-*
-.github/prompts/specfact-*
+.cursor/commands/specfact.*.md
+.cursor/commands/opsx-*.md
+
+.cursor/skills/openspec-*/
+
+.github/prompts/specfact.*.md
+.github/prompts/opsx-*.md
+
+.claude/commands/opsx/
+.claude/skills/openspec-*/
+!.claude/skills/openspec-workflows/
 
 # Semgrep rules (generated from tools/semgrep/ - source rules are versioned)
 .semgrep/
@@ -127,4 +133,9 @@ findings.json
 answers.json
 questions.json
 docs/project-plans/
-harness_contracts.py
+harness_contracts.py
+
+# semgrep artifacts
+lang.json
+Language.ml
+Language.mli

{specfact_cli-0.26.17 → specfact_cli-0.28.0}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: specfact-cli
-Version: 0.26.17
-Summary: Brownfield-first CLI: Reverse engineer legacy Python → specs → enforced contracts. Automate legacy code documentation and prevent modernization regressions.
+Version: 0.28.0
+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
 Project-URL: Documentation, https://github.com/nold-ai/specfact-cli#readme
@@ -211,7 +211,7 @@ License:                                  Apache License
            See the License for the specific language governing permissions and
            limitations under the License.
 License-File: LICENSE.md
-Keywords: async,beartype,brownfield,cli,code-documentation,code-to-spec,contract-driven-development,contracts,crosshair,icontract,legacy-code,modernization,property-based-testing,quality-gates,refactoring,reverse-engineering,spec-first,specfact,state-machine,tdd,technical-debt
+Keywords: agile,backlog,beartype,ceremonies,cli,contract-driven-development,contracts,crosshair,devops,existing-code,icontract,kanban,legacy,modernization,policy-as-code,property-based-testing,safe,scrum,specfact,specs,tdd,validation
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: Apache Software License
@@ -278,319 +278,194 @@ Description-Content-Type: text/markdown
 
 # SpecFact CLI
 
-> **Brownfield-first legacy code modernization with runtime contract enforcement.**  
-> Analyze existing Python code → Extract specs → Find gaps → Enforce contracts → Prevent regressions
+> **The "swiss knife" CLI that turns any codebase into a clear, safe, and shippable workflow.**
+> Keep backlog, specs, tests, and code in sync so AI-assisted changes do not break production.
+> Works for brand-new projects and long-lived codebases - even if you are new to coding.
 
 **No API keys required. Works offline. Zero vendor lock-in.**
 
-[![PyPI version](https://img.shields.io/pypi/v/specfact-cli.svg)](https://pypi.org/project/specfact-cli/)
+[![PyPI version](https://img.shields.io/pypi/v/specfact-cli.svg?color=22c55e)](https://pypi.org/project/specfact-cli/)
 [![Python versions](https://img.shields.io/pypi/pyversions/specfact-cli.svg)](https://pypi.org/project/specfact-cli/)
 [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE.md)
-[![Status](https://img.shields.io/badge/status-beta-orange.svg)](https://github.com/nold-ai/specfact-cli)
+[![Status](https://img.shields.io/badge/status-beta-F59E0B.svg)](https://github.com/nold-ai/specfact-cli)
 
 <div align="center">
 
-**[🌐 specfact.com](https://specfact.com)** • **[📚 specfact.io](https://specfact.io)** • **[👨‍💻 specfact.dev](https://specfact.dev)** • **[📖 Documentation](https://docs.specfact.io/)** • **[💬 Support](mailto:hello@noldai.com)**
+**[specfact.com](https://specfact.com)** • **[specfact.io](https://specfact.io)** • **[specfact.dev](https://specfact.dev)** • **[Documentation](https://docs.specfact.io/)** • **[Support](mailto:hello@noldai.com)**
 
 </div>
 
-## 🌐 SpecFact Domains
-
-- **[specfact.com](https://specfact.com)** - Commercial landing page (marketing, pricing, enterprise)
-- **[specfact.io](https://specfact.io)** - Product ecosystem hub (CLI reference, integrations, changelog, product docs)
-- **[specfact.dev](https://specfact.dev)** - Developer community (tutorials, guides, blog, community content) ⭐ **For developers**
-- **[docs.specfact.io](https://docs.specfact.io/)** - Complete online documentation
-
----
-
-## What is SpecFact?
-
-**SpecFact CLI analyzes your existing Python code** to automatically extract specifications, find missing tests and contracts, and enforce them to prevent bugs during modernization.
-
-**Perfect for:** Teams modernizing legacy Python systems who can't afford production bugs during migration.
-
-### Why SpecFact?
-
-AI coding assistants are powerful but unpredictable when requirements live in chat history. SpecFact adds a **brownfield-first analysis workflow** that understands existing code, extracts specs automatically, and enforces them as runtime contracts, giving you deterministic, reviewable outputs.
-
-**Key outcomes:**
-
-- **Understand legacy code** in minutes, not weeks (automatic spec extraction)
-- **Find gaps** in tests, contracts, and documentation automatically
-- **Prevent regressions** with runtime contract enforcement during modernization
-- **Works with the tools you already use**: VS Code, Cursor, GitHub Actions, pre-commit hooks
-- **No API keys required** - Works completely offline
-
 ---
 
-## 🚀 Quick Start
+## Start Here (60 seconds)
 
-### Step 1: Install SpecFact CLI
+### Install
 
 ```bash
-# Zero-install (recommended - no setup needed)
+# Zero-install (recommended)
 uvx specfact-cli@latest
 
 # Or install globally
 pip install -U specfact-cli
 ```
 
-### Step 2: Initialize IDE Integration
-
-**Set up slash commands in your IDE (Cursor, VS Code, Copilot, etc.):**
+### Initialize IDE Integration (optional but recommended)
 
 ```bash
-# Auto-detect IDE and initialize
 specfact init
-
-# Or specify IDE explicitly
 specfact init --ide cursor
 specfact init --ide vscode
-
-# Install required packages for contract enhancement
-specfact init --ide cursor --install-deps
 ```
 
-**What this does:**
-
-- Copies prompt templates to your IDE
-- Makes slash commands available in your IDE's AI chat
-- Optionally installs required packages (`beartype`, `icontract`, `crosshair-tool`, `pytest`)
-
-### Step 3: Run Your First Analysis
-
-**In your IDE's AI chat, use the slash command:**
-
-```bash
-# In IDE chat (Cursor, VS Code, Copilot, etc.)
-/specfact.01-import my-project --repo .
-```
-
-**Or use the CLI directly:**
+### Run Your First Flow
 
 ```bash
-# Analyze legacy codebase (most common use case)
+# Analyze an existing codebase
 specfact import from-code my-project --repo .
 
-# Or validate external codebase without modifying source (sidecar validation)
+# Validate external code without modifying source
 specfact validate sidecar init my-project /path/to/repo
 specfact validate sidecar run my-project /path/to/repo
 ```
 
-**⏱️ Timing:** Analysis typically takes **10-15 minutes** for typical repositories (e.g., `specfact-cli` itself with several hundred features & contracts). Smaller codebases may complete in 2-5 minutes. Large codebases (3000+ features) may take 15-30 minutes, but progress reporting shows real-time status. The analysis performs AST parsing, Semgrep pattern detection, and Specmatic integration.
+**AI IDE quick start**
 
-**💾 Checkpointing:** Features are saved immediately after initial analysis, so you can safely interrupt and resume the import process without losing progress.
-
-**⚡ Performance:** Optimized for large codebases with pre-computed AST parsing and file hashes (5-15x faster than previous versions).
+```bash
+# In your IDE chat (Cursor, VS Code, Copilot, etc.)
+/specfact.01-import my-project --repo .
+```
 
-**That's it!** SpecFact will extract features and stories from your code, find missing tests and contracts, and generate a plan bundle you can enforce.
+**Next steps**
 
-👉 **[Getting Started Guide](docs/getting-started/README.md)** - Complete walkthrough with examples  
-👉 **[AI IDE Workflow Guide](docs/guides/ai-ide-workflow.md)** ⭐ - Complete AI-assisted development workflow
+- **[Getting Started](docs/getting-started/README.md)**
+- **[AI IDE Workflow](docs/guides/ai-ide-workflow.md)**
+- **[Command Chains](docs/guides/command-chains.md)**
 
 ---
 
-## 🎯 Find Your Path
-
-### New to SpecFact?
-
-**Primary Goal**: Analyze legacy Python → find gaps → enforce contracts
-
-1. **[Getting Started](docs/getting-started/README.md)** - Install and run your first command
-2. **[Command Chains Reference](docs/guides/command-chains.md)** ⭐ **NEW** - Complete workflows from start to finish
-3. **[Common Tasks Quick Reference](docs/guides/common-tasks.md)** ⭐ **NEW** - Quick answers to "How do I X?"
-4. **[Modernizing Legacy Code?](docs/guides/brownfield-engineer.md)** ⭐ - Brownfield-first guide
-5. **[The Brownfield Journey](docs/guides/brownfield-journey.md)** ⭐ - Complete modernization workflow
-
-**Time**: < 10 minutes | **Result**: Running your first brownfield analysis
-
-### Using AI IDEs? (Cursor, Copilot, Claude)
+## Proof and Expectations
 
-**Primary Goal**: Let SpecFact find gaps, use your AI IDE to fix them
-
-👉 **[AI IDE Workflow Guide](docs/guides/ai-ide-workflow.md)** ⭐ **NEW** - Complete AI-assisted development workflow
-
-### Working with a Team?
-
-**Primary Goal**: Enable team collaboration with role-based workflows
-
-👉 **[Agile/Scrum Workflows](docs/guides/agile-scrum-workflows.md)** ⭐ - Persona-based team collaboration
-
-### Need Integrations?
-
-**Primary Goal**: Integrate with Spec-Kit, OpenSpec, Specmatic, or DevOps tools
-
-👉 **[Integrations Overview](docs/guides/integrations-overview.md)** ⭐ **NEW** - Complete guide to all integrations
+- **Typical runtime**: 2-15 minutes depending on repo size and complexity.
+- **Checkpointing**: Progress is saved during analysis so you can resume safely.
+- **Performance**: Optimized for large codebases with cached parsing and file hashes.
 
 ---
 
-## Key Features
-
-### 🔍 Code Analysis
-
-- **Reverse engineer** legacy code into documented specs
-- **Find gaps** in tests, contracts, and documentation
-- **Works with** any Python project (no special setup required)
-
-👉 **[Command Chains](docs/guides/command-chains.md)** - See complete workflows
-
-### 🛡️ Contract Enforcement
-
-- **Prevent regressions** with runtime contract validation
-- **CI/CD integration** - Block bad code from merging
-- **Works offline** - No cloud required
-- **Sidecar validation** - Validate external codebases without modifying source code
-
-👉 **[Command Reference](docs/reference/commands.md)** - All enforcement commands  
-👉 **[Sidecar Validation Guide](docs/guides/sidecar-validation.md)** - Validate external codebases
-
-### 👥 Team Collaboration
-
-- **Role-based workflows** - Product Owners, Architects, Developers work in parallel
-- **Markdown-based** - No YAML editing required
-- **Agile/scrum ready** - DoR checklists, story points, dependencies
-- **Backlog standardization** 🆕 - Template-driven refinement with persona/framework filtering
-- **Sprint/iteration filtering** 🆕 - Filter by sprint, release, iteration for agile workflows
-- **Interactive field mapping** 🆕 - Discover and map Azure DevOps fields with arrow-key navigation
-- **Azure DevOps integration** 🆕 - Full support for ADO work items with automatic token resolution
+## Why It Matters (Plain Language)
 
-👉 **[Agile/Scrum Workflows](docs/guides/agile-scrum-workflows.md)** - Team collaboration guide  
-👉 **[Backlog Refinement](docs/guides/backlog-refinement.md)** 🆕 - Standardize backlog items with templates  
-👉 **[Custom Field Mapping](docs/guides/custom-field-mapping.md)** 🆕 - Map ADO fields interactively
-
-### 🔌 Integrations
-
-- **VS Code, Cursor** - Catch bugs before you commit
-- **GitHub Actions** - Automated quality gates
-- **AI IDEs** - Generate prompts for fixing gaps
-- **DevOps tools** - Sync with GitHub Issues, Azure DevOps, Linear, Jira
-- **Backlog Refinement** 🆕 - AI-assisted template-driven refinement for standardizing work items
-- **Azure DevOps field mapping** 🆕 - Interactive field discovery and mapping for custom ADO process templates
-- **Spec-Kit, OpenSpec, Specmatic** - Works with your existing tools
-
-👉 **[Integrations Overview](docs/guides/integrations-overview.md)** - All integration options  
-👉 **[Backlog Refinement Guide](docs/guides/backlog-refinement.md)** 🆕 **NEW** - Template-driven backlog standardization  
-👉 **[Custom Field Mapping](docs/guides/custom-field-mapping.md)** 🆕 **NEW** - Interactive ADO field mapping
+- **Clarity**: Turn messy code into clear specs your team can trust.
+- **Safety**: Catch risky changes early with validation and contract checks.
+- **Sync**: Keep backlog items, specs, tests, and code aligned end to end.
+- **Adoption**: Simple CLI, no platform lock-in, works offline.
 
 ---
 
-## Common Use Cases
-
-### 1. Modernizing Legacy Code ⭐ **Most Common**
-
-**Problem:** Existing codebase with no specs or outdated documentation
-
-👉 **[Brownfield Modernization Guide](docs/guides/brownfield-engineer.md)** - Complete walkthrough
-
-### 1.5. Validating External Codebases (Sidecar Validation) 🆕
-
-**Problem:** Need to validate third-party libraries or legacy codebases without modifying source code
+## Who It Is For
 
-👉 **[Sidecar Validation Guide](docs/guides/sidecar-validation.md)** - Validate external codebases with contract testing
+- **Vibe coders and new builders** who want to ship fast with guardrails and confidence.
+- **Legacy professionals** who want AI speed without lowering standards.
+- **DevOps and engineering leaders** who need evidence and repeatable workflows.
 
-### 2. Working with a Team
+---
 
-**Problem:** Need team collaboration with role-based workflows
+## How It Works (High Level)
 
-👉 **[Agile/Scrum Workflows Guide](docs/guides/agile-scrum-workflows.md)** - Team collaboration guide
+1. **Analyze**: Read code and extract specs, gaps, and risks.
+2. **Sync**: Connect specs, backlog items, and plans in one workflow.
+3. **Validate**: Enforce contracts and block regressions before production.
 
-### 3. Using AI IDEs (Cursor, Copilot, Claude)
+---
 
-**Problem:** Want AI to fix gaps, but need validation
+## The Missing Link (Coder + DevOps Bridge)
 
-👉 **[AI IDE Workflow Guide](docs/guides/ai-ide-workflow.md)** - Complete AI-assisted workflow
+Most tools help **either** coders **or** agile teams. SpecFact does both:
 
-### 4. Integrating with Other Tools
+- **Backlog sync that is actually strong**: round-trip sync + refinement with GitHub, Azure DevOps, Jira, Linear.
+- **Ceremony support teams can run**: standup, refinement, sprint planning, flow metrics (Scrum/Kanban/SAFe).
+- **Policy + validation**: DoR/DoD/flow checks plus contract enforcement for production-grade stability.
 
-**Problem:** Want to use SpecFact with Spec-Kit, OpenSpec, or Specmatic
+**Try it now**
 
-👉 **[Integrations Overview](docs/guides/integrations-overview.md)** - Choose the right integration
+- **Coders**: [AI IDE Workflow](docs/guides/ai-ide-workflow.md)
+- **Agile teams**: [Agile/Scrum Workflows](docs/guides/agile-scrum-workflows.md)
 
 ---
 
-## Documentation
+## Modules and Capabilities
 
-### Quick References
+**Core modules**
 
-- **[Command Chains](docs/guides/command-chains.md)** ⭐ **NEW** - Complete workflows from start to finish
-- **[Common Tasks](docs/guides/common-tasks.md)** ⭐ **NEW** - Quick answers to "How do I X?"
-- **[Command Reference](docs/reference/commands.md)** - All commands documented
+- **Analyze**: Extract specs and plans from existing code.
+- **Validate**: Enforce contracts, run reproducible checks, and block regressions.
+- **Report**: CI/CD summaries and evidence outputs.
 
-### Getting Started
+**Agile DevOps modules**
 
-- **[Getting Started Guide](docs/getting-started/README.md)** - Install and first commands
-- **[Modernizing Legacy Code?](docs/guides/brownfield-engineer.md)** ⭐ - Brownfield-first guide
-- **[The Brownfield Journey](docs/guides/brownfield-journey.md)** ⭐ - Complete modernization workflow
+- **Backlog**: Refinement, dependency analysis, sprint summaries, risk rollups.
+- **Ceremony**: Standup, refinement, and planning entry points.
+- **Policy**: DoR, DoD, flow, PI readiness checks.
+- **Patch**: Preview, apply, and write changes safely.
 
-### Guides
+**Adapters and bridges**
 
-- **[AI IDE Workflow](docs/guides/ai-ide-workflow.md)** ⭐ **NEW** - AI-assisted development
-- **[Agile/Scrum Workflows](docs/guides/agile-scrum-workflows.md)** ⭐ - Team collaboration
-- **[Integrations Overview](docs/guides/integrations-overview.md)** ⭐ **NEW** - All integrations
-- **[Sidecar Validation](docs/guides/sidecar-validation.md)** 🆕 - Validate external codebases without modifying source
-- **[Use Cases](docs/guides/use-cases.md)** - Common scenarios
+- **Specs**: Spec-Kit and OpenSpec
+- **Backlogs**: GitHub Issues, Azure DevOps, Jira, Linear
+- **Contracts**: Specmatic, OpenAPI
 
-### Integration Guides
+---
 
-- **[Spec-Kit Journey](docs/guides/speckit-journey.md)** - From Spec-Kit to SpecFact
-- **[OpenSpec Journey](docs/guides/openspec-journey.md)** - OpenSpec integration
-- **[Specmatic Integration](docs/guides/specmatic-integration.md)** - API contract testing
-- **[DevOps Adapter Integration](docs/guides/devops-adapter-integration.md)** - GitHub Issues, Azure DevOps, Linear, Jira
-- **[Backlog Refinement](docs/guides/backlog-refinement.md)** 🆕 **NEW** - AI-assisted template-driven backlog standardization
-- **[Custom Field Mapping](docs/guides/custom-field-mapping.md)** 🆕 **NEW** - Interactive Azure DevOps field mapping
+## Developer Note: Command Layout
 
-👉 **[Full Documentation Index](docs/README.md)** - Browse all documentation  
-👉 **[Online Documentation](https://docs.specfact.io/)** - Complete documentation site
+- Primary command implementations live in `src/specfact_cli/modules/<module>/src/commands.py`.
+- Legacy imports from `src/specfact_cli/commands/*.py` are compatibility shims and only guarantee `app` re-exports.
+- Preferred imports for module code:
+  - `from specfact_cli.modules.<module>.src.commands import app`
+  - `from specfact_cli.modules.<module>.src.commands import <symbol>`
+- Shim deprecation timeline:
+  - Legacy shim usage is deprecated for non-`app` symbols now.
+  - Shim removal is planned no earlier than `v0.30` (or the next major migration window).
 
 ---
 
-## How SpecFact Compares
+## Where SpecFact Fits
 
-**New to spec-driven development?** Here's how SpecFact compares to other tools:
+SpecFact complements your stack rather than replacing it.
 
-| Tool | Best For | SpecFact's Focus |
-|------|----------|------------------|
-| **GitHub Spec-Kit** | Greenfield specs, multi-language, interactive authoring | **Brownfield analysis**, runtime enforcement, formal verification |
-| **OpenSpec** | Specification anchoring, change tracking, cross-repo workflows | **Code analysis**, contract enforcement, DevOps integration |
-| **Traditional Testing** | Manual test writing, code review | **Automated gap detection**, contract-first validation, CI/CD gates |
+- **Spec-Kit/OpenSpec** for authoring and change tracking
+- **Backlog tools** for planning and delivery
+- **CI/CD** for enforcement and regression prevention
 
-**Key Differentiators:**
+**SpecFact connects them** with adapters, policy checks, and deterministic validation.
 
-- ✅ **Brownfield-first** - Reverse engineers existing code (primary use case)
-- ✅ **Runtime enforcement** - Contracts prevent regressions automatically
-- ✅ **Formal verification** - CrossHair symbolic execution (not just LLM suggestions)
-- ✅ **Team collaboration** - Role-based workflows for agile/scrum teams
-- ✅ **Works offline** - No API keys, no cloud, zero vendor lock-in
+**Integrations snapshot**: GitHub, Azure DevOps, Jira, Linear, Spec-Kit, OpenSpec, Specmatic.
 
-👉 **[See detailed comparison guide](docs/guides/speckit-comparison.md)** - Understand when to use SpecFact, Spec-Kit, OpenSpec, or all together
+- **[Integrations Overview](docs/guides/integrations-overview.md)**
+- **[DevOps Adapter Integration](docs/guides/devops-adapter-integration.md)**
 
 ---
 
-## Benefits
-
-### Works with Your Existing Tools
+## Recommended Paths
 
-- ✅ **No new platform** - Pure CLI, works offline
-- ✅ **No account required** - Fully local, zero vendor lock-in
-- ✅ **Integrates everywhere** - VS Code, Cursor, GitHub Actions, pre-commit hooks
+- **I want a quick win**: [Getting Started](docs/getting-started/README.md)
+- **I use an AI IDE**: [AI IDE Workflow](docs/guides/ai-ide-workflow.md)
+- **We have a team backlog**: [Agile/Scrum Workflows](docs/guides/agile-scrum-workflows.md)
+- **We have a long-lived codebase**: [Working With Existing Code](docs/guides/brownfield-engineer.md)
 
-### Built for Real Teams
-
-- ✅ **Role-based workflows** - Product Owners, Architects, Developers work in parallel
-- ✅ **Markdown-based** - No YAML editing, human-readable conflicts
-- ✅ **Agile/scrum ready** - DoR checklists, story points, sprint planning
+---
 
-### Proven Results
+## Documentation Map
 
-- ✅ **Catches real bugs** - See [Integration Showcases](docs/examples/integration-showcases/)
-- ✅ **Prevents regressions** - Runtime contract enforcement
-- ✅ **Works on legacy code** - Analyzed itself successfully
+- **[Documentation Index](docs/README.md)**
+- **[Command Reference](docs/reference/commands.md)**
+- **[Backlog Refinement](docs/guides/backlog-refinement.md)**
+- **[Sidecar Validation](docs/guides/sidecar-validation.md)**
+- **[OpenSpec Journey](docs/guides/openspec-journey.md)**
 
 ---
 
 ## Contributing
 
-We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
+We welcome contributions. See [CONTRIBUTING.md](CONTRIBUTING.md).
 
 ```bash
 git clone https://github.com/nold-ai/specfact-cli.git
@@ -603,11 +478,7 @@ hatch run contract-test-full
 
 ## License
 
-**Apache License 2.0** - Open source and enterprise-friendly
-
-- ✅ Free to use for any purpose (commercial or non-commercial)
-- ✅ Modify and distribute as needed
-- ✅ Enterprise-friendly with explicit patent grant
+**Apache License 2.0** - Open source and enterprise-friendly.
 
 [Full license](LICENSE.md)
 
@@ -615,17 +486,16 @@ hatch run contract-test-full
 
 ## Support
 
-- 💬 **Questions?** [GitHub Discussions](https://github.com/nold-ai/specfact-cli/discussions)
-- 🐛 **Found a bug?** [GitHub Issues](https://github.com/nold-ai/specfact-cli/issues)
-- 🔍 **Debugging I/O or API issues?** Run with `--debug`; logs are written to `~/.specfact/logs/specfact-debug.log`. With `--debug`, ADO API errors include response snippet and patch paths in the log. See [Debug Logging](docs/reference/debug-logging.md).
-- 📧 **Need help?** [hello@noldai.com](mailto:hello@noldai.com)
-- 🌐 **Learn more:** [specfact.com](https://specfact.com) • [specfact.io](https://specfact.io) • [specfact.dev](https://specfact.dev)
+- **GitHub Discussions**: https://github.com/nold-ai/specfact-cli/discussions
+- **GitHub Issues**: https://github.com/nold-ai/specfact-cli/issues
+- **Email**: hello@noldai.com
+- **Debug logs**: Run with `--debug` and check `~/.specfact/logs/specfact-debug.log`.
 
 ---
 
 <div align="center">
 
-**Built with ❤️ by [NOLD AI](https://noldai.com)**
+**Built by [NOLD AI](https://noldai.com)**
 
 Copyright © 2025-2026 Nold AI (Owner: Dominikus Nold)