specsmith 0.10.1.dev262__tar.gz → 0.10.1.dev277__tar.gz

{specsmith-0.10.1.dev262/src/specsmith.egg-info → specsmith-0.10.1.dev277}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specsmith
-Version: 0.10.1.dev262
+Version: 0.10.1.dev277
 Summary: Applied Epistemic Engineering toolkit — AEE agent sessions, execution profiles, FPGA/HDL governance, tool installer, 50+ CLI commands.
 Author: BitConcepts
 License-Expression: MIT
@@ -38,8 +38,6 @@ Requires-Dist: ruff>=0.4; extra == "dev"
 Requires-Dist: mypy>=1.10; extra == "dev"
 Requires-Dist: pre-commit>=3.0; extra == "dev"
 Requires-Dist: types-pyyaml>=6.0; extra == "dev"
-Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
-Requires-Dist: pytest-textual-snapshot>=1.0; extra == "dev"
 Provides-Extra: docs
 Requires-Dist: mkdocs>=1.6; extra == "docs"
 Requires-Dist: mkdocs-material>=9.5; extra == "docs"
@@ -53,10 +51,6 @@ Provides-Extra: mistral
 Requires-Dist: openai>=1.0; extra == "mistral"
 Provides-Extra: gui
 Requires-Dist: PySide6>=6.6; extra == "gui"
-Provides-Extra: tui
-Requires-Dist: textual>=3.0; extra == "tui"
-Provides-Extra: webui
-Requires-Dist: nicegui>=3.0; extra == "webui"
 Provides-Extra: ag2
 Requires-Dist: ag2[ollama]; extra == "ag2"
 Provides-Extra: history-semantic
