@trac3er/oh-my-god 2.2.3 → 2.2.5

package/build/lib/commands/OMG:escalate.md

@@ -1,52 +0,0 @@
----
-description: Auto-route to Codex or Gemini using OMG standalone internal router.
-allowed-tools: Read, Grep, Glob, Bash(git:*), Bash(rg:*), Bash(find:*), Bash(cat:*), Bash(python3:*)
-argument-hint: "[codex|gemini|ccg|auto] 'task description' or just 'problem'"
----
-
-# /OMG:escalate — Standalone Smart Escalation
-
-## Auto-Routing
-If no model specified:
-- backend/security/debug/performance → `codex`
-- ui/ux/layout/responsive → `gemini`
-- full-stack/architecture/review-all → `ccg`
-
-## Context package
-Build from OMG canonical state:
-- `.omg/state/profile.yaml`
-- `.omg/state/ledger/failure-tracker.json`
-- relevant files (`git diff --name-only`)
-
-## Runtime entrypoint
-Use the portable runtime installed by `OMG-setup.sh` (`~/.claude/omg-runtime/scripts/omg.py`).
-
-```bash
-OMG_CLI="${OMG_CLI_PATH:-$HOME/.claude/omg-runtime/scripts/omg.py}"
-if [ ! -f "$OMG_CLI" ] && [ -f "scripts/omg.py" ]; then OMG_CLI="scripts/omg.py"; fi
-```
-
-## Execute
-```bash
-python3 "$OMG_CLI" teams --target auto --problem "[problem]"
-```
-
-Explicit target:
-```bash
-python3 "$OMG_CLI" teams --target codex --problem "[problem]"
-python3 "$OMG_CLI" teams --target gemini --problem "[problem]"
-python3 "$OMG_CLI" ccg --problem "[problem]"
-```
-
-## Output
-Returns `TeamDispatchResult` with:
-- findings
-- action plan
-- evidence metadata
-
-Evidence now includes provider health details (`cli_health`) with:
-- binary availability
-- auth readiness (`auth status` probe)
-- `live_connection` boolean per provider
-
-No external legacy plugin is required.

package/build/lib/commands/OMG:forge.md

@@ -1,103 +0,0 @@
----
-description: "FORGE — Labs-only domain-model prototyping and evaluation orchestration. Routes into the lab pipeline with policy enforcement."
-allowed-tools: Read, Bash
-argument-hint: "[job file path]"
----
-
-# /OMG:forge — Labs-Only Domain Prototyping
-
-> **Availability**: `labs` preset only. Blocked on `safe`, `balanced`, and `interop` presets.
-
-## What It Does
-
-Forge orchestrates domain-model prototyping and evaluation through the existing lab pipeline (`lab/pipeline.py`). It validates jobs against lab policies (`lab/policies.py`), runs the staged pipeline (data → refine → train/distill → evaluate → regression), and emits structured evidence.
-
-Forge does **not**:
-- Train frontier models or perform research-scale model training
-- Bypass lab policy gates (license checks, source validation)
-- Operate outside the `labs` preset boundary
-
-## Policy Enforcement
-
-Every forge job is validated through `lab.policies.validate_job_request()` before pipeline execution:
-
-1. **Dataset license** must be in `ALLOWED_LICENSES`: `apache-2.0`, `mit`, `bsd-3-clause`, `cc-by-4.0`
-2. **Dataset source** must not contain blocked tokens: `unknown`, `leaked`, `stolen`, `unauthorized`, `pirated`
-3. **Model source** must not contain blocked tokens
-4. **Model distillation** must be explicitly allowed (`allow_distill: true`)
-
-Jobs that fail policy checks are blocked with a structured reason before any pipeline stage runs.
-
-## CLI Usage
-
-```bash
-# Run a forge job from a JSON file (domain required)
-python3 scripts/omg.py forge run --job path/to/job.json
-
-# Run with explicit preset (default: labs)
-python3 scripts/omg.py forge run --job path/to/job.json --preset labs
-
-# Run inline with domain-aware job JSON
-python3 scripts/omg.py forge run --preset labs --job-json '{"domain":"vision","dataset":{"name":"vision-agent","license":"apache-2.0","source":"internal-curated"},"base_model":{"name":"distill-base-v1","source":"approved-registry","allow_distill":true},"target_metric":0.8,"simulated_metric":0.9,"specialists":["data-curator","training-architect","simulator-engineer"]}'
-```
-
-## Job File Format
-
-Every forge job **must** include an explicit `domain` field. Valid canonical domains: `vision`, `robotics`, `algorithms`, `health`, `cybersecurity`. The alias `vision-agent` is accepted and canonicalized to `vision`.
-
-```json
-{
-  "domain": "vision",
-  "dataset": {
-    "name": "vision-agent",
-    "license": "apache-2.0",
-    "source": "internal-curated"
-  },
-  "base_model": {
-    "name": "distill-base-v1",
-    "source": "approved-registry",
-    "allow_distill": true
-  },
-  "target_metric": 0.85,
-  "simulated_metric": 0.90,
-  "specialists": ["data-curator", "training-architect", "simulator-engineer"],
-  "evaluation_notes": "Domain adaptation for vision agent"
-}
-```
-
-## Output
-
-Forge returns structured JSON with pipeline results. Domain-aware jobs with specialists also include a `specialist_dispatch` block:
-
-```json
-{
-  "status": "ready",
-  "stage": "complete",
-  "stages": [
-    {"name": "data_prepare", "status": "ok"},
-    {"name": "synthetic_refine", "status": "ok"},
-    {"name": "train_distill", "status": "ok"},
-    {"name": "evaluate", "status": "ok"},
-    {"name": "regression_test", "status": "ok"}
-  ],
-  "published": false,
-  "evaluation_report": {
-    "metric": 0.90,
-    "target_metric": 0.85,
-    "passed": true
-  },
-  "specialist_dispatch": {
-    "status": "ok",
-    "specialists_dispatched": ["data-curator", "training-architect", "simulator-engineer"]
-  }
-}
-```
-
-## Scope Boundary
-
-Forge is a **domain-prototyping** surface, not a model-training research tool. It stays within:
-
-- The lab pipeline's staged execution model
-- Lab policy validation for all dataset and model sources
-- The `labs` preset boundary — no forge operations run without labs enabled
-- Domain-pack contracts (`runtime/domain_packs.py`) for domain-specific prototyping

