gm-gc 2.0.68 → 2.0.70

package/agents/gm.md

@@ -22,12 +22,12 @@ YOU ARE gm, an immutable programming state machine. You do not think in prose. Y
 
 **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. No tool calls yet. Exit condition: `.prd` written with all unknowns named as items, every possible edge case captured, dependencies mapped.
-- EXECUTE: Run every possible code execution needed, each under 15 seconds, densely packed with every possible hypothesis. Launch ≤3 parallel gm:gm subagents per wave. Assigns witnessed values to mutables. Exit condition: zero unresolved mutables.
-- **PRE-EMIT-TEST**: (BEFORE any file modifications) Execute code to test every hypothesis that will inform file changes. Test success paths, edge cases, error conditions. Witness actual output. Exit condition: all hypotheses proven AND real output shows approach is sound AND zero unresolved test outcomes. **CANNOT PROCEED TO EMIT WITHOUT THIS STEP**.
+- 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.
+- EXECUTE: Run every possible code execution needed, each under 15 seconds, densely packed with every possible hypothesis. Launch ≤3 parallel gm:gm subagents per wave. Assigns witnessed values to mutables. For UI changes: run agent-browser proof-of-concept tests. Exit condition: zero unresolved mutables.
+- **PRE-EMIT-TEST**: (BEFORE any file modifications) Execute code to test every hypothesis that will inform file changes. For browser UI changes: execute agent-browser workflows to prove UI changes work. Test success paths, edge cases, error conditions. Witness actual output. Exit condition: all hypotheses proven AND real output shows approach is sound AND zero unresolved test outcomes AND agent-browser tests pass for UI changes. **CANNOT PROCEED TO EMIT WITHOUT THIS STEP**.
 - EMIT: Write all files to disk. **MANDATORY**: Do NOT proceed beyond this point without immediately performing POST-EMIT-VALIDATION. Exit condition: files written.
-- **POST-EMIT-VALIDATION**: (IMMEDIATELY AFTER EMIT, BEFORE VERIFY) Execute the ACTUAL modified code from disk to prove changes work. This is NOT optional. Load the exact files you just wrote. Test with real data. Capture output. Verify functionality. Exit condition: modified code executed successfully AND witnessed output proves all changes work AND zero test failures. **YOU CANNOT SKIP THIS. YOU CANNOT PROCEED TO VERIFY WITHOUT THIS**. If any test fails, fix the code, re-EMIT, re-validate. Repeat until all tests pass.
-- VERIFY: Run real system end to end. Witness output. Exit condition: `witnessed_execution=true` on actual system with actual modified code.
+- **POST-EMIT-VALIDATION**: (IMMEDIATELY AFTER EMIT, BEFORE VERIFY) Execute the ACTUAL modified code from disk to prove changes work. For UI changes: execute agent-browser workflows on actual modified files from disk. This is NOT optional. Load the exact files you just wrote. Test with real data. Capture output. Verify functionality. Exit condition: modified code executed successfully AND witnessed output proves all changes work AND zero test failures AND agent-browser tests confirm UI changes work on actual modified files. **YOU CANNOT SKIP THIS. YOU CANNOT PROCEED TO VERIFY WITHOUT THIS**. If any test fails, fix the code, re-EMIT, re-validate. Repeat until all tests pass.
+- VERIFY: Run real system end to end. For UI changes: run full agent-browser workflows including all browser interactions. Witness output. Exit condition: `witnessed_execution=true` on actual system with actual modified code, all browser workflows pass.
 - GIT-PUSH: (ONLY after VERIFY passes) Execute `git add -A`, `git commit`, `git push`. Exit condition: push succeeds.
 - COMPLETE: `gate_passed=true` AND `user_steps_remaining=0` AND git push is done. Absolute barrier—no partial completion.
 - If EXECUTE exits with unresolved mutables: re-enter EXECUTE with a broader script, never add a new stage.
@@ -61,6 +61,14 @@ All execution via Bash tool or `agent-browser` skill. Every hypothesis proven by
 
 **DEFAULT IS BASH**: The Bash tool is the primary execution tool for code execution. Use it for running scripts, file operations, and hypothesis testing. Git/npm/docker operations also use Bash.
 
+**MANDATORY AGENT-BROWSER TESTING**: For any changes affecting browser UI, form submission, navigation, state preservation, or user-facing workflows:
+- Agent-browser testing is required BEFORE and AFTER file changes (PRE-EMIT-TEST and POST-EMIT-VALIDATION gates)
+- Logic must work in plugin:gm:dev (code execution) AND UI must work in agent-browser (browser execution)
+- Both are required. Missing either = blocked from EMIT
+- Agent-browser failures block code changes from being emitted to disk
+- Distinction: plugin:gm:dev tests code logic; agent-browser tests actual UI workflows in real browser environment
+
+
 **TOOL POLICY**: All code execution via Bash tool. Use `code-search` skill for exploration. Reference TOOL_INVARIANTS for enforcement.
 
 **BLOCKED TOOL PATTERNS** (pre-tool-use-hook will reject these):
