Skip to content

The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.

chore: sync Codex marketplace v4.18.0

github-actions[bot]5e1d7ce193b1
diff --git a/plugins/omo/.codex-plugin/plugin.json b/plugins/omo/.codex-plugin/plugin.json
index 7bc9d976..09ccc190 100644
--- a/plugins/omo/.codex-plugin/plugin.json
+++ b/plugins/omo/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "omo",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "One Codex plugin namespace for Yeongyu's local Codex components.",
"author": {
"name": "Yeongyu Kim",
diff --git a/plugins/omo/components/bootstrap/hooks/hooks.json b/plugins/omo/components/bootstrap/hooks/hooks.json
index c3876fa7..d6c40efb 100644
--- a/plugins/omo/components/bootstrap/hooks/hooks.json
+++ b/plugins/omo/components/bootstrap/hooks/hooks.json
@@ -8,7 +8,7 @@
"command": "node \"${PLUGIN_ROOT}/components/bootstrap/dist/cli.js\" hook session-start",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\bootstrap.ps1\"",
"timeout": 30,
- "statusMessage": "(OmO 4.17.1) Checking Bootstrap Provisioning"
+ "statusMessage": "(OmO 4.18.0) Checking Bootstrap Provisioning"
}
]
}
diff --git a/plugins/omo/components/bootstrap/package.json b/plugins/omo/components/bootstrap/package.json
index afb8b00a..1b1fd1ce 100644
--- a/plugins/omo/components/bootstrap/package.json
+++ b/plugins/omo/components/bootstrap/package.json
@@ -1,6 +1,6 @@
{
"name": "@sisyphuslabs/codex-bootstrap",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex SessionStart bootstrap component that provisions LazyCodex runtime dependencies from a detached worker.",
"type": "module",
"private": true,
diff --git a/plugins/omo/components/codegraph/package.json b/plugins/omo/components/codegraph/package.json
index 99afb90c..063b3daf 100644
--- a/plugins/omo/components/codegraph/package.json
+++ b/plugins/omo/components/codegraph/package.json
@@ -1,6 +1,6 @@
{
"name": "@sisyphuslabs/codex-codegraph",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex plugin MCP wrapper for CodeGraph.",
"type": "module",
"private": true,
diff --git a/plugins/omo/components/comment-checker/hooks/hooks.json b/plugins/omo/components/comment-checker/hooks/hooks.json
index 30765214..08c7102e 100644
--- a/plugins/omo/components/comment-checker/hooks/hooks.json
+++ b/plugins/omo/components/comment-checker/hooks/hooks.json
@@ -8,7 +8,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
"timeout": 30,
- "statusMessage": "(OmO 4.17.1) Checking Comments"
+ "statusMessage": "(OmO 4.18.0) Checking Comments"
}
]
}
diff --git a/plugins/omo/components/comment-checker/package.json b/plugins/omo/components/comment-checker/package.json
index 418f3fb9..dfd7f96e 100644
--- a/plugins/omo/components/comment-checker/package.json
+++ b/plugins/omo/components/comment-checker/package.json
@@ -1,6 +1,6 @@
{
"name": "@code-yeongyu/codex-comment-checker",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex plugin that runs comment-checker after edit-like PostToolUse hooks.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/components/git-bash/hooks/hooks.json b/plugins/omo/components/git-bash/hooks/hooks.json
index 46aa818b..df99aee3 100644
--- a/plugins/omo/components/git-bash/hooks/hooks.json
+++ b/plugins/omo/components/git-bash/hooks/hooks.json
@@ -8,7 +8,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook pre-tool-use",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Recommending Git Bash MCP"
+ "statusMessage": "(OmO 4.18.0) Recommending Git Bash MCP"
}
]
}
@@ -20,7 +20,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-compact",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Resetting Git Bash MCP Reminder"
+ "statusMessage": "(OmO 4.18.0) Resetting Git Bash MCP Reminder"
}
]
}
diff --git a/plugins/omo/components/git-bash/package.json b/plugins/omo/components/git-bash/package.json
index 6b90802a..7fcc10b0 100644
--- a/plugins/omo/components/git-bash/package.json
+++ b/plugins/omo/components/git-bash/package.json
@@ -1,6 +1,6 @@
{
"name": "@sisyphuslabs/codex-git-bash-hook",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex hook component that reminds Windows sessions to prefer the OMO git_bash MCP.",
"type": "module",
"private": true,
diff --git a/plugins/omo/components/lazycodex-executor-verify/hooks/hooks.json b/plugins/omo/components/lazycodex-executor-verify/hooks/hooks.json
index 11d6a856..347fd177 100644
--- a/plugins/omo/components/lazycodex-executor-verify/hooks/hooks.json
+++ b/plugins/omo/components/lazycodex-executor-verify/hooks/hooks.json
@@ -8,7 +8,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/lazycodex-executor-verify/dist/cli.js\" hook subagent-stop",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Verifying LazyCodex Executor Evidence"
+ "statusMessage": "(OmO 4.18.0) Verifying LazyCodex Executor Evidence"
}
]
}
diff --git a/plugins/omo/components/lazycodex-executor-verify/package.json b/plugins/omo/components/lazycodex-executor-verify/package.json
index cd0cd933..78e01938 100644
--- a/plugins/omo/components/lazycodex-executor-verify/package.json
+++ b/plugins/omo/components/lazycodex-executor-verify/package.json
@@ -1,6 +1,6 @@
{
"name": "@code-yeongyu/codex-lazycodex-executor-verify",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex SubagentStop evidence verifier for LazyCodex executor completions.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/components/lsp/hooks/hooks.json b/plugins/omo/components/lsp/hooks/hooks.json
index 2de86a18..677a74b0 100644
--- a/plugins/omo/components/lsp/hooks/hooks.json
+++ b/plugins/omo/components/lsp/hooks/hooks.json
@@ -8,7 +8,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
"timeout": 60,
- "statusMessage": "(OmO 4.17.1) Checking LSP Diagnostics"
+ "statusMessage": "(OmO 4.18.0) Checking LSP Diagnostics"
}
]
}
@@ -21,7 +21,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-compact",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Resetting LSP Diagnostics Cache"
+ "statusMessage": "(OmO 4.18.0) Resetting LSP Diagnostics Cache"
}
]
}
diff --git a/plugins/omo/components/lsp/package.json b/plugins/omo/components/lsp/package.json
index 4cc92412..074c36a8 100644
--- a/plugins/omo/components/lsp/package.json
+++ b/plugins/omo/components/lsp/package.json
@@ -1,6 +1,6 @@
{
"name": "@code-yeongyu/codex-lsp",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex plugin that exposes Language Server Protocol tools and post-edit diagnostics.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/components/rules/bundled-rules/hephaestus/gpt-5.6.md b/plugins/omo/components/rules/bundled-rules/hephaestus/gpt-5.6.md
index 8df931ae..da661ca9 100644
--- a/plugins/omo/components/rules/bundled-rules/hephaestus/gpt-5.6.md
+++ b/plugins/omo/components/rules/bundled-rules/hephaestus/gpt-5.6.md
@@ -9,7 +9,7 @@ You are Hephaestus, an autonomous deep worker based on GPT-5.6. You and the user
User instructions override these defaults; newer instructions override older. Safety and type-safety constraints never yield.
-Implement, don't propose. "How does X work?" means understand, then fix; "Why is A broken?" means diagnose, then fix; a message is answer-only when the user says so ("just explain", "don't change anything"). State your read in one line before acting: "I detect [intent type] - [reason]. [What I'm doing now]." That line commits you to finish the named work this turn.
+Implement, don't propose. "How does X work?" means understand, then fix; "Why is A broken?" means diagnose, then fix; a message is answer-only when the user says so ("just explain", "don't change anything"). State your read in one line before acting: "I detect [intent type] - [reason]. [What I'm doing now]. I'll stop right away when [the exact, observable condition that ends this turn]." That line commits you to finish the named work this turn, and the stop condition you declared is BINDING - the instant it is met, stop (see Stop Goal).
Requests to answer, review, diagnose, or plan: inspect and report. Requests to change, build, or fix: implement and run non-destructive validation without asking. Confirm only destructive actions, external writes, or material scope expansion; resolve other blockers from context and reasonable assumptions.
@@ -29,13 +29,15 @@ Implement surgically, matching codebase style (naming, indentation, imports, err
# Subagents
-Read-only Codex subagent roles live in `CODEX_HOME/agents/`. Spawn: `multi_agent_v1.spawn_agent({"message":"TASK: act as a <role>. ...","fork_context":false})`. If your tool list instead has a flat `spawn_agent` with a required `task_name` (`multi_agent_v2`): `spawn_agent({"task_name":"<lowercase_digits_underscores>","message":"TASK: act as a <role>. ...","fork_turns":"none"})` - finished agents end on their own; `wait_agent` takes only `timeout_ms`.
+Read-only Codex subagent roles live in `CODEX_HOME/agents/`. Spawn: `multi_agent_v1.spawn_agent({"message":"TASK: act as a <role>. GOAL: ... STOP WHEN: ... EVIDENCE: ...","fork_context":false})`. If your tool list instead has a flat `spawn_agent` with a required `task_name` (`multi_agent_v2`): `spawn_agent({"task_name":"<lowercase_digits_underscores>","message":"TASK: act as a <role>. GOAL: ... STOP WHEN: ... EVIDENCE: ...","fork_turns":"none"})` - finished agents end on their own; `wait_agent` takes only `timeout_ms`.
- `explorer` - codebase search
- `librarian` - external docs, OSS code, API contracts
- `plan` - planning when design is still open after discovery; never for a known checklist or for work being delegated onward
- `lazycodex-gate-reviewer` - final verification of a finished change
+Every spawn message MUST fill all three labels - **GOAL** (the one outcome that makes the child done), **STOP WHEN** (the exact, observable condition that ends its run; the child stops the moment it holds, exactly like your own intent line), **EVIDENCE** (what the child returns so you can SEE, not trust, that the condition held). A spawn missing any label is a defect: the child wanders past its goal, overworks, or reports "done" you cannot verify. Judge a child by its returned EVIDENCE against its STOP WHEN, never by its self-report. Fill the labels with outcomes and binding constraints, never mechanisms: name the behavior the child's work must achieve or distinguish, not a copy-ready assertion string, prompt fragment, expected pass/assert count, or "marker used by current tests" — a prescribed mechanism that is wrong gets implemented faithfully and the defect ships behind a green suite.
+
Spawn in parallel for independent investigations; do non-overlapping prep while they run, integrate on return. Never duplicate a running search or poll without a completion signal; post brief status updates while children run (active subagent count, latest `WORKING:` phase).
# Manual QA Gate
@@ -68,16 +70,16 @@ On a multi-step task, open with one or two visible sentences naming the first st
Final message: lead with the result, group by outcome, no conversational openers. Keep all required facts, decisions, caveats, and next steps; trim introductions, repetition, and generic reassurance first. For review requests, findings come first, ordered by severity with file references; if none, say so and name residual risks. No emojis or em dashes unless requested. Never output broken inline citations like `【F:README.md†L5-L14】` - they break the CLI.
-# Success Criteria and Stop Rules
+# Stop Goal
-Done when ALL of:
+Your STOP GOAL — the turn is over the moment ALL of these hold:
- Every requested behavior implemented - no partial delivery.
- Diagnostics clean on changed files; build exits 0; tests pass or pre-existing failures are named.
- The artifact passed the Manual QA Gate this turn.
- The final message reports what you did, verified, could not verify (and why), and pre-existing issues left alone.
-When you think you are done: re-read the request and your intent line, re-run verification, then report. Until all are true, keep going - through failed tool calls, long turns, and the urge to hand back a draft.
+Until the stop goal holds, keep going - through failed tool calls, long turns, and the urge to hand back a draft. The moment it holds: re-read the request and your intent line once, confirm each item against evidence already captured, confirm the stop condition you declared in your intent line is met, deliver the final message, and STOP. STOPPING IS MANDATORY AND IMMEDIATE - not a judgment call, not an invitation for one more check. No extra validation loop, no re-polish, no bonus refactor, no drive-by cleanup. Every action past the stop goal is a defect, not diligence.
Hard invariants, regardless of pressure to ship:
diff --git a/plugins/omo/components/rules/hooks/hooks.json b/plugins/omo/components/rules/hooks/hooks.json
index 67fab62b..ab8a0a1e 100644
--- a/plugins/omo/components/rules/hooks/hooks.json
+++ b/plugins/omo/components/rules/hooks/hooks.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook session-start",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Loading Project Rules"
+ "statusMessage": "(OmO 4.18.0) Loading Project Rules"
}
]
}
@@ -19,7 +19,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook user-prompt-submit",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Loading Project Rules"
+ "statusMessage": "(OmO 4.18.0) Loading Project Rules"
}
]
}
@@ -32,7 +32,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Matching Project Rules"
+ "statusMessage": "(OmO 4.18.0) Matching Project Rules"
}
]
}
@@ -45,7 +45,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-compact",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Resetting Project Rule Cache"
+ "statusMessage": "(OmO 4.18.0) Resetting Project Rule Cache"
}
]
}
diff --git a/plugins/omo/components/rules/package.json b/plugins/omo/components/rules/package.json
index c1d365ae..b41a94c1 100644
--- a/plugins/omo/components/rules/package.json
+++ b/plugins/omo/components/rules/package.json
@@ -1,6 +1,6 @@
{
"name": "@code-yeongyu/codex-rules",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex plugin that injects project rule files into model context through lifecycle hooks.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/components/start-work-continuation/hooks/hooks.json b/plugins/omo/components/start-work-continuation/hooks/hooks.json
index 4558e53b..20d5df9e 100644
--- a/plugins/omo/components/start-work-continuation/hooks/hooks.json
+++ b/plugins/omo/components/start-work-continuation/hooks/hooks.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/start-work-continuation/dist/cli.js\" hook stop",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Start-Work Continuation"
+ "statusMessage": "(OmO 4.18.0) Checking Start-Work Continuation"
}
]
}
@@ -19,7 +19,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/start-work-continuation/dist/cli.js\" hook subagent-stop",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Start-Work Continuation"
+ "statusMessage": "(OmO 4.18.0) Checking Start-Work Continuation"
}
]
}
diff --git a/plugins/omo/components/start-work-continuation/package.json b/plugins/omo/components/start-work-continuation/package.json
index b4bd8acf..9133bd9d 100644
--- a/plugins/omo/components/start-work-continuation/package.json
+++ b/plugins/omo/components/start-work-continuation/package.json
@@ -1,6 +1,6 @@
{
"name": "@code-yeongyu/codex-start-work-continuation",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex Stop hook continuation injector for omo-codex start-work plans.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/components/teammode/hooks/hooks.json b/plugins/omo/components/teammode/hooks/hooks.json
index 50b6a85a..28fb230e 100644
--- a/plugins/omo/components/teammode/hooks/hooks.json
+++ b/plugins/omo/components/teammode/hooks/hooks.json
@@ -8,7 +8,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Thread Title Hygiene"
+ "statusMessage": "(OmO 4.18.0) Checking Thread Title Hygiene"
}
]
}
diff --git a/plugins/omo/components/teammode/package.json b/plugins/omo/components/teammode/package.json
index 1c21ffaa..98c0ee7f 100644
--- a/plugins/omo/components/teammode/package.json
+++ b/plugins/omo/components/teammode/package.json
@@ -1,6 +1,6 @@
{
"name": "@sisyphuslabs/codex-teammode",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex team-mode hook component that keeps background thread titles descriptive after create_thread.",
"type": "module",
"private": true,
diff --git a/plugins/omo/components/telemetry/hooks/hooks.json b/plugins/omo/components/telemetry/hooks/hooks.json
index 6a2726cf..afdb0b2b 100644
--- a/plugins/omo/components/telemetry/hooks/hooks.json
+++ b/plugins/omo/components/telemetry/hooks/hooks.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook session-start",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Recording Session Telemetry"
+ "statusMessage": "(OmO 4.18.0) Recording Session Telemetry"
}
]
}
diff --git a/plugins/omo/components/telemetry/package.json b/plugins/omo/components/telemetry/package.json
index 1abb7d60..cf1ec03a 100644
--- a/plugins/omo/components/telemetry/package.json
+++ b/plugins/omo/components/telemetry/package.json
@@ -1,6 +1,6 @@
{
"name": "@code-yeongyu/codex-telemetry",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex plugin component that emits omo-codex anonymous daily-active telemetry on SessionStart.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/components/ultrawork/directive.md b/plugins/omo/components/ultrawork/directive.md
index d837e70a..260bbaf2 100644
--- a/plugins/omo/components/ultrawork/directive.md
+++ b/plugins/omo/components/ultrawork/directive.md
@@ -121,9 +121,13 @@ are delegating never justify a planner: plan directly in the notepad.
Never spawn `plan` before the discovery wave has returned.
## 1. Create the goal with binding success criteria
-Call `create_goal` (or open your reply with a `# Goal` block treated as
-binding) using exactly `objective`. Do not include `status`. Goals are
-unlimited; never invent a numeric budget or limit.
+You MUST register the goal with the `create_goal` tool — NOT prose,
+NOT the notepad, NOT the plan: the registered goal is the binding
+contract for the whole run, and skipping it is a defect. Call it with
+exactly `objective`; do not include `status`. Only when no goal tool
+exists on this surface, open your reply with a `# Goal` block treated
+as binding. Goals are unlimited; never invent a numeric budget or
+limit.
The criteria MUST list, upfront:
- The user-visible deliverable in one line, and the tier with its
justification.
@@ -136,6 +140,9 @@ The criteria MUST list, upfront:
- For each criterion, the failing-first proof (test id or scenario)
that will be captured RED BEFORE the implementation and GREEN after.
Evidence added after the green code does NOT satisfy this.
+- WHEN TO STOP, in one line: "I'll stop right away when <the exact
+ observable state that ends this run>". The Stop rules bind to this
+ line — the moment it holds, you stop.
These scenarios are the contract. You are not done until every one of
them PASSES with its evidence captured.
@@ -236,6 +243,18 @@ Until every success criterion PASSES with its evidence captured:
scenario captured failing when no test seam exists. It must fail
for the RIGHT reason (not a syntax error, not a missing import).
Paste RED output into the notepad. No production code yet.
+ TEST-ONLY TARGET (regression coverage for behavior that is already
+ correct): there is no natural RED and no production change to make
+ — this is the sole exception to the production-RED/GREEN steps.
+ Substitute a mutation proof: temporarily force the exact regression
+ each new assertion names (revert the fix commit or break the seam,
+ never committed), capture the assertion failing, then revert the
+ mutation and capture GREEN. An assertion that stays green under its
+ mutation is not coverage — fix the fixture (a value equal to the
+ default it must override proves nothing) or assert the artifact the
+ criterion names, never an expected value re-derived from the output
+ under test. Reverting the probe IS the GREEN; skip step 3's
+ production change for a TEST-ONLY task and go to step 4.
PROSE TARGET (prompt, SKILL.md, rule, markdown): the wording is
NOT the behavior — never pin sentences, phrase presence/absence,
or word/char counts. PIN only a machine-consumed value (parsed
@@ -244,7 +263,8 @@ Until every success criterion PASSES with its evidence captured:
two shipped copies. A pure-prose change with no machine consumer
has NO seam: ship it on review + QA-by-read, NO test — a text grep
is pretend-coverage, not RED proof.
-3. GREEN: write the SMALLEST production change that flips RED→GREEN.
+3. GREEN (skip for TEST-ONLY — reverting the mutation is GREEN): write
+ the SMALLEST production change that flips RED→GREEN.
Before GREEN work that depends on external review, PR, issue, or
branch state, refresh current branch/PR/issue state and preserve existing ordering/policy;
separate compatibility detection from policy changes unless the goal
@@ -382,10 +402,11 @@ message + present for approval.
revert, capture the proof failing, then redo the change. Exempt
only: pure formatting, comment-only edits, dependency bumps with no
behavior delta, rename-only moves — justify each in `## Findings`.
-- A test that mirrors its implementation — asserting mocks were
- called, pinning a constant, or unable to fail under any plausible
- regression — is NOT evidence. Prefer a real-surface proof with no
- new test over a tautological test.
+- A test that cannot fail for the regression it names is NOT
+ evidence: mock-call assertions, pinned constants, a fixture equal
+ to the default it must override, an expected value re-derived from
+ the output under test. Prefer a real-surface proof with no new
+ test over a tautological one.
- Refactors: characterization tests pinning current observable
behavior FIRST, green against the old code, green throughout.
- Smallest correct change. No drive-by refactors.
@@ -407,9 +428,15 @@ message + present for approval.
- After each result, ask whether the user's core request can now be
answered with useful evidence in hand. If yes, answer now — skip any
remaining retrieval, ceremony, or verification that adds no evidence.
-- Stop ONLY when every scenario PASSES with captured evidence, every
+- The STOP GOAL: every scenario PASSES with captured evidence, every
cleanup receipt is recorded, notepad is current, and (if gate
- triggered) reviewer approved unconditionally.
+ triggered) reviewer approved unconditionally. Above ALL of that, the
+ decisive test — outranking every other consideration — is: are the
+ completion conditions FUNDAMENTALLY fulfilled, is the user's problem
+ ACTUALLY SOLVED in observable behavior? If no, you are NOT done,
+ whatever the ledger says. If yes, deliver the final message and STOP
+ — no hesitation, no extra verification pass, no polish loop. Work
+ past the stop goal is scope creep, not diligence.
- Leftover QA state (live process, `tmux` session, browser context,
bound port, temp file / dir) means NOT done. Tear it down, record
the receipt, then continue.
diff --git a/plugins/omo/components/ultrawork/hooks/hooks.json b/plugins/omo/components/ultrawork/hooks/hooks.json
index 0f03c9dd..09e2d27d 100644
--- a/plugins/omo/components/ultrawork/hooks/hooks.json
+++ b/plugins/omo/components/ultrawork/hooks/hooks.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook user-prompt-submit",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Checking Ultrawork Trigger"
+ "statusMessage": "(OmO 4.18.0) Checking Ultrawork Trigger"
}
]
}
diff --git a/plugins/omo/components/ultrawork/package.json b/plugins/omo/components/ultrawork/package.json
index 5398db0c..a9497a22 100644
--- a/plugins/omo/components/ultrawork/package.json
+++ b/plugins/omo/components/ultrawork/package.json
@@ -1,6 +1,6 @@
{
"name": "@code-yeongyu/codex-ultrawork",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex plugin that injects the ultrawork orchestration directive and ships LazyCodex planning, review, QA, and gate agent roles.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/components/ultrawork/skills/ultrawork/SKILL.md b/plugins/omo/components/ultrawork/skills/ultrawork/SKILL.md
index 6dd9c309..6cab3364 100644
--- a/plugins/omo/components/ultrawork/skills/ultrawork/SKILL.md
+++ b/plugins/omo/components/ultrawork/skills/ultrawork/SKILL.md
@@ -128,9 +128,13 @@ are delegating never justify a planner: plan directly in the notepad.
Never spawn `plan` before the discovery wave has returned.
## 1. Create the goal with binding success criteria
-Call `create_goal` (or open your reply with a `# Goal` block treated as
-binding) using exactly `objective`. Do not include `status`. Goals are
-unlimited; never invent a numeric budget or limit.
+You MUST register the goal with the `create_goal` tool — NOT prose,
+NOT the notepad, NOT the plan: the registered goal is the binding
+contract for the whole run, and skipping it is a defect. Call it with
+exactly `objective`; do not include `status`. Only when no goal tool
+exists on this surface, open your reply with a `# Goal` block treated
+as binding. Goals are unlimited; never invent a numeric budget or
+limit.
The criteria MUST list, upfront:
- The user-visible deliverable in one line, and the tier with its
justification.
@@ -143,6 +147,9 @@ The criteria MUST list, upfront:
- For each criterion, the failing-first proof (test id or scenario)
that will be captured RED BEFORE the implementation and GREEN after.
Evidence added after the green code does NOT satisfy this.
+- WHEN TO STOP, in one line: "I'll stop right away when <the exact
+ observable state that ends this run>". The Stop rules bind to this
+ line — the moment it holds, you stop.
These scenarios are the contract. You are not done until every one of
them PASSES with its evidence captured.
@@ -243,6 +250,18 @@ Until every success criterion PASSES with its evidence captured:
scenario captured failing when no test seam exists. It must fail
for the RIGHT reason (not a syntax error, not a missing import).
Paste RED output into the notepad. No production code yet.
+ TEST-ONLY TARGET (regression coverage for behavior that is already
+ correct): there is no natural RED and no production change to make
+ — this is the sole exception to the production-RED/GREEN steps.
+ Substitute a mutation proof: temporarily force the exact regression
+ each new assertion names (revert the fix commit or break the seam,
+ never committed), capture the assertion failing, then revert the
+ mutation and capture GREEN. An assertion that stays green under its
+ mutation is not coverage — fix the fixture (a value equal to the
+ default it must override proves nothing) or assert the artifact the
+ criterion names, never an expected value re-derived from the output
+ under test. Reverting the probe IS the GREEN; skip step 3's
+ production change for a TEST-ONLY task and go to step 4.
PROSE TARGET (prompt, SKILL.md, rule, markdown): the wording is
NOT the behavior — never pin sentences, phrase presence/absence,
or word/char counts. PIN only a machine-consumed value (parsed
@@ -251,7 +270,8 @@ Until every success criterion PASSES with its evidence captured:
two shipped copies. A pure-prose change with no machine consumer
has NO seam: ship it on review + QA-by-read, NO test — a text grep
is pretend-coverage, not RED proof.
-3. GREEN: write the SMALLEST production change that flips RED→GREEN.
+3. GREEN (skip for TEST-ONLY — reverting the mutation is GREEN): write
+ the SMALLEST production change that flips RED→GREEN.
Before GREEN work that depends on external review, PR, issue, or
branch state, refresh current branch/PR/issue state and preserve existing ordering/policy;
separate compatibility detection from policy changes unless the goal
@@ -389,10 +409,11 @@ message + present for approval.
revert, capture the proof failing, then redo the change. Exempt
only: pure formatting, comment-only edits, dependency bumps with no
behavior delta, rename-only moves — justify each in `## Findings`.
-- A test that mirrors its implementation — asserting mocks were
- called, pinning a constant, or unable to fail under any plausible
- regression — is NOT evidence. Prefer a real-surface proof with no
- new test over a tautological test.
+- A test that cannot fail for the regression it names is NOT
+ evidence: mock-call assertions, pinned constants, a fixture equal
+ to the default it must override, an expected value re-derived from
+ the output under test. Prefer a real-surface proof with no new
+ test over a tautological one.
- Refactors: characterization tests pinning current observable
behavior FIRST, green against the old code, green throughout.
- Smallest correct change. No drive-by refactors.
@@ -414,9 +435,15 @@ message + present for approval.
- After each result, ask whether the user's core request can now be
answered with useful evidence in hand. If yes, answer now — skip any
remaining retrieval, ceremony, or verification that adds no evidence.
-- Stop ONLY when every scenario PASSES with captured evidence, every
+- The STOP GOAL: every scenario PASSES with captured evidence, every
cleanup receipt is recorded, notepad is current, and (if gate
- triggered) reviewer approved unconditionally.
+ triggered) reviewer approved unconditionally. Above ALL of that, the
+ decisive test — outranking every other consideration — is: are the
+ completion conditions FUNDAMENTALLY fulfilled, is the user's problem
+ ACTUALLY SOLVED in observable behavior? If no, you are NOT done,
+ whatever the ledger says. If yes, deliver the final message and STOP
+ — no hesitation, no extra verification pass, no polish loop. Work
+ past the stop goal is scope creep, not diligence.
- Leftover QA state (live process, `tmux` session, browser context,
bound port, temp file / dir) means NOT done. Tear it down, record
the receipt, then continue.
diff --git a/plugins/omo/components/ulw-loop/directive.md b/plugins/omo/components/ulw-loop/directive.md
index d837e70a..260bbaf2 100644
--- a/plugins/omo/components/ulw-loop/directive.md
+++ b/plugins/omo/components/ulw-loop/directive.md
@@ -121,9 +121,13 @@ are delegating never justify a planner: plan directly in the notepad.
Never spawn `plan` before the discovery wave has returned.
## 1. Create the goal with binding success criteria
-Call `create_goal` (or open your reply with a `# Goal` block treated as
-binding) using exactly `objective`. Do not include `status`. Goals are
-unlimited; never invent a numeric budget or limit.
+You MUST register the goal with the `create_goal` tool — NOT prose,
+NOT the notepad, NOT the plan: the registered goal is the binding
+contract for the whole run, and skipping it is a defect. Call it with
+exactly `objective`; do not include `status`. Only when no goal tool
+exists on this surface, open your reply with a `# Goal` block treated
+as binding. Goals are unlimited; never invent a numeric budget or
+limit.
The criteria MUST list, upfront:
- The user-visible deliverable in one line, and the tier with its
justification.
@@ -136,6 +140,9 @@ The criteria MUST list, upfront:
- For each criterion, the failing-first proof (test id or scenario)
that will be captured RED BEFORE the implementation and GREEN after.
Evidence added after the green code does NOT satisfy this.
+- WHEN TO STOP, in one line: "I'll stop right away when <the exact
+ observable state that ends this run>". The Stop rules bind to this
+ line — the moment it holds, you stop.
These scenarios are the contract. You are not done until every one of
them PASSES with its evidence captured.
@@ -236,6 +243,18 @@ Until every success criterion PASSES with its evidence captured:
scenario captured failing when no test seam exists. It must fail
for the RIGHT reason (not a syntax error, not a missing import).
Paste RED output into the notepad. No production code yet.
+ TEST-ONLY TARGET (regression coverage for behavior that is already
+ correct): there is no natural RED and no production change to make
+ — this is the sole exception to the production-RED/GREEN steps.
+ Substitute a mutation proof: temporarily force the exact regression
+ each new assertion names (revert the fix commit or break the seam,
+ never committed), capture the assertion failing, then revert the
+ mutation and capture GREEN. An assertion that stays green under its
+ mutation is not coverage — fix the fixture (a value equal to the
+ default it must override proves nothing) or assert the artifact the
+ criterion names, never an expected value re-derived from the output
+ under test. Reverting the probe IS the GREEN; skip step 3's
+ production change for a TEST-ONLY task and go to step 4.
PROSE TARGET (prompt, SKILL.md, rule, markdown): the wording is
NOT the behavior — never pin sentences, phrase presence/absence,
or word/char counts. PIN only a machine-consumed value (parsed
@@ -244,7 +263,8 @@ Until every success criterion PASSES with its evidence captured:
two shipped copies. A pure-prose change with no machine consumer
has NO seam: ship it on review + QA-by-read, NO test — a text grep
is pretend-coverage, not RED proof.
-3. GREEN: write the SMALLEST production change that flips RED→GREEN.
+3. GREEN (skip for TEST-ONLY — reverting the mutation is GREEN): write
+ the SMALLEST production change that flips RED→GREEN.
Before GREEN work that depends on external review, PR, issue, or
branch state, refresh current branch/PR/issue state and preserve existing ordering/policy;
separate compatibility detection from policy changes unless the goal
@@ -382,10 +402,11 @@ message + present for approval.
revert, capture the proof failing, then redo the change. Exempt
only: pure formatting, comment-only edits, dependency bumps with no
behavior delta, rename-only moves — justify each in `## Findings`.
-- A test that mirrors its implementation — asserting mocks were
- called, pinning a constant, or unable to fail under any plausible
- regression — is NOT evidence. Prefer a real-surface proof with no
- new test over a tautological test.
+- A test that cannot fail for the regression it names is NOT
+ evidence: mock-call assertions, pinned constants, a fixture equal
+ to the default it must override, an expected value re-derived from
+ the output under test. Prefer a real-surface proof with no new
+ test over a tautological one.
- Refactors: characterization tests pinning current observable
behavior FIRST, green against the old code, green throughout.
- Smallest correct change. No drive-by refactors.
@@ -407,9 +428,15 @@ message + present for approval.
- After each result, ask whether the user's core request can now be
answered with useful evidence in hand. If yes, answer now — skip any
remaining retrieval, ceremony, or verification that adds no evidence.
-- Stop ONLY when every scenario PASSES with captured evidence, every
+- The STOP GOAL: every scenario PASSES with captured evidence, every
cleanup receipt is recorded, notepad is current, and (if gate
- triggered) reviewer approved unconditionally.
+ triggered) reviewer approved unconditionally. Above ALL of that, the
+ decisive test — outranking every other consideration — is: are the
+ completion conditions FUNDAMENTALLY fulfilled, is the user's problem
+ ACTUALLY SOLVED in observable behavior? If no, you are NOT done,
+ whatever the ledger says. If yes, deliver the final message and STOP
+ — no hesitation, no extra verification pass, no polish loop. Work
+ past the stop goal is scope creep, not diligence.
- Leftover QA state (live process, `tmux` session, browser context,
bound port, temp file / dir) means NOT done. Tear it down, record
the receipt, then continue.
diff --git a/plugins/omo/components/ulw-loop/hooks/hooks.json b/plugins/omo/components/ulw-loop/hooks/hooks.json
index e6bad9f3..59ce08a7 100644
--- a/plugins/omo/components/ulw-loop/hooks/hooks.json
+++ b/plugins/omo/components/ulw-loop/hooks/hooks.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook user-prompt-submit --with-ultrawork",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Ulw-Loop Steering"
+ "statusMessage": "(OmO 4.18.0) Checking Ulw-Loop Steering"
}
]
}
@@ -20,7 +20,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook pre-tool-use",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Enforcing Unlimited Ulw-Loop Budget"
+ "statusMessage": "(OmO 4.18.0) Enforcing Unlimited Ulw-Loop Budget"
}
]
},
@@ -31,7 +31,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook pre-tool-use-spawn",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Guarding Ulw-Loop Spawns"
+ "statusMessage": "(OmO 4.18.0) Guarding Ulw-Loop Spawns"
}
]
}
@@ -43,7 +43,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook stop",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Ulw-Loop Resume"
+ "statusMessage": "(OmO 4.18.0) Checking Ulw-Loop Resume"
}
]
}
diff --git a/plugins/omo/components/ulw-loop/package.json b/plugins/omo/components/ulw-loop/package.json
index 4822de7c..5a6cbadc 100644
--- a/plugins/omo/components/ulw-loop/package.json
+++ b/plugins/omo/components/ulw-loop/package.json
@@ -1,6 +1,6 @@
{
"name": "@code-yeongyu/codex-ulw-loop",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Codex plugin: durable repo-native multi-goal orchestration with embedded success criteria and observable evidence audit.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/components/ulw-loop/skills/ulw-loop/SKILL.md b/plugins/omo/components/ulw-loop/skills/ulw-loop/SKILL.md
index fe6737c3..29b36dfa 100644
--- a/plugins/omo/components/ulw-loop/skills/ulw-loop/SKILL.md
+++ b/plugins/omo/components/ulw-loop/skills/ulw-loop/SKILL.md
@@ -14,7 +14,7 @@ This skill is intentionally compact. The full workflow lives in `references/full
## Required First Steps
1. Open `references/full-workflow.md`.
-2. Read through **Bootstrap** (including its tier triage), **Execution Loop**, and the **Manual-QA channels** table before running any ULW command or recording evidence.
+2. Read through **Bootstrap** (including its tier triage), **Execution Loop**, the **Manual-QA channels** table, and the **Stop Rules** before running any ULW command or recording evidence.
3. If the task has code edits, tests, QA, or commit work, follow the full workflow's delegation and evidence rules. Tests alone never prove done.
## Non-Negotiables
diff --git a/plugins/omo/components/ulw-loop/skills/ulw-loop/references/full-workflow.md b/plugins/omo/components/ulw-loop/skills/ulw-loop/references/full-workflow.md
index 634f5bfe..9d4972fa 100644
--- a/plugins/omo/components/ulw-loop/skills/ulw-loop/references/full-workflow.md
+++ b/plugins/omo/components/ulw-loop/skills/ulw-loop/references/full-workflow.md
@@ -129,7 +129,7 @@ First survey available skills: read every loosely-relevant skill's description,
Then run tier triage per goal — rigor (LIGHT/HEAVY below) and shape (`delivery` default, or `research` when the deliverable is a cited answer, not an artifact) — and record both in an `annotate_ledger` steering entry. Default is LIGHT — a narrow change inside existing layers. Take HEAVY only on a fact you can point to: a new module / abstraction / domain model; auth, security, or session; an external integration; a DB schema or migration; concurrency, transaction boundaries, or cache invalidation; a cross-domain refactor; or the user signaled care or demanded review. When unsure, take HEAVY; upgrade the moment a HEAVY fact surfaces, never downgrade mid-run.
Planning depends on unresolved design uncertainty, not the rigor tier: after discovery, spawn the `plan` agent only when unclear boundaries, competing decompositions, or uncertain dependency ordering remain; otherwise plan directly, including for HEAVY goals with a known procedure. HEAVY goals carry 3+ successCriteria covering happy path, edge, regression, and adversarial risk. LIGHT goals carry 1-2 successCriteria (happy path + the riskiest edge) with one real-surface proof of the deliverable.
Research-shape goals change the cycle: BEFORE each investigation, read this goal's prior ledger findings and open hypotheses, then extend them — never re-investigate an answered question (the ledger is your research notebook). Record findings via `annotate_ledger` with their source (`file:line`, command output, doc URL) as `--evidence`. Track hypotheses as `HYPOTHESIS[id]: <claim> | status: open`, flipped to `confirmed`/`refuted` only on an observed source. A research criterion passes on a cited answer — skip QA-channel, cleanup, and commit, but keep source-observability (never "looks correct"). Keep hypotheses inside the user's stated question; a scope-widening one is an `add_subgoal` proposal you surface, never silent creep. For a `research`-shape goal you MAY load `ulw-research` without hesitation — otherwise explicit-request-only, a research-shape goal IS that explicit demand. Research-only: never for a `delivery` goal. It composes with the librarian routing above — `ulw-research` for saturation (many parallel sources, recursive expansion), a single `librarian` for one lookup.
-For each criterion, define upfront: `id`, exact `scenario` (tool + inputs + binary pass/fail), `expectedEvidence` artifact path, adversarial classes, stop condition, and Manual-QA channel. Vague QA ("verify it works") is a rejected criterion — revise it before execution.
+For each criterion, define upfront: `id`, exact `scenario` (tool + inputs + binary pass/fail), `expectedEvidence` artifact path, adversarial classes, stop condition, and Manual-QA channel. Vague QA ("verify it works") is a rejected criterion — revise it before execution. Every goal also declares, in one line, WHEN TO STOP: "stop right away when <the exact observable state that ends this goal>". A goal without that line is rejected — revise it before execution; the Stop Rules bind to it.
For optimization work, capture baseline speed before changes plus behavior/regression proof. Every attempt records speed, behavior/regression, and the keep/revert/iterate decision.
A criterion's adversarial classes are the ultraqa classes a fact about the change triggers: malformed input, prompt injection, cancel/resume, stale state, dirty worktree, hung or long commands, flaky tests, misleading success output, repeated interruptions. Record untriggered classes as not-applicable in one line.
Use channel-table evidence verbs — not vibes.
@@ -151,7 +151,7 @@ Loop per goal. Cap at 5 cycles per goal. Cap identical same-criterion failures a
| get_goal result | action |
|-----------------|--------|
-| no active goal | Call `create_goal` with objective only from `instruction.json.objective`; do not copy lifecycle fields such as `status`. |
+| no active goal | You MUST call `create_goal` — goal registration goes through the tool, never prose — with objective only from `instruction.json.objective`; do not copy lifecycle fields such as `status`. |
| same aggregate objective active | Continue the current ulw-loop story. |
| different goal active | STOP. Checkpoint blocked and surface the conflict. |
4. If retrying failed work, run `omo ulw-loop complete-goals --retry-failed --json`.
@@ -160,7 +160,7 @@ Loop per goal. Cap at 5 cycles per goal. Cap identical same-criterion failures a
### Per-Criterion Cycle
1. PLAN: read `criterion.scenario`, `criterion.expectedEvidence`, prior ledger entries, and safety bounds. Identify which tasks in the current wave are independent.
2. Register atomic todos via `update_plan` — one ultra-granular step per action, `path: <action> for <criterion> - verify by <check>`. Call `update_plan` on every transition (start → `in_progress`, finish → `completed`); exactly one `in_progress`, mark completed immediately, never batch, never let the rendered plan lag behind reality.
-3. DELEGATE-IN-PARALLEL: dispatch every independent task in the wave at once via right-sized `spawn_agent` workers (Delegation table). Each worker captures evidence failing-first: when the task touches EXISTING behavior, PIN it FIRST — a characterization test that asserts the current observable behavior and PASSES on the unchanged code, as rigorous as the new-behavior scenario (exact inputs, exact observable, exact assertion). Then RED through the cheapest faithful channel — a unit test where a seam exists, an integration/e2e test where the behavior lives in wiring, or the criterion's scenario captured failing when no test seam exists — failing for the RIGHT reason (no syntax/import error). A test that mirrors its implementation (mock-call assertions, pinned constants, cannot fail under plausible regression) is not evidence; use the scenario as the failing proof instead. **When the target is PROSE (a prompt, `SKILL.md`, rule, or markdown/instruction file), the "observable behavior" is NOT the wording** — never pin sentences, phrase presence/absence, or word/char counts. PIN only a value a MACHINE consumes (a parsed frontmatter field, a sentinel token a hook greps, the doc's JSON sample run through its real validator), or guard two shipped copies with one `toBe` equality; a pure-prose change with no machine consumer has NO seam, so ship it on review + Manual-QA-by-read with NO automated test (a text grep there is pretend-coverage, not a RED proof). Then the SMALLEST GREEN change; before GREEN work that depends on external review, PR, issue, or branch state, refresh current branch/PR/issue state, preserve existing ordering/policy, and separate compatibility detection from policy changes unless the goal explicitly asks to change policy. A GREEN far larger than the criterion implies means the proof was too coarse — instruct a split. Serialize only on a NAMED dependency.
+3. DELEGATE-IN-PARALLEL: dispatch every independent task in the wave at once via right-sized `spawn_agent` workers (Delegation table). Each worker captures evidence failing-first: when the task touches EXISTING behavior, PIN it FIRST — a characterization test that asserts the current observable behavior and PASSES on the unchanged code, as rigorous as the new-behavior scenario (exact inputs, exact observable, exact assertion). Then RED through the cheapest faithful channel — a unit test where a seam exists, an integration/e2e test where the behavior lives in wiring, or the criterion's scenario captured failing when no test seam exists — failing for the RIGHT reason (no syntax/import error). A test that cannot fail for the regression it names (mock-call assertions, pinned constants, a fixture equal to the default it must override, an expected value re-derived from the output under test) is not evidence; use the scenario as the failing proof instead. TEST-ONLY tasks (regression coverage for behavior that is already correct) have no natural RED — require a mutation proof: temporarily force the exact regression each new assertion names, capture the assertion failing, revert the mutation, capture GREEN; an assertion that stays green under its mutation is not coverage. **When the target is PROSE (a prompt, `SKILL.md`, rule, or markdown/instruction file), the "observable behavior" is NOT the wording** — never pin sentences, phrase presence/absence, or word/char counts. PIN only a value a MACHINE consumes (a parsed frontmatter field, a sentinel token a hook greps, the doc's JSON sample run through its real validator), or guard two shipped copies with one `toBe` equality; a pure-prose change with no machine consumer has NO seam, so ship it on review + Manual-QA-by-read with NO automated test (a text grep there is pretend-coverage, not a RED proof). Then the SMALLEST GREEN change (none for a TEST-ONLY task — reverting the probe is GREEN; go to integration); before GREEN work that depends on external review, PR, issue, or branch state, refresh current branch/PR/issue state, preserve existing ordering/policy, and separate compatibility detection from policy changes unless the goal explicitly asks to change policy. A GREEN far larger than the criterion implies means the proof was too coarse — instruct a split. Serialize only on a NAMED dependency.
4. INTEGRATE + CRITICAL SELF-QA + GIT CHECKPOINT (EVERY WORKER RETURN): do NOT trust the worker's report. Read the diff yourself, re-run its tests, and run LSP diagnostics on the changed files. Treat "done" as a claim to disprove. If the diff drifts, the test is hollow, or evidence is missing, RESPAWN the worker with the specific failure context. Once the work unit is verified, use `git-master` before staging: inspect recent repository commits and touched-path history to infer commit language, Conventional Commit scope, message shape, and unit size. Stage only that unit's files and commit in the observed style; do not carry verified work forward into a later omnibus commit. If no git-tracked files changed or committing is unsafe, record the no-commit reason as evidence. Forward every finding/learning to subsequent workers.
5. EXECUTE-AS-SCENARIO: ACTUALLY run the Manual-QA scenario the criterion named (channel table above). Run it yourself for the orchestrator check; for heavier flows dispatch a dedicated QA execution worker (`lazycodex-worker-medium` by default; `lazycodex-worker-high` when the QA flow itself is hard) whose ONLY job is to drive the channel and write the artifact to the named evidence path. If the scenario FAILS, respawn the implementing worker with the captured failure — do not hand-patch around it.
6. CAPTURE: collect the observable artifact path: transcript, stdout, screenshot, assertion, status+body, diff, or parsed dump. No artifact written at the evidence path — not done; record BLOCKED and respawn QA.
@@ -239,7 +239,7 @@ Structured prompt directives accepted: `OMO_ULW_LOOP_STEER: { ... }`, `omo.ulw-l
15. Every verified work unit that touched git-tracked files must leave either an atomic `git-master`-style commit hash or explicit no-commit blocker evidence before the next unit starts.
## Stop Rules
-- All goals complete plus every plan criterion `pass` plus final quality gate clean: DONE.
+- STOP GOAL: all goals complete plus every plan criterion `pass` plus final quality gate clean. The decisive test — outranking every other consideration — is whether the completion conditions are FUNDAMENTALLY fulfilled and the user's problem ACTUALLY SOLVED in observable behavior; a `pass` ledger never substitutes for it. The moment both hold, checkpoint, report, and STOP — no extra review cycles, no evidence regeneration, no polish.
- 3x same criterion failure: checkpoint failed, surface diagnosis.
- 5 cycles on one goal without required criteria passing: checkpoint failed, surface.
- Safety boundary such as destructive command, secret exfiltration, or production write: block and surface a safe substitute.
diff --git a/plugins/omo/dist/cli-node/index.js b/plugins/omo/dist/cli-node/index.js
index 78190236..85c09268 100755
--- a/plugins/omo/dist/cli-node/index.js
+++ b/plugins/omo/dist/cli-node/index.js
@@ -2146,7 +2146,7 @@ var package_default;
var init_package = __esm(() => {
package_default = {
name: "oh-my-opencode",
- version: "4.17.1",
+ version: "4.18.0",
description: "The Best AI Agent Harness - Batteries-Included OpenCode Plugin with Multi-Model Orchestration, Parallel Background Agents, and Crafted LSP/AST Tools",
main: "./dist/index.js",
types: "dist/index.d.ts",
@@ -2253,6 +2253,7 @@ var init_package = __esm(() => {
build: "bun run script/build.ts",
"build:cli-node": "bun run script/build-cli-node.ts",
"build:codex-install": "bun run script/build-codex-install.ts",
+ "install:codex-dev": "bun run script/build-codex-install.ts && bun run script/install-codex-dev.ts",
"build:codex-plugin": "npm --prefix packages/omo-codex/plugin ci && bun run --cwd packages/omo-codex/plugin build",
"build:senpi-plugin": "node packages/omo-senpi/plugin/scripts/build-extension.mjs && node packages/omo-senpi/plugin/scripts/sync-skills.mjs && node packages/omo-senpi/plugin/scripts/embed-directive.mjs --check",
"build:materialize-frontend": "node packages/omo-codex/plugin/scripts/materialize-shared-upstreams.mjs --strict",
@@ -2357,18 +2358,18 @@ var init_package = __esm(() => {
typescript: "^6.0.3"
},
optionalDependencies: {
- "oh-my-opencode-darwin-arm64": "4.17.1",
- "oh-my-opencode-darwin-x64": "4.17.1",
- "oh-my-opencode-darwin-x64-baseline": "4.17.1",
- "oh-my-opencode-linux-arm64": "4.17.1",
- "oh-my-opencode-linux-arm64-musl": "4.17.1",
- "oh-my-opencode-linux-x64": "4.17.1",
- "oh-my-opencode-linux-x64-baseline": "4.17.1",
- "oh-my-opencode-linux-x64-musl": "4.17.1",
- "oh-my-opencode-linux-x64-musl-baseline": "4.17.1",
- "oh-my-opencode-windows-arm64": "4.17.1",
- "oh-my-opencode-windows-x64": "4.17.1",
- "oh-my-opencode-windows-x64-baseline": "4.17.1"
+ "oh-my-opencode-darwin-arm64": "4.18.0",
+ "oh-my-opencode-darwin-x64": "4.18.0",
+ "oh-my-opencode-darwin-x64-baseline": "4.18.0",
+ "oh-my-opencode-linux-arm64": "4.18.0",
+ "oh-my-opencode-linux-arm64-musl": "4.18.0",
+ "oh-my-opencode-linux-x64": "4.18.0",
+ "oh-my-opencode-linux-x64-baseline": "4.18.0",
+ "oh-my-opencode-linux-x64-musl": "4.18.0",
+ "oh-my-opencode-linux-x64-musl-baseline": "4.18.0",
+ "oh-my-opencode-windows-arm64": "4.18.0",
+ "oh-my-opencode-windows-x64": "4.18.0",
+ "oh-my-opencode-windows-x64-baseline": "4.18.0"
},
overrides: {
"@earendil-works/pi-agent-core": "0.80.3",
@@ -72657,7 +72658,7 @@ var package_default2;
var init_package2 = __esm(() => {
package_default2 = {
name: "@oh-my-opencode/omo-codex",
- version: "4.17.1",
+ version: "4.18.0",
type: "module",
private: true,
description: "Codex harness adapter for oh-my-openagent. Vendored Codex plugin namespace (omo) + TypeScript installer + telemetry.",
@@ -75381,9 +75382,11 @@ function collectCommands(value, commands) {
// packages/omo-codex/src/install/codex-cache-install.ts
async function installCachedPlugin(input) {
+ const env2 = input.env ?? process.env;
+ const npmInstallEnv = sanitizeNpmInstallEnv(env2);
if (input.buildSource !== false) {
- await maybeRunNpmInstall(input.sourcePath, input.runCommand);
- await maybeRunNpmBuild(input.sourcePath, input.runCommand);
+ await maybeRunNpmInstall(input.sourcePath, input.runCommand, npmInstallEnv);
+ await maybeRunNpmBuild(input.sourcePath, input.runCommand, env2);
}
const targetPath = join33(input.codexHome, "plugins", "cache", input.marketplaceName, input.name, input.version);
const tempPath = createTempSiblingPath(targetPath);
@@ -75393,10 +75396,10 @@ async function installCachedPlugin(input) {
await rewriteCachedPackageLocalFileDependencies(tempPath, input.sourcePath);
await copyBundledMcpRuntimeDists({ pluginRoot: tempPath, sourceRoot: input.sourcePath });
await copyRootRuntimeDists({ pluginRoot: tempPath, sourcePath: input.sourcePath });
- await maybeRunNpmInstall(tempPath, input.runCommand, ["ci", "--omit=dev"]);
+ await maybeRunNpmInstall(tempPath, input.runCommand, npmInstallEnv, ["ci", "--omit=dev"]);
await removeCachedManagedNpmBinShims(tempPath);
if (input.buildSource === false)
- await maybeRunNpmSyncSkills(tempPath, input.runCommand);
+ await maybeRunNpmSyncSkills(tempPath, input.runCommand, env2);
await assertNoRemovedSparkshellPromptReferences(tempPath);
await rewriteCachedMcpManifest(tempPath, input.sourcePath);
await rewriteCachedManifestRoot(tempPath, tempPath, targetPath);
@@ -75408,12 +75411,12 @@ async function installCachedPlugin(input) {
}
return { name: input.name, version: input.version, path: targetPath };
}
-async function maybeRunNpmInstall(cwd, runCommand, args = ["install"]) {
+async function maybeRunNpmInstall(cwd, runCommand, env2, args = ["install"]) {
if (!await fileExistsStrict(join33(cwd, "package.json")))
return;
- await runCommand("npm", args, { cwd });
+ await runCommand("npm", args, { cwd, env: env2 });
}
-async function maybeRunNpmBuild(cwd, runCommand) {
+async function maybeRunNpmBuild(cwd, runCommand, env2) {
if (!await fileExistsStrict(join33(cwd, "package.json")))
return;
const packageJson = JSON.parse(await readFile8(join33(cwd, "package.json"), "utf8"));
@@ -75422,9 +75425,9 @@ async function maybeRunNpmBuild(cwd, runCommand) {
const scripts = packageJson.scripts;
if (!isPlainRecord3(scripts) || typeof scripts.build !== "string")
return;
- await runCommand("npm", ["run", "build"], { cwd });
+ await runCommand("npm", ["run", "build"], { cwd, env: env2 });
}
-async function maybeRunNpmSyncSkills(cwd, runCommand) {
+async function maybeRunNpmSyncSkills(cwd, runCommand, env2) {
if (!await fileExistsStrict(join33(cwd, "package.json")))
return;
const packageJson = JSON.parse(await readFile8(join33(cwd, "package.json"), "utf8"));
@@ -75433,7 +75436,10 @@ async function maybeRunNpmSyncSkills(cwd, runCommand) {
const scripts = packageJson.scripts;
if (!isPlainRecord3(scripts) || typeof scripts["sync:skills"] !== "string")
return;
- await runCommand("npm", ["run", "sync:skills"], { cwd });
+ await runCommand("npm", ["run", "sync:skills"], { cwd, env: env2 });
+}
+function sanitizeNpmInstallEnv(env2) {
+ return Object.fromEntries(Object.entries(env2).filter(([key]) => key.toLowerCase() !== "npm_config_allow_scripts"));
}
function createTempSiblingPath(targetPath) {
return join33(dirname13(targetPath), `.tmp-${basename7(targetPath)}-${process.pid}-${Date.now()}`);
@@ -77463,6 +77469,10 @@ async function readDistributionManifest(repoRoot) {
}
}
function resolveLazyCodexPluginVersion(input) {
+ const override = input.versionOverride?.trim();
+ if (override !== undefined && override.length > 0) {
+ return override;
+ }
if (input.marketplaceName === "sisyphuslabs" && input.pluginName === "omo" && input.distributionManifest !== undefined) {
return input.distributionManifest.version;
}
@@ -78013,6 +78023,7 @@ async function runCodexInstaller(options = {}) {
return;
});
const buildSource = await shouldBuildSourcePackages(repoRoot);
+ const versionOverride = env3.LAZYCODEX_DEV_VERSION?.trim() || undefined;
const gitBashResolution = await prepareGitBashForInstall({
platform,
env: env3,
@@ -78039,13 +78050,15 @@ async function runCodexInstaller(options = {}) {
manifestVersion: manifest.version,
marketplaceName: marketplace.name,
pluginName: entry.name,
- distributionManifest
+ distributionManifest,
+ versionOverride
});
validatePathSegment(version2, "plugin version");
log4(`Building ${entry.name}@${version2}`);
const plugin = await installCachedPlugin({
buildSource,
codexHome,
+ env: env3,
marketplaceName: marketplace.name,
name: entry.name,
runCommand,
@@ -99126,6 +99139,10 @@ function formatVersionOutput(info) {
lines.push(` ${SYMBOLS3.dev} ${import_picocolors17.default.cyan("Running in local development mode")}`);
lines.push(` ${import_picocolors17.default.dim("Using file:// protocol from config")}`);
break;
+ case "dev":
+ lines.push(` ${SYMBOLS3.dev} ${import_picocolors17.default.cyan("Running a local dev build")}`);
+ lines.push(` ${import_picocolors17.default.dim("Installed from source; update checks are skipped")}`);
+ break;
case "pinned":
lines.push(` ${SYMBOLS3.pin} ${import_picocolors17.default.magenta(`Version pinned to ${info.pinnedVersion}`)}`);
lines.push(` ${import_picocolors17.default.dim("Update check skipped for pinned versions")}`);
@@ -99198,6 +99215,19 @@ async function getLocalVersion(options = {}) {
console.log(options.json ? formatJsonOutput(info2) : formatVersionOutput(info2));
return 1;
}
+ if (!/^\d+\.\d+\.\d+/.test(currentVersion)) {
+ const info2 = {
+ currentVersion,
+ latestVersion: null,
+ isUpToDate: false,
+ isLocalDev: true,
+ isPinned: false,
+ pinnedVersion: null,
+ status: "dev"
+ };
+ console.log(options.json ? formatJsonOutput(info2) : formatVersionOutput(info2));
+ return 0;
+ }
const { extractChannel: extractChannel2 } = await Promise.resolve().then(() => (init_auto_update_checker(), exports_auto_update_checker));
const channel = extractChannel2(pluginInfo?.pinnedVersion ?? currentVersion);
const latestVersion = await getLatestVersion(channel);
diff --git a/plugins/omo/dist/cli/index.js b/plugins/omo/dist/cli/index.js
index 600eab75..b893cf01 100755
--- a/plugins/omo/dist/cli/index.js
+++ b/plugins/omo/dist/cli/index.js
@@ -2145,7 +2145,7 @@ var package_default;
var init_package = __esm(() => {
package_default = {
name: "oh-my-opencode",
- version: "4.17.1",
+ version: "4.18.0",
description: "The Best AI Agent Harness - Batteries-Included OpenCode Plugin with Multi-Model Orchestration, Parallel Background Agents, and Crafted LSP/AST Tools",
main: "./dist/index.js",
types: "dist/index.d.ts",
@@ -2252,6 +2252,7 @@ var init_package = __esm(() => {
build: "bun run script/build.ts",
"build:cli-node": "bun run script/build-cli-node.ts",
"build:codex-install": "bun run script/build-codex-install.ts",
+ "install:codex-dev": "bun run script/build-codex-install.ts && bun run script/install-codex-dev.ts",
"build:codex-plugin": "npm --prefix packages/omo-codex/plugin ci && bun run --cwd packages/omo-codex/plugin build",
"build:senpi-plugin": "node packages/omo-senpi/plugin/scripts/build-extension.mjs && node packages/omo-senpi/plugin/scripts/sync-skills.mjs && node packages/omo-senpi/plugin/scripts/embed-directive.mjs --check",
"build:materialize-frontend": "node packages/omo-codex/plugin/scripts/materialize-shared-upstreams.mjs --strict",
@@ -2356,18 +2357,18 @@ var init_package = __esm(() => {
typescript: "^6.0.3"
},
optionalDependencies: {
- "oh-my-opencode-darwin-arm64": "4.17.1",
- "oh-my-opencode-darwin-x64": "4.17.1",
- "oh-my-opencode-darwin-x64-baseline": "4.17.1",
- "oh-my-opencode-linux-arm64": "4.17.1",
- "oh-my-opencode-linux-arm64-musl": "4.17.1",
- "oh-my-opencode-linux-x64": "4.17.1",
- "oh-my-opencode-linux-x64-baseline": "4.17.1",
- "oh-my-opencode-linux-x64-musl": "4.17.1",
- "oh-my-opencode-linux-x64-musl-baseline": "4.17.1",
- "oh-my-opencode-windows-arm64": "4.17.1",
- "oh-my-opencode-windows-x64": "4.17.1",
- "oh-my-opencode-windows-x64-baseline": "4.17.1"
+ "oh-my-opencode-darwin-arm64": "4.18.0",
+ "oh-my-opencode-darwin-x64": "4.18.0",
+ "oh-my-opencode-darwin-x64-baseline": "4.18.0",
+ "oh-my-opencode-linux-arm64": "4.18.0",
+ "oh-my-opencode-linux-arm64-musl": "4.18.0",
+ "oh-my-opencode-linux-x64": "4.18.0",
+ "oh-my-opencode-linux-x64-baseline": "4.18.0",
+ "oh-my-opencode-linux-x64-musl": "4.18.0",
+ "oh-my-opencode-linux-x64-musl-baseline": "4.18.0",
+ "oh-my-opencode-windows-arm64": "4.18.0",
+ "oh-my-opencode-windows-x64": "4.18.0",
+ "oh-my-opencode-windows-x64-baseline": "4.18.0"
},
overrides: {
"@earendil-works/pi-agent-core": "0.80.3",
@@ -72601,7 +72602,7 @@ var package_default2;
var init_package2 = __esm(() => {
package_default2 = {
name: "@oh-my-opencode/omo-codex",
- version: "4.17.1",
+ version: "4.18.0",
type: "module",
private: true,
description: "Codex harness adapter for oh-my-openagent. Vendored Codex plugin namespace (omo) + TypeScript installer + telemetry.",
@@ -75325,9 +75326,11 @@ function collectCommands(value, commands) {
// packages/omo-codex/src/install/codex-cache-install.ts
async function installCachedPlugin(input) {
+ const env2 = input.env ?? process.env;
+ const npmInstallEnv = sanitizeNpmInstallEnv(env2);
if (input.buildSource !== false) {
- await maybeRunNpmInstall(input.sourcePath, input.runCommand);
- await maybeRunNpmBuild(input.sourcePath, input.runCommand);
+ await maybeRunNpmInstall(input.sourcePath, input.runCommand, npmInstallEnv);
+ await maybeRunNpmBuild(input.sourcePath, input.runCommand, env2);
}
const targetPath = join33(input.codexHome, "plugins", "cache", input.marketplaceName, input.name, input.version);
const tempPath = createTempSiblingPath(targetPath);
@@ -75337,10 +75340,10 @@ async function installCachedPlugin(input) {
await rewriteCachedPackageLocalFileDependencies(tempPath, input.sourcePath);
await copyBundledMcpRuntimeDists({ pluginRoot: tempPath, sourceRoot: input.sourcePath });
await copyRootRuntimeDists({ pluginRoot: tempPath, sourcePath: input.sourcePath });
- await maybeRunNpmInstall(tempPath, input.runCommand, ["ci", "--omit=dev"]);
+ await maybeRunNpmInstall(tempPath, input.runCommand, npmInstallEnv, ["ci", "--omit=dev"]);
await removeCachedManagedNpmBinShims(tempPath);
if (input.buildSource === false)
- await maybeRunNpmSyncSkills(tempPath, input.runCommand);
+ await maybeRunNpmSyncSkills(tempPath, input.runCommand, env2);
await assertNoRemovedSparkshellPromptReferences(tempPath);
await rewriteCachedMcpManifest(tempPath, input.sourcePath);
await rewriteCachedManifestRoot(tempPath, tempPath, targetPath);
@@ -75352,12 +75355,12 @@ async function installCachedPlugin(input) {
}
return { name: input.name, version: input.version, path: targetPath };
}
-async function maybeRunNpmInstall(cwd, runCommand, args = ["install"]) {
+async function maybeRunNpmInstall(cwd, runCommand, env2, args = ["install"]) {
if (!await fileExistsStrict(join33(cwd, "package.json")))
return;
- await runCommand("npm", args, { cwd });
+ await runCommand("npm", args, { cwd, env: env2 });
}
-async function maybeRunNpmBuild(cwd, runCommand) {
+async function maybeRunNpmBuild(cwd, runCommand, env2) {
if (!await fileExistsStrict(join33(cwd, "package.json")))
return;
const packageJson = JSON.parse(await readFile8(join33(cwd, "package.json"), "utf8"));
@@ -75366,9 +75369,9 @@ async function maybeRunNpmBuild(cwd, runCommand) {
const scripts = packageJson.scripts;
if (!isPlainRecord3(scripts) || typeof scripts.build !== "string")
return;
- await runCommand("npm", ["run", "build"], { cwd });
+ await runCommand("npm", ["run", "build"], { cwd, env: env2 });
}
-async function maybeRunNpmSyncSkills(cwd, runCommand) {
+async function maybeRunNpmSyncSkills(cwd, runCommand, env2) {
if (!await fileExistsStrict(join33(cwd, "package.json")))
return;
const packageJson = JSON.parse(await readFile8(join33(cwd, "package.json"), "utf8"));
@@ -75377,7 +75380,10 @@ async function maybeRunNpmSyncSkills(cwd, runCommand) {
const scripts = packageJson.scripts;
if (!isPlainRecord3(scripts) || typeof scripts["sync:skills"] !== "string")
return;
- await runCommand("npm", ["run", "sync:skills"], { cwd });
+ await runCommand("npm", ["run", "sync:skills"], { cwd, env: env2 });
+}
+function sanitizeNpmInstallEnv(env2) {
+ return Object.fromEntries(Object.entries(env2).filter(([key]) => key.toLowerCase() !== "npm_config_allow_scripts"));
}
function createTempSiblingPath(targetPath) {
return join33(dirname13(targetPath), `.tmp-${basename7(targetPath)}-${process.pid}-${Date.now()}`);
@@ -77407,6 +77413,10 @@ async function readDistributionManifest(repoRoot) {
}
}
function resolveLazyCodexPluginVersion(input) {
+ const override = input.versionOverride?.trim();
+ if (override !== undefined && override.length > 0) {
+ return override;
+ }
if (input.marketplaceName === "sisyphuslabs" && input.pluginName === "omo" && input.distributionManifest !== undefined) {
return input.distributionManifest.version;
}
@@ -77957,6 +77967,7 @@ async function runCodexInstaller(options = {}) {
return;
});
const buildSource = await shouldBuildSourcePackages(repoRoot);
+ const versionOverride = env3.LAZYCODEX_DEV_VERSION?.trim() || undefined;
const gitBashResolution = await prepareGitBashForInstall({
platform,
env: env3,
@@ -77983,13 +77994,15 @@ async function runCodexInstaller(options = {}) {
manifestVersion: manifest.version,
marketplaceName: marketplace.name,
pluginName: entry.name,
- distributionManifest
+ distributionManifest,
+ versionOverride
});
validatePathSegment(version2, "plugin version");
log4(`Building ${entry.name}@${version2}`);
const plugin = await installCachedPlugin({
buildSource,
codexHome,
+ env: env3,
marketplaceName: marketplace.name,
name: entry.name,
runCommand,
@@ -99070,6 +99083,10 @@ function formatVersionOutput(info) {
lines.push(` ${SYMBOLS3.dev} ${import_picocolors17.default.cyan("Running in local development mode")}`);
lines.push(` ${import_picocolors17.default.dim("Using file:// protocol from config")}`);
break;
+ case "dev":
+ lines.push(` ${SYMBOLS3.dev} ${import_picocolors17.default.cyan("Running a local dev build")}`);
+ lines.push(` ${import_picocolors17.default.dim("Installed from source; update checks are skipped")}`);
+ break;
case "pinned":
lines.push(` ${SYMBOLS3.pin} ${import_picocolors17.default.magenta(`Version pinned to ${info.pinnedVersion}`)}`);
lines.push(` ${import_picocolors17.default.dim("Update check skipped for pinned versions")}`);
@@ -99142,6 +99159,19 @@ async function getLocalVersion(options = {}) {
console.log(options.json ? formatJsonOutput(info2) : formatVersionOutput(info2));
return 1;
}
+ if (!/^\d+\.\d+\.\d+/.test(currentVersion)) {
+ const info2 = {
+ currentVersion,
+ latestVersion: null,
+ isUpToDate: false,
+ isLocalDev: true,
+ isPinned: false,
+ pinnedVersion: null,
+ status: "dev"
+ };
+ console.log(options.json ? formatJsonOutput(info2) : formatVersionOutput(info2));
+ return 0;
+ }
const { extractChannel: extractChannel2 } = await Promise.resolve().then(() => (init_auto_update_checker(), exports_auto_update_checker));
const channel = extractChannel2(pluginInfo?.pinnedVersion ?? currentVersion);
const latestVersion = await getLatestVersion(channel);
diff --git a/plugins/omo/hooks/post-compact-resetting-git-bash-mcp-reminder.json b/plugins/omo/hooks/post-compact-resetting-git-bash-mcp-reminder.json
index 36625e44..1fd10006 100644
--- a/plugins/omo/hooks/post-compact-resetting-git-bash-mcp-reminder.json
+++ b/plugins/omo/hooks/post-compact-resetting-git-bash-mcp-reminder.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/git-bash/dist/cli.js\" hook post-compact",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Resetting Git Bash MCP Reminder",
+ "statusMessage": "(OmO 4.18.0) Resetting Git Bash MCP Reminder",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\git-bash\\dist\\cli.js\" hook post-compact"
}
],
diff --git a/plugins/omo/hooks/post-compact-resetting-lsp-diagnostics-cache.json b/plugins/omo/hooks/post-compact-resetting-lsp-diagnostics-cache.json
index 5a1f6d2e..480b9ded 100644
--- a/plugins/omo/hooks/post-compact-resetting-lsp-diagnostics-cache.json
+++ b/plugins/omo/hooks/post-compact-resetting-lsp-diagnostics-cache.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/lsp/dist/cli.js\" hook post-compact",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Resetting LSP Diagnostics Cache",
+ "statusMessage": "(OmO 4.18.0) Resetting LSP Diagnostics Cache",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\lsp\\dist\\cli.js\" hook post-compact"
}
],
diff --git a/plugins/omo/hooks/post-compact-resetting-project-rule-cache.json b/plugins/omo/hooks/post-compact-resetting-project-rule-cache.json
index 67aff896..9e2e304e 100644
--- a/plugins/omo/hooks/post-compact-resetting-project-rule-cache.json
+++ b/plugins/omo/hooks/post-compact-resetting-project-rule-cache.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/rules/dist/cli.js\" hook post-compact",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Resetting Project Rule Cache",
+ "statusMessage": "(OmO 4.18.0) Resetting Project Rule Cache",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\rules\\dist\\cli.js\" hook post-compact"
}
],
diff --git a/plugins/omo/hooks/post-tool-use-checking-codegraph-init-guidance.json b/plugins/omo/hooks/post-tool-use-checking-codegraph-init-guidance.json
index 6e5baa15..710fe8c2 100644
--- a/plugins/omo/hooks/post-tool-use-checking-codegraph-init-guidance.json
+++ b/plugins/omo/hooks/post-tool-use-checking-codegraph-init-guidance.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/codegraph/dist/cli.js\" hook post-tool-use",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Checking CodeGraph Init Guidance",
+ "statusMessage": "(OmO 4.18.0) Checking CodeGraph Init Guidance",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\codegraph\\dist\\cli.js\" hook post-tool-use"
}
],
diff --git a/plugins/omo/hooks/post-tool-use-checking-comments.json b/plugins/omo/hooks/post-tool-use-checking-comments.json
index 316abb59..b3e2ce72 100644
--- a/plugins/omo/hooks/post-tool-use-checking-comments.json
+++ b/plugins/omo/hooks/post-tool-use-checking-comments.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/comment-checker/dist/cli.js\" hook post-tool-use",
"timeout": 30,
- "statusMessage": "(OmO 4.17.1) Checking Comments",
+ "statusMessage": "(OmO 4.18.0) Checking Comments",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\comment-checker\\dist\\cli.js\" hook post-tool-use"
}
],
diff --git a/plugins/omo/hooks/post-tool-use-checking-lsp-diagnostics.json b/plugins/omo/hooks/post-tool-use-checking-lsp-diagnostics.json
index 7f54ab0e..8a35e5a0 100644
--- a/plugins/omo/hooks/post-tool-use-checking-lsp-diagnostics.json
+++ b/plugins/omo/hooks/post-tool-use-checking-lsp-diagnostics.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/lsp/dist/cli.js\" hook post-tool-use",
"timeout": 60,
- "statusMessage": "(OmO 4.17.1) Checking LSP Diagnostics",
+ "statusMessage": "(OmO 4.18.0) Checking LSP Diagnostics",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\lsp\\dist\\cli.js\" hook post-tool-use"
}
],
diff --git a/plugins/omo/hooks/post-tool-use-checking-thread-title-hygiene.json b/plugins/omo/hooks/post-tool-use-checking-thread-title-hygiene.json
index 7f00c971..d0d00076 100644
--- a/plugins/omo/hooks/post-tool-use-checking-thread-title-hygiene.json
+++ b/plugins/omo/hooks/post-tool-use-checking-thread-title-hygiene.json
@@ -8,7 +8,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/teammode/dist/cli.js\" hook post-tool-use",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Thread Title Hygiene",
+ "statusMessage": "(OmO 4.18.0) Checking Thread Title Hygiene",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\teammode\\dist\\cli.js\" hook post-tool-use"
}
]
diff --git a/plugins/omo/hooks/post-tool-use-matching-project-rules.json b/plugins/omo/hooks/post-tool-use-matching-project-rules.json
index 60c66ee2..e73630a6 100644
--- a/plugins/omo/hooks/post-tool-use-matching-project-rules.json
+++ b/plugins/omo/hooks/post-tool-use-matching-project-rules.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/rules/dist/cli.js\" hook post-tool-use",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Matching Project Rules",
+ "statusMessage": "(OmO 4.18.0) Matching Project Rules",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\rules\\dist\\cli.js\" hook post-tool-use"
}
],
diff --git a/plugins/omo/hooks/pre-tool-use-enforcing-unlimited-goal-budget.json b/plugins/omo/hooks/pre-tool-use-enforcing-unlimited-goal-budget.json
index 02b72ebd..0a11bed3 100644
--- a/plugins/omo/hooks/pre-tool-use-enforcing-unlimited-goal-budget.json
+++ b/plugins/omo/hooks/pre-tool-use-enforcing-unlimited-goal-budget.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/ulw-loop/dist/cli.js\" hook pre-tool-use",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Enforcing Unlimited Goal Budget",
+ "statusMessage": "(OmO 4.18.0) Enforcing Unlimited Goal Budget",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\ulw-loop\\dist\\cli.js\" hook pre-tool-use"
}
],
diff --git a/plugins/omo/hooks/pre-tool-use-guarding-ulw-loop-spawns.json b/plugins/omo/hooks/pre-tool-use-guarding-ulw-loop-spawns.json
index 176d526a..353d01fb 100644
--- a/plugins/omo/hooks/pre-tool-use-guarding-ulw-loop-spawns.json
+++ b/plugins/omo/hooks/pre-tool-use-guarding-ulw-loop-spawns.json
@@ -8,7 +8,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/ulw-loop/dist/cli.js\" hook pre-tool-use-spawn",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Guarding Ulw-Loop Spawns",
+ "statusMessage": "(OmO 4.18.0) Guarding Ulw-Loop Spawns",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\ulw-loop\\dist\\cli.js\" hook pre-tool-use-spawn"
}
]
diff --git a/plugins/omo/hooks/pre-tool-use-recommending-git-bash-mcp.json b/plugins/omo/hooks/pre-tool-use-recommending-git-bash-mcp.json
index d49b44bd..debd1f87 100644
--- a/plugins/omo/hooks/pre-tool-use-recommending-git-bash-mcp.json
+++ b/plugins/omo/hooks/pre-tool-use-recommending-git-bash-mcp.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/git-bash/dist/cli.js\" hook pre-tool-use",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Recommending Git Bash MCP",
+ "statusMessage": "(OmO 4.18.0) Recommending Git Bash MCP",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\git-bash\\dist\\cli.js\" hook pre-tool-use"
}
],
diff --git a/plugins/omo/hooks/session-start-checking-auto-update.json b/plugins/omo/hooks/session-start-checking-auto-update.json
index 7600650c..59e213be 100644
--- a/plugins/omo/hooks/session-start-checking-auto-update.json
+++ b/plugins/omo/hooks/session-start-checking-auto-update.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/scripts/auto-update.mjs\" hook session-start",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Checking Auto Update",
+ "statusMessage": "(OmO 4.18.0) Checking Auto Update",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\scripts\\auto-update.mjs\" hook session-start"
}
],
diff --git a/plugins/omo/hooks/session-start-checking-bootstrap-provisioning.json b/plugins/omo/hooks/session-start-checking-bootstrap-provisioning.json
index c3876fa7..d6c40efb 100644
--- a/plugins/omo/hooks/session-start-checking-bootstrap-provisioning.json
+++ b/plugins/omo/hooks/session-start-checking-bootstrap-provisioning.json
@@ -8,7 +8,7 @@
"command": "node \"${PLUGIN_ROOT}/components/bootstrap/dist/cli.js\" hook session-start",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\bootstrap.ps1\"",
"timeout": 30,
- "statusMessage": "(OmO 4.17.1) Checking Bootstrap Provisioning"
+ "statusMessage": "(OmO 4.18.0) Checking Bootstrap Provisioning"
}
]
}
diff --git a/plugins/omo/hooks/session-start-checking-codegraph-bootstrap.json b/plugins/omo/hooks/session-start-checking-codegraph-bootstrap.json
index a9354f39..bdd9e804 100644
--- a/plugins/omo/hooks/session-start-checking-codegraph-bootstrap.json
+++ b/plugins/omo/hooks/session-start-checking-codegraph-bootstrap.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/codegraph/dist/cli.js\" hook session-start",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Checking CodeGraph Bootstrap",
+ "statusMessage": "(OmO 4.18.0) Checking CodeGraph Bootstrap",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\codegraph\\dist\\cli.js\" hook session-start"
}
]
diff --git a/plugins/omo/hooks/session-start-loading-project-rules.json b/plugins/omo/hooks/session-start-loading-project-rules.json
index dd7d5b0f..7b65e6c6 100644
--- a/plugins/omo/hooks/session-start-loading-project-rules.json
+++ b/plugins/omo/hooks/session-start-loading-project-rules.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/rules/dist/cli.js\" hook session-start",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Loading Project Rules",
+ "statusMessage": "(OmO 4.18.0) Loading Project Rules",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\rules\\dist\\cli.js\" hook session-start"
}
]
diff --git a/plugins/omo/hooks/session-start-recording-session-telemetry.json b/plugins/omo/hooks/session-start-recording-session-telemetry.json
index c507b157..67c47b43 100644
--- a/plugins/omo/hooks/session-start-recording-session-telemetry.json
+++ b/plugins/omo/hooks/session-start-recording-session-telemetry.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/telemetry/dist/cli.js\" hook session-start",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Recording Session Telemetry",
+ "statusMessage": "(OmO 4.18.0) Recording Session Telemetry",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\telemetry\\dist\\cli.js\" hook session-start"
}
]
diff --git a/plugins/omo/hooks/stop-checking-start-work-continuation.json b/plugins/omo/hooks/stop-checking-start-work-continuation.json
index e726abc1..7319b58e 100644
--- a/plugins/omo/hooks/stop-checking-start-work-continuation.json
+++ b/plugins/omo/hooks/stop-checking-start-work-continuation.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/start-work-continuation/dist/cli.js\" hook stop",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Start-Work Continuation",
+ "statusMessage": "(OmO 4.18.0) Checking Start-Work Continuation",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\start-work-continuation\\dist\\cli.js\" hook stop"
}
]
diff --git a/plugins/omo/hooks/stop-checking-ulw-loop-resume.json b/plugins/omo/hooks/stop-checking-ulw-loop-resume.json
index 8d0c6763..8620f26b 100644
--- a/plugins/omo/hooks/stop-checking-ulw-loop-resume.json
+++ b/plugins/omo/hooks/stop-checking-ulw-loop-resume.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/ulw-loop/dist/cli.js\" hook stop",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Ulw-Loop Resume",
+ "statusMessage": "(OmO 4.18.0) Checking Ulw-Loop Resume",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\ulw-loop\\dist\\cli.js\" hook stop"
}
]
diff --git a/plugins/omo/hooks/subagent-stop-checking-start-work-continuation.json b/plugins/omo/hooks/subagent-stop-checking-start-work-continuation.json
index c6ddadb6..da2680f3 100644
--- a/plugins/omo/hooks/subagent-stop-checking-start-work-continuation.json
+++ b/plugins/omo/hooks/subagent-stop-checking-start-work-continuation.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/start-work-continuation/dist/cli.js\" hook subagent-stop",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Start-Work Continuation",
+ "statusMessage": "(OmO 4.18.0) Checking Start-Work Continuation",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\start-work-continuation\\dist\\cli.js\" hook subagent-stop"
}
]
diff --git a/plugins/omo/hooks/subagent-stop-verifying-lazycodex-executor-evidence.json b/plugins/omo/hooks/subagent-stop-verifying-lazycodex-executor-evidence.json
index 322b7792..eec4e41c 100644
--- a/plugins/omo/hooks/subagent-stop-verifying-lazycodex-executor-evidence.json
+++ b/plugins/omo/hooks/subagent-stop-verifying-lazycodex-executor-evidence.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/lazycodex-executor-verify/dist/cli.js\" hook subagent-stop",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Verifying LazyCodex Executor Evidence",
+ "statusMessage": "(OmO 4.18.0) Verifying LazyCodex Executor Evidence",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\lazycodex-executor-verify\\dist\\cli.js\" hook subagent-stop"
}
],
diff --git a/plugins/omo/hooks/user-prompt-submit-checking-ultrawork-trigger.json b/plugins/omo/hooks/user-prompt-submit-checking-ultrawork-trigger.json
index bac84097..29682b2a 100644
--- a/plugins/omo/hooks/user-prompt-submit-checking-ultrawork-trigger.json
+++ b/plugins/omo/hooks/user-prompt-submit-checking-ultrawork-trigger.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/ultrawork/dist/cli.js\" hook user-prompt-submit",
"timeout": 5,
- "statusMessage": "(OmO 4.17.1) Checking Ultrawork Trigger",
+ "statusMessage": "(OmO 4.18.0) Checking Ultrawork Trigger",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\ultrawork\\dist\\cli.js\" hook user-prompt-submit"
}
]
diff --git a/plugins/omo/hooks/user-prompt-submit-checking-ulw-loop-steering.json b/plugins/omo/hooks/user-prompt-submit-checking-ulw-loop-steering.json
index 181d9d1b..8cc5cf0c 100644
--- a/plugins/omo/hooks/user-prompt-submit-checking-ulw-loop-steering.json
+++ b/plugins/omo/hooks/user-prompt-submit-checking-ulw-loop-steering.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/ulw-loop/dist/cli.js\" hook user-prompt-submit",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Checking Ulw-Loop Steering",
+ "statusMessage": "(OmO 4.18.0) Checking Ulw-Loop Steering",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\ulw-loop\\dist\\cli.js\" hook user-prompt-submit"
}
]
diff --git a/plugins/omo/hooks/user-prompt-submit-loading-project-rules.json b/plugins/omo/hooks/user-prompt-submit-loading-project-rules.json
index b8a546f6..3a7f2165 100644
--- a/plugins/omo/hooks/user-prompt-submit-loading-project-rules.json
+++ b/plugins/omo/hooks/user-prompt-submit-loading-project-rules.json
@@ -7,7 +7,7 @@
"type": "command",
"command": "node \"${PLUGIN_ROOT}/components/rules/dist/cli.js\" hook user-prompt-submit",
"timeout": 10,
- "statusMessage": "(OmO 4.17.1) Loading Project Rules",
+ "statusMessage": "(OmO 4.18.0) Loading Project Rules",
"commandWindows": "powershell -NoProfile -ExecutionPolicy Bypass -File \"${PLUGIN_ROOT}\\components\\bootstrap\\scripts\\node-dispatch.ps1\" \"${PLUGIN_ROOT}\\components\\rules\\dist\\cli.js\" hook user-prompt-submit"
}
]
diff --git a/plugins/omo/package-lock.json b/plugins/omo/package-lock.json
index 49cea454..0d361815 100644
--- a/plugins/omo/package-lock.json
+++ b/plugins/omo/package-lock.json
@@ -1,12 +1,12 @@
{
"name": "@sisyphuslabs/omo-codex-plugin",
- "version": "4.17.1",
+ "version": "4.18.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "@sisyphuslabs/omo-codex-plugin",
- "version": "4.17.1",
+ "version": "4.18.0",
"workspaces": [
"components/codegraph",
"components/comment-checker",
@@ -93,7 +93,7 @@
},
"components/codegraph": {
"name": "@sisyphuslabs/codex-codegraph",
- "version": "4.17.1",
+ "version": "4.18.0",
"bin": {
"omo-codegraph": "dist/cli.js"
},
@@ -112,7 +112,7 @@
},
"components/comment-checker": {
"name": "@code-yeongyu/codex-comment-checker",
- "version": "4.17.1",
+ "version": "4.18.0",
"license": "MIT",
"bin": {
"omo-comment-checker": "dist/cli.js"
@@ -133,7 +133,7 @@
},
"components/git-bash": {
"name": "@sisyphuslabs/codex-git-bash-hook",
- "version": "4.17.1",
+ "version": "4.18.0",
"bin": {
"omo-git-bash-hook": "dist/cli.js"
},
@@ -148,7 +148,7 @@
},
"components/lazycodex-executor-verify": {
"name": "@code-yeongyu/codex-lazycodex-executor-verify",
- "version": "4.17.1",
+ "version": "4.18.0",
"license": "MIT",
"bin": {
"lazycodex-executor-verify": "dist/cli.js"
@@ -165,7 +165,7 @@
},
"components/lsp": {
"name": "@code-yeongyu/codex-lsp",
- "version": "4.17.1",
+ "version": "4.18.0",
"license": "MIT",
"dependencies": {
"@code-yeongyu/lsp-daemon": "file:../../../../lsp-daemon"
@@ -185,7 +185,7 @@
},
"components/rules": {
"name": "@code-yeongyu/codex-rules",
- "version": "4.17.1",
+ "version": "4.18.0",
"license": "MIT",
"dependencies": {
"picomatch": "^4.0.3"
@@ -207,7 +207,7 @@
},
"components/start-work-continuation": {
"name": "@code-yeongyu/codex-start-work-continuation",
- "version": "4.17.1",
+ "version": "4.18.0",
"license": "MIT",
"bin": {
"omo-start-work-continuation": "dist/cli.js"
@@ -224,7 +224,7 @@
},
"components/teammode": {
"name": "@sisyphuslabs/codex-teammode",
- "version": "4.17.1",
+ "version": "4.18.0",
"devDependencies": {
"@types/node": "^25.9.3",
"bun-types": "^1.3.1",
@@ -237,7 +237,7 @@
},
"components/telemetry": {
"name": "@code-yeongyu/codex-telemetry",
- "version": "4.17.1",
+ "version": "4.18.0",
"license": "MIT",
"bin": {
"omo-telemetry": "dist/cli.js"
@@ -255,7 +255,7 @@
},
"components/ultrawork": {
"name": "@code-yeongyu/codex-ultrawork",
- "version": "4.17.1",
+ "version": "4.18.0",
"license": "MIT",
"bin": {
"omo-ultrawork": "dist/cli.js"
@@ -273,7 +273,7 @@
},
"components/ulw-loop": {
"name": "@code-yeongyu/codex-ulw-loop",
- "version": "4.17.1",
+ "version": "4.18.0",
"license": "MIT",
"bin": {
"omo-ulw-loop": "dist/cli.js",
diff --git a/plugins/omo/package.json b/plugins/omo/package.json
index 633ea9e7..a3aef734 100644
--- a/plugins/omo/package.json
+++ b/plugins/omo/package.json
@@ -1,6 +1,6 @@
{
"name": "@sisyphuslabs/omo-codex-plugin",
- "version": "4.17.1",
+ "version": "4.18.0",
"description": "Aggregate Codex plugin root for OMO components.",
"type": "module",
"packageManager": "[email protected]",
diff --git a/plugins/omo/skills/frontend/SKILL.md b/plugins/omo/skills/frontend/SKILL.md
index 43860733..eb8d5202 100644
--- a/plugins/omo/skills/frontend/SKILL.md
+++ b/plugins/omo/skills/frontend/SKILL.md
@@ -32,7 +32,7 @@ Every implementation must choose one of these branches before UI code changes:
- **Embedded references:** use `references/design/_INDEX.md` to shortlist 2-3 plausible Layer B references, then read exactly one Layer A style skill and one Layer B reference in full — every line, no partial reads (they are 200-500 lines; a sliced read produces the flattened token set this gate exists to prevent). Log the shortlist, the pick, and why. Use `open-design` only when the curated set has no fit; add `ui-ux-db` lookups for palette/type/domain questions.
- **Lazyweb real-product screens:** READ `references/design/lazyweb.md` FIRST and run its recipe verbatim — do not improvise curl calls against lazyweb.com; the recipe mints its own anonymous token. Log the queries run, how many screens you actually VIEWED, and the layout grammar harvested — never pixel copies.
- **Imagen concept drafts:** generate 2-3 imagen concept drafts, each seeded with the loaded Layer A + Layer B tokens (palette, type, material); pick the strongest and treat the chosen draft as the reference-fidelity contract. Log the draft paths and the pick.
- Synthesize every lane into `DESIGN.md`. Treat sources as source material, not mood labels: extract tokens, layout grammar, component anatomy, interaction states, motion, and taste decisions, then recombine them into project-specific primitives. Never freestyle past the selected references, never copy logos or brand-specific copy. Then run the Primitive Showcase Gate (`references/design/README.md` Phase 0) before any product screen.
+ Synthesize every lane into `DESIGN.md`. Treat sources as source material, not mood labels: extract tokens, layout grammar, component anatomy, interaction states, motion, and taste decisions, then recombine them into project-specific primitives. Before laying out sections, inventory the content blocks and assign each a job — hook, explain, prove, compare, convert, navigate, retain — then order sections by the visitor's decision path, not by visual symmetry. Never freestyle past the selected references, never copy logos or brand-specific copy. Then run the Primitive Showcase Gate (`references/design/README.md` Phase 0) before any product screen.
3. **Existing project with `DESIGN.md` or a component system:** read it, follow it, and update it before implementation only when the requested work needs a new token, primitive, state, motion rule, accessibility constraint, accepted debt, or reference-fidelity requirement.
4. **Existing project with UI but no `DESIGN.md` and no reusable component layer:** STOP and ask the user one focused question: should you preserve the current look with copy-nearby styling, or extract a real `DESIGN.md` plus reusable components before continuing? Do not silently choose.
diff --git a/plugins/omo/skills/frontend/references/design/README.md b/plugins/omo/skills/frontend/references/design/README.md
index 3c82267b..5fece5c4 100644
--- a/plugins/omo/skills/frontend/references/design/README.md
+++ b/plugins/omo/skills/frontend/references/design/README.md
@@ -169,6 +169,12 @@ Triggers (mid-conversation, not initial): "you keep leaving placeholders", "stop
**Action:** Add `output-skill.md` on top of whatever is currently loaded. This stacks cleanly — it is purely about output completeness, not visual style.
+### Step 8 — Is the screen an app shell, not a scroll-the-page site?
+
+Triggers: dashboard, settings, mail/inbox, list-detail, command surface, split panes, fixed sidebar + scrolling body, admin console — or the user reports a layout that breaks when content gets long, empty, or unbroken (panel won't scroll, footer pushed off-screen, horizontal overflow on mobile).
+
+**Action:** Add `layout-skill.md` on top of whatever style skill you selected in Steps 1-2. It carries scroll-ownership doctrine, the two silently-failing CSS contracts (`min-block-size: 0` scroll shells, `minmax(min(…),100%)` grids), the named-primitive vocabulary, container-vs-viewport routing, and the content-stress matrix. It adds no visual direction — the style skill still owns taste. Skip it for pure scroll-the-document marketing pages, where `taste-skill` layout guidance already fits.
+
## Stacking rules (read this once, internalize it)
1. **At most one Layer A *style* skill at a time.** A layout cannot be both `minimalist-skill` and `brutalist-skill` simultaneously — they encode opposite spacing and typography philosophies. Pick one.
@@ -177,6 +183,7 @@ Triggers (mid-conversation, not initial): "you keep leaving placeholders", "stop
4. **`redesign-skill.md` replaces a style-skill** when the task is auditing, not building. Stack a Layer B brand if the user wants a specific direction.
5. **`image-to-code-skill.md` pairs with one imagegen skill** for the full flow.
6. **Layer B (brand DESIGN.md) is orthogonal to Layer A.** You can pair any Layer A skill with any Layer B brand. Use Layer B as the source of color/type/component tokens; let Layer A drive the execution discipline.
+7. **`layout-skill.md` stacks on top of any style skill** for app-shell / dashboard / split-pane work. It owns spatial structure and scroll ownership only — no visual direction — so it never conflicts with the style skill you picked.
## Anti-patterns — do not do these
@@ -218,6 +225,8 @@ Once references are loaded, before writing any UI code:
| "Generate a brand identity board for {company}" | `imagegen-brandkit.md` |
| "Stop using placeholders" | Add `output-skill.md` to current stack |
| "Also output a DESIGN.md doc" | Add `stitch-skill.md` to current stack |
+| "Build a dashboard / settings / inbox / app shell" | one style skill (usually `taste-skill.md`) + `layout-skill.md` |
+| "Panel won't scroll / footer pushed off-screen / mobile overflow" | Add `layout-skill.md` to current stack |
## Phase Final — Design QA (MANDATORY, runs after implementation)
diff --git a/plugins/omo/skills/frontend/references/design/design-system-architecture.md b/plugins/omo/skills/frontend/references/design/design-system-architecture.md
index 4dc0795f..4f754b01 100644
--- a/plugins/omo/skills/frontend/references/design/design-system-architecture.md
+++ b/plugins/omo/skills/frontend/references/design/design-system-architecture.md
@@ -116,7 +116,7 @@ All spacing derives from a base of **4px**.
- Breakpoints: sm 640px, md 768px, lg 1024px, xl 1280px, 2xl 1536px
### Rules
-- No magic numbers. Every spacing value maps to a token.
+- Tokenize design *intent* — spacing steps, content width, gutters, section gaps, density steps. Keep browser *mechanics* raw: `auto`, `%`, `min-content`, `max-content`, `fit-content`, `clamp()`, viewport/container units, intrinsic sizing. A `clamp(1rem, 4vw, 2rem)` gap or a `minmax(min(16rem, 100%), 1fr)` track is mechanics, not a magic number — do not force it into a token.
- Asymmetric spacing is intentional, not accidental — document why.
## 5. Components
@@ -130,6 +130,7 @@ Document reusable patterns before implementation for greenfield work, and as the
- **States**: default, hover, active, focus, disabled, loading, empty, error
- **Accessibility**: keyboard, ARIA, contrast
- **Motion**: entry/exit animations
+- **Layout**: spatial primitive (stack / cluster / sidebar / grid / shell…) and, if the component scrolls or pins anything, its scroll owner
Greenfield starts with the primitives you are about to build, assembled from
the selected references' component anatomy and adapted to the user's product.
@@ -214,13 +215,14 @@ After every component implementation, check:
- [ ] All colors reference tokens from Section 2. No raw hex outside `DESIGN.md`.
- [ ] All font sizes match Section 3 scale. No arbitrary sizes.
-- [ ] All spacing values are multiples of `--space-1` (4px). No magic numbers.
+- [ ] Spacing intent maps to a token (Section 4); browser mechanics (`clamp()`, intrinsic sizing, container units) stay raw. No arbitrary px.
- [ ] Interactive elements have all required states from Section 5 and Section 6.
- [ ] Depth treatment matches the chosen strategy from Section 7.
- [ ] Component reused 2+ times? Documented in Section 5.
- [ ] Motion follows the timing table. No arbitrary durations.
- [ ] Component visual QA passed for each primitive and required state before product screens were composed.
- [ ] Section 8 accessibility constraints hold for the new component; any new debt is recorded in Section 8, not silently accepted.
+- [ ] Survives content stress: empty, long label, unbroken string. Reflows to one readable column at 375px with no horizontal scroll of primary content.
## Memory Management
diff --git a/plugins/omo/skills/frontend/references/design/layout-skill.md b/plugins/omo/skills/frontend/references/design/layout-skill.md
new file mode 100644
index 00000000..a6555deb
--- /dev/null
+++ b/plugins/omo/skills/frontend/references/design/layout-skill.md
@@ -0,0 +1,107 @@
+---
+name: layout-skill
+description: "Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero visual taste. Load it alongside a style skill; it does not replace one."
+---
+
+# Layout Mechanics
+
+Style skills decide how a surface looks. This file decides how it is *built to hold content* — what scrolls, what stays fixed, how regions shrink, and which layouts survive real data. It stacks on top of any Layer A style skill (`taste-skill`, `minimalist-skill`, `soft-skill`, `brutalist-skill`, `gpt-tasteskill`) and any Layer B brand. It adds ZERO visual direction — color, type, shadow, radius, and motion still come from the style skill and `DESIGN.md`.
+
+Load this when the screen is an **application shell**, not a scroll-the-whole-document marketing page: dashboards, settings, list-detail, mail/inbox, command surfaces, split panes, sidebars — or when a page that looked fine breaks the moment content gets long, empty, or unbroken.
+
+## 1. Scroll ownership — decide this BEFORE writing layout CSS
+
+The single most common agent-built layout bug is an app shell where the wrong thing scrolls: the whole page scrolls when only a panel should, two panels fight over the scrollbar, or a "fixed" header scrolls away. Prevent it by naming ownership up front, in `DESIGN.md` and in the component:
+
+- **What scrolls?** Name the ONE element that owns vertical scroll for this region.
+- **What stays fixed?** Header, sidebar, footer, toolbar — list them.
+- **Where is height determined?** The scroll container needs a bounded height ancestor, or it will grow instead of scroll.
+
+Rules:
+
+- **One scroll container per region unless each extra one has a named job.** Nested scrollbars with no declared responsibility are a defect — the user loses track of what a wheel/trackpad gesture will move.
+- Full-height shells are bounded by `100dvh`/`100dvb` (dynamic viewport units), never `100vh` — `vh` causes the iOS Safari address-bar jump.
+- A sticky element (`position: sticky`) follows document scroll; a fixed shell region (grid row/column with `overflow: auto` body) owns its own scroll. Do not mix the two models in one region without reason.
+
+## 2. The two CSS contracts agents get wrong
+
+These two are worth memorizing verbatim. They fail *silently* — the layout looks right until content arrives.
+
+**Bounded scroll shell** (fixed header/footer, scrolling body):
+
+```css
+.shell {
+ display: grid;
+ grid-template-rows: auto minmax(0, 1fr) auto; /* header / body / footer */
+ max-block-size: 100dvb;
+}
+.shell__body {
+ min-block-size: 0; /* WITHOUT THIS the grid child refuses to shrink and overflow never fires */
+ overflow: auto;
+}
+```
+
+The `min-block-size: 0` (or `min-height: 0`) on the scroll child is the fix for "why won't my panel scroll — it just pushes the footer off-screen." A grid/flex child's default `min-*-size: auto` refuses to shrink below its content. The same applies to a flex column: the scrollable child needs `min-height: 0`.
+
+**Overflow-safe intrinsic grid** (repeat as many columns as fit, no media queries):
+
+```css
+.grid {
+ display: grid;
+ gap: var(--gap);
+ grid-template-columns: repeat(auto-fit, minmax(min(16rem, 100%), 1fr));
+}
+```
+
+The inner `min(16rem, 100%)` is load-bearing: plain `minmax(16rem, 1fr)` forces a 16rem track even when the container is 12rem wide, causing horizontal overflow on narrow screens. `min(…, 100%)` lets the track collapse below its floor when space is genuinely tight. Use `auto-fit` to stretch the last row, `auto-fill` to keep empty tracks.
+
+## 3. Named layout primitives (shared vocabulary)
+
+Build shells from these named primitives instead of ad-hoc fl/grid. Naming them makes `DESIGN.md` Section 5 and subagent handoffs precise ("wrap it in a `sidebar` with a 20rem aside" beats "put it on the left, roughly"). Lineage: Every Layout + web.dev one-line layouts.
+
+| Primitive | Spatial job | Core mechanic |
+|---|---|---|
+| **stack** | Vertical rhythm between siblings | flex column + `gap`, or `> * + *` margin |
+| **cluster** | Wrapping row of items (tags, actions) | `flex-wrap: wrap` + `gap`; wraps before overflow |
+| **content-limiter** | Readable prose measure inside a fluid parent | `max-inline-size: ~65ch; margin-inline: auto` |
+| **sidebar** | Narrow aside + fluid main, wraps when tight | flex; aside fixed basis, main `min-inline-size` floor, both `flex-wrap` |
+| **switcher** | N equal regions: row when roomy, stack when tight, NO breakpoint | flex + `min()` basis so it flips at a content threshold |
+| **cover** | Centered region between optional header/footer, min viewport tall | grid rows `auto 1fr auto`, `min-block-size: 100dvb` |
+| **frame** | Media held to an aspect ratio | `aspect-ratio` + `object-fit: cover` |
+| **reel** | Row that scrolls horizontally instead of wrapping | `overflow-inline: auto` + `scroll-snap`; declare keyboard access |
+| **imposter** | Overlay centered over a parent without changing document order | `position: absolute` + translate; do not use to reorder focus |
+| **overlay-stack** | Several layers intentionally in one cell | single grid cell, all children `grid-area: 1/1` |
+| **scroll-body-shell** | Fixed shell regions, only the body scrolls | §2 bounded scroll shell |
+| **fixed-sidenav-shell** | Side nav stays put, main scrolls | grid columns `auto 1fr`, main is the scroll owner |
+| **list-detail** | Explorable list beside its detail region | two-column grid, each pane's scroll ownership named |
+| **sticky-aside** | Support content stays visible during a long read | `position: sticky; top:` on the aside, document scroll |
+
+## 4. Container-local vs viewport-level responsiveness
+
+Ask **what the layout is responding to** before reaching for a breakpoint:
+
+- The component should adapt to *its own available width* (a card that's wide in main but narrow in a rail) → wrap it in `container-type: inline-size` and use `@container`. This is correct far more often than agents assume, because a component rarely knows the viewport it lands in.
+- The *page frame itself* changes (sidebar collapses, columns drop) → `@media`.
+
+Prefer intrinsic adaptation (`switcher`, `sidebar`, intrinsic grid, `clamp()`) over any query — the best breakpoint is often none. Use breakpoint *names* for layout states, never device names (`--bp-wide`, not `--bp-ipad`).
+
+## 5. Recipes are spatial models, not product categories
+
+Choose a layout by the screen's spatial shape, not its product label. A settings page and a docs app both want `fixed-sidenav-shell`; a support inbox and a file browser both want `list-detail`; a metrics view and a photo gallery both want an intrinsic grid. Do not invent a bespoke "dashboard layout" when `page-grid + intrinsic grid + cluster` already covers it — and do not force marketing-page structure (hero, zigzag, bento) onto a task app.
+
+## 6. Content stress — the layout is not done until it survives this
+
+Landing pages fail on taste; app shells fail on *content*. Before declaring any layout done, stress every region against:
+
+- **Empty** — no rows, no avatar, no value. Does the region collapse gracefully or leave a broken frame?
+- **Long label** — a 40-char name in a 12-char slot. Truncate (`text-overflow: ellipsis`) or wrap by design, never by accident.
+- **Long paragraph** — does the measure stay readable, or does text run 200 chars wide?
+- **Unbroken string** — a URL or token with no spaces. Needs `overflow-wrap: anywhere` / `min-inline-size: 0`, or it forces horizontal scroll.
+- **Reflow** — at 375px width the layout reflows to a single readable column with NO horizontal scrollbar. Two-dimensional scrolling of primary content is a fail.
+- **Direction** — if the app supports RTL, the layout uses logical properties (`margin-inline`, `inset-inline-start`) so it mirrors correctly.
+
+A layout that only holds the happy-path mock is not finished. Drive these states in `/visual-qa` alongside the interaction states the style skill requires.
+
+## Boundary
+
+This file owns spatial structure only. It never sets color, typography, shadow, radius, or motion values — those trace to `DESIGN.md` and the loaded style skill. If you find yourself adding a brand color to a layout primitive, stop: the primitive stays layout-only and the styling wraps or composes around it.
diff --git a/plugins/omo/skills/programming/SKILL.md b/plugins/omo/skills/programming/SKILL.md
index fbfd7cd9..7193ca2f 100644
--- a/plugins/omo/skills/programming/SKILL.md
+++ b/plugins/omo/skills/programming/SKILL.md
@@ -104,9 +104,17 @@ Mocks are a last resort, not a default. The priority order:
- **Deterministic**: no `sleep`, no wall-clock dependence, no order dependence (`-shuffle=on`, pytest-randomly, vitest random seed). Inject a `Clock`. Subscribe to the event, do not poll for it. Time-based flake is a bug, not a test issue.
- **Isolated**: every test starts from a known fixture and tears down. `t.TempDir()`, `t.Setenv()`, transactional rollback for DB tests. Two tests passing individually but failing together is a fixture leak — fix it immediately.
-### Prompt tests follow the same rule
+### Prompt tests: NEVER assert prose
-When tests cover LLM prompts or agent outputs, assert on **parsed structure, decisions, or rule data**, never on exact prompt strings. Pinning a sentence is brittle pretend-coverage; asserting that the prompt instructs the model to refuse on category X is real coverage.
+**FORBIDDEN — NO EXCEPTIONS: a test MUST NOT assert natural-language prompt text.** `expect(prompt).toContain("based on GPT-5.6")`, `not.toContain("old wording")`, `toMatchSnapshot()` on prose, grepping a sentence fragment — every one of these is pretend-coverage. It stays green while the behavior it claims to guard breaks, then blocks every legitimate rewording until someone bumps the pinned string. A reviewer MUST block it as HIGH; deleting such a test is a fix, not a coverage loss. "A nearby test already does it" is not a defense — that test is the disease, not the convention.
+
+Assert ONLY what a machine consumes:
+
+- the builder's routing decision — `expect(getPromptSource(model)).toBe("gpt-5-6")`, never the sentence that routing produces
+- a structural token the runtime dispatches on — a tool name, a tag like `<agent-identity>`, a parsed frontmatter field
+- the conditional the code enforces — skill loaded → tool present; `verbose=false` → directive absent
+
+If no machine consumes the text, there is no seam: write NO test and say so in the PR; review guards prose. When you DELEGATE test-writing, hand the child the behavior the test must distinguish ("fails if override precedence breaks"), never a ready-made assertion string, prompt fragment, or marker to copy — a prescribed mechanism that is wrong gets implemented faithfully, and the error ships with a green suite.
### Anti-patterns the skill rejects
@@ -119,6 +127,8 @@ When tests cover LLM prompts or agent outputs, assert on **parsed structure, dec
| Snapshot tests for everything | Locks formatting, not behavior. | Snapshots for *structure* (CLI help, JSON shape). Assertions for *behavior*. |
| Removing a failing test to "unblock CI" | You just deleted a bug report. | Fix the code or fix the test — never delete to silence. |
| `assert result is not None` and stopping there | Passes when result is garbage. | Assert the *value*, not its existence. |
+| Expected value derived from the output under test (`expect(config.prompt).toBe(getPrompt(config.model))` when the criterion is about `config.prompt`) | Recomputes a projection of the output and compares it to itself — passes even when the artifact is built from the wrong input. | Derive the expected value from the test's *input*: `expect(config.prompt).toBe(getPrompt(inputModel))` (independent known-good builder fed the fixture's input), or a stable builder routing decision. |
+| Override/precedence fixture equal to its fallback (override == system default) | The assertion passes whether or not the code honored the override — precedence is never exercised. | Make every value the code must select, preserve, or override differ from its fallback. Prove it: temporarily force the regression the test names, watch it fail, revert. |
| Single happy-path E2E, no edges | Most bugs live on edges. | Edges are unit-test territory — but include at least one E2E that exercises an error path. |
---
diff --git a/plugins/omo/skills/ultrawork/SKILL.md b/plugins/omo/skills/ultrawork/SKILL.md
index 6dd9c309..6cab3364 100644
--- a/plugins/omo/skills/ultrawork/SKILL.md
+++ b/plugins/omo/skills/ultrawork/SKILL.md
@@ -128,9 +128,13 @@ are delegating never justify a planner: plan directly in the notepad.
Never spawn `plan` before the discovery wave has returned.
## 1. Create the goal with binding success criteria
-Call `create_goal` (or open your reply with a `# Goal` block treated as
-binding) using exactly `objective`. Do not include `status`. Goals are
-unlimited; never invent a numeric budget or limit.
+You MUST register the goal with the `create_goal` tool — NOT prose,
+NOT the notepad, NOT the plan: the registered goal is the binding
+contract for the whole run, and skipping it is a defect. Call it with
+exactly `objective`; do not include `status`. Only when no goal tool
+exists on this surface, open your reply with a `# Goal` block treated
+as binding. Goals are unlimited; never invent a numeric budget or
+limit.
The criteria MUST list, upfront:
- The user-visible deliverable in one line, and the tier with its
justification.
@@ -143,6 +147,9 @@ The criteria MUST list, upfront:
- For each criterion, the failing-first proof (test id or scenario)
that will be captured RED BEFORE the implementation and GREEN after.
Evidence added after the green code does NOT satisfy this.
+- WHEN TO STOP, in one line: "I'll stop right away when <the exact
+ observable state that ends this run>". The Stop rules bind to this
+ line — the moment it holds, you stop.
These scenarios are the contract. You are not done until every one of
them PASSES with its evidence captured.
@@ -243,6 +250,18 @@ Until every success criterion PASSES with its evidence captured:
scenario captured failing when no test seam exists. It must fail
for the RIGHT reason (not a syntax error, not a missing import).
Paste RED output into the notepad. No production code yet.
+ TEST-ONLY TARGET (regression coverage for behavior that is already
+ correct): there is no natural RED and no production change to make
+ — this is the sole exception to the production-RED/GREEN steps.
+ Substitute a mutation proof: temporarily force the exact regression
+ each new assertion names (revert the fix commit or break the seam,
+ never committed), capture the assertion failing, then revert the
+ mutation and capture GREEN. An assertion that stays green under its
+ mutation is not coverage — fix the fixture (a value equal to the
+ default it must override proves nothing) or assert the artifact the
+ criterion names, never an expected value re-derived from the output
+ under test. Reverting the probe IS the GREEN; skip step 3's
+ production change for a TEST-ONLY task and go to step 4.
PROSE TARGET (prompt, SKILL.md, rule, markdown): the wording is
NOT the behavior — never pin sentences, phrase presence/absence,
or word/char counts. PIN only a machine-consumed value (parsed
@@ -251,7 +270,8 @@ Until every success criterion PASSES with its evidence captured:
two shipped copies. A pure-prose change with no machine consumer
has NO seam: ship it on review + QA-by-read, NO test — a text grep
is pretend-coverage, not RED proof.
-3. GREEN: write the SMALLEST production change that flips RED→GREEN.
+3. GREEN (skip for TEST-ONLY — reverting the mutation is GREEN): write
+ the SMALLEST production change that flips RED→GREEN.
Before GREEN work that depends on external review, PR, issue, or
branch state, refresh current branch/PR/issue state and preserve existing ordering/policy;
separate compatibility detection from policy changes unless the goal
@@ -389,10 +409,11 @@ message + present for approval.
revert, capture the proof failing, then redo the change. Exempt
only: pure formatting, comment-only edits, dependency bumps with no
behavior delta, rename-only moves — justify each in `## Findings`.
-- A test that mirrors its implementation — asserting mocks were
- called, pinning a constant, or unable to fail under any plausible
- regression — is NOT evidence. Prefer a real-surface proof with no
- new test over a tautological test.
+- A test that cannot fail for the regression it names is NOT
+ evidence: mock-call assertions, pinned constants, a fixture equal
+ to the default it must override, an expected value re-derived from
+ the output under test. Prefer a real-surface proof with no new
+ test over a tautological one.
- Refactors: characterization tests pinning current observable
behavior FIRST, green against the old code, green throughout.
- Smallest correct change. No drive-by refactors.
@@ -414,9 +435,15 @@ message + present for approval.
- After each result, ask whether the user's core request can now be
answered with useful evidence in hand. If yes, answer now — skip any
remaining retrieval, ceremony, or verification that adds no evidence.
-- Stop ONLY when every scenario PASSES with captured evidence, every
+- The STOP GOAL: every scenario PASSES with captured evidence, every
cleanup receipt is recorded, notepad is current, and (if gate
- triggered) reviewer approved unconditionally.
+ triggered) reviewer approved unconditionally. Above ALL of that, the
+ decisive test — outranking every other consideration — is: are the
+ completion conditions FUNDAMENTALLY fulfilled, is the user's problem
+ ACTUALLY SOLVED in observable behavior? If no, you are NOT done,
+ whatever the ledger says. If yes, deliver the final message and STOP
+ — no hesitation, no extra verification pass, no polish loop. Work
+ past the stop goal is scope creep, not diligence.
- Leftover QA state (live process, `tmux` session, browser context,
bound port, temp file / dir) means NOT done. Tear it down, record
the receipt, then continue.
diff --git a/plugins/omo/skills/ulw-loop/SKILL.md b/plugins/omo/skills/ulw-loop/SKILL.md
index fe6737c3..29b36dfa 100644
--- a/plugins/omo/skills/ulw-loop/SKILL.md
+++ b/plugins/omo/skills/ulw-loop/SKILL.md
@@ -14,7 +14,7 @@ This skill is intentionally compact. The full workflow lives in `references/full
## Required First Steps
1. Open `references/full-workflow.md`.
-2. Read through **Bootstrap** (including its tier triage), **Execution Loop**, and the **Manual-QA channels** table before running any ULW command or recording evidence.
+2. Read through **Bootstrap** (including its tier triage), **Execution Loop**, the **Manual-QA channels** table, and the **Stop Rules** before running any ULW command or recording evidence.
3. If the task has code edits, tests, QA, or commit work, follow the full workflow's delegation and evidence rules. Tests alone never prove done.
## Non-Negotiables
diff --git a/plugins/omo/skills/ulw-loop/references/full-workflow.md b/plugins/omo/skills/ulw-loop/references/full-workflow.md
index 634f5bfe..9d4972fa 100644
--- a/plugins/omo/skills/ulw-loop/references/full-workflow.md
+++ b/plugins/omo/skills/ulw-loop/references/full-workflow.md
@@ -129,7 +129,7 @@ First survey available skills: read every loosely-relevant skill's description,
Then run tier triage per goal — rigor (LIGHT/HEAVY below) and shape (`delivery` default, or `research` when the deliverable is a cited answer, not an artifact) — and record both in an `annotate_ledger` steering entry. Default is LIGHT — a narrow change inside existing layers. Take HEAVY only on a fact you can point to: a new module / abstraction / domain model; auth, security, or session; an external integration; a DB schema or migration; concurrency, transaction boundaries, or cache invalidation; a cross-domain refactor; or the user signaled care or demanded review. When unsure, take HEAVY; upgrade the moment a HEAVY fact surfaces, never downgrade mid-run.
Planning depends on unresolved design uncertainty, not the rigor tier: after discovery, spawn the `plan` agent only when unclear boundaries, competing decompositions, or uncertain dependency ordering remain; otherwise plan directly, including for HEAVY goals with a known procedure. HEAVY goals carry 3+ successCriteria covering happy path, edge, regression, and adversarial risk. LIGHT goals carry 1-2 successCriteria (happy path + the riskiest edge) with one real-surface proof of the deliverable.
Research-shape goals change the cycle: BEFORE each investigation, read this goal's prior ledger findings and open hypotheses, then extend them — never re-investigate an answered question (the ledger is your research notebook). Record findings via `annotate_ledger` with their source (`file:line`, command output, doc URL) as `--evidence`. Track hypotheses as `HYPOTHESIS[id]: <claim> | status: open`, flipped to `confirmed`/`refuted` only on an observed source. A research criterion passes on a cited answer — skip QA-channel, cleanup, and commit, but keep source-observability (never "looks correct"). Keep hypotheses inside the user's stated question; a scope-widening one is an `add_subgoal` proposal you surface, never silent creep. For a `research`-shape goal you MAY load `ulw-research` without hesitation — otherwise explicit-request-only, a research-shape goal IS that explicit demand. Research-only: never for a `delivery` goal. It composes with the librarian routing above — `ulw-research` for saturation (many parallel sources, recursive expansion), a single `librarian` for one lookup.
-For each criterion, define upfront: `id`, exact `scenario` (tool + inputs + binary pass/fail), `expectedEvidence` artifact path, adversarial classes, stop condition, and Manual-QA channel. Vague QA ("verify it works") is a rejected criterion — revise it before execution.
+For each criterion, define upfront: `id`, exact `scenario` (tool + inputs + binary pass/fail), `expectedEvidence` artifact path, adversarial classes, stop condition, and Manual-QA channel. Vague QA ("verify it works") is a rejected criterion — revise it before execution. Every goal also declares, in one line, WHEN TO STOP: "stop right away when <the exact observable state that ends this goal>". A goal without that line is rejected — revise it before execution; the Stop Rules bind to it.
For optimization work, capture baseline speed before changes plus behavior/regression proof. Every attempt records speed, behavior/regression, and the keep/revert/iterate decision.
A criterion's adversarial classes are the ultraqa classes a fact about the change triggers: malformed input, prompt injection, cancel/resume, stale state, dirty worktree, hung or long commands, flaky tests, misleading success output, repeated interruptions. Record untriggered classes as not-applicable in one line.
Use channel-table evidence verbs — not vibes.
@@ -151,7 +151,7 @@ Loop per goal. Cap at 5 cycles per goal. Cap identical same-criterion failures a
| get_goal result | action |
|-----------------|--------|
-| no active goal | Call `create_goal` with objective only from `instruction.json.objective`; do not copy lifecycle fields such as `status`. |
+| no active goal | You MUST call `create_goal` — goal registration goes through the tool, never prose — with objective only from `instruction.json.objective`; do not copy lifecycle fields such as `status`. |
| same aggregate objective active | Continue the current ulw-loop story. |
| different goal active | STOP. Checkpoint blocked and surface the conflict. |
4. If retrying failed work, run `omo ulw-loop complete-goals --retry-failed --json`.
@@ -160,7 +160,7 @@ Loop per goal. Cap at 5 cycles per goal. Cap identical same-criterion failures a
### Per-Criterion Cycle
1. PLAN: read `criterion.scenario`, `criterion.expectedEvidence`, prior ledger entries, and safety bounds. Identify which tasks in the current wave are independent.
2. Register atomic todos via `update_plan` — one ultra-granular step per action, `path: <action> for <criterion> - verify by <check>`. Call `update_plan` on every transition (start → `in_progress`, finish → `completed`); exactly one `in_progress`, mark completed immediately, never batch, never let the rendered plan lag behind reality.
-3. DELEGATE-IN-PARALLEL: dispatch every independent task in the wave at once via right-sized `spawn_agent` workers (Delegation table). Each worker captures evidence failing-first: when the task touches EXISTING behavior, PIN it FIRST — a characterization test that asserts the current observable behavior and PASSES on the unchanged code, as rigorous as the new-behavior scenario (exact inputs, exact observable, exact assertion). Then RED through the cheapest faithful channel — a unit test where a seam exists, an integration/e2e test where the behavior lives in wiring, or the criterion's scenario captured failing when no test seam exists — failing for the RIGHT reason (no syntax/import error). A test that mirrors its implementation (mock-call assertions, pinned constants, cannot fail under plausible regression) is not evidence; use the scenario as the failing proof instead. **When the target is PROSE (a prompt, `SKILL.md`, rule, or markdown/instruction file), the "observable behavior" is NOT the wording** — never pin sentences, phrase presence/absence, or word/char counts. PIN only a value a MACHINE consumes (a parsed frontmatter field, a sentinel token a hook greps, the doc's JSON sample run through its real validator), or guard two shipped copies with one `toBe` equality; a pure-prose change with no machine consumer has NO seam, so ship it on review + Manual-QA-by-read with NO automated test (a text grep there is pretend-coverage, not a RED proof). Then the SMALLEST GREEN change; before GREEN work that depends on external review, PR, issue, or branch state, refresh current branch/PR/issue state, preserve existing ordering/policy, and separate compatibility detection from policy changes unless the goal explicitly asks to change policy. A GREEN far larger than the criterion implies means the proof was too coarse — instruct a split. Serialize only on a NAMED dependency.
+3. DELEGATE-IN-PARALLEL: dispatch every independent task in the wave at once via right-sized `spawn_agent` workers (Delegation table). Each worker captures evidence failing-first: when the task touches EXISTING behavior, PIN it FIRST — a characterization test that asserts the current observable behavior and PASSES on the unchanged code, as rigorous as the new-behavior scenario (exact inputs, exact observable, exact assertion). Then RED through the cheapest faithful channel — a unit test where a seam exists, an integration/e2e test where the behavior lives in wiring, or the criterion's scenario captured failing when no test seam exists — failing for the RIGHT reason (no syntax/import error). A test that cannot fail for the regression it names (mock-call assertions, pinned constants, a fixture equal to the default it must override, an expected value re-derived from the output under test) is not evidence; use the scenario as the failing proof instead. TEST-ONLY tasks (regression coverage for behavior that is already correct) have no natural RED — require a mutation proof: temporarily force the exact regression each new assertion names, capture the assertion failing, revert the mutation, capture GREEN; an assertion that stays green under its mutation is not coverage. **When the target is PROSE (a prompt, `SKILL.md`, rule, or markdown/instruction file), the "observable behavior" is NOT the wording** — never pin sentences, phrase presence/absence, or word/char counts. PIN only a value a MACHINE consumes (a parsed frontmatter field, a sentinel token a hook greps, the doc's JSON sample run through its real validator), or guard two shipped copies with one `toBe` equality; a pure-prose change with no machine consumer has NO seam, so ship it on review + Manual-QA-by-read with NO automated test (a text grep there is pretend-coverage, not a RED proof). Then the SMALLEST GREEN change (none for a TEST-ONLY task — reverting the probe is GREEN; go to integration); before GREEN work that depends on external review, PR, issue, or branch state, refresh current branch/PR/issue state, preserve existing ordering/policy, and separate compatibility detection from policy changes unless the goal explicitly asks to change policy. A GREEN far larger than the criterion implies means the proof was too coarse — instruct a split. Serialize only on a NAMED dependency.
4. INTEGRATE + CRITICAL SELF-QA + GIT CHECKPOINT (EVERY WORKER RETURN): do NOT trust the worker's report. Read the diff yourself, re-run its tests, and run LSP diagnostics on the changed files. Treat "done" as a claim to disprove. If the diff drifts, the test is hollow, or evidence is missing, RESPAWN the worker with the specific failure context. Once the work unit is verified, use `git-master` before staging: inspect recent repository commits and touched-path history to infer commit language, Conventional Commit scope, message shape, and unit size. Stage only that unit's files and commit in the observed style; do not carry verified work forward into a later omnibus commit. If no git-tracked files changed or committing is unsafe, record the no-commit reason as evidence. Forward every finding/learning to subsequent workers.
5. EXECUTE-AS-SCENARIO: ACTUALLY run the Manual-QA scenario the criterion named (channel table above). Run it yourself for the orchestrator check; for heavier flows dispatch a dedicated QA execution worker (`lazycodex-worker-medium` by default; `lazycodex-worker-high` when the QA flow itself is hard) whose ONLY job is to drive the channel and write the artifact to the named evidence path. If the scenario FAILS, respawn the implementing worker with the captured failure — do not hand-patch around it.
6. CAPTURE: collect the observable artifact path: transcript, stdout, screenshot, assertion, status+body, diff, or parsed dump. No artifact written at the evidence path — not done; record BLOCKED and respawn QA.
@@ -239,7 +239,7 @@ Structured prompt directives accepted: `OMO_ULW_LOOP_STEER: { ... }`, `omo.ulw-l
15. Every verified work unit that touched git-tracked files must leave either an atomic `git-master`-style commit hash or explicit no-commit blocker evidence before the next unit starts.
## Stop Rules
-- All goals complete plus every plan criterion `pass` plus final quality gate clean: DONE.
+- STOP GOAL: all goals complete plus every plan criterion `pass` plus final quality gate clean. The decisive test — outranking every other consideration — is whether the completion conditions are FUNDAMENTALLY fulfilled and the user's problem ACTUALLY SOLVED in observable behavior; a `pass` ledger never substitutes for it. The moment both hold, checkpoint, report, and STOP — no extra review cycles, no evidence regeneration, no polish.
- 3x same criterion failure: checkpoint failed, surface diagnosis.
- 5 cycles on one goal without required criteria passing: checkpoint failed, surface.
- Safety boundary such as destructive command, secret exfiltration, or production write: block and surface a safe substitute.