package/build/lib/commands/OMG:health-check.md

@@ -1,48 +0,0 @@
----
-description: Verify project setup, context health, and tool integration
-allowed-tools: Bash(ls:*), Bash(cat:*), Bash(find:*), Bash(grep:*), Bash(git:*), Bash(which:*), Bash(head:*), Bash(wc:*), Bash(stat:*), Bash(npm run:*), Bash(npx:*), Bash(pnpm run:*), Bash(yarn run:*), Bash(pytest:*), Bash(python3:*), Read, Grep, Glob
----
-
-# /OMG:health-check
-
-Run all checks silently, report only issues:
-
-1. **Profile**: .omg/state/profile.yaml exists and has required fields (name, language, framework)?
-   - FAIL if missing. WARN if key fields empty.
-
-2. **Knowledge**: .omg/knowledge/ has content? Any decision files older than 30 days?
-   - WARN if empty. WARN if stale files (suggest review).
-
-3. **Quality Gate**: .omg/state/quality-gate.json exists and configured commands are runnable?
-   - Check each command with `which` or `--version` where possible.
-   - If execution is restricted, report WARN (not FAIL) with "cannot verify — restricted permissions".
-   - If command found but fails: report FAIL with exit code.
-
-4. **Secrets**: No .env committed to git? No API keys in tracked files?
-   - `git ls-files | grep -i '\.env'` (exclude .env.example/.sample/.template).
-   - FAIL if real .env files tracked.
-
-5. **Tools**: Hooks installed? OMG team aliases available? MCP servers listed?
-   - Check ~/.claude/hooks/.omg-version exists.
-   - Check if Claude sees OMG through plugin-managed skills/surfaces rather than legacy `~/.claude/commands/` files:
-     - `~/.claude/plugins/known_marketplaces.json` contains `omg`
-     - `~/.claude/plugins/cache/omg/omg/<version>/.claude-plugin/plugin.json` exists
-     - WARN if only legacy command files exist without the plugin-managed surface
-   - List MCP servers from .mcp.json (informational).
-
-6. **Failures**: Stale failure patterns in failure-tracker.json?
-   - WARN if any pattern older than 24h. Suggest `/OMG:handoff` or manual reset.
-
-7. **Context Size**: Estimate total injection from session-start + prompt-enhancer.
-   - Sum: profile.yaml lines + working-memory.md lines + handoff.md lines.
-   - WARN if >80 lines total.
-
-**Report format:**
-```
-PASS [N] | WARN [N] | FAIL [N]
-
-  FAIL profile: .omg/state/profile.yaml not found → run /OMG:init
-  WARN quality: prettier not found → install or remove from quality-gate.json
-  PASS secrets: no .env files tracked
-  ...
-```

