spec-kitty-cli 3.1.2a1__tar.gz → 3.1.2a2__tar.gz

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/CHANGELOG.md

@@ -9,6 +9,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.1.2a2] - 2026-04-11
+
+### Added
+
+- **Hosted readiness control surfaces** — the CLI now exposes the canonical SaaS rollout/readiness module, a six-state hosted readiness evaluator, and a background-daemon policy/intent model that keeps stealth rollout behavior explicit while making enabled-mode failures actionable.
+
+### Changed
+
+- **Tracker command classification is corrected for first-run flows** — `tracker discover` no longer requires an existing mission binding, `tracker providers` remains available as static output without hosted prerequisites, and hosted/manual-daemon checks are applied according to command intent rather than indiscriminately.
+- **Tracker dependency advances to the hardened hosted-discovery release line** — the CLI now targets `spec-kitty-tracker==0.4.1`, aligning the prerelease with the published runtime validation and canonical discovery contract shipped in the tracker SDK.
+
+### Fixed
+
+- **Background-daemon policy no longer blocks local-provider sync flows** — local tracker providers continue to execute direct sync operations even when hosted SaaS daemon startup is set to manual.
+
 ## [3.1.2a1] - 2026-04-10
 
 ### Added

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spec-kitty-cli
-Version: 3.1.2a1
+Version: 3.1.2a2
 Summary: Spec Kitty, a tool for Specification Driven Development (SDD) agentic projects, with kanban and git worktree isolation.
 Project-URL: Repository, https://github.com/Priivacy-ai/spec-kitty
 Project-URL: Issues, https://github.com/Priivacy-ai/spec-kitty/issues
@@ -67,7 +67,7 @@ Requires-Dist: rich>=14.3.3
 Requires-Dist: ruamel-yaml>=0.18.0
 Requires-Dist: spec-kitty-events==3.0.0
 Requires-Dist: spec-kitty-runtime==0.4.3
-Requires-Dist: spec-kitty-tracker==0.3.0
+Requires-Dist: spec-kitty-tracker==0.4.1
 Requires-Dist: toml>=0.10.2
 Requires-Dist: transitions>=0.9.2
 Requires-Dist: truststore>=0.10.4
@@ -81,6 +81,7 @@ Requires-Dist: ruff>=0.4.0; extra == 'lint'
 Requires-Dist: types-jsonschema>=4.0.0; extra == 'lint'
 Requires-Dist: types-psutil>=5.9.0; extra == 'lint'
 Requires-Dist: types-pyyaml>=6.0; extra == 'lint'
+Requires-Dist: types-requests>=2.31.0; extra == 'lint'
 Requires-Dist: types-toml>=0.10.0; extra == 'lint'
 Provides-Extra: test
 Requires-Dist: build>=1.0.0; extra == 'test'
@@ -194,7 +195,7 @@ graph LR
 
 </div>
 
-**Current stable release line:** `v3.1.x` (development version 3.1.2a1; `main`, GitHub Releases, and PyPI)
+**Current stable release line:** `v3.1.x` (development version 3.1.2a2; `main`, GitHub Releases, and PyPI)
 
 **3.1.0 highlights:**
 - **Planning integrity** — read-only status commands no longer dirty the git tree; `spec-kitty next` without `--result` is a safe query-only operation

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/README.md

@@ -97,7 +97,7 @@ graph LR
 
 </div>
 
-**Current stable release line:** `v3.1.x` (development version 3.1.2a1; `main`, GitHub Releases, and PyPI)
+**Current stable release line:** `v3.1.x` (development version 3.1.2a2; `main`, GitHub Releases, and PyPI)
 
 **3.1.0 highlights:**
 - **Planning integrity** — read-only status commands no longer dirty the git tree; `spec-kitty next` without `--result` is a safe query-only operation

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/architecture/README.md

