spec-kitty-cli 3.2.0rc14__tar.gz → 3.2.0rc15__tar.gz

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/.gitignore

@@ -78,7 +78,22 @@ kitty-specs/*/.kittify/dossiers/*/snapshot-latest.json
 .kittify/charter/directives.yaml
 .kittify/charter/provenance/
 .kittify/charter/synthesis-manifest.yaml
-.kittify/doctrine/
+
+# Doctrine artifacts are version-controlled — that is the point of
+# `spec-kitty agent retrospect synthesize --apply` writing them. Use
+# `/**` (not the bare directory) so the doctrine directory itself stays
+# traversable for whitelists; then re-include the canonical artifact
+# subdirectories (directive/, tactic/, procedure/, overlays/). Tracked
+# upstream as Priivacy-ai/spec-kitty#1166.
+.kittify/doctrine/**
+!.kittify/doctrine/directive/
+!.kittify/doctrine/directive/**
+!.kittify/doctrine/tactic/
+!.kittify/doctrine/tactic/**
+!.kittify/doctrine/procedure/
+!.kittify/doctrine/procedure/**
+!.kittify/doctrine/overlays/
+!.kittify/doctrine/overlays/**
 
 # Generated glossary entity pages — never commit
 .kittify/charter/compiled/glossary/

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/CHANGELOG.md

@@ -9,6 +9,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.2.0rc15] - 2026-05-19
+
+Ships the Phase 4 canary unblock work landed via PR `#1180`:
+
+- Closes `#1142`: broadens `is_mission_lifecycle_row` in
+  `src/specify_cli/audit/shape_registry.py` to accept all four canonical
+  aggregate types (`Project`, `Mission`, `WorkPackage`, `MissionDossier`)
+  rather than `Mission` alone. Fresh missions no longer trip the
+  `FORBIDDEN_KEY` TeamSpace gate when `sync now` runs.
+- Closes `#1141`: adds a diagnostic breadcrumb at `fire_saas_fanout` entry in
+  `src/specify_cli/status/adapters.py` plus regression coverage that the
+  backward `in_review → planned` rollback reaches fanout with the expected
+  shape. **Note**: this is a diagnostic landing, not the full root-cause fix
+  — the silent replacement that the canary scenario 4 peek catches likely
+  lives downstream in `OfflineQueue.queue_event` and is expected to be
+  chased on a follow-up RC if it reproduces.
+- Bundles the +30 targeted audit / status-emit-sequence tests from `#1180`.
+
 ## [3.2.0rc14] - 2026-05-19
 
 Ships the next 3.2 release candidate after the doctrine/charter and

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: spec-kitty-cli
-Version: 3.2.0rc14
+Version: 3.2.0rc15
 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.0rc15/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.0rc15/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.0rc14 → spec_kitty_cli-3.2.0rc15}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "spec-kitty-cli"
-version = "3.2.0rc14"
+version = "3.2.0rc15"
 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.0rc14 → spec_kitty_cli-3.2.0rc15}/src/doctrine/schemas/toolguide.schema.yaml

@@ -26,7 +26,7 @@ properties:
     minLength: 1
   guide_path:
     type: string
-    pattern: ^src/doctrine/.+\.md$
+    pattern: ^[^/].*\.md$
   summary:
     type: string
     minLength: 1

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/src/doctrine/toolguides/models.py

@@ -12,7 +12,7 @@ class Toolguide(BaseModel):
     schema_version: str = Field(pattern=r"^1\.0$")
     tool: str
     title: str
-    guide_path: str = Field(pattern=r"^src/doctrine/.+\.md$")
+    guide_path: str = Field(pattern=r"^[^/].*\.md$")
     summary: str
     commands: list[str] = Field(default_factory=list)
     applies_to_languages: list[str] = Field(default_factory=list)

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/src/specify_cli/audit/shape_registry.py

@@ -8,10 +8,15 @@ for any top-level key that is not in the known set, not a legacy key, and not
 a forbidden key (those have dedicated finding codes).
 
 Also exposes ``is_mission_lifecycle_row()`` — a row-family classifier that
-distinguishes legitimate mission-lifecycle event rows
-(``aggregate_type == "Mission"`` AND non-empty ``event_type``) from canonical
-status-transition rows (``from_lane`` / ``to_lane``). The audit engine consults
-this predicate to scope the ``FORBIDDEN_KEYS`` rule to non-lifecycle rows.
+distinguishes legitimate lifecycle event rows (those carrying a non-empty
+``event_type`` AND an ``aggregate_type`` in the known lifecycle set
+``{"Mission", "Project", "WorkPackage", "MissionDossier"}``) from canonical
+status-transition rows (``from_lane`` / ``to_lane``). The audit engine
+consults this predicate to scope the ``FORBIDDEN_KEYS`` rule to non-lifecycle
+rows. Issue #1142 broadened the accepted set beyond ``"Mission"`` so that
+``Project``, ``WorkPackage``, and ``MissionDossier`` lifecycle rows emitted
+by the events package no longer raise ``FORBIDDEN_KEY`` findings on
+legitimate keys.
 
 Reference: ``kitty-specs/unblock-sync-identity-boundary-canary-01KRZJ07/
 contracts/audit-row-family.md``.
@@ -165,26 +170,46 @@ KNOWN_TOP_LEVEL_KEYS_BY_ARTIFACT: dict[str, frozenset[str]] = {
 # Row-family classifiers
 # ---------------------------------------------------------------------------
 
+# Aggregate types that legitimately carry the ``event_type`` discriminator.
+# Issue #1142: the original predicate accepted only ``"Mission"``, which
+# mis-classified ``Project``, ``WorkPackage``, and ``MissionDossier``
+# lifecycle rows emitted by the events package as malformed
+# status-transition rows. The audit engine then raised ``FORBIDDEN_KEY``
+# findings against legitimate lifecycle keys (``event_type``,
+# ``aggregate_type``), blocking canary scenarios 1 + 2 with
+# ``TeamSpace migration required. Finding codes: FORBIDDEN_KEY``.
+LIFECYCLE_AGGREGATE_TYPES: frozenset[str] = frozenset(
+    {"Mission", "Project", "WorkPackage", "MissionDossier"}
+)
+
 
 def is_mission_lifecycle_row(row: Mapping[str, Any]) -> bool:
-    """Return ``True`` iff *row* matches the mission-lifecycle row family.
+    """Return ``True`` iff *row* matches the lifecycle event-row family.
 
-    Mission-lifecycle rows are written by ``status/lifecycle_events.py`` (and
-    its peers) into ``status.events.jsonl``. They carry the lifecycle
+    Lifecycle rows are written by ``status/lifecycle_events.py`` (and its
+    peers) into ``status.events.jsonl``. They carry the lifecycle
     discriminator ``event_type`` (e.g. ``"MissionCreated"``,
-    ``"SpecifyStarted"``) and identify the aggregate via
-    ``aggregate_type == "Mission"``. **Both** predicates must hold; either
-    alone does NOT classify as a lifecycle row — that distinction is what
-    keeps the ``FORBIDDEN_KEYS`` audit rule effective against malformed
-    status-transition rows that carry ``event_type`` without
-    ``aggregate_type``.
+    ``"SpecifyStarted"``, ``"WPStatusChanged"``) and identify the aggregate
+    via ``aggregate_type`` set to one of
+    ``{"Mission", "Project", "WorkPackage", "MissionDossier"}``. **Both**
+    predicates must hold; either alone does NOT classify as a lifecycle
+    row — that distinction is what keeps the ``FORBIDDEN_KEYS`` audit rule
+    effective against malformed status-transition rows that carry
+    ``event_type`` without a matching ``aggregate_type``.
+
+    Issue #1142 broadened the accepted ``aggregate_type`` set beyond the
+    original ``"Mission"``-only check. The events package legitimately
+    emits ``Project``/``WorkPackage``/``MissionDossier`` lifecycle rows
+    and the audit must not flag those as forbidden-key violations.
 
     Args:
         row: A parsed JSONL row (typically from ``status.events.jsonl``).
 
     Returns:
-        ``True`` when *row* is a mission-lifecycle row; ``False`` otherwise
-        (including for non-mapping inputs, which are conservatively rejected).
+        ``True`` when *row* is a lifecycle row; ``False`` otherwise
+        (including for non-mapping inputs, which are conservatively
+        rejected, and for rows whose ``aggregate_type`` is absent,
+        empty, or outside the known lifecycle set).
 
     Reference:
         ``kitty-specs/unblock-sync-identity-boundary-canary-01KRZJ07/
@@ -192,7 +217,8 @@ def is_mission_lifecycle_row(row: Mapping[str, Any]) -> bool:
     """
     if not isinstance(row, Mapping):
         return False
-    if row.get("aggregate_type") != "Mission":
+    aggregate_type = row.get("aggregate_type")
+    if aggregate_type not in LIFECYCLE_AGGREGATE_TYPES:
         return False
     event_type = row.get("event_type")
     return isinstance(event_type, str) and bool(event_type)

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/src/specify_cli/cli/commands/agent/status.py

@@ -724,7 +724,7 @@ def validate(
         spec-kitty agent status validate --mission 034-my-feature
         spec-kitty agent status validate --json
     """
-    from specify_cli.status.store import read_events_raw
+    from specify_cli.status.store import read_events, read_events_raw
     from specify_cli.status.validate import (
         ValidationResult,
         validate_done_evidence,
@@ -781,11 +781,13 @@ def validate(
             console.print("[green]Result: PASS[/green]")
         raise typer.Exit(0)
 
-    for event in raw_events:
+    status_events = [event.to_dict() for event in read_events(feature_dir)]
+
+    for event in status_events:
         result.errors.extend(validate_event_schema(event))
 
-    result.errors.extend(validate_transition_legality(raw_events))
-    result.errors.extend(validate_done_evidence(raw_events))
+    result.errors.extend(validate_transition_legality(status_events))
+    result.errors.extend(validate_done_evidence(status_events))
 
     # Drift detection: event log is sole authority, drift is always an error
     drift_findings = validate_materialization_drift(feature_dir)

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/src/specify_cli/cli/commands/upgrade.py

@@ -528,6 +528,12 @@ def upgrade(  # noqa: C901
             metadata.last_upgraded_at = datetime.now()
             metadata.save(kittify_dir)
 
+        if not dry_run:
+            from specify_cli.migration.schema_version import REQUIRED_SCHEMA_VERSION
+
+            if REQUIRED_SCHEMA_VERSION is not None:
+                MigrationRunner._stamp_schema_version(kittify_dir, REQUIRED_SCHEMA_VERSION)
+
         if not dry_run:
             auto_committed, auto_commit_paths, auto_commit_warning = _auto_commit_upgrade_changes(
                 project_path=project_path,

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/src/specify_cli/doctrine_synthesizer/apply.py

@@ -183,6 +183,14 @@ def _assert_within(base: Path, target: Path) -> Path:
     return resolved_target
 
 
+def _repo_relative_posix(path: Path, repo_root: Path) -> str:
+    """Return a stable repo-relative path for persisted event payloads."""
+    try:
+        return path.resolve().relative_to(repo_root.resolve()).as_posix()
+    except ValueError:
+        return path.as_posix()
+
+
 def _apply_add_glossary_term(
     payload: AddGlossaryTermPayload,
     repo_root: Path,
@@ -739,7 +747,7 @@ def _apply_one(
                 proposal_id=proposal.id,
                 kind=proposal.kind,
                 target_urn=target_urn,
-                provenance_ref=str(prov_path),
+                provenance_ref=_repo_relative_posix(prov_path, repo_root),
                 applied_by=actor,
             ),
         )

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/src/specify_cli/status/adapters.py

@@ -117,12 +117,35 @@ def fire_saas_fanout(**kwargs: Any) -> None:
     - Exceptions are caught per handler, logged at WARNING level, and
       never propagate to the caller.
     - If no handlers are registered, this is a no-op.
+
+    Logs an INFO-level entry breadcrumb (issue #1141) so silent fan-out
+    failures on review-rejection / backward-rewind transitions are
+    correlatable with the originating canonical event in operator logs.
+    The breadcrumb identifies the WP, lane delta, and force flag; the
+    full kwargs are NOT logged (PII / payload-size reasons).
     """
+    # Diagnostic breadcrumb (issue #1141). Cheap dict.get() calls avoid
+    # raising if the caller drops a key; the breadcrumb is best-effort and
+    # never blocks fan-out. Log even with zero handlers; a missing handler
+    # registration is one of the states this breadcrumb is meant to reveal.
+    logger.info(
+        "fire_saas_fanout: wp_id=%s from=%s to=%s force=%s handlers=%d",
+        kwargs.get("wp_id"),
+        kwargs.get("from_lane"),
+        kwargs.get("to_lane"),
+        kwargs.get("force"),
+        len(_saas_handlers),
+    )
     for handler in _saas_handlers:
         try:
             handler(**kwargs)
         except Exception:
             logger.warning(
-                "SaaS fan-out handler failed; canonical status log unaffected",
+                "SaaS fan-out handler failed; canonical status log unaffected "
+                "(wp_id=%s from=%s to=%s force=%s)",
+                kwargs.get("wp_id"),
+                kwargs.get("from_lane"),
+                kwargs.get("to_lane"),
+                kwargs.get("force"),
                 exc_info=True,
             )

{spec_kitty_cli-3.2.0rc14 → spec_kitty_cli-3.2.0rc15}/src/specify_cli/status/validate.py

@@ -188,35 +188,43 @@ def validate_done_evidence(events: list[dict]) -> list[str]:
     return findings
 
 
+def _validate_materialization_files(status_path: Path, events_path: Path) -> list[str] | None:
+    """Return early materialization file findings, or None when both files exist."""
+    if not events_path.exists():
+        if status_path.exists():
+            return ["status.json exists but status.events.jsonl is missing"]
+        return []
+
+    if not status_path.exists():
+        return ["status.events.jsonl exists but status.json is missing (run 'spec-kitty agent status materialize' to generate)"]
+
+    return None
+
+
 def validate_materialization_drift(feature_dir: Path) -> list[str]:
     """Compare status.json on disk vs reducer output from the event log.
 
     Returns findings describing any drift detected. An empty list means
     no drift.
     """
-    from .reducer import SNAPSHOT_FILENAME, reduce
-    from .store import EVENTS_FILENAME, read_events
+    from .reducer import SNAPSHOT_FILENAME, materialize_snapshot
+    from .store import EVENTS_FILENAME
 
     findings: list[str] = []
 
     status_path = feature_dir / SNAPSHOT_FILENAME
     events_path = feature_dir / EVENTS_FILENAME
 
-    if not events_path.exists():
-        if status_path.exists():
-            findings.append("status.json exists but status.events.jsonl is missing")
-        return findings
-
-    if not status_path.exists():
-        findings.append("status.events.jsonl exists but status.json is missing (run 'spec-kitty agent status materialize' to generate)")
-        return findings
+    file_findings = _validate_materialization_files(status_path, events_path)
+    if file_findings is not None:
+        return file_findings
 
     # Read on-disk snapshot
     disk_data = json.loads(status_path.read_text(encoding="utf-8"))
 
-    # Compute expected snapshot from events
-    events = read_events(feature_dir)
-    expected_snapshot = reduce(events)
+    # Compute expected snapshot from all compatible event families.
+    expected_snapshot = materialize_snapshot(feature_dir)
+    expected_data = expected_snapshot.to_dict()
 
     # Compare work_packages and summary (skip materialized_at which is timestamp)
     disk_wps = disk_data.get("work_packages", {})
@@ -238,6 +246,9 @@ def validate_materialization_drift(feature_dir: Path) -> list[str]:
             elif disk_wp != expected_wp:
                 findings.append(f"Materialization drift: {wp_id} state differs between status.json and reducer output")
 
+    if disk_data.get("retrospective") != expected_data.get("retrospective"):
+        findings.append("Materialization drift: retrospective snapshot differs between status.json and reducer output")
+
     # Also check event count and last_event_id
     if disk_data.get("event_count") != expected_snapshot.event_count:
         findings.append(f"Materialization drift: event_count={disk_data.get('event_count')} in status.json but reducer counted {expected_snapshot.event_count}")