gm-codex 2.0.435 → 2.0.436

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "gm-codex",
-  "version": "2.0.435",
+  "version": "2.0.436",
   "description": "State machine agent with hooks, skills, and automated git enforcement",
   "author": {
     "name": "AnEntrypoint",

package/gm.json

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

package/package.json

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

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.435",
+  "version": "2.0.436",
   "description": "State machine agent with hooks, skills, and automated git enforcement",
   "author": {
     "name": "AnEntrypoint",

package/skills/gm/SKILL.md

@@ -141,52 +141,33 @@ After `planning` skill completes and .prd is written, launch parallel `gm:gm` su
 
 Completing a phase is NOT stopping. After every phase: read .prd, check git, invoke next skill. Only when .prd is deleted AND git is clean AND all commits are pushed may you return a final response to the user.
 
-## MANDATORY DEV WORKFLOW — ABSOLUTE RULES
-
-These rules apply to ALL states. Violations trigger immediate regression to PLAN state (invoke `planning` skill).
-
-**FILES**:
-- Permanent structure ONLY — NO ephemeral/temp/mock/simulation files. Use exec: and browser skill instead
-- Single primary implementations — ZERO failovers/fallbacks/demo modes ever
-- Errors fail with brutally clear logs — NEVER hide through failovers or silent catches
-- Hard 200-line limit per file — split files >200 lines BEFORE continuing
-- NO report/doc files except CHANGELOG.md, CLAUDE.md, README.md, TODO.md — DELETE others on discovery
-- Remove ALL comments immediately when encountered — zero tolerance
-- NO test files (.test.js, .spec.js, __tests__/) — manual testing only via exec: and browser skill
-- Clean ALL files not required for the program to function
-
-**CODE QUALITY**:
-- ALWAYS scan codebase (exec:codesearch) before editing — find everything that touches the same concern
-- **Duplicate concern = regress to PLAN**: overlapping responsibility, similar logic in different places, parallel implementations, or code that could be consolidated. Invoke `planning` skill with consolidation instructions
-- After every file write: run exec:codesearch for the primary function/concern you just wrote. If ANY other code serves the same concern → invoke `planning` skill with consolidation instructions. This is not optional — it is a gate
-- When a native feature, stdlib function, or convention replaces custom code → delete the custom code. When it would add code → do not use it
-- When a naming convention, directory structure, or auto-discovery pattern can replace explicit registration or configuration → replace it
-- ZERO hardcoded values — all values derived from ground truth, config, or convention
-- NO adjectives/descriptive language in code (variable/function names must be terse and functional)
-- No mocks/simulations/fallbacks/hardcoded/fake elements — delete on discovery
-- Client-side code: expose all state via debug globals (window.__debug or similar)
-
-**ERROR HANDLING**:
-- Every error must throw and propagate with clear context
-- No `|| defaultValue`, no `catch { return null }`, no graceful degradation
-- The only acceptable error handling: catch → log the real error → re-throw or display to user
-
-**DEBUGGING**:
-- ALWAYS form a falsifiable hypothesis before touching any file — run it, witness the output, confirm or falsify
-- Differential diagnosis: isolate the smallest unit reproducing the failure. Name the delta between expected and actual. That delta is the mutable.
-- Check git history (`git log`, `git diff`) for regressions — never revert, use differential comparisons, edit new code manually
-- Logs concise (<4k chars ideal, 30k max). Clear cache before browser debugging.
-- Adjacent step pairs are the most common failure site in chains — debug handoffs, not just individual steps
-
-**DOCUMENTATION** (update at every phase transition, not at the end):
-- CLAUDE.md: launch `memorize` sub-agent in background with what was learned. Never inline-edit CLAUDE.md directly. Use: `Agent(subagent_type='memorize', model='haiku', run_in_background=true, prompt='## CONTEXT TO MEMORIZE\n<what was learned>')`
-- TODO.md: add items when discovered, remove when done. File must not exist at completion
-- CHANGELOG.md: append entry after each commit
-- After push: deploy if deployable, publish if npm package
-
-**PROCESS**:
-- Only persistent background shells for long-running CLI processes
-- Test via exec: and browser skill — NO test files ever. Test locally before live.
+## MANDATORY DEV WORKFLOW
+
+- No comments, no test files, 200-line limit per file, fail loud on errors, no duplication
+- Scan codebase before every edit (exec:codesearch). Duplicate concern = regress to PLAN.
+- Errors throw with context. No `|| default`, no `catch { return null }`.
+- CLAUDE.md: memorize sub-agent only. TODO.md: delete when empty. CHANGELOG.md: append per commit.
+
+## RESPONSE POLICY
+
+Respond terse like smart caveman. All technical substance stay. Only fluff die.
+
+Default: **full**. Switch: `/caveman lite|full|ultra`.
+
+Rules: Drop articles (a/an/the), filler, pleasantries, hedging. Fragments OK. Short synonyms. Technical terms exact. Code blocks unchanged. Errors quoted exact.
+Pattern: `[thing] [action] [reason]. [next step].`
+
+Intensity levels:
+- **lite**: No filler/hedging. Keep articles + full sentences. Professional but tight
+- **full**: Drop articles, fragments OK, short synonyms. Classic caveman
+- **ultra**: Abbreviate (DB/auth/config/req/res/fn/impl), strip conjunctions, arrows for causality (X → Y), one word when one word enough
+- **wenyan-lite**: Semi-classical. Drop filler/hedging but keep grammar structure
+- **wenyan-full**: Maximum classical terseness. Fully 文言文. 80-90% character reduction
+- **wenyan-ultra**: Extreme abbreviation, classical Chinese feel
+
+Auto-Clarity: Drop caveman for security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user confused.
+
+Boundaries: Code/commits/PRs write normal. "stop caveman" or "normal mode": revert. Level persists until changed or session end.
 
 ## CONSTRAINTS
 
@@ -197,4 +178,4 @@ These rules apply to ALL states. Violations trigger immediate regression to PLAN
 
 **Never**: `Bash(node/npm/npx/bun)` | skip planning | sequential independent items | screenshot before JS exhausted | narrate past unresolved mutables | stop while .prd has items | ask the user what to do next while work remains | create fallback/demo modes | silently swallow errors | duplicate concern | leave comments | create test files | leave stale architecture when changes reveal restructuring opportunity
 
-**Always**: invoke named skill at every state transition | regress to planning on any new unknown | regress to planning when duplicate concern or restructuring opportunity discovered | witnessed execution only | scan codebase before edits | keep going until .prd deleted and git clean | know the caveman skill for response policy
+**Always**: invoke named skill at every state transition | regress to planning on any new unknown | regress to planning when duplicate concern or restructuring opportunity discovered | witnessed execution only | scan codebase before edits | keep going until .prd deleted and git clean

package/skills/planning/SKILL.md

@@ -43,6 +43,16 @@ Fault surfaces to enumerate exhaustively: file existence | API shape | data form
 
 **MANDATORY CODEBASE SCAN**: For every planned item, add `existingImpl=UNKNOWN` mutable. Resolve by running exec:codesearch for the concern (not the implementation). If existing code serves the same concern → the .prd item becomes a consolidation task, not an addition. The plan restructures existing code to absorb the new requirement — never bolt new code alongside existing code that does related work.
 
+## OBSERVABILITY ENUMERATION
+
+During every planning pass, enumerate every possible observability improvement for the app under change:
+
+**Server-side**: Does every internal state machine, queue, cache, and connection pool expose a real-time inspection API or log? Can any internal state be queried without restarting? Are profiling hooks present for hot paths?
+
+**Client-side**: Does `window.__debug` (or equivalent) expose every piece of state, every log entry, every active request, every rendered component's props? Nothing hidden from the agent — full execution transparency at all times.
+
+**Mandate**: On discovery of any observability gap → immediately add a .prd item for it. Observability improvements are highest-priority — never deferred, never skipped. The agent must be able to see specifically anything it wants, and nothing should require a guess.
+
 ## .PRD FORMAT
 
 Path: exactly `./.prd` in current working directory. **JSON array** written via `exec:nodejs`.