@@ -72,6 +72,12 @@ ls -1 architecture/2.x/adr | sort
 rg -n "Status:|Decision Outcome|Technical Story" architecture/1.x/adr architecture/2.x/adr
 ```
 
+### Notable Recent ADRs (2.x)
+
+| Filename | Title | Status | Date |
+|---|---|---|---|
+| `2026-04-11-1-saas-rollout-and-readiness.md` | SaaS Rollout Gate and Hosted Readiness Split | Accepted | 2026-04-11 |
+
 See also:
 
 - `architecture/ARCHITECTURE_DOCS_GUIDE.md`

spec_kitty_cli-3.1.2a2/kitty-specs/080-ci-hardening-and-lint-cleanup/tasks/README.md

@@ -0,0 +1,64 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files.
+
+## Directory Structure (v0.9.0+)
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`. Status is tracked in `status.events.jsonl`, not in WP frontmatter.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+dependencies: []
+planning_base_branch: "feat/080-ci-hardening-and-lint-cleanup"
+merge_target_branch: "feat/080-ci-hardening-and-lint-cleanup"
+branch_strategy: "Planning artifacts were generated on feat/080-ci-hardening-and-lint-cleanup; completed changes must merge back into feat/080-ci-hardening-and-lint-cleanup."
+subtasks:
+  - "T001"
+  - "T002"
+phase: "Phase 1 - Setup"
+assignee: ""
+agent: ""
+shell_pid: ""
+history:
+  - timestamp: "2025-01-01T00:00:00Z"
+    agent: "system"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 – Work Package Title
+
+[Content follows...]
+```
+
+## Status Tracking
+
+Status is tracked via the canonical event log (`status.events.jsonl`), not in WP frontmatter.
+Use `spec-kitty agent tasks move-task` to change WP status:
+
+```bash
+spec-kitty agent tasks move-task <WPID> --to <lane>
+```
+
+Example:
+```bash
+spec-kitty agent tasks move-task WP01 --to doing
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`

spec_kitty_cli-3.1.2a2/kitty-specs/081-canonical-baseline-and-repository-boundary/tasks/README.md

@@ -0,0 +1,64 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files.
+
+## Directory Structure (v0.9.0+)
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`. Status is tracked in `status.events.jsonl`, not in WP frontmatter.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+dependencies: []
+planning_base_branch: "main"
+merge_target_branch: "main"
+branch_strategy: "Planning artifacts were generated on main; completed changes must merge back into main."
+subtasks:
+  - "T001"
+  - "T002"
+phase: "Phase 1 - Setup"
+assignee: ""
+agent: ""
+shell_pid: ""
+history:
+  - timestamp: "2025-01-01T00:00:00Z"
+    agent: "system"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 – Work Package Title
+
+[Content follows...]
+```
+
+## Status Tracking
+
+Status is tracked via the canonical event log (`status.events.jsonl`), not in WP frontmatter.
+Use `spec-kitty agent tasks move-task` to change WP status:
+
+```bash
+spec-kitty agent tasks move-task <WPID> --to <lane>
+```
+
+Example:
+```bash
+spec-kitty agent tasks move-task WP01 --to doing
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`

spec_kitty_cli-3.1.2a2/kitty-specs/082-stealth-gated-saas-sync-hardening/tasks/README.md

@@ -0,0 +1,64 @@
+# Tasks Directory
+
+This directory contains work package (WP) prompt files.
+
+## Directory Structure (v0.9.0+)
+
+```
+tasks/
+├── WP01-setup-infrastructure.md
+├── WP02-user-authentication.md
+├── WP03-api-endpoints.md
+└── README.md
+```
+
+All WP files are stored flat in `tasks/`. Status is tracked in `status.events.jsonl`, not in WP frontmatter.
+
+## Work Package File Format
+
+Each WP file **MUST** use YAML frontmatter:
+
+```yaml
+---
+work_package_id: "WP01"
+title: "Work Package Title"
+dependencies: []
+planning_base_branch: "main"
+merge_target_branch: "main"
+branch_strategy: "Planning artifacts were generated on main; completed changes must merge back into main."
+subtasks:
+  - "T001"
+  - "T002"
+phase: "Phase 1 - Setup"
+assignee: ""
+agent: ""
+shell_pid: ""
+history:
+  - timestamp: "2025-01-01T00:00:00Z"
+    agent: "system"
+    action: "Prompt generated via /spec-kitty.tasks"
+---
+
+# Work Package Prompt: WP01 – Work Package Title
+
+[Content follows...]
+```
+
+## Status Tracking
+
+Status is tracked via the canonical event log (`status.events.jsonl`), not in WP frontmatter.
+Use `spec-kitty agent tasks move-task` to change WP status:
+
+```bash
+spec-kitty agent tasks move-task <WPID> --to <lane>
+```
+
+Example:
+```bash
+spec-kitty agent tasks move-task WP01 --to doing
+```
+
+## File Naming
+
+- Format: `WP01-kebab-case-slug.md`
+- Examples: `WP01-setup-infrastructure.md`, `WP02-user-auth.md`

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "spec-kitty-cli"
-version = "3.1.2a1"
+version = "3.1.2a2"
 description = "Spec Kitty, a tool for Specification Driven Development (SDD) agentic projects, with kanban and git worktree isolation."
 readme = "README.md"
 license = { file = "LICENSE" }
@@ -62,7 +62,7 @@ dependencies = [
     "psutil>=5.9.0",  # Cross-platform process management for dashboard
     "spec-kitty-events==3.0.0",
     "spec-kitty-runtime==0.4.3",
-    "spec-kitty-tracker==0.3.0",
+    "spec-kitty-tracker==0.4.1",
     "websockets>=12.0",  # WebSocket client for sync protocol
     "toml>=0.10.2",  # Config file parsing
     "filelock>=3.13.0",  # Credential storage locking
@@ -100,6 +100,7 @@ lint = [
     "types-jsonschema>=4.0.0",
     "types-psutil>=5.9.0",
     "types-PyYAML>=6.0",
+    "types-requests>=2.31.0",
     "types-toml>=0.10.0",
     "bandit>=1.7.0",
     "pip-audit>=2.7.0",
@@ -163,6 +164,7 @@ markers = [
     "platform_darwin: macOS-specific tests (case-insensitive FS)",
     "platform_linux: Linux-specific tests",
     "requires_symlinks: Tests that need symlink support",
+    "no_readiness_stub: Opt out of any autouse readiness-stub fixture so the test exercises its own readiness wiring (mission 082 tracker CLI tests)",
 ]
 
 [tool.ruff]
@@ -200,6 +202,13 @@ max-complexity = 15  # Match SonarCloud S3776 threshold
 # Keep strict mode as the default quality bar for actively maintained code.
 strict = true
 
+[[tool.mypy.overrides]]
+# When checking a narrow file path under ``specify_cli``, mypy otherwise walks
+# the package's CLI bootstrap import graph via ``specify_cli.__init__`` and
+# reports unrelated module errors instead of the target file's own issues.
+module = ["specify_cli.*"]
+follow_imports = "skip"
+
 [[tool.mypy.overrides]]
 # Transitional quarantine for legacy modules that are still being migrated to strict typing.
 module = [

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/src/charter/catalog.py

@@ -242,7 +242,7 @@ def _load_template_sets(doctrine_root: Path) -> set[str]:
     return template_sets
 
 
-def _load_template_sets_with_presence(doctrine_root: Path) -> tuple[set[str], bool]:
+def _load_template_sets_with_presence(_doctrine_root: Path) -> tuple[set[str], bool]:
     """Load available template set IDs, also reporting domain presence.
 
     Returns:

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/src/charter/resolver.py

@@ -117,10 +117,11 @@ def resolve_governance(
         resolved_directives = list(doctrine.selected_directives)
         directives_source = "charter"
     else:
-        if directives_cfg.directives:
-            resolved_directives = [directive.id for directive in directives_cfg.directives]
-        else:
-            resolved_directives = sorted(doctrine_catalog.directives)
+        resolved_directives = (
+            [directive.id for directive in directives_cfg.directives]
+            if directives_cfg.directives
+            else sorted(doctrine_catalog.directives)
+        )
         directives_source = "catalog_fallback"
 
     if doctrine.template_set:

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/src/doctrine/missions/glossary_hook.py

@@ -131,7 +131,7 @@ def execute_with_glossary(
         # the concrete runner into the kernel registry.
         try:
             module = import_module("specify_cli.glossary.attachment")
-            GlossaryAwarePrimitiveRunner = getattr(module, "GlossaryAwarePrimitiveRunner")
+            GlossaryAwarePrimitiveRunner = module.GlossaryAwarePrimitiveRunner
             register(GlossaryAwarePrimitiveRunner)
             runner_cls = get_runner()
         except Exception:

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/src/doctrine/missions/repository.py

@@ -3,11 +3,13 @@
 from __future__ import annotations
 
 from pathlib import Path
-from typing import Any
+from typing import Any, cast
 
 from ruamel.yaml import YAML
 from ruamel.yaml.error import YAMLError
 
+ParsedConfig = dict[str, Any] | list[Any]
+
 
 class TemplateResult:
     """Value object wrapping template content with origin metadata.
@@ -16,29 +18,27 @@ class TemplateResult:
     Consumers should not instantiate directly.
     """
 
-    __slots__ = ("_data",)
+    __slots__ = ("_content", "_origin", "_tier")
 
     def __init__(self, content: str, origin: str, tier: Any = None) -> None:
-        self._data: dict[str, Any] = {
-            "content": content,
-            "origin": origin,
-            "tier": tier,
-        }
+        self._content = content
+        self._origin = origin
+        self._tier = tier
 
     @property
     def content(self) -> str:
         """Raw template text (UTF-8)."""
-        return self._data["content"]
+        return self._content
 
     @property
     def origin(self) -> str:
         """Human-readable origin label (e.g. 'doctrine/software-dev/command-templates/implement.md')."""
-        return self._data["origin"]
+        return self._origin
 
     @property
     def tier(self) -> Any:
         """Resolution tier (ResolutionTier enum or None for doctrine-level lookups)."""
-        return self._data["tier"]
+        return self._tier
 
     def __repr__(self) -> str:
         return f"TemplateResult(origin={self.origin!r}, tier={self.tier})"
@@ -51,29 +51,27 @@ class ConfigResult:
     Consumers should not instantiate directly.
     """
 
-    __slots__ = ("_data",)
+    __slots__ = ("_content", "_origin", "_parsed")
 
-    def __init__(self, content: str, origin: str, parsed: dict | list) -> None:
-        self._data: dict[str, Any] = {
-            "content": content,
-            "origin": origin,
-            "parsed": parsed,
-        }
+    def __init__(self, content: str, origin: str, parsed: ParsedConfig) -> None:
+        self._content = content
+        self._origin = origin
+        self._parsed = parsed
 
     @property
     def content(self) -> str:
         """Raw YAML text (UTF-8)."""
-        return self._data["content"]
+        return self._content
 
     @property
     def origin(self) -> str:
         """Human-readable origin label (e.g. 'doctrine/software-dev/mission.yaml')."""
-        return self._data["origin"]
+        return self._origin
 
     @property
-    def parsed(self) -> dict | list:
+    def parsed(self) -> ParsedConfig:
         """Pre-parsed YAML data (parsed with ruamel.yaml YAML(typ='safe'))."""
-        return self._data["parsed"]
+        return self._parsed
 
     def __repr__(self) -> str:
         return f"ConfigResult(origin={self.origin!r})"
@@ -240,7 +238,7 @@ class MissionTemplateRepository:
         try:
             content = path.read_text(encoding="utf-8")
             yaml = YAML(typ="safe")
-            parsed = yaml.load(content)
+            parsed = cast(ParsedConfig | None, yaml.load(content))
             if parsed is None:
                 return None
             origin = f"doctrine/{mission}/actions/{action}/index.yaml"
@@ -283,7 +281,7 @@ class MissionTemplateRepository:
         try:
             content = path.read_text(encoding="utf-8")
             yaml = YAML(typ="safe")
-            parsed = yaml.load(content)
+            parsed = cast(ParsedConfig | None, yaml.load(content))
             if parsed is None:
                 return None
             origin = f"doctrine/{mission}/mission.yaml"
@@ -306,7 +304,7 @@ class MissionTemplateRepository:
         try:
             content = path.read_text(encoding="utf-8")
             yaml = YAML(typ="safe")
-            parsed = yaml.load(content)
+            parsed = cast(ParsedConfig | None, yaml.load(content))
             if parsed is None:
                 return None
             origin = f"doctrine/{mission}/expected-artifacts.yaml"

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/src/doctrine/skills/spec-kitty-implement-review/SKILL.md

@@ -556,8 +556,8 @@ WP01 (approved) --> WP02 (approved) --> WP03 (approved) --> merge --> all done
 ```
 
 1. Implement WP01, review, approve