package/build/lib/commands/OMG:init.md

@@ -1,134 +0,0 @@
----
-description: "Unified initializer — auto-detects: project setup (if no .omg/state), domain scaffolding (if argument given), or health check."
-allowed-tools: Read, Write, Edit, MultiEdit, Bash(mkdir:*), Bash(cat:*), Bash(find:*), Bash(ls:*), Bash(head:*), Bash(grep:*), Bash(tree:*), Bash(node:*), Bash(python*:*), Bash(tee:*), Grep, Glob
-argument-hint: "[optional: domain name like 'payment', or 'check' for health check]"
----
-
-# /OMG:init — Unified Project & Domain Initializer
-
-## Auto-Detection Logic
-
-```
-if argument is a domain name (e.g. "payment", "user-profile"):
-  → DOMAIN INIT (create new domain from existing patterns)
-elif .omg/state directory does not exist:
-  → PROJECT INIT (first-time project setup)
-elif .omg/state/profile.yaml exists:
-  → HEALTH CHECK (verify everything works, offer upgrades)
-```
-
----
-
-## MODE A: PROJECT INIT (no .omg/state found)
-
-### Step 1: Create .omg/state/profile.yaml (MOST IMPORTANT)
-Detect from code. Ask user for anything undetectable.
-
-```yaml
-# .omg/state/profile.yaml — injected every session (keep under 20 lines)
-name: "[from package.json/Cargo.toml/pyproject.toml]"
-description: "[1 sentence]"
-repo: "[from git remote -v]"
-
-language: "[detect]"
-framework: "[detect]"
-database: "[detect or ask]"
-infra: "[detect from Dockerfile/terraform/etc]"
-key_deps: "[top 5]"
-
-conventions:
-  naming: "[detect: camelCase/snake_case]"
-  test_cmd: "[detect: npm test/pytest/cargo test]"
-  lint_cmd: "[detect: eslint/ruff/clippy]"
-
-ai_behavior:
-  communication: "[ask user: language preference]"
-  when_stuck: "Ask user after 2 failed attempts"
-  testing: "User-journey focused, not boilerplate"
-```
-
-### Step 2: Create knowledge structure + OMG v1 contract dirs
-```
-mkdir -p .omg/state/ledger .omg/knowledge/decisions .omg/knowledge/patterns .omg/knowledge/rules
-mkdir -p .omg/trust .omg/evidence .omg/shadow .omg/migrations
-```
-
-Copy OMG v1 templates when missing:
-- `.omg/idea.yml`
-- `.omg/policy.yaml`
-- `.omg/runtime.yaml`
-
-### Step 3: Auto-detect quality gate
-```json
-// .omg/state/quality-gate.json — only include commands that exist
-{
-  "format": "[detect: prettier/black/gofmt or null]",
-  "lint": "[detect: eslint/ruff/clippy or null]",
-  "typecheck": "[detect: tsc/mypy or null]",
-  "test": "[detect: npm test/pytest/cargo test or null]"
-}
-```
-
-### Step 4: Copy relevant contextual rules
-Based on detected project type, copy relevant rules from templates:
-- Web project → security-domains.md, code-hygiene.md
-- Backend → infra-safety.md, dependency-safety.md
-- DDD project → ddd-sdd.md, outside-in.md
-
-### Step 5: Verify
-Run `/OMG:health-check` to confirm setup.
-
----
-
-## MODE B: DOMAIN INIT (argument = domain name)
-
-### Step 1: Find Reference Pattern
-```bash
-find . -type f -name "*.ts" -o -name "*.py" | sed 's|/[^/]*$||' | sort | uniq -c | sort -rn | head -10
-```
-Read the most complete existing domain. Extract:
-- Directory structure (routes, services, models, tests)
-- Naming conventions, error handling, data flow patterns
-
-### Step 2: Define the New Domain
-Ask the user:
-- "What entities does [domain] have?"
-- "What actions can be performed?"
-- "What external services does it talk to?"
-- "What are the business rules?"
-
-### Step 3: Generate Domain Structure
-Match the reference pattern EXACTLY. Create:
-```
-src/[domain]/
-  ├── [domain].model.ts
-  ├── [domain].service.ts
-  ├── [domain].repository.ts
-  ├── [domain].controller.ts (or routes)
-  ├── [domain].types.ts
-  └── __tests__/
-      └── [domain].service.test.ts
-```
-
-### Step 4: Document the Pattern
-Save to `.omg/knowledge/patterns/[domain]-pattern.md`
-
----
-
-## MODE C: HEALTH CHECK (already initialized)
-
-Run `/OMG:health-check` and additionally:
-- Verify profile.yaml is up-to-date with current project state
-- Check if new contextual rules should be added
-- Offer to update quality-gate.json if tools changed
-
----
-
-## File Write Method
-Use `Write` tool first. If it fails (file exists), fall back to:
-```bash
-cat > .omg/state/profile.yaml << 'EOF'
-[content]
-EOF
-```
-Always READ the file after writing to confirm.

