spec-kitty-cli 3.2.0rc33__tar.gz → 3.2.0rc35__tar.gz

{spec_kitty_cli-3.2.0rc33 → spec_kitty_cli-3.2.0rc35}/.gitignore

@@ -66,6 +66,7 @@ pyproject.local.toml
 .kittify/dossiers/
 .kittify/workspaces/
 .kittify/merge-state.json
+.kittify/sync-state.json
 .kittify/lint-report.json
 .kittify/preflight-warning.json
 .kittify/.migration-backup/
@@ -80,8 +81,6 @@ kitty-specs/**/.kittify/dossiers/
 kitty-specs/*/.kittify/dossiers/*/snapshot-latest.json
 .kittify/charter/context-state.json
 .kittify/charter/directives.yaml
-.kittify/charter/provenance/
-.kittify/charter/synthesis-manifest.yaml
 
 # Doctrine artifacts are version-controlled — that is the point of
 # `spec-kitty agent retrospect synthesize --apply` writing them. Use
@@ -98,6 +97,7 @@ kitty-specs/*/.kittify/dossiers/*/snapshot-latest.json
 !.kittify/doctrine/procedure/**
 !.kittify/doctrine/overlays/
 !.kittify/doctrine/overlays/**
+!.kittify/doctrine/graph.yaml
 
 # Generated glossary entity pages — never commit
 .kittify/charter/compiled/glossary/

{spec_kitty_cli-3.2.0rc33 → spec_kitty_cli-3.2.0rc35}/CHANGELOG.md

@@ -9,14 +9,64 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.2.0rc35] - 2026-06-02
+
+### Added
+
+- Added agent upgrade prompts and slash-command repair diagnostics so project
+  upgrades can detect and repair stale agent command surfaces.
+- Added doctrine/profile activation closure work, including canonical kind
+  resolution, DRG-backed profile lineage, layered charter listing, template
+  discovery, and single-source doctrine health reporting.
+
+### Changed
+
+- Reworked parent-mission acceptance docs and charter boundary documentation
+  around status-commit terminology and profile integrity closeout.
+- Tightened coordination topology handling across runtime prompts, decision
+  logs, dependency gates, move-task transitions, and orchestrator API paths.
+
+### Fixed
+
+- Fixed slash-command install and audit gaps that left generated command files
+  stale after upgrades.
+- Fixed coordination-topology edge cases that could read stale checkout state,
+  miss decision logs, or proceed across topology gaps without failing closed.
+- Fixed charter activation and closeout CI instability, including layer-aware
+  activation and clean-install latency recalibration.
+
+## [3.2.0rc34] - 2026-06-02
+
+### Changed
+
+- Clarified that live canary and cross-repo end-to-end runs remain required
+  release-candidate hygiene under the charter, but are run locally before
+  tagging instead of as tag-time PyPI publish workflow blockers.
+- Transactional mission status reads now resolve the coordination worktree
+  without creating or mutating checkout state, keeping lane views aligned with
+  the coordination branch.
+
+### Fixed
+
+- Planning-artifact commits now preserve append-only coordination event logs
+  instead of clobbering lane history with stale primary-checkout copies.
+- Planning-artifact claim commits now parse git porcelain status structurally,
+  fail closed on unrelated structural changes, and skip idempotent
+  already-on-coordination content.
+- Move-task transitions now derive source and target lanes from transactional
+  coordination status so review handoffs do not fail after coordination/feature
+  branch desync.
+- `.kittify/sync-state.json` is treated as local relay state, while charter
+  synthesis provenance can be tracked with the required commit reminder.
+
 ## [3.2.0rc33] - 2026-06-01
 
 ### Changed
 
 - Tag-time PyPI publishing now stays focused on release-local checks. Live
   canary evidence and the cross-repo end-to-end consumer scenario are no longer
-  blocking jobs in `.github/workflows/release.yml`; operators can still run
-  those suites locally before cutting a release.
+  blocking jobs in `.github/workflows/release.yml`; they remain required local
+  release-candidate hygiene before tagging.
 - Release metadata now aligns `.kittify/metadata.yaml` with `pyproject.toml`
   for `3.2.0rc33`.
 

{spec_kitty_cli-3.2.0rc33 → spec_kitty_cli-3.2.0rc35}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spec-kitty-cli
-Version: 3.2.0rc33
+Version: 3.2.0rc35
 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

spec_kitty_cli-3.2.0rc35/kitty-specs/org-doctrine-profile-integrity-activation-closure-01KT1TV1/contracts/README.md

@@ -0,0 +1,19 @@
+# Contracts Index
+
+Behavioral/interface contracts for the mission. This is a CLI + library mission (no HTTP API), so contracts are expressed as **testable Given/When/Then assertions** against module interfaces and CLI surfaces. Each contract maps to FRs and a WP wave. ATDD-first (charter C-011): these contracts become acceptance/contract tests authored before implementation.
+
+| File | Wave | Covers (FRs) |
+|------|------|--------------|
+| [wave0-foundation.md](wave0-foundation.md) | 0 | kind/ID resolver (FR-027), `SPECIALIZES_FROM` + silent-drop (FR-001/002/003), merge relocation + layer rule (C-009/OQ-2-ii) |
+| [wave1-diagnostics.md](wave1-diagnostics.md) | 1 | profile diagnostics (FR-005..007, NFR-002/005), doctor health report (FR-008..010, NFR-001), dead-symbol wiring (FR-035/036/020) |
+| [wave2-authoring-migration.md](wave2-authoring-migration.md) | 2 | fragment-authoring validation (FR-028/029), augmentation single-source + parity (FR-030/031/032), field-retirement migration (NFR-007), lineage via DRG (FR-002/004) |
+| [wave3-activation.md](wave3-activation.md) | 3 | plan/commit non-mutation (FR-011/012, NFR-003), cascade scope (FR-013/014), shared-reference deactivation (FR-015/016, C-005) |
+| [wave4-runtime-catalog.md](wave4-runtime-catalog.md) | 4 | OperationalContext (FR-017..020, C-006, NFR-004), `list --all` + `--include` (FR-022..026), templates (FR-033/034) |
+
+## Cross-cutting contracts (apply to every WP)
+
+- **CC-1 Layer rule**: no `import` from a higher layer (`kernel ← doctrine ← charter ← specify_cli`). `tests/architectural/test_layer_rules.py` passes; specifically `doctrine` imports neither `charter` nor `specify_cli` after the merge relocation.
+- **CC-2 Quality gate** (`DIRECTIVE_030`): `ruff check .`, `mypy`, and `pytest` pass per WP.
+- **CC-3 ATDD test-first** (C-011, **binding**): the test subtask listed last in each WP is a **readability convention only** — execute it **first**. Author and commit the failing acceptance/contract test as a **separate commit BEFORE any implementation commit** (RED on the WP's `planning_base_branch`), then implement to green. The reviewer verifies red→green. Subtask numbering (e.g. the `Txxx` test row) does not imply execution order.
+- **CC-4 Canonical kinds** (I-K1): no module re-declares the kind set; all derive from `ArtifactKind` + `from_operator_token`.
+- **CC-5 Bulk-edit gate** (`DIRECTIVE_035`): WPs in the field-retirement surface comply with `occurrence_map.yaml`; `implement` refuses an unclassified occurrence.

spec_kitty_cli-3.2.0rc35/kitty-specs/org-doctrine-profile-integrity-activation-closure-01KT1TV1/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: "mission/org-doctrine-profile-integrity-activation-closure"
+merge_target_branch: "mission/org-doctrine-profile-integrity-activation-closure"
+branch_strategy: "Planning artifacts were generated on mission/org-doctrine-profile-integrity-activation-closure; completed changes must merge back into mission/org-doctrine-profile-integrity-activation-closure."
+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.0rc35/kitty-specs/org-doctrine-profile-integrity-closeout-01KT3G68/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: "mission/org-doctrine-profile-integrity-activation-closure"
+merge_target_branch: "mission/org-doctrine-profile-integrity-activation-closure"
+branch_strategy: "Planning artifacts were generated on mission/org-doctrine-profile-integrity-activation-closure; completed changes must merge back into mission/org-doctrine-profile-integrity-activation-closure."
+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.0rc35/kitty-specs/unblock-sync-identity-boundary-canary-01KRZJ07/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.0rc35/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.0rc33 → spec_kitty_cli-3.2.0rc35}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "spec-kitty-cli"
-version = "3.2.0rc33"
+version = "3.2.0rc35"
 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.0rc33 → spec_kitty_cli-3.2.0rc35}/scripts/release/README.md

@@ -114,6 +114,12 @@ Release PR check ownership:
 2. `CI Quality` owns tests, wheel build, lockfile checks, exact install verification, and SaaS consumer compatibility evidence.
 3. `Check Shared Package Drift` owns shared-package pin drift evidence.
 
+Live canary and cross-repo end-to-end runs are release-candidate hygiene, not
+tag-time publish jobs. The charter still requires them before a release
+candidate is tagged; the release owner must run them locally from a trusted
+runner and record the pass, product failure, inconclusive result, or explicit
+maintainer waiver.
+
 Tag-time publish workflow sequence:
 
 1. run tests
@@ -149,21 +155,28 @@ python scripts/release/check_candidate_consumer_compat.py \
   --consumer-contract ../spec-kitty-saas/contracts/consumer-compatibility.json
 twine check dist/*
 
-# 3) clean build artifacts
+# 3) release-candidate hygiene (local trusted-runner evidence, before tagging)
+pushd ../../spec-kitty-end-to-end-testing
+uv sync
+SPEC_KITTY_ENABLE_SAAS_SYNC=1 uv run pytest tests/ -v
+./scripts/run-canary.sh --profile local --phase all
+popd
+
+# 4) clean build artifacts
 rm -rf dist/ build/
 
-# 4) commit, push, and merge the release metadata through a PR
+# 5) commit, push, and merge the release metadata through a PR
 spec-kitty safe-commit --message "chore(release): prepare 3.1.0a0" pyproject.toml CHANGELOG.md
 git push origin release/3.1.0a0
 gh pr create --base main --title "Release 3.1.0a0" --fill
 
-# 5a) prerelease publish from updated main
+# 6a) prerelease publish from updated main
 git checkout main
 git pull origin main
 git tag v3.1.0a0 -m "Release 3.1.0a0"
 git push origin v3.1.0a0
 
-# 5b) stable publish from updated main
+# 6b) stable publish from updated main
 #     Edit pyproject.toml to "3.1.0" and rename the changelog heading to [3.1.0]
 git tag v3.1.0 -m "Release 3.1.0"
 git push origin v3.1.0