-2. THEN implement WP02 (`--base WP01`), review, approve
-3. THEN implement WP03 (`--base WP02`), review, approve
+2. THEN implement WP02, review, approve. The implementation workspace base is inferred automatically from the approved dependency graph.
+3. THEN implement WP03, review, approve. The implementation workspace base is inferred automatically from the approved dependency graph.
 4. `spec-kitty merge --mission <slug>`
 
 ### Parallel Opportunities (Independent WPs)

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/src/kernel/_safe_re.py

@@ -38,6 +38,8 @@ from __future__ import annotations
 import re as _stdlib_re
 import sys
 import types
+from collections.abc import Iterator
+from contextlib import suppress
 
 __all__ = ["re", "is_re2_active"]
 
@@ -161,7 +163,7 @@ def _findall(pattern: str, string: str, flags: int = 0) -> list:  # type: ignore
     return _re2_compile(pattern, flags).findall(string)
 
 
-def _finditer(pattern: str, string: str, flags: int = 0):  # type: ignore[return]
+def _finditer(pattern: str, string: str, flags: int = 0) -> Iterator[_stdlib_re.Match[str]]:
     return _re2_compile(pattern, flags).finditer(string)
 
 
@@ -182,10 +184,8 @@ def _escape(pattern: str) -> str:
 
 
 def _purge() -> None:
-    try:
+    with suppress(AttributeError):
         _re2_mod.purge()
-    except AttributeError:
-        pass
     _stdlib_re.purge()
 
 

{spec_kitty_cli-3.1.2a1 → spec_kitty_cli-3.1.2a2}/src/specify_cli/.contextive/orchestration.yml

@@ -7,6 +7,8 @@ contexts:
   - name: "Orchestration"
     domainVisionStatement: "Terms describing lifecycle and runtime orchestration semantics."
     terms:
+      - name: "Build"
+        definition: "One checkout or worktree execution context inside a Repository, identified by machine and build-scoped runtime identity."
       - name: "Command Envelope"
         definition: "Standard JSON wrapper used to send commands to the orchestrator API. Contains identity fields, a version number, and the command payload."
       - name: "Command Template"
@@ -39,6 +41,8 @@ contexts:
         definition: "JSON-based interface that lets external orchestration tools interact with spec-kitty CLI operations programmatically, without going through the human-facing CLI."
       - name: "Project"
         definition: "Entire repository initialized for Spec Kitty workflow execution."
+      - name: "Repository"
+        definition: "The local git repository that a Project is initialized from and executes within."
       - name: "Runtime Bridge"
         definition: "The adapter that connects the CLI's decision loop to the mission execution engine. It translates internal runtime decisions into the format the HiC or agent sees while keeping mission identity separate from mission-run identity."
       - name: "Step Contract"