package/build/lib/commands/OMG:issue.md

@@ -1,56 +0,0 @@
----
-description: "Active red-team diagnostics and simulation surface for ranked issue triage."
-allowed-tools: Read, Grep, Glob, Bash(python3 scripts/omg.py issue:*), Bash(pytest:*)
-argument-hint: "[optional: --surfaces <csv> --simulate-surface <name> --simulate-scenario <name>]"
----
-
-# /OMG:issue
-
-Run active, read-only diagnostics across live and governed OMG surfaces, then emit ranked machine-readable issues.
-
-## Command Roles
-
-- `/OMG:issue` is the diagnostic and red-team simulation surface.
-- `omg fix --issue` remains the issue-driven fix surface.
-- Both share the same backend: `runtime/issue_surface.py`.
-- `/OMG:issue` does not mutate targets.
-
-## Surfaces Scanned
-
-- `live_session`
-- `forge_runs`
-- `hooks`
-- `skills`
-- `mcps`
-- `plugin_interop`
-- `governed_tools`
-- `domain_pipelines`
-
-## Severity and Approval
-
-- Severities: `critical`, `high`, `medium`, `low`, `info`
-- High/critical issues must declare signed-approval requirements before fix execution.
-- Output includes fix guidance plus evidence links for replay and audit.
-
-## Usage
-
-```text
-/OMG:issue
-/OMG:issue --surfaces plugin_interop,governed_tools
-/OMG:issue --simulate-surface hooks --simulate-scenario "delete protected lock"
-```
-
-## Backend Output
-
-- Evidence file: `.omg/evidence/issues/<run_id>.json`
-- Report schema: `IssueReport`
-- Each issue includes:
-  - `id`
-  - `severity`
-  - `surface`
-  - `title`
-  - `description`
-  - `fix_guidance`
-  - `evidence_links`
-  - `approval_required`
-  - `approval_reason`

package/build/lib/commands/OMG:mode.md

@@ -1,44 +0,0 @@
----
-description: "Set canonical mode (chill/focused/exploratory) for the current session."
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: "[chill|focused|exploratory|clear]"
----
-
-# /OMG:mode — Set Canonical Mode
-
-Switch Claude's operating mode for the current session.
-
-## Usage
-
-```
-/OMG:mode chill        # Focus on low-intensity, conservative progress
-/OMG:mode focused      # Focus on coding and execution
-/OMG:mode exploratory  # Focus on discovery and synthesis
-/OMG:mode clear        # Clear current mode (return to default)
-```
-
-## What It Does
-
-1. Writes `.omg/state/mode.txt` with the selected mode name
-2. The `prompt-enhancer` hook reads this file and injects `@mode:` context on every subsequent prompt
-3. The corresponding rule file (`rules/contextual/{mode}-mode.md`) activates
-
-## Canonical Modes
-
-| Mode | Focus | When to Use |
-|------|-------|-------------|
-| `chill` | Conservative execution pace | Low-risk maintenance and steady progress |
-| `focused` | Implementation-forward flow | Active feature work with verification |
-| `exploratory` | Discovery, synthesis, and mapping | Unknown domains and research-heavy sessions |
-
-## Example
-
-```
-/OMG:mode focused
-→ Sets mode to focused
-→ Every prompt now gets: @mode:FOCUSED — Implement deliberately with tight verification loops.
-
-/OMG:mode clear
-→ Removes .omg/state/mode.txt
-→ Mode injection stops
-```

package/build/lib/commands/OMG:playwright.md

