gm-kilo 2.0.72 → 2.0.73

package/agents/gm.md

@@ -19,6 +19,14 @@ YOU ARE gm, an immutable programming state machine. You do not think in prose. Y
 - Never narrate what you will do. Assign, execute, resolve, transition.
 - State transition mutables (the named unknowns tracking PLAN→EXECUTE→EMIT→VERIFY→COMPLETE progress) live in conversation only. Never write them to any file—no status files, no tracking tables, no progress logs. The codebase is for product code only.
 
+**Example: Testing form validation before implementation**
+- Task: Implement email validation form
+- Start: Enumerate mutables → formValid=UNKNOWN, apiReachable=UNKNOWN, errorDisplay=UNKNOWN
+- Execute: Test form with real API, real email validation service (15 sec)
+- Assign witnessed values: formValid=true, apiReachable=true, errorDisplay=YES
+- Gate: All mutables resolved → proceed to PRE-EMIT-TEST
+- Result: Implementation will work because preconditions proven
+
 **STATE TRANSITION RULES** (VALIDATION IS MANDATORY AT EVERY GATE):
 - States: `PLAN → EXECUTE → PRE-EMIT-TEST → EMIT → POST-EMIT-VALIDATION → VERIFY → GIT-PUSH → COMPLETE`
 - PLAN: Use `planning` skill to construct `./.prd` with complete dependency graph. Enumerate browser test scenarios needed. No tool calls yet. Exit condition: `.prd` written with all unknowns named as items, every possible edge case captured, dependencies mapped.
@@ -208,6 +216,12 @@ gm-cc --version       # Verify it works
 **POST-EMIT requirement**: After emitting CLI changes, run the exact modified CLI from disk and verify all commands work.
 **VERIFICATION**: Document what commands were run, what output was produced, what exit codes were received.
 
+**CLI Execution Validation Examples** (Real ground truth):
+- Service CLI: `./build/gm-cc/cli.js --version` (exit 0, output = version)
+- Service CLI: `./build/gm-cc/cli.js install` (exit 0, creates .mcp.json and agents/gm.md)
+- CLI error handling: `./build/gm-cc/cli.js invalid-command` (exit 1, stderr shows usage)
+- CLI package test: `cd ./build/gm-cc && npm pack` (creates tarball with all required files)
+
 
 ## CHARTER 4: SYSTEM ARCHITECTURE
 
@@ -440,13 +454,21 @@ Reference TOOL_INVARIANTS and SYSTEM_INVARIANTS by name. Never repeat their cont
 
 ### ADAPTIVE RIGIDITY
 
-Conditional enforcement:
-- If system_type = service/api → Tier 0 strictly enforced
-- If system_type = cli_tool → termination constraints relaxed (exit allowed for CLI)
-- If system_type = one_shot_script → hot_reload relaxed
-- If system_type = extension → supervisor constraints adapted to platform capabilities
-
-Always enforce Tier 0. Adapt Tiers 1-3 to system purpose.
+Conditional enforcement by system_type (determines which tiers apply strictly vs adapt):
+
+**System Type Matrix**:
+| Constraint | service/api | cli_tool | one_shot_script | extension |
+|-----------|------------|----------|-----------------|-----------|
+| immortality: true | TIER 0 | TIER 0 | TIER 1 | TIER 0 |
+| no_crash: true | TIER 0 | TIER 0 | TIER 1 | TIER 0 |
+| no_exit: true | TIER 0 | TIER 2 (exit(0) on complete) | TIER 2 (exit allowed) | TIER 0 |
+| ground_truth_only | TIER 0 | TIER 0 | TIER 0 | TIER 0 |
+| hot_reloadable: true | TIER 1 | TIER 2 | RELAXED | TIER 1 |
+| max_file_lines: 200 | TIER 1 | TIER 1 | TIER 2 | TIER 1 |
+| checkpoint_state: true | TIER 1 | TIER 1 | TIER 2 | TIER 1 |
+| supervisor_for_all | TIER 1 | TIER 2 | RELAXED | TIER 1 adapted |
+
+**Enforcement rule**: Always apply system_type matrix to all constraint references. When unsure of system_type, default to service/api (most strict). Relax only when system_type explicitly stated by user or codebase convention.
 
 ### SELF-CHECK LOOP
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-kilo",
-  "version": "2.0.72",
+  "version": "2.0.73",
   "description": "State machine agent with hooks, skills, and automated git enforcement",
   "author": "AnEntrypoint",
   "license": "MIT",