chore: update project files

Author: tbitcs

.gitignore

@@ -71,7 +71,11 @@ _diag_*.py
 .specsmith/esdb_migration_manifest.json
 
 # Old Warp branding directory — renamed to .kairos/; prevent accidental re-creation
-.warp/
+# Exception: .warp/workflows/ is the standard Warp terminal repository workflow location.
+# Use .warp/* (not .warp/) so git recurses into subdirectories for the !-exceptions below.
+.warp/*
+!.warp/workflows
+!.warp/workflows/**
 
 # Rust build artifacts
 crates/chronomemory/target/

.warp/workflows/specsmith-audit.yaml

@@ -0,0 +1,9 @@
+name: specsmith — Audit
+command: specsmith audit
+tags:
+  - specsmith
+  - governance
+description: >
+  Run the specsmith governance audit. Checks requirements vs tests vs
+  architecture for drift. Required before advancing an AEE phase.
+  All 27 checks must pass (or be suppressed) before a phase advance.

.warp/workflows/specsmith-checkpoint.yaml

@@ -0,0 +1,10 @@
+name: specsmith — Checkpoint (Governance Anchor)
+command: specsmith checkpoint
+tags:
+  - specsmith
+  - governance
+description: >
+  Emit the GOVERNANCE ANCHOR block showing current phase, health, REQ/TEST
+  counts, and active work items. Run every 8-10 turns in an AI session,
+  or any time you suspect drift. Output must be included verbatim in any
+  context summary.

.warp/workflows/specsmith-phase.yaml

@@ -0,0 +1,10 @@
+name: specsmith — Phase Status
+command: specsmith phase show
+tags:
+  - specsmith
+  - governance
+description: >
+  Show the current AEE phase and its readiness checklist. Phases are:
+  inception → architecture → requirements → test_spec → implementation →
+  verification → release. Use `specsmith phase next` to advance after a
+  clean audit.

.warp/workflows/specsmith-preflight.yaml

@@ -0,0 +1,14 @@
+name: specsmith — Preflight
+command: specsmith preflight "{{intent}}" --json
+tags:
+  - specsmith
+  - governance
+description: >
+  Run a governance preflight check before any code change. Describe what
+  you intend to do; the broker returns accepted / needs_clarification /
+  rejected plus a work_item_id. Never make a code change without an
+  accepted preflight.
+arguments:
+  - name: intent
+    description: One sentence describing the change you are about to make (e.g. "fix the parser bug in lexer.py")
+    default_value: describe your intended change here

.warp/workflows/specsmith-save.yaml

@@ -0,0 +1,10 @@
+name: specsmith — Save (commit + push + ESDB backup)
+command: specsmith save
+tags:
+  - specsmith
+  - governance
+description: >
+  Governance-aware save: backs up the ESDB (ChronoStore), creates a
+  governed git commit if there are staged changes, and pushes. Always
+  use this instead of plain `git commit`. Run at the end of every
+  session or after completing a feature or fix.

.warp/workflows/specsmith-session-end.yaml

@@ -0,0 +1,10 @@
+name: specsmith — Session End
+command: specsmith save && specsmith kill-session
+tags:
+  - specsmith
+  - governance
+description: >
+  End-of-session teardown: runs specsmith save (ESDB backup + commit +
+  push) then kills governance-serve and any tracked agent processes.
+  Always run this before closing Warp. Never leave a session with
+  uncommitted governance changes.

.warp/workflows/specsmith-session-start.yaml

@@ -0,0 +1,10 @@
+name: specsmith — Session Start
+command: specsmith kill-session 2>/dev/null || true && specsmith migrate run && specsmith audit && specsmith sync && specsmith checkpoint
+tags:
+  - specsmith
+  - governance
+description: >
+  Full specsmith session bootstrap: kill any orphaned processes, apply
+  pending migrations, run governance audit, confirm machine sync, and
+  emit the GOVERNANCE ANCHOR checkpoint. Run this at the start of every
+  session before touching any code.