@@ -84,8 +78,6 @@ Dynamic: license-file
 [![PyPI](https://img.shields.io/pypi/v/specsmith?label=stable&style=flat&color=blue&cacheSeconds=60)](https://pypi.org/project/specsmith/)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
-[![VS Code Extension](https://img.shields.io/badge/VS%20Code-AEE%20Workbench-4ec9b0?logo=visualstudiocode)](https://github.com/BitConcepts/specsmith-vscode)
-
 **Applied Epistemic Engineering toolkit for AI-assisted development.**
 
 > Intelligence proposes. Constraints decide. The ledger remembers.
@@ -94,23 +86,17 @@ specsmith treats belief systems like code: codable, testable, and deployable. It
 epistemically-governed projects, stress-tests requirements as BeliefArtifacts, runs
 cryptographically-sealed trace vaults, and orchestrates AI agents under formal AEE governance.
 
-**0.10.0 — Multi-Agent + BYOE.** A `/plan` goes to the architect, `/fix`
-goes to the coder, `/review` goes to a reviewer that runs on a different
-model family. Each *profile* is a `(provider, model, endpoint?, fallback_chain)`
-bundle stored in `~/.specsmith/agents.json`; an *activity routing table*
-maps slash commands and AEE phases to profiles; **BYOE endpoints**
-(`~/.specsmith/endpoints.json`) let you point a profile at any
-OpenAI-v1-compatible backend you self-host (vLLM, llama.cpp `server`,
-LM Studio, TGI, ...). Cross-family **diversity guard**, capability
-filtering, transient-failure fallback chains, and TraceVault decision
-seals on every `/agent` pin are wired in by default. See
-[`docs/site/agents.md`](docs/site/agents.md) for the five-minute walkthrough.
+**0.10.1 — Governance REST API, machine-state sync, and least-privilege permissions.**
+Specsmith now serves as the governance backend for Kairos (the epistemically-governed
+Rust terminal) via `specsmith governance-serve`, keeps `.specsmith/` JSON in sync
+with `docs/` Markdown via `specsmith sync`, and gates every agent tool call via
+`specsmith agent permissions-check`. Multi-agent profiles, BYOE endpoints, and the
+AEE phase lifecycle are all fully wired.
 
 ```bash
-specsmith agents preset apply default       # frontier coder + cross-family reviewer
-specsmith endpoints add --id home-vllm \
-  --base-url http://10.0.0.4:8000/v1 --auth bearer-keyring
-specsmith run --agent opus-reviewer         # one-shot per-session pin
+specsmith governance-serve --port 7700     # Kairos governance REST API
+specsmith sync                              # sync .specsmith/ from docs/ markdown
+specsmith agent permissions-check git_push # check tool permission (REG-012)
 ```
 
 It also co-installs the standalone `epistemic` Python library for direct use in any project:
@@ -154,23 +140,15 @@ specsmith phase set requirements  # jump to a specific phase
 specsmith phase list     # list all phases
 ```
 
-The current phase is persisted in `scaffold.yml` as `aee_phase` and displayed in the VS Code
-Settings Panel. Each phase has a checklist of file/command criteria, recommended commands,
-and a readiness percentage.
+The current phase is persisted in `scaffold.yml` as `aee_phase` and displayed in the
+Kairos Governance page. Each phase has a checklist of file/command criteria, recommended
+commands, and a readiness percentage.
 
 ---
 
 ## Install
 
-**Recommended — via the VS Code extension (creates a project-isolated environment):**
-
-1. Install the [specsmith AEE Workbench](https://github.com/BitConcepts/specsmith-vscode) VS Code extension
-2. Open `Ctrl+Shift+,` (⚙ specsmith Settings)
-3. Click **🔒 Create Environment** — creates `~/.specsmith/venv/` with specsmith + your provider packages
-
-The extension uses this environment for all agent sessions and terminal commands.
-
-**Or via pipx (system-wide):**
+**Recommended — via pipx (works with Kairos, any terminal, and CI):**
 
 ```bash
 pipx install specsmith                    # core CLI + epistemic library
@@ -232,47 +210,82 @@ specsmith phase --project-dir ./my-project
 
 ---
 
-## AG2 Agent Shell — Local AI Agents over Ollama
+## Machine State Sync
 
-specsmith includes an AG2-based agent shell with three specialized agents:
+`.specsmith/` always mirrors the human-readable `docs/` governance files.
+Run `specsmith sync` after any change to `docs/REQUIREMENTS.md` or `docs/TESTS.md`:
 
-- **Planner** — inspects repo, generates execution plans with acceptance criteria
-- **Builder** — makes code/doc changes following the plan
-- **Verifier** — runs tests, accepts or rejects changes
+```bash
+specsmith sync                     # regenerate .specsmith/requirements.json + testcases.json
+specsmith sync --check             # CI mode: exits 1 if out of sync without writing
+specsmith sync --json              # emit sync result as JSON
+```
 
-All agents run locally on Ollama (default: `qwen2.5:14b`). Zero cloud cost.
+## Least-Privilege Agent Permissions (REG-012)
 
 ```bash
-pip install "specsmith[ag2]"              # install AG2 + Ollama support
-specsmith agent status                    # verify config + Ollama running
-specsmith agent run "fix lint errors"     # Plan → Build → Verify pipeline
-specsmith agent improve "add tests for config.py"  # self-improvement with reports
+specsmith agent permissions                      # show active permission profile
+specsmith agent permissions-check git_push       # check if git_push is allowed
+specsmith agent permissions-check git_push --no-log  # dry-run (no ledger write)
 ```
 
-The agent shell stores structured reports at `.specsmith/agent-reports/` with task ID,
-files changed, test results, verdict (ACCEPT/REJECT), and follow-up tasks.
-
-Configurable per-project in `scaffold.yml` under `agents:` or via the VS Code
-Project Settings → Agent tab.
+Configure in `docs/SPECSMITH.yml`:
+```yaml
+agent:
+  permissions:
+    preset: standard       # read_only | standard | extended | admin
+    # Or custom:
+    allow: [read_file, write_file, run_shell, git_status]
+    deny:  [git_push, git_create_pr]
+```
 
 ---
 
-## Nexus — Plain-English Governance, Local-First
+## Kairos + Governance REST API
 
-**Nexus** is the local-first Nexus runtime that turns plain English into Specsmith-governed
-work. You speak in your own words; Specsmith stays the sole authority on what counts as a
-requirement, a test, or a work item — Nexus just brokers the conversation and runs the work.
+**Kairos** is the companion Rust terminal runtime (`BitConcepts/kairos`). specsmith
+acts as the governance backend: Kairos spawns `specsmith governance-serve` at startup
+and routes all preflight and verify calls through it.
 
 ```bash
+# Start the governance REST API (Kairos calls this automatically)
+specsmith governance-serve --port 7700 --project-dir .
+
 # Classify a natural-language utterance under Specsmith governance
 specsmith preflight "fix the cleanup dry-run regression" --json
 
-# Or drop into the Nexus REPL
+# Start the agentic REPL
+specsmith run
+> what does the cleanup module do?           # read-only ask -> answered
+> fix the cleanup dry-run regression          # change -> Specsmith approves, runs
+> delete the entire dist directory            # destructive -> needs clarification
+```
+
+---
+
+## Nexus
+
+The Nexus runtime is specsmith's local-first agentic REPL — a
+governance-gated broker that sits between you and the LLM.
+
+Every utterance passes through `specsmith preflight` before execution.
+The broker classifies intent, matches requirements, and gates the action.
+After execution, `specsmith verify` checks equilibrium. The `/why` command
+shows the full governance trace.
+
+```bash
+# Interactive REPL with governance
 specsmith run
-nexus> what does the cleanup module do?           # read-only ask -> answered
-nexus> fix the cleanup dry-run regression          # change -> Specsmith approves, runs
-nexus> delete the entire dist directory            # destructive -> needs clarification
-nexus> /why                                        # toggle governance details on/off
+nexus> fix the cleanup bug         # broker classifies → accepts → executes → verifies
+nexus> /why                         # show governance trace for last action
+nexus> /exit
+```
+
+The Nexus broker:
+- **Preflight gate**: every change goes through `specsmith preflight`
+- **Bounded retry**: failed actions retry up to 3× with strategy classification
+- **Execution trace**: every action is sealed in the cryptographic trace vault
+- **`/why` toggle**: shows governance rationale in human-readable form
 ```
 
 **How it works.** A natural-language **broker** classifies intent, infers scope from
@@ -293,36 +306,20 @@ requirement, test, and work-item identifiers Specsmith assigned.
 
 ---
 
-## VS Code Extension
+## Kairos — Flagship Terminal Client
 
-The **specsmith AEE Workbench** VS Code extension is the flagship client:
+**[Kairos](https://github.com/BitConcepts/kairos)** is the recommended terminal client for specsmith.
+Kairos spawns specsmith as a managed governance child process at startup and routes all
+preflight, verify, and BYOE proxy calls through it. The Governance settings page shows live
+specsmith status, version, and one-click update.
 
-```
-# VS Code: Ctrl+Shift+P → specsmith: New Agent Session
-# Settings:         Ctrl+Shift+,     (⚙ specsmith Settings — global)
-# Project Settings: Ctrl+Shift+G     (⚙ Project Settings — per-project)
+```bash
+# Kairos starts specsmith automatically; or run manually:
+specsmith governance-serve --port 7700 --project-dir .
 ```
 
-**Key features:**
-- **Dual-panel architecture** — **⚙ specsmith Settings** (global: venv, version, Ollama, system)
-  and **⚙ Project Settings** (per-project: scaffold, tools, files, actions, execution)
-- **Global environment management** — `~/.specsmith/venv/` with Create / Update / Rebuild / Delete;
-  persistent restart banner; Remove System Installs cleanup button
-- **VCS context at session start** — git status + recent commits shown in chat and in system prompt
-- **Execution profiles** — safe / standard / open / admin; custom allow/block command lists
-- **AEE phase indicator** — shows current phase with readiness %, Next Phase button, phase selector
-- **AI agent sessions** — independent process per project, JSONL bridge, chat with file injection
-- **AG2 agent shell** — Planner/Builder/Verifier agents over Ollama in Actions tab
-- **Agent tab** — per-project provider/model/context/iteration config (overrides global defaults)
-- **Live model listing** — Anthropic, OpenAI, Gemini, Mistral, local Ollama (GPU-aware)
-- **Ollama model catalog** — 16 models, 4 tiers, GPU-aware recommendations, filter by installed/available
-- **Ollama integration** — model manager (update/remove/update-all), version check, upgrade
-- **FPGA/HDL tool support** — vivado, gtkwave, vsg, ghdl, verilator, yosys, nextpnr, and 15 more
-- **Tool installer** — scan installed tools; one-click install via winget/brew/apt for missing tools
-- **API key management** — stored in OS credential store (Windows Credential Manager / macOS Keychain)
-- **Update checker** — PyPI version check, auto-checks on panel open, release channel selector
-
-**[→ specsmith-vscode on GitHub](https://github.com/BitConcepts/specsmith-vscode)**
+The VS Code extension (`specsmith-vscode`) has been **deprecated** in favour of Kairos.
+Use `pipx install specsmith` for standalone CLI usage from any terminal.
 
 ---
 
@@ -330,7 +327,7 @@ The **specsmith AEE Workbench** VS Code extension is the flagship client:
 
 specsmith is open source and built by a small team. Every bit of support helps:
 
-- ⭐ **Star** [specsmith](https://github.com/BitConcepts/specsmith) and [specsmith-vscode](https://github.com/BitConcepts/specsmith-vscode) on GitHub
+- ⭐ **Star** [specsmith](https://github.com/BitConcepts/specsmith) and [kairos](https://github.com/BitConcepts/kairos) on GitHub
 - 📣 **Tell your friends and colleagues** — word of mouth is our best marketing
 - 🐛 **Report bugs** via [GitHub Issues](https://github.com/BitConcepts/specsmith/issues) — even small ones help
 - 💡 **Suggest features** via [GitHub Discussions](https://github.com/BitConcepts/specsmith/discussions) — we read every suggestion
@@ -353,8 +350,8 @@ specsmith ollama suggest requirements  # task-based recommendations
 specsmith ollama list                  # show installed models
 ```
 
-GPU-aware context sizing in the VS Code extension: 4K/8K/16K/32K tokens based on detected VRAM.
-Override with `specsmith.ollamaContextLength` in VS Code settings.
+GPU-aware context sizing: 4K/8K/16K/32K tokens based on detected VRAM.
+Override via `SPECSMITH_OLLAMA_CONTEXT_LENGTH` env var or `ollama.context_length` in `.specsmith/config.yml`.
 
 ---
 
@@ -455,20 +452,20 @@ Use cases: linguistics research, compliance pipelines, AI alignment, patent pros
 
 specsmith governs itself — the specsmith repo is a specsmith-managed project. Run `specsmith audit`
 in this repo to check its governance health. This means every feature we add to specsmith is
-immediately dogfooded on specsmith itself. The [VS Code extension](https://github.com/BitConcepts/specsmith-vscode)
-is developed alongside it as the flagship client.
+immediately dogfooded on specsmith itself. [Kairos](https://github.com/BitConcepts/kairos)
+is the companion terminal and flagship client.
 
 ## Documentation
 
 **[specsmith.readthedocs.io](https://specsmith.readthedocs.io)** — Full manual: AEE primer,
-command reference, project types, tool registry, governance model, Ollama guide, VS Code extension.
+command reference, project types, tool registry, governance model, Ollama guide, Kairos integration.
 
 ## Links
 
 - [PyPI](https://pypi.org/project/specsmith/)
 - [Documentation](https://specsmith.readthedocs.io)
 - [Changelog](CHANGELOG.md)
-- [VS Code Extension](https://github.com/BitConcepts/specsmith-vscode)
+- [Kairos terminal client](https://github.com/BitConcepts/kairos)
 - [Contributing](CONTRIBUTING.md)
 - [Security](SECURITY.md)
 

{specsmith-0.10.1.dev262 → specsmith-0.10.1.dev277}/README.md

@@ -6,8 +6,6 @@
 [![PyPI](https://img.shields.io/pypi/v/specsmith?label=stable&style=flat&color=blue&cacheSeconds=60)](https://pypi.org/project/specsmith/)
 [![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
-[![VS Code Extension](https://img.shields.io/badge/VS%20Code-AEE%20Workbench-4ec9b0?logo=visualstudiocode)](https://github.com/BitConcepts/specsmith-vscode)
-
 **Applied Epistemic Engineering toolkit for AI-assisted development.**
 
 > Intelligence proposes. Constraints decide. The ledger remembers.
@@ -16,23 +14,17 @@ specsmith treats belief systems like code: codable, testable, and deployable. It
 epistemically-governed projects, stress-tests requirements as BeliefArtifacts, runs
 cryptographically-sealed trace vaults, and orchestrates AI agents under formal AEE governance.
 
-**0.10.0 — Multi-Agent + BYOE.** A `/plan` goes to the architect, `/fix`
-goes to the coder, `/review` goes to a reviewer that runs on a different
-model family. Each *profile* is a `(provider, model, endpoint?, fallback_chain)`
-bundle stored in `~/.specsmith/agents.json`; an *activity routing table*
-maps slash commands and AEE phases to profiles; **BYOE endpoints**
-(`~/.specsmith/endpoints.json`) let you point a profile at any
-OpenAI-v1-compatible backend you self-host (vLLM, llama.cpp `server`,
-LM Studio, TGI, ...). Cross-family **diversity guard**, capability
-filtering, transient-failure fallback chains, and TraceVault decision
-seals on every `/agent` pin are wired in by default. See
-[`docs/site/agents.md`](docs/site/agents.md) for the five-minute walkthrough.
+**0.10.1 — Governance REST API, machine-state sync, and least-privilege permissions.**
+Specsmith now serves as the governance backend for Kairos (the epistemically-governed
+Rust terminal) via `specsmith governance-serve`, keeps `.specsmith/` JSON in sync
+with `docs/` Markdown via `specsmith sync`, and gates every agent tool call via
+`specsmith agent permissions-check`. Multi-agent profiles, BYOE endpoints, and the
+AEE phase lifecycle are all fully wired.
 
 ```bash
-specsmith agents preset apply default       # frontier coder + cross-family reviewer
-specsmith endpoints add --id home-vllm \
-  --base-url http://10.0.0.4:8000/v1 --auth bearer-keyring
-specsmith run --agent opus-reviewer         # one-shot per-session pin
+specsmith governance-serve --port 7700     # Kairos governance REST API
+specsmith sync                              # sync .specsmith/ from docs/ markdown
+specsmith agent permissions-check git_push # check tool permission (REG-012)
 ```
 
 It also co-installs the standalone `epistemic` Python library for direct use in any project:
@@ -76,23 +68,15 @@ specsmith phase set requirements  # jump to a specific phase
 specsmith phase list     # list all phases
 ```
 
-The current phase is persisted in `scaffold.yml` as `aee_phase` and displayed in the VS Code
-Settings Panel. Each phase has a checklist of file/command criteria, recommended commands,
-and a readiness percentage.
+The current phase is persisted in `scaffold.yml` as `aee_phase` and displayed in the
+Kairos Governance page. Each phase has a checklist of file/command criteria, recommended
+commands, and a readiness percentage.
 
 ---
 
 ## Install
 
-**Recommended — via the VS Code extension (creates a project-isolated environment):**
-
-1. Install the [specsmith AEE Workbench](https://github.com/BitConcepts/specsmith-vscode) VS Code extension
-2. Open `Ctrl+Shift+,` (⚙ specsmith Settings)
-3. Click **🔒 Create Environment** — creates `~/.specsmith/venv/` with specsmith + your provider packages
-
-The extension uses this environment for all agent sessions and terminal commands.
-
-**Or via pipx (system-wide):**
+**Recommended — via pipx (works with Kairos, any terminal, and CI):**
 
 ```bash
 pipx install specsmith                    # core CLI + epistemic library
@@ -154,47 +138,82 @@ specsmith phase --project-dir ./my-project
 
 ---
 
-## AG2 Agent Shell — Local AI Agents over Ollama
+## Machine State Sync
 
-specsmith includes an AG2-based agent shell with three specialized agents:
+`.specsmith/` always mirrors the human-readable `docs/` governance files.
+Run `specsmith sync` after any change to `docs/REQUIREMENTS.md` or `docs/TESTS.md`:
 
-- **Planner** — inspects repo, generates execution plans with acceptance criteria
-- **Builder** — makes code/doc changes following the plan
-- **Verifier** — runs tests, accepts or rejects changes
+```bash
+specsmith sync                     # regenerate .specsmith/requirements.json + testcases.json
+specsmith sync --check             # CI mode: exits 1 if out of sync without writing
+specsmith sync --json              # emit sync result as JSON
+```
 
-All agents run locally on Ollama (default: `qwen2.5:14b`). Zero cloud cost.
+## Least-Privilege Agent Permissions (REG-012)
 
 ```bash
-pip install "specsmith[ag2]"              # install AG2 + Ollama support
-specsmith agent status                    # verify config + Ollama running
-specsmith agent run "fix lint errors"     # Plan → Build → Verify pipeline
-specsmith agent improve "add tests for config.py"  # self-improvement with reports
+specsmith agent permissions                      # show active permission profile
+specsmith agent permissions-check git_push       # check if git_push is allowed
+specsmith agent permissions-check git_push --no-log  # dry-run (no ledger write)
 ```
 
-The agent shell stores structured reports at `.specsmith/agent-reports/` with task ID,
-files changed, test results, verdict (ACCEPT/REJECT), and follow-up tasks.
-
-Configurable per-project in `scaffold.yml` under `agents:` or via the VS Code
-Project Settings → Agent tab.
+Configure in `docs/SPECSMITH.yml`:
+```yaml
+agent:
+  permissions:
+    preset: standard       # read_only | standard | extended | admin
+    # Or custom:
+    allow: [read_file, write_file, run_shell, git_status]
+    deny:  [git_push, git_create_pr]
+```
 
 ---
 
-## Nexus — Plain-English Governance, Local-First
+## Kairos + Governance REST API
 
-**Nexus** is the local-first Nexus runtime that turns plain English into Specsmith-governed
-work. You speak in your own words; Specsmith stays the sole authority on what counts as a
-requirement, a test, or a work item — Nexus just brokers the conversation and runs the work.
+**Kairos** is the companion Rust terminal runtime (`BitConcepts/kairos`). specsmith
+acts as the governance backend: Kairos spawns `specsmith governance-serve` at startup
+and routes all preflight and verify calls through it.
 
 ```bash
+# Start the governance REST API (Kairos calls this automatically)
+specsmith governance-serve --port 7700 --project-dir .
+
 # Classify a natural-language utterance under Specsmith governance
 specsmith preflight "fix the cleanup dry-run regression" --json
 
-# Or drop into the Nexus REPL
+# Start the agentic REPL
+specsmith run
+> what does the cleanup module do?           # read-only ask -> answered
+> fix the cleanup dry-run regression          # change -> Specsmith approves, runs
+> delete the entire dist directory            # destructive -> needs clarification
+```
+
+---
+
+## Nexus
+
+The Nexus runtime is specsmith's local-first agentic REPL — a
+governance-gated broker that sits between you and the LLM.
+
+Every utterance passes through `specsmith preflight` before execution.
+The broker classifies intent, matches requirements, and gates the action.
+After execution, `specsmith verify` checks equilibrium. The `/why` command
+shows the full governance trace.
+
+```bash
+# Interactive REPL with governance
 specsmith run
-nexus> what does the cleanup module do?           # read-only ask -> answered
-nexus> fix the cleanup dry-run regression          # change -> Specsmith approves, runs
-nexus> delete the entire dist directory            # destructive -> needs clarification
-nexus> /why                                        # toggle governance details on/off
+nexus> fix the cleanup bug         # broker classifies → accepts → executes → verifies
+nexus> /why                         # show governance trace for last action
+nexus> /exit
+```
+
+The Nexus broker:
+- **Preflight gate**: every change goes through `specsmith preflight`
+- **Bounded retry**: failed actions retry up to 3× with strategy classification
+- **Execution trace**: every action is sealed in the cryptographic trace vault
+- **`/why` toggle**: shows governance rationale in human-readable form
 ```
 
 **How it works.** A natural-language **broker** classifies intent, infers scope from
@@ -215,36 +234,20 @@ requirement, test, and work-item identifiers Specsmith assigned.
 
 ---
 
-## VS Code Extension
+## Kairos — Flagship Terminal Client
 
-The **specsmith AEE Workbench** VS Code extension is the flagship client:
+**[Kairos](https://github.com/BitConcepts/kairos)** is the recommended terminal client for specsmith.
+Kairos spawns specsmith as a managed governance child process at startup and routes all
+preflight, verify, and BYOE proxy calls through it. The Governance settings page shows live
+specsmith status, version, and one-click update.
 
-```
-# VS Code: Ctrl+Shift+P → specsmith: New Agent Session
-# Settings:         Ctrl+Shift+,     (⚙ specsmith Settings — global)
-# Project Settings: Ctrl+Shift+G     (⚙ Project Settings — per-project)
+```bash
+# Kairos starts specsmith automatically; or run manually:
+specsmith governance-serve --port 7700 --project-dir .
 ```
 
-**Key features:**
-- **Dual-panel architecture** — **⚙ specsmith Settings** (global: venv, version, Ollama, system)
-  and **⚙ Project Settings** (per-project: scaffold, tools, files, actions, execution)
-- **Global environment management** — `~/.specsmith/venv/` with Create / Update / Rebuild / Delete;
-  persistent restart banner; Remove System Installs cleanup button
-- **VCS context at session start** — git status + recent commits shown in chat and in system prompt
-- **Execution profiles** — safe / standard / open / admin; custom allow/block command lists
-- **AEE phase indicator** — shows current phase with readiness %, Next Phase button, phase selector
-- **AI agent sessions** — independent process per project, JSONL bridge, chat with file injection
-- **AG2 agent shell** — Planner/Builder/Verifier agents over Ollama in Actions tab
-- **Agent tab** — per-project provider/model/context/iteration config (overrides global defaults)
-- **Live model listing** — Anthropic, OpenAI, Gemini, Mistral, local Ollama (GPU-aware)
-- **Ollama model catalog** — 16 models, 4 tiers, GPU-aware recommendations, filter by installed/available
-- **Ollama integration** — model manager (update/remove/update-all), version check, upgrade
-- **FPGA/HDL tool support** — vivado, gtkwave, vsg, ghdl, verilator, yosys, nextpnr, and 15 more
-- **Tool installer** — scan installed tools; one-click install via winget/brew/apt for missing tools
-- **API key management** — stored in OS credential store (Windows Credential Manager / macOS Keychain)
-- **Update checker** — PyPI version check, auto-checks on panel open, release channel selector
-
-**[→ specsmith-vscode on GitHub](https://github.com/BitConcepts/specsmith-vscode)**
+The VS Code extension (`specsmith-vscode`) has been **deprecated** in favour of Kairos.
+Use `pipx install specsmith` for standalone CLI usage from any terminal.
 
 ---
 
@@ -252,7 +255,7 @@ The **specsmith AEE Workbench** VS Code extension is the flagship client:
 
 specsmith is open source and built by a small team. Every bit of support helps:
 
-- ⭐ **Star** [specsmith](https://github.com/BitConcepts/specsmith) and [specsmith-vscode](https://github.com/BitConcepts/specsmith-vscode) on GitHub
+- ⭐ **Star** [specsmith](https://github.com/BitConcepts/specsmith) and [kairos](https://github.com/BitConcepts/kairos) on GitHub
 - 📣 **Tell your friends and colleagues** — word of mouth is our best marketing
 - 🐛 **Report bugs** via [GitHub Issues](https://github.com/BitConcepts/specsmith/issues) — even small ones help
 - 💡 **Suggest features** via [GitHub Discussions](https://github.com/BitConcepts/specsmith/discussions) — we read every suggestion
@@ -275,8 +278,8 @@ specsmith ollama suggest requirements  # task-based recommendations
 specsmith ollama list                  # show installed models
 ```
 
-GPU-aware context sizing in the VS Code extension: 4K/8K/16K/32K tokens based on detected VRAM.
-Override with `specsmith.ollamaContextLength` in VS Code settings.
+GPU-aware context sizing: 4K/8K/16K/32K tokens based on detected VRAM.
+Override via `SPECSMITH_OLLAMA_CONTEXT_LENGTH` env var or `ollama.context_length` in `.specsmith/config.yml`.
 
 ---
 
@@ -377,20 +380,20 @@ Use cases: linguistics research, compliance pipelines, AI alignment, patent pros
 
 specsmith governs itself — the specsmith repo is a specsmith-managed project. Run `specsmith audit`
 in this repo to check its governance health. This means every feature we add to specsmith is
-immediately dogfooded on specsmith itself. The [VS Code extension](https://github.com/BitConcepts/specsmith-vscode)
-is developed alongside it as the flagship client.
+immediately dogfooded on specsmith itself. [Kairos](https://github.com/BitConcepts/kairos)
+is the companion terminal and flagship client.
 
 ## Documentation
 
 **[specsmith.readthedocs.io](https://specsmith.readthedocs.io)** — Full manual: AEE primer,
-command reference, project types, tool registry, governance model, Ollama guide, VS Code extension.
+command reference, project types, tool registry, governance model, Ollama guide, Kairos integration.
 
 ## Links
 
 - [PyPI](https://pypi.org/project/specsmith/)
 - [Documentation](https://specsmith.readthedocs.io)
 - [Changelog](CHANGELOG.md)
-- [VS Code Extension](https://github.com/BitConcepts/specsmith-vscode)
+- [Kairos terminal client](https://github.com/BitConcepts/kairos)
 - [Contributing](CONTRIBUTING.md)
 - [Security](SECURITY.md)
 

{specsmith-0.10.1.dev262 → specsmith-0.10.1.dev277}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "specsmith"
-version = "0.10.1.dev262"
+version = "0.10.1.dev277"
 description = "Applied Epistemic Engineering toolkit — AEE agent sessions, execution profiles, FPGA/HDL governance, tool installer, 50+ CLI commands."
 readme = "README.md"
 license = "MIT"
@@ -51,8 +51,6 @@ dev = [
     "mypy>=1.10",
     "pre-commit>=3.0",
     "types-pyyaml>=6.0",
-    "pytest-asyncio>=0.23",
-    "pytest-textual-snapshot>=1.0",
 ]
 docs = [
     "mkdocs>=1.6",
@@ -67,8 +65,6 @@ openai = ["openai>=1.0"]
 gemini = ["google-genai>=1.0"]
 mistral = ["openai>=1.0"]  # Mistral uses the openai SDK pointed at api.mistral.ai
 gui = ["PySide6>=6.6"]
-tui = ["textual>=3.0"]
-webui = ["nicegui>=3.0"]
 # AG2 agent shell (Planner/Builder/Verifier over Ollama)
 ag2 = ["ag2[ollama]"]
 # Optional semantic backend for `specsmith history search --semantic` (REQ-135).
@@ -186,15 +182,9 @@ module = [
     "specsmith.serve",
     "specsmith.toolrules",
     "specsmith.tool_installer",
-    "specsmith.commands.*",
-    "specsmith.eval.*",
-    "specsmith.feature_flags",
-    "specsmith.instinct",
-    "specsmith.tui.*",
-    "specsmith.webui.*",
+    "specsmith.commands.intelligence",
 ]
 ignore_errors = true
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]
-asyncio_mode = "auto"