spec-kitty-cli 3.2.0a5__tar.gz → 3.2.0a7__tar.gz

{spec_kitty_cli-3.2.0a5 → spec_kitty_cli-3.2.0a7}/CHANGELOG.md

@@ -17,18 +17,48 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Removed
 
-## [3.2.0a6] — Tranche 2 (bug-only)
+## [3.2.0a7] - 2026-05-01
 
-Tranche 2 of the 3.2.0a6 release is a bug-only sweep that restores the
-documented fresh-project golden path (`init` → charter `setup`/`generate`/
+3.2.0a7 is a focused prerelease that bounds WebSocket sync startup and
+shutdown behavior. Short-lived agent commands now fail over to batch sync
+instead of hanging indefinitely when a local sync socket accepts the
+connection but never emits the initial snapshot.
+
+### Fixed
+
+- WebSocket sync startup now has bounded open, initial snapshot, and close
+  deadlines so `spec-kitty agent mission setup-plan` and other short-lived
+  commands degrade to batch sync instead of blocking forever on a stalled
+  sync socket (#936).
+
+### Internal
+
+- Added regression coverage for a WebSocket connection that never sends the
+  initial snapshot and for shutdown paths where the close handshake stalls.
+- Aligned existing Bandit suppressions in touched sync/readiness callsites so
+  local and CI security scans recognize the intended safe dynamic SQL and
+  localhost URL patterns.
+
+## [3.2.0a6] - 2026-04-30
+
+3.2.0a6 is a prerelease hardening sweep that restores the documented
+fresh-project golden path (`init` → charter `setup`/`generate`/
 `synthesize` → `next`), locks in strict JSON for covered `--json` commands
 under any SaaS state, fixes agent identity parsing and review-cycle
-accounting, and adds paired profile-invocation lifecycle observability for
-`spec-kitty next`. No new public CLI subcommands and no new top-level
-runtime dependencies were introduced.
+accounting, adds paired profile-invocation lifecycle observability for
+`spec-kitty next`, and tightens merge/review/status recovery paths. The
+release introduces the new top-level `spec-kitty review` mission-review
+command and no new top-level runtime dependencies.
 
 ### Fixed
 
+- `charter bundle validate --json` now fail-closes on incomplete Charter
+  synthesis state while preserving strict JSON stdout. Sidecar-only bundles,
+  manifest-only bundles, incompatible bundle versions, missing provenance
+  sidecars, dangling sidecar references, and synthesis manifest integrity
+  failures all produce parseable failure envelopes with actionable
+  `synthesis_state` details (#914, closes the final Phase 7 release gap for
+  #469/#515).
 - Stamp `schema_version` and a `schema_capabilities` block in
   `.kittify/metadata.yaml` on `spec-kitty init` so a fresh project no
   longer requires hand-edits before subsequent CLI commands; existing
@@ -59,6 +89,27 @@ runtime dependencies were introduced.
   with no hand-seeded `.kittify/doctrine/`; the bounded fresh-project
   path materialises a minimal doctrine tree (`PROVENANCE.md`) so the
   shipped doctrine layer can supply content (#839, WP06).
+- `spec-kitty merge --abort` now clears the global merge lock, removes
+  legacy merge-state files, aborts an in-progress Git merge when present,
+  and remains idempotent when no merge is active (#903).
+- Approved/done work packages with stale `verdict: rejected` review
+  artifacts are now surfaced across status views, including
+  `spec-kitty agent tasks status` and `show_kanban_status()`. Review
+  artifact lookup follows the real `tasks/<WP-slug>/review-cycle-N.md`
+  layout, and `in_review` work packages now warn when reviewer movement
+  stalls beyond the configured threshold (#904, #909).
+- Review lane-guard failures now name the planning branch and include a
+  concrete `git show <planning-branch>:<path>` command for the first
+  contaminated path, instead of a placeholder path (#905).
+- Work-package review definition-of-done coverage now includes real error
+  path and artifact-deletion regressions, not only happy-path review
+  behavior (#906).
+- Broad `except Exception` / BLE001 suppressions in touched runtime paths
+  were audited and now carry inline justification where fail-open behavior
+  is intentional (#907).
+- `spec-kitty review <mission>` is now a first-class mission-review CLI
+  command with structured status/exit behavior for post-merge mission
+  fidelity checks (#908).
 
 ### Internal
 
@@ -74,6 +125,10 @@ runtime dependencies were introduced.
   `charter generate` now auto-tracks `charter.md`, removing any
   expectation that operators run `git add` between `generate` and
   `bundle validate` (WP07).
+- Added regression coverage for merge abort cleanup, stale rejected review
+  artifacts, stalled in-review work packages, lane-guard remediation text,
+  mission-review command behavior, review DoD deletion/error cases, and
+  agent-shard coverage for status warning paths (#903-#909).
 
 ### Tranche-2 acceptance pass (SC-001..SC-008)
 
@@ -84,7 +139,7 @@ runtime dependencies were introduced.
 - **SC-005 (Lifecycle observability)** — `tests/integration/test_next_lifecycle_records.py` (WP05) covers ≥5 issuances with mid-cycle orphan; the consolidated E2E asserts at least one `started` record after `next` issues an action and that the `canonical_action_id` matches the issued step id.
 - **SC-006 (Charter parity rate)** — `tests/specify_cli/cli/commands/test_charter_generate_autotrack.py` (WP06) covers the auto-track + non-git fail-fast contract; the consolidated E2E exercises `generate → bundle validate` with no intervening git ops.
 - **SC-007 (Documentation/CLI agreement)** — `docs/how-to/setup-governance.md` updated; no documented governance-setup flow contains a `git add charter.md` step between `charter generate` and `charter bundle validate`.
-- **SC-008 (Bug-only discipline)** — Diff inventory: zero new public CLI subcommands at the top level, zero new top-level runtime dependencies. WP05 added `spec-kitty doctor invocation-pairing` — that is a SUBCOMMAND under the existing `doctor` top-level command, not a new top-level public CLI surface, and is the minimum viable observability wiring required by FR-011/FR-012. No additions to `pyproject.toml` `[project.dependencies]` in the tranche-2 diff.
+- **SC-008 (Release-surface discipline)** — Diff inventory: one new top-level public CLI command, `spec-kitty review`, added for mission-review fidelity checks (#908); one new `spec-kitty doctor invocation-pairing` subcommand under the existing `doctor` group for lifecycle observability; zero new top-level runtime dependencies in `pyproject.toml` `[project.dependencies]`.
 
 ## [3.2.0a5] - 2026-04-27
 
@@ -1312,6 +1367,7 @@ All fixes include comprehensive test coverage (54+ new tests) and maintain backw
   - **Errors handled**: TimeoutExpired (>10s git commands), general exceptions with warning
 
 ### Added
+
 - Git commit validation for "done" status transitions - prevents completing WPs with uncommitted changes
 - Empty branch detection in merge-base creation - warns when dependencies have no commits
 - Git commit workflow section in documentation mission template (consistency with software-dev/research)
@@ -1319,11 +1375,13 @@ All fixes include comprehensive test coverage (54+ new tests) and maintain backw
 - Migration to add commit workflow section to existing projects (`m_0_13_5_add_commit_workflow_to_templates.py`)
 
 ### Changed
+
 - `move-task --to done` now validates git status (same checks as "for_review")
 - Use `--force` flag to bypass validation (not recommended)
 - Warning messages in multi-parent merge now output to stderr instead of stdout (preserves JSON output integrity)
 
 ### Fixed (Non-Critical)
+
 - WP agents can no longer mark tasks as "done" without committing implementation files
 - Multi-parent merge-bases no longer silently accept empty dependency branches
 - Documentation mission now instructs agents to commit work before review
@@ -1385,7 +1443,7 @@ All fixes include comprehensive test coverage (54+ new tests) and maintain backw
   - Unit tests: `test_implement_validation.py` (11 tests)
   - Integration tests: `test_agent_command_wrappers.py` (11 tests)
 - Added `TestMigrationRegistryCompleteness` test (prevents 0.13.2-style release blocker)
-  - Verifies all m_*.py migration files are imported in __init__.py
+  - Verifies all `m_*.py` migration files are imported in `__init__.py`
   - Prevents silent bugs where migrations exist but never run
 - Added integration tests for merge with untracked branches
 - Added unit tests for `has_tracking_branch()` function
@@ -1807,9 +1865,9 @@ The migration will remove mission-specific constitution directories:
   - `signal.SIGKILL` and `signal.SIGTERM` don't exist on Windows
   - Added `psutil>=5.9.0` dependency for cross-platform process management
   - Refactored `src/specify_cli/dashboard/lifecycle.py`:
-    * `os.kill(pid, 0)` → `psutil.Process(pid).is_running()`
-    * `signal.SIGKILL` → `psutil.Process(pid).kill()` (6 locations)
-    * `signal.SIGTERM` → `psutil.Process(pid).terminate()` with timeout
+    - `os.kill(pid, 0)` → `psutil.Process(pid).is_running()`
+    - `signal.SIGKILL` → `psutil.Process(pid).kill()` (6 locations)
+    - `signal.SIGTERM` → `psutil.Process(pid).terminate()` with timeout
   - Added proper exception handling (NoSuchProcess, AccessDenied, TimeoutExpired)
   - Dashboard now starts, serves HTML, and stops cleanly on Windows 10/11
   - All 41 dashboard tests passing

{spec_kitty_cli-3.2.0a5 → spec_kitty_cli-3.2.0a7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spec-kitty-cli
-Version: 3.2.0a5
+Version: 3.2.0a7
 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
@@ -143,7 +143,7 @@ Spec Kitty addresses this with repository-native artifacts, work package workflo
 
 ---
 
-## 🚀 What You Get on `main` (`3.2.0a5`)
+## 🚀 What You Get on `main` (`3.2.0a7`)
 
 | Capability | What Spec Kitty provides |
 |------------|--------------------------|
@@ -203,9 +203,9 @@ graph LR
 
 </div>
 
-**Current stable release line:** `v3.1.x` (current stable release: `3.1.6` on GitHub Releases and PyPI)
+**Current stable release line:** `v3.1.x` (current stable release: `3.1.8` on GitHub Releases and PyPI)
 
-**Current `main` development version:** `3.2.0a5`
+**Current `main` development version:** `3.2.0a7`
 
 **Current `main` highlights:**
 - **Brief-first and ticket-first intake** — `spec-kitty intake` ingests external plans into `.kittify/mission-brief.md`, and `spec-kitty mission create --from-ticket <provider:KEY>` seeds tracker context before `/spec-kitty.specify`
@@ -213,7 +213,7 @@ graph LR
 - **Hosted tracker reads and Teamspace-aware sync** — `issue-search`, `tracker discover` / `tracker list-tickets`, encrypted local auth sessions, `sync routes`, repository sharing, and Private Teamspace routing tighten the SaaS workflow
 - **Charter synthesis is harness-owned and inspectable** — generated-artifact adapters, `charter status --provenance`, `charter resynthesize --list-topics`, bundle validation, and stronger neutrality rules make synthesis auditable
 - **Compatibility and release governance are stricter** — `doctor shim-registry`, mutation-testing guidance, shared-package drift checks, SBOM-attached prereleases, and safer publish validation harden upgrades and releases
-- **Review and runtime recovery keep improving** — sparse-checkout defenses, offline/auth refresh fixes, provider-aware tracker readiness, action-routing hardening, and post-merge fixes to the profile-invocation flow reduce recovery work
+- **Review and runtime recovery keep improving** — `spec-kitty review`, stale review-artifact warnings, merge-abort cleanup, provider-aware tracker readiness, action-routing hardening, and profile-invocation pairing reduce recovery work
 - **15 AI integrations are supported** — 13 user-global slash/prompt surfaces plus Codex CLI and Mistral Vibe via shared Agent Skills, with Kiro fully documented and legacy `q` retained for compatibility
 
 **Jump to:**
@@ -228,17 +228,18 @@ graph LR
 
 ## 📌 Release Channels
 
-Spec Kitty currently ships stable `3.1.x` releases while `main` carries the active `3.2.0a5` prerelease/dev line.
+Spec Kitty currently ships stable `3.1.x` releases while `main` carries the active `3.2.0a7` prerelease/dev line.
 The former `1.x` line is deprecated and lives on `1.x-maintenance` for maintenance-only fixes.
 
 | Source | Version | Status | Install |
 |--------|---------|--------|---------|
-| **PyPI / GitHub Releases** | **3.1.6** | Current stable line | `pip install spec-kitty-cli` |
-| **main** | **3.2.0a5** | Active prerelease / development line | Install from a source checkout or a published prerelease tag |
+| **PyPI / GitHub Releases** | **3.1.8** | Current stable line | `pip install spec-kitty-cli` |
+| **main** | **3.2.0a7** | Active prerelease / development line | Install from a source checkout or a published prerelease tag |
 | **1.x-maintenance** | **1.x** | Deprecated, maintenance-only | Install from a pinned maintenance tag or source checkout |
 
 **For users:** install the stable line from PyPI with `pip install spec-kitty-cli`.
 **For testers following `main`:** use a source checkout or published prerelease builds to get the intake, profile-invocation, hosted tracker-read, and Teamspace-routing work that is newer than stable `3.1.x`.
+After `3.2.0a7` is published, testers can install the exact prerelease with `pip install "spec-kitty-cli==3.2.0a7"` or opt into prereleases with `pip install --pre spec-kitty-cli`.
 **For existing 3.0.x users:** upgrade to `3.1.x` and run `spec-kitty upgrade` in each project — the charter rename, mission identity, and prompt-neutrality migrations remain automatic.
 **For existing 1.x or 2.x users:** migrate to `3.1.x`; `1.x-maintenance` is maintenance-only and will no longer publish new PyPI releases.
 

{spec_kitty_cli-3.2.0a5 → spec_kitty_cli-3.2.0a7}/README.md

@@ -45,7 +45,7 @@ Spec Kitty addresses this with repository-native artifacts, work package workflo
 
 ---
 
-## 🚀 What You Get on `main` (`3.2.0a5`)
+## 🚀 What You Get on `main` (`3.2.0a7`)
 
 | Capability | What Spec Kitty provides |
 |------------|--------------------------|
@@ -105,9 +105,9 @@ graph LR
 
 </div>
 
-**Current stable release line:** `v3.1.x` (current stable release: `3.1.6` on GitHub Releases and PyPI)
+**Current stable release line:** `v3.1.x` (current stable release: `3.1.8` on GitHub Releases and PyPI)
 
-**Current `main` development version:** `3.2.0a5`
+**Current `main` development version:** `3.2.0a7`
 
 **Current `main` highlights:**
 - **Brief-first and ticket-first intake** — `spec-kitty intake` ingests external plans into `.kittify/mission-brief.md`, and `spec-kitty mission create --from-ticket <provider:KEY>` seeds tracker context before `/spec-kitty.specify`
@@ -115,7 +115,7 @@ graph LR
 - **Hosted tracker reads and Teamspace-aware sync** — `issue-search`, `tracker discover` / `tracker list-tickets`, encrypted local auth sessions, `sync routes`, repository sharing, and Private Teamspace routing tighten the SaaS workflow
 - **Charter synthesis is harness-owned and inspectable** — generated-artifact adapters, `charter status --provenance`, `charter resynthesize --list-topics`, bundle validation, and stronger neutrality rules make synthesis auditable
 - **Compatibility and release governance are stricter** — `doctor shim-registry`, mutation-testing guidance, shared-package drift checks, SBOM-attached prereleases, and safer publish validation harden upgrades and releases
-- **Review and runtime recovery keep improving** — sparse-checkout defenses, offline/auth refresh fixes, provider-aware tracker readiness, action-routing hardening, and post-merge fixes to the profile-invocation flow reduce recovery work
+- **Review and runtime recovery keep improving** — `spec-kitty review`, stale review-artifact warnings, merge-abort cleanup, provider-aware tracker readiness, action-routing hardening, and profile-invocation pairing reduce recovery work
 - **15 AI integrations are supported** — 13 user-global slash/prompt surfaces plus Codex CLI and Mistral Vibe via shared Agent Skills, with Kiro fully documented and legacy `q` retained for compatibility
 
 **Jump to:**
@@ -130,17 +130,18 @@ graph LR
 
 ## 📌 Release Channels
 
-Spec Kitty currently ships stable `3.1.x` releases while `main` carries the active `3.2.0a5` prerelease/dev line.
+Spec Kitty currently ships stable `3.1.x` releases while `main` carries the active `3.2.0a7` prerelease/dev line.
 The former `1.x` line is deprecated and lives on `1.x-maintenance` for maintenance-only fixes.
 
 | Source | Version | Status | Install |
 |--------|---------|--------|---------|
-| **PyPI / GitHub Releases** | **3.1.6** | Current stable line | `pip install spec-kitty-cli` |
-| **main** | **3.2.0a5** | Active prerelease / development line | Install from a source checkout or a published prerelease tag |
+| **PyPI / GitHub Releases** | **3.1.8** | Current stable line | `pip install spec-kitty-cli` |
+| **main** | **3.2.0a7** | Active prerelease / development line | Install from a source checkout or a published prerelease tag |
 | **1.x-maintenance** | **1.x** | Deprecated, maintenance-only | Install from a pinned maintenance tag or source checkout |
 
 **For users:** install the stable line from PyPI with `pip install spec-kitty-cli`.
 **For testers following `main`:** use a source checkout or published prerelease builds to get the intake, profile-invocation, hosted tracker-read, and Teamspace-routing work that is newer than stable `3.1.x`.
+After `3.2.0a7` is published, testers can install the exact prerelease with `pip install "spec-kitty-cli==3.2.0a7"` or opt into prereleases with `pip install --pre spec-kitty-cli`.
 **For existing 3.0.x users:** upgrade to `3.1.x` and run `spec-kitty upgrade` in each project — the charter rename, mission identity, and prompt-neutrality migrations remain automatic.
 **For existing 1.x or 2.x users:** migrate to `3.1.x`; `1.x-maintenance` is maintenance-only and will no longer publish new PyPI releases.
 

spec_kitty_cli-3.2.0a7/kitty-specs/stabilization-release-core-bug-fixes-01KPQJAN/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.2.0a7/kitty-specs/unified-charter-bundle-chokepoint-01KP5Q2G/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.2.0a5 → spec_kitty_cli-3.2.0a7}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "spec-kitty-cli"
-version = "3.2.0a5"
+version = "3.2.0a7"
 description = "Spec Kitty, a tool for Specification Driven Development (SDD) agentic projects, with kanban and git worktree isolation."
 readme = "README.md"
 license = { file = "LICENSE" }

{spec_kitty_cli-3.2.0a5 → spec_kitty_cli-3.2.0a7}/src/charter/bundle.py

@@ -162,15 +162,15 @@ def validate_synthesis_state(repo_root: Path) -> BundleValidationResult:
     _check_stale_failed_dirs(repo_root, result)
 
     doctrine_root = repo_root / DOCTRINE_DIR
-    if not doctrine_root.exists():
-        return result
+    provenance_root = repo_root / PROVENANCE_DIR
+    manifest_path = repo_root / SYNTHESIS_MANIFEST_PATH
 
-    artifact_files = _collect_artifact_files(doctrine_root)
-    if not artifact_files and not (repo_root / PROVENANCE_DIR).exists():
+    artifact_files = _collect_artifact_files(doctrine_root) if doctrine_root.exists() else []
+    provenance_files = sorted(provenance_root.glob("*.yaml")) if provenance_root.exists() else []
+    if not artifact_files and not provenance_files and not manifest_path.exists():
         return result
 
     result.synthesis_state_present = True
-    provenance_root = repo_root / PROVENANCE_DIR
 
     _check_artifacts_have_provenance(repo_root, artifact_files, provenance_root, result)
     _check_provenance_have_artifacts(repo_root, doctrine_root, provenance_root, result)
@@ -249,7 +249,7 @@ def _check_provenance_have_artifacts(
 
 
 def _check_manifest_integrity(repo_root: Path, result: BundleValidationResult) -> None:
-    """Step 3: verify synthesis manifest content hashes if manifest is present."""
+    """Step 3: verify synthesis manifest content hashes and self-hash if present."""
     manifest_path = repo_root / SYNTHESIS_MANIFEST_PATH
     if not manifest_path.exists():
         return
@@ -257,14 +257,20 @@ def _check_manifest_integrity(repo_root: Path, result: BundleValidationResult) -
         from .synthesizer.manifest import (  # noqa: PLC0415
             load_yaml as load_manifest,
             verify as verify_manifest,
+            verify_manifest_hash,
         )
         manifest = load_manifest(manifest_path)
-        try:
-            verify_manifest(manifest, repo_root)
-        except Exception as exc:
-            result.errors.append(f"Synthesis manifest integrity check failed: {exc}")
     except Exception as exc:
         result.errors.append(f"Could not load synthesis manifest: {exc}")
+        return
+    try:
+        verify_manifest(manifest, repo_root)
+    except Exception as exc:
+        result.errors.append(f"Synthesis manifest integrity check failed: {exc}")
+    try:
+        verify_manifest_hash(manifest)
+    except Exception as exc:
+        result.errors.append(f"Synthesis manifest self-hash mismatch: {exc}")
 
 
 def _kind_and_slug_from_artifact(path: Path) -> tuple[str | None, str | None]:

{spec_kitty_cli-3.2.0a5 → spec_kitty_cli-3.2.0a7}/src/charter/synthesizer/manifest.py

@@ -33,6 +33,8 @@ if TYPE_CHECKING:
 
 # Canonical location of the synthesis manifest.
 MANIFEST_PATH = Path(".kittify/charter/synthesis-manifest.yaml")
+_ARTIFACT_PATH_PREFIX = Path(".kittify/doctrine")
+_PROVENANCE_PATH_PREFIX = Path(".kittify/charter/provenance")
 
 
 # ---------------------------------------------------------------------------
@@ -159,6 +161,57 @@ def load_yaml(path: Path) -> SynthesisManifest:
     return SynthesisManifest.model_validate(raw)
 
 
+def verify_manifest_hash(manifest: SynthesisManifest) -> None:
+    """Verify the manifest self-hash field.
+
+    Recomputes SHA-256 of the canonical YAML serialization of all manifest
+    fields except ``manifest_hash`` itself and compares to the stored value.
+
+    Raises
+    ------
+    ValueError
+        If the computed hash does not match ``manifest.manifest_hash``.
+    """
+    data = manifest.model_dump(mode="python")
+    data_without_hash = {k: v for k, v in data.items() if k != "manifest_hash"}
+    computed = hashlib.sha256(canonical_yaml(data_without_hash)).hexdigest()
+    if computed != manifest.manifest_hash:
+        raise ValueError(
+            f"manifest_hash mismatch (stored {manifest.manifest_hash[:12]}..., "
+            f"computed {computed[:12]}...)"
+        )
+
+
+def _validate_manifest_path(raw_path: str, *, field_name: str, required_prefix: Path) -> Path:
+    """Return a safe repo-relative manifest path under ``required_prefix``."""
+    path = Path(raw_path.replace("\\", "/"))
+    if path.is_absolute() or ".." in path.parts:
+        raise ValueError(
+            f"{field_name} must be repo-relative and stay under "
+            f"{required_prefix.as_posix()}: {raw_path}"
+        )
+    try:
+        path.relative_to(required_prefix)
+    except ValueError as exc:
+        raise ValueError(
+            f"{field_name} must be under {required_prefix.as_posix()}: {raw_path}"
+        ) from exc
+    return path
+
+
+def _resolve_under_repo(repo_root: Path, rel_path: Path, *, field_name: str) -> Path:
+    """Resolve ``rel_path`` and fail if symlinks escape ``repo_root``."""
+    repo_resolved = repo_root.resolve(strict=False)
+    resolved = (repo_root / rel_path).resolve(strict=False)
+    try:
+        resolved.relative_to(repo_resolved)
+    except ValueError as exc:
+        raise ValueError(
+            f"{field_name} resolves outside repository root: {rel_path.as_posix()}"
+        ) from exc
+    return resolved
+
+
 def verify(manifest: SynthesisManifest, repo_root: Path) -> None:
     """Verify that every artifact listed in the manifest exists with matching hash.
 
@@ -180,7 +233,21 @@ def verify(manifest: SynthesisManifest, repo_root: Path) -> None:
     """
     manifest_path = str(MANIFEST_PATH)
     for entry in manifest.artifacts:
-        artifact_path = repo_root / entry.path
+        artifact_rel = _validate_manifest_path(
+            entry.path,
+            field_name="manifest artifact path",
+            required_prefix=_ARTIFACT_PATH_PREFIX,
+        )
+        _validate_manifest_path(
+            entry.provenance_path,
+            field_name="manifest provenance path",
+            required_prefix=_PROVENANCE_PATH_PREFIX,
+        )
+        artifact_path = _resolve_under_repo(
+            repo_root,
+            artifact_rel,
+            field_name="manifest artifact path",
+        )
         if not artifact_path.exists():
             raise ManifestIntegrityError(
                 manifest_path=manifest_path,
@@ -202,4 +269,5 @@ __all__ = [
     "dump_yaml",
     "load_yaml",
     "verify",
+    "verify_manifest_hash",
 ]