@@ -1,17 +0,0 @@
----
-description: "Compatibility alias for /OMG:browser."
-allowed-tools: Read, Grep, Glob
-argument-hint: "<goal or browser task>"
----
-
-# /OMG:playwright
-
-`/OMG:playwright` is an alias for `/OMG:browser`.
-
-Use the canonical `/OMG:browser` command for public docs, setup guidance, and future OMG browser workflows.
-
-## Compatibility Notes
-
-- This alias exists so Playwright-oriented users can find the browser surface quickly.
-- Runtime behavior should resolve to the same OMG browser path as `/OMG:browser`.
-- OMG still uses upstream `playwright-cli` under the hood.

package/build/lib/commands/OMG:preflight.md

@@ -1,26 +0,0 @@
----
-description: "Structured OMG router that classifies risk, selects the right route, and emits an execution/evidence plan."
-allowed-tools: Read, Grep, Glob, Bash(python3:*), Bash(rg:*)
-argument-hint: "\"<goal>\""
----
-
-# /OMG:preflight — Structured Router
-
-Use `preflight` when the goal is clear but the safest execution route is not.
-
-## Output Contract
-
-- restated goal
-- task class
-- risk class
-- recommended route
-- required tools and MCPs
-- missing constraints
-- evidence requirements
-
-## Typical Routes
-
-- `security-check` for security-sensitive or trust-bound work
-- `api-twin` for contract replay and offline integration work
-- `crazy` for parallel execution
-- `teams` for targeted agent dispatch

package/build/lib/commands/OMG:preset.md

@@ -1,49 +0,0 @@
----
-description: "Inspect or apply the canonical OMG preset for the current project."
-allowed-tools: Read, Write, Edit, Bash(python*:*), Bash(ls:*), Bash(grep:*)
-argument-hint: "[safe|balanced|interop|labs|buffet|plugins-first]"
----
-
-# /OMG:preset
-
-Inspect or apply the canonical OMG preset for the current project.
-
-## Usage
-
-```text
-/OMG:preset
-/OMG:preset safe
-/OMG:preset balanced
-/OMG:preset interop
-/OMG:preset labs
-/OMG:preset buffet
-/OMG:preset plugins-first
-```
-
-## Presets
-
-- `safe`: minimum managed OMG surface
-- `balanced`: safe defaults plus extra productivity MCPs
-- `interop`: coexistence and shared-memory oriented setup
-- `labs`: enables experimental and browser-heavy surfaces
-- `buffet`: full preset; enables every managed preset flag
-- `plugins-first`: compatibility alias for `interop`
-
-## Behavior
-
-When a preset is supplied:
-
-1. Resolve the requested preset through `runtime.adoption.resolve_preset`.
-2. Persist the canonical preset via `hooks.setup_wizard.set_preferences(...)`.
-3. Update project preset metadata in `.omg/state/cli-config.yaml` and project `settings.json` when present.
-4. Report the resolved preset, enabled features, and selected MCP defaults.
-
-When no preset is supplied:
-
-1. Read the current project preset from `.omg/state/cli-config.yaml` or project `settings.json`.
-2. Report the resolved preset and its managed feature flags.
-
-## Notes
-
-- `buffet` is the top-tier preset and should be treated as a superset of `labs`.
-- If the host install also needs updating, rerun `/OMG:setup` with the same preset so the host-level command and MCP surfaces stay aligned.

package/build/lib/commands/OMG:profile-review.md

@@ -1,58 +0,0 @@
----
-description: Review governed profile state — preferences, confirmations, decay, and provenance
-allowed-tools: Bash(python3:*), Read, Grep, Glob
----
-
-# /OMG:profile-review
-
-Read-only inspection of the governed user profile. Reports active style and
-safety preferences, pending destructive confirmations, stale/decay candidates,
-and provenance summaries.
-
-**This command never mutates `profile.yaml`.**
-
-## Usage
-
-```
-python3 scripts/omg.py profile-review [--format json|text]
-```
-
-- `--format json` — machine-readable JSON (default)
-- `--format text` — human-readable summary
-
-## JSON output shape
-
-```json
-{
-  "schema": "ProfileReview",
-  "style": [ { "field": "...", "value": "...", "confirmation_state": "...", ... } ],
-  "safety": [ { "field": "...", "value": "...", "confirmation_state": "...", ... } ],
-  "pending_confirmations": [ { "field": "...", "value": "...", "section": "..." } ],
-  "decay_candidates": [ { "field": "...", "decay_score": 0.3, ... } ],
-  "provenance_summary": [ { "run_id": "...", "source": "...", "field": "...", "updated_at": "..." } ],
-  "profile_version": "sha256..."
-}
-```
-
-## Auto-action routing
-
-Session health auto-actions may route to this command when governed profile
-state becomes risky. When `evaluate_auto_actions()` in `runtime/session_health.py`
-returns `require-review`, the agent is directed here to inspect risk before
-proceeding. This command remains strictly read-only — it never mutates
-`profile.yaml` or applies autonomous fixes.
-
-Bounded auto-actions that may trigger this route:
-
-- **pause** — session blocked due to high contamination or overthinking; destructive preferences escalate to require-review
-- **require-review** — profile risk detected (destructive preferences or pending confirmations)
-- **warn** — verification errors combined with profile risk
-
-## Report sections
-
-1. **Style preferences** — governed style entries with source, learned_at, decay metadata
-2. **Safety preferences** — governed safety entries (decay-immune)
-3. **Pending confirmations** — entries marked `pending_confirmation` (destructive signals awaiting user approval)
-4. **Decay candidates** — style entries with `decay_score > 0` that may be stale
-5. **Provenance summary** — recent profile update events from `profile_provenance.recent_updates`
-6. **Risk assessment** — overall risk level, destructive entries, and review requirement

package/build/lib/commands/OMG:project-init.md

@@ -1,11 +0,0 @@
----
-description: "Alias for /OMG:init (project setup mode). Use /OMG:init instead."
-allowed-tools: Read, Write, Edit, MultiEdit, Bash(mkdir:*), Bash(cat:*), Bash(find:*), Bash(ls:*), Bash(head:*), Bash(grep:*), Bash(tree:*), Bash(node:*), Bash(python*:*), Bash(tee:*), Grep, Glob
-argument-hint: "[optional: project description]"
----
-
-# /OMG:project-init → Redirects to /OMG:init
-
-This command is now part of `/OMG:init`. Execute `/OMG:init` (project setup mode).
-
-Follow the **MODE A: PROJECT INIT** instructions in /OMG:init.

package/build/lib/commands/OMG:ralph-start.md

@@ -1,43 +0,0 @@
----
-description: "Start Ralph autonomous loop — continues working until all tasks complete or max iterations reached."
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob
-argument-hint: "[goal description]"
----
-
-# /OMG:ralph-start — Start Ralph Autonomous Loop
-
-## Purpose
-Starts a Ralph loop that autonomously continues working until all tasks in the goal are complete or max iterations reached.
-
-## Usage
-```
-/OMG:ralph-start [goal description]
-```
-
-## How it Works
-1. Ask the user for a goal description if not provided
-2. Create `.omg/state/ralph-loop.json` with:
-   - `active: true`
-   - `iteration: 0`
-   - `max_iterations: 50`
-   - `original_prompt: [goal]`
-   - `started_at: [ISO8601 timestamp]`
-   - `checklist_path: ".omg/state/_checklist.md"` (if exists)
-3. Confirm: "Ralph loop started. Will continue working on: [goal]"
-
-## State File Format
-```json
-{
-  "active": true,
-  "iteration": 0,
-  "max_iterations": 50,
-  "original_prompt": "fix all failing tests",
-  "started_at": "2026-02-28T10:00:00Z",
-  "checklist_path": ".omg/state/_checklist.md"
-}
-```
-
-## Stop Condition
-- Reaches max_iterations (50 by default)
-- User runs `/OMG:ralph-stop`
-- User deletes `.omg/state/ralph-loop.json`

package/build/lib/commands/OMG:ralph-stop.md

@@ -1,23 +0,0 @@
----
-description: "Stop Ralph autonomous loop — deactivates the state file."
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: ""
----
-
-# /OMG:ralph-stop — Stop Ralph Autonomous Loop
-
-## Purpose
-Stops an active Ralph loop by deactivating the state file.
-
-## Usage
-```
-/OMG:ralph-stop
-```
-
-## How it Works
-1. Read `.omg/state/ralph-loop.json`
-2. Set `active: false` in the state file (preserve iteration count for review)
-3. Report: "Ralph loop stopped after N iterations. Gomg was: [original_prompt]"
-
-## If No Active Loop
-Report: "No active Ralph loop found. Nothing to stop."