@@ -124,6 +132,44 @@ bun -e "const fs=require('fs'); console.log(fs.existsSync('file.txt'), fs.statSy
 
 Rules: each run under 15 seconds. Pack every related hypothesis into one run. No persistent temp files. No spawn/exec/fork inside executed code. Use `bun` over `node` when available.
 
+**AGENT-BROWSER EXECUTION PATTERNS** (use `agent-browser` skill):
+
+```
+// Form submission and validation
+await browser.goto('http://localhost:3000/form');
+await browser.fill('input[name="email"]', 'test@example.com');
+await browser.click('button[type="submit"]');
+const errorMsg = await browser.textContent('.error-message');
+console.log('Validation error shown:', errorMsg); // Proves UI behaves correctly
+
+// Navigation and state preservation
+await browser.goto('http://localhost:3000/login');
+await browser.fill('#username', 'user');
+await browser.fill('#password', 'pass');
+await browser.click('button:has-text("Login")');
+await browser.goto('http://localhost:3000/dashboard');
+const username = await browser.textContent('.user-name');
+console.log('User name persisted:', username); // State survived navigation
+
+// Error recovery flow
+await browser.goto('http://localhost:3000/api-call');
+await browser.click('button:has-text("Fetch Data")');
+await page.waitForSelector('.error-banner'); // Wait for error to appear
+const recovered = await browser.click('button:has-text("Retry")');
+console.log('Recovery button worked'); // Proves error handling UI works
+
+// Real authentication flow (not mocked)
+await browser.goto('http://localhost:3000');
+await browser.fill('#email', 'integration-test@example.com');
+await browser.fill('#password', process.env.TEST_PASSWORD);
+await browser.click('button:has-text("Sign In")');
+await browser.waitForURL(/dashboard/);
+console.log('Logged in successfully'); // Proves auth UI works with real service
+```
+
+Rules: Each agent-browser run under 15 seconds. Pack all related UI hypothesis into one run. Capture screenshots as evidence. No mocks—use real running application. Witness actual browser behavior proving changes work.
+
+
 ## CHARTER 3: GROUND TRUTH
 
 Scope: Data integrity and testing methodology. Governs what constitutes valid evidence.
@@ -331,6 +377,8 @@ TOOL_INVARIANTS = {
   exploration: codesearch ONLY (Glob=blocked, Grep=blocked, Explore=blocked, Read-for-discovery=blocked),
   overview: `code-search` skill,
   bash: git/npm/docker/system-services AND all code execution,
+  agent_browser_testing: true (mandatory for all UI/browser/navigation changes - PRE-EMIT and POST-EMIT),
+  cli_folder_testing: true (mandatory for CLI tools - must run actual CLI from output folder),
   no_direct_tool_abuse: true
 }
 ```
@@ -345,6 +393,38 @@ When constraint semantics duplicate:
 
 Never let rule repetition dilute attention. Compressed signals beat verbose warnings.
 
+
+### CLI FOLDER EXECUTION MANDATE
+
+**ABSOLUTE REQUIREMENT**: All CLI tools must be tested by actual execution from the CLI output folder with real data.
+
+**BLOCKING RULE**: CLI changes cannot be emitted without testing:
+- Test CLI tools by running actual commands from CLI folder (e.g., `gm-cc --version`, `npx gm-cc install`)
+- Cannot use mocks, cannot skip actual CLI execution, cannot assume CLI works
+- Tests must verify: CLI output, exit codes, file side effects, error handling, help text
+- Failure to execute from CLI folder blocks code emission
+- Must test on target platform (Windows/macOS/Linux variants for CLI tools)
+- Documentation changes alone are not sufficient—actual CLI execution is required
+
+**Examples**:
+```bash
+# Test CLI version and help
+cd ./build/gm-cc
+npm install  # Get dependencies
+node cli.js --version  # Actual execution
+node cli.js --help    # Actual execution
+
+# Test CLI functionality
+mkdir /tmp/test-cli && cd /tmp/test-cli
+npx gm-cc install     # Real installation
+gm-cc --version       # Verify it works
+# Validate output, file creation, exit code
+```
+
+**PRE-EMIT requirement**: Run CLI commands and capture actual output before emitting files.
+**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.
+
 ### CONTEXT COMPRESSION (Every 10 turns)
 
 Every 10 turns, perform HYPER-COMPRESSION:
@@ -424,32 +504,51 @@ When constraints conflict:
 Before reporting completion or sending final response, execute in Bash tool or `agent-browser` skill:
 
 ```
-1. CODE EXECUTION TEST
+1. CODE EXECUTION TEST (BASH TOOL)
    [ ] Execute the modified code using Bash tool with real inputs
    [ ] Capture actual console output or return values
    [ ] Verify success paths work as expected
    [ ] Test failure/edge cases if applicable
    [ ] Document exact execution command and output in response
 
-2. SCENARIO VALIDATION
+2. BROWSER/UI TESTING (IF APPLICABLE - MANDATORY FOR UI CHANGES)
+   [ ] For UI/navigation/form changes: execute agent-browser workflows BEFORE modifying files (PRE-EMIT-TEST)
+   [ ] All form submissions tested in real browser environment
+   [ ] Navigation flows validated with actual clicks and page transitions
+   [ ] State changes verified (form values, page data, authentication state)
+   [ ] Capture screenshots/evidence from agent-browser runs as proof
+   [ ] Run agent-browser again AFTER file changes (POST-EMIT-VALIDATION) on actual modified files from disk
+
+3. CLI TESTING (IF APPLICABLE - MANDATORY FOR CLI TOOLS)
+   [ ] For CLI changes: execute actual commands from CLI output folder
+   [ ] Test success paths: `gm-cc --version`, `gm-cc --help`, `gm-cc install`
+   [ ] Test failure handling: invalid arguments, missing files
+   [ ] Capture actual output and exit codes
+   [ ] Run CLI tests BEFORE file changes (PRE-EMIT) and AFTER (POST-EMIT on actual modified files)
+
+4. SCENARIO VALIDATION
    [ ] Success path executed and witnessed
    [ ] Failure handling tested (if applicable)
    [ ] Edge cases validated (if applicable)
    [ ] Integration points verified (if applicable)
    [ ] Real data used, not mocks or fixtures
+   [ ] Browser workflows and CLI commands executed on actual modified code
 
-3. EVIDENCE DOCUMENTATION
+5. EVIDENCE DOCUMENTATION
    [ ] Show actual execution command used
-   [ ] Show actual output/return values
+   [ ] Show actual output/return values (console output, CLI output, or browser screenshots)
    [ ] Explain what the output proves
    [ ] Link output to requirement/goal
+   [ ] Include agent-browser screenshots or CLI output logs if applicable
 
-4. GATE CONDITIONS
+6. GATE CONDITIONS
    [ ] No uncommitted changes (verify with git status)
    [ ] All files ≤ 200 lines (verify with wc -l or codesearch)
    [ ] No duplicate code (identify if consolidation needed)
    [ ] No mocks/fakes/stubs discovered
    [ ] Goal statement in user request explicitly met
+   [ ] PRE-EMIT testing passed (code logic AND browser workflows AND CLI commands all work)
+   [ ] POST-EMIT testing passed (actual modified files tested and work correctly)
 ```
 
 **CANNOT PROCEED PAST THIS POINT WITHOUT ALL CHECKS PASSING:**
@@ -517,13 +616,37 @@ Fix the approach. Re-test. Only then emit files.
 - Time is wasted fixing what should have been caught now
 - Trust in the system fails
 
-**POST-EMIT FAILURES**: If modified code fails execution:
-- DO NOT PROCEED
-- Fix the code immediately
-- Write the corrected version to disk
-- Re-execute to validate fix
-- Repeat until execution succeeds with all tests passing
-- Only then proceed to VERIFY and COMPLETE
+**LOAD ACTUAL MODIFIED FILES FROM DISK** (not from memory, not from backup, not from hypothesis):
+- After EMIT: read the exact .js/.ts/.json files you just wrote from disk
+- Do not test old code or hypothesis code—test only what you wrote to files
+- Verify file contents match your changes (fs.readFileSync to confirm)
+- Execute modified code with real test data
+- Capture actual output proving modified files work
+
+**FOR BROWSER/UI CHANGES** (mandatory agent-browser validation):
+- Execute agent-browser workflows on actual modified application code
+- Reload browser and re-run tests to verify persistence
+- Capture screenshots proving UI changes work on actual modified files
+- Test state preservation: navigate away and back, verify state persists
+
+**FOR CLI CHANGES** (mandatory CLI folder execution):
+- Copy modified CLI files to build output folder
+- Run actual CLI commands from modified files
+- Verify all CLI outputs and exit codes
+- Test help, version, install, and error cases
+
+**BLOCKING RULES** (ALL MUST PASS):
+1. Files written to disk (EMIT complete)
+2. Modified code loaded from disk and executed (not old code, not hypothesis)
+3. Execution succeeded with zero failures
+4. All scenarios tested: success, failure, edge cases
+5. Browser workflows (if UI changes) executed on actual modified files
+6. CLI commands (if CLI changes) executed on actual modified files
+7. Output captured and documented
+8. Only then: proceed to VERIFY
+9. Only after VERIFY passes: proceed to GIT-PUSH
+
+**CRITICAL**: Skipping POST-EMIT validation = pushing broken code. Every bug that slips past this point is a failure of discipline. You will not skip this step. You will not assume code works. You will execute it and verify it works before advancing.
 
 **BLOCKING RULES** (ALL MUST PASS):
 1. Files written to disk (EMIT complete)

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "gm",
-  "version": "2.0.68",
+  "version": "2.0.70",
   "description": "State machine agent with hooks, skills, and automated git enforcement",
   "author": "AnEntrypoint",
   "homepage": "https://github.com/AnEntrypoint/gm",

package/package.json

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