@r1z4x/tezgah 1.11.0 → 1.14.0

package/docs/status-line.md

@@ -15,8 +15,8 @@ host-neutrally by `health_segments()` (`hooks/tezgah_context.py::health_segments
 groups (`hooks/tezgah_context.py::render_line`). The group is *data on each segment*: a renderer building its
 own line from `--json` separates on `seg.group` and matches `render_line()`
 without a second copy of the partition (`hooks/tezgah_context.py::health_segments`) — opencode and dsh do exactly
-that (hosts/opencode/tui/tezgah-tui.tsx:108-111,
-hosts/dsh/statusline/lib/client.js:86-90).
+that (`TezgahBar` in `hosts/opencode/tui/tezgah-tui.tsx`,
+`TezgahStatusLine` in `hosts/dsh/statusline/lib/client.js`).
 
 | group | members | why together |
 |---|---|---|
@@ -173,7 +173,12 @@ group separators stay identical for every extension. An extension never has to
 know the gutter. It must name `text` and `state`. tezgah fills a missing `glyph`
 from the state's own mark, so a chip reads like a built-in. The per-extension cap
 (`MAX_SEGMENTS`) and the hard timeout (`timeout_ms`, default
-`DEFAULT_TIMEOUT_MS`) bound one row.
+`DEFAULT_TIMEOUT_MS`) bound one row. The command prints one JSON object whose
+`segments` key holds that list. tezgah reads a bare list on stdout as malformed output:
+
+```json
+{"segments": [{"key": "cyber-eng", "state": "on", "text": "eng"}]}
+```
 
 It is a subprocess and not an import on purpose. The extension is the user's
 repo, in whatever language, and may be slow or broken. A bounded child keeps a
@@ -229,10 +234,13 @@ python is asked (`hooks/tezgah_context.py::skill_read_kind`). A surface that can
 was never opened", so it declares what it can see and those marks render `info`
 (dim, no glyph) instead of `ready` (`observable`, `hooks/tezgah_context.py::health_segments`; the set constant
 `TOOL_USE_MEASURES`, `hooks/tezgah_context.py::TOOL_USE_MEASURES`). The `--observable=` flag carries it on the CLI
-(`bin/tezgah-status::main`). Two callers pass the tool-use set: Cursor's
-status line (statusline.py:117-121) and Codex, which renders the line plain into
-`systemMessage` (`hosts/codex/hook.py::main`); dsh passes the literal flag
-string (hosts/dsh/statusline/lib/index.js:16-19,84,96), which names the five marks its
+(`bin/tezgah-status::main`). Every host whose line reads the store and cannot see
+a skill read passes the tool-use set: the status line for Cursor, Qwen, Droid, Copilot and Antigravity
+(`statusline.py::HOST`, `statusline.py::observable`), and Codex, Command Code
+and Gemini, which render the line plain into `systemMessage`
+(`hosts/codex/hook.py::main`, `hosts/commandcode/hook.py::status`,
+`hosts/gemini/hook.py::status`); dsh passes the literal flag
+string (`OBSERVABLE` in `hosts/dsh/statusline/lib/index.js`), which names the five marks its
 own hook can record - `judge` included, since dsh wires the same PostToolUse hook
 every other host does. The set is what a host can write, not what it happens to
 have written: a mark the literal omits reads `info` there rather than a claim.
@@ -248,15 +256,15 @@ the five kinds are ever written (`hooks/tezgah_context.py::record`).
 
 Writers: the shared PostToolUse hook `hooks/projects-posttooluse.py` — `graph` from
 an MCP tool name, else the shell tokenizer's answer, which counts a tool only when
-the command really ran it (34-38,84) and is the one writer that can earn `judge`
+the command really ran it (`hooks/projects-posttooluse.py::used_kind`) and is the one writer that can earn `judge`
 (a run of `bin/tezgah-triage` or `bin/tezgah-docs`, `shell_kind`, `hooks/tezgah_context.py::shell_kind`)
 — plus `hooks/projects-auto-init.py::main`
 (`orch` on subagent start), `hosts/codex/hook.py::main`,
-`hosts/cursor/hook.py::dispatch`, hosts/opencode/plugins/tezgah.js:2167-2174,
-hosts/opencode/plugins/tezgah.js:2725, `hosts/omp/hook.py::handle`. Both Claude (hooks/hooks.json) and dsh
+`hosts/cursor/hook.py::dispatch`, `record` in `hosts/opencode/plugins/tezgah.js`,
+`hosts/omp/hook.py::handle`. Both Claude (hooks/hooks.json) and dsh
 (hosts/dsh/hooks.json) wire PostToolUse to that one shared hook, which is how dsh
 gets any used mark at all: with no local transcript, the store is the only channel
-its line has (hooks/projects-posttooluse.py:45-49).
+its line has (`hooks/projects-posttooluse.py::used_kind`).
 
 Claude's line never reads the store: it parses `tool_use` blocks out of
 `payload["transcript_path"]` plus the subagent transcripts under it, which is how
@@ -269,15 +277,15 @@ Every other surface reads the store.
   picks the host from `--cursor` or `TEZGAH_STATUS_HOST`, renders
   `render_line(segs, color=color_default())`, and joins Orca's own status line to
   the tezgah segment with `  |  `; `TEZGAH_STATUS_LEGEND=1` appends the legend
-  (31-34,40-48,116-122). ANSI is dropped under `NO_COLOR` or
+  (`statusline.py::HOST`, `statusline.py::seg`, `statusline.py::out`). ANSI is dropped under `NO_COLOR` or
   `TEZGAH_STATUS_COLOR=0` (`color_default()`, `hooks/tezgah_context.py::color_default`).
 - **omp** — hosts/omp/tezgah-hook.ts.in: `draw()` prefers
   `ctx.ui.setWidget("tezgah", [line], {placement: "belowEditor"})`, which renders
   the colored string as-is; `setStatus` is the fallback for a build without
-  `setWidget`, and it is plain because omp strips ANSI (12-29). `status_line()`
+  `setWidget`, and it is plain because omp strips ANSI (`draw` in `hosts/omp/tezgah-hook.ts.in`). `status_line()`
   builds the line and carries `idx_override`, so a per-tool redraw forks no git
   (`hosts/omp/hook.py::status_line`); it redraws on session start, session switch, turn end
-  and each watched tool result (hosts/omp/tezgah-hook.ts.in:596-636,674-679,720-745).
+  and each watched tool result (`refresh` and `WATCHED` in `hosts/omp/tezgah-hook.ts.in`).
   **Motion:** while the agent runs (`agent_start` until an `agent_end` whose
   `isTerminal` is not `false`) the widget leads with a braille spinner, the tool
   in flight (`tool_execution_start`/`_end`, "thinking" between tools) and the
@@ -297,20 +305,26 @@ Every other surface reads the store.
   (`tui.json`'s `plugin` array, not the server plugin) registering an `app_bottom`
   slot, shelling out to `tezgah-status <dir> --json <sessionID>`, coloring each
   segment from the active theme and rebuilding the separator from `seg.group`
-  (56-88,hosts/opencode/tui/tezgah-tui.tsx:108-111). Its `tezgah: status legend` command opens a dialog running
-  `--legend` (141-147).
+  (`TezgahBar` in `hosts/opencode/tui/tezgah-tui.tsx`). Its `tezgah: status legend` command opens a dialog running
+  `--legend` (`LegendDialog` in `hosts/opencode/tui/tezgah-tui.tsx`).
   On opencode 2 the same line comes from hosts/opencode/tui/cli/tui.tsx, a
   `Plugin.define` CLI plugin listed in `cli.json`. It reuses the v1 file's `run`.
 - **dsh** — hosts/dsh/statusline/lib/index.js serves `GET /api/tezgah.status`
   behind the Web UI's own authenticated fetch fence, so the browser fetches it
-  same-origin with no extra token handling (14,34-38); it always passes
-  `--observable=consult,research,graph,orch,judge` (18,47-48) and returns `{segments,
-  legend}` for `?format=json`, plain text otherwise (49-56,63). Its client half
+  same-origin with no extra token handling (`apply` in `hosts/dsh/statusline/lib/index.js`); it always passes
+  `--observable=consult,research,graph,orch,judge` (`OBSERVABLE` in `hosts/dsh/statusline/lib/index.js`) and returns `{segments,
+  legend}` for `?format=json`, plain text otherwise (`statusText` in `hosts/dsh/statusline/lib/index.js`). Its client half
   (hosts/dsh/statusline/lib/client.js) renders the marks in the session header in
   fixed light/dark colors, polls every 10 s while the tab is visible, and shows the
-  legend on hover, pins it on click (16-19,35,47-52,63-64).
+  legend on hover, pins it on click (`TezgahStatusLine` in `hosts/dsh/statusline/lib/client.js`).
 - **Codex** — hosts/codex/hook.py puts the plain line in `systemMessage`
-  (182-184,195-198).
+  (`hosts/codex/hook.py::main`).
+- **Amp** — the plugin draws the widest plain tier
+  (`hosts/amp/hook.py::status_line`) on Amp's experimental status item
+  (`createStatusItem`, TUI only, plain text). It draws only for the thread the
+  user is looking at. It redraws on `session.start`, `agent.end` and each
+  watched tool result, and shows `hook✗` while the hook fails. A build without
+  the API has no status surface (`hosts/amp/tezgah-plugin.ts.in`).
 
 ## Seeing and debugging the line
 
@@ -330,7 +344,8 @@ tezgah-status --judge                        # what the judge used last, and why
 
 The session id is the second positional argument or `TEZGAH_SESSION`; without it
 the used marks cannot light up (`bin/tezgah-status::main`). `--color`/`--no-color` force ANSI or plain,
-`--observable=` narrows the measures as above, and an unknown flag exits 2 (`bin/tezgah-status::main`).
+`--observable=` narrows the measures as above, and an unknown flag exits 2. So does
+an `--observable=` measure outside `TOOL_USE_MEASURES` plus `pony` and `adhd` (`bin/tezgah-status::main`).
 
 `--counters` is not the marks: it prints `tezgah_integrity.counters(session)` —
 `steps`, `tool_error_rate`, `claims`, `false_completion`, `shape_blocked`,
@@ -407,7 +422,8 @@ could not be read - so the mark refuses to say either fresh or stale, and
 `index_notice()` says on the turn that the graph's age is unknown. On a host that
 sandboxes hook writes (dsh) the stamp is never written, and before that state
 existed the mark read green there for good. That is why `observable` exists (`hooks/tezgah_context.py::health_segments`),
-why the skill-read check is documented as unavailable on Codex, Cursor and dsh
+why the skill-read check is documented as unavailable on every host that passes
+the tool-use set or the dsh literal (see `--observable=` above)
 (`hooks/tezgah_context.py::skill_read_kind`), why omp ignores any `idx` value that is not one of
 its five glyphs (`hosts/omp/hook.py::status_line`) - a value outside that set re-probes
 instead of being reused, one fork and never a wrong mark - and

package/docs/testing.md

@@ -47,7 +47,7 @@ baseline on the next run. Only `--clarity --update` raises it.
 A pin is a claim about what ran, not a guarantee about what will. This repository
 has two, and both are about the language rather than about dependencies: the
 floor `py310` (`pyproject.toml:5`) and the CI matrix that proves it
-(`.github/workflows/ci.yml:114`). There is no dependency lockfile to pin
+(the `test` job's `python-version` matrix in `.github/workflows/ci.yml`). There is no dependency lockfile to pin
 because there is no package: tezgah is a set of scripts run in place, and no
 `[project]` or build system is declared (`pyproject.toml:1-2`). The only
 third-party tool the checks name is ruff, at a version in
@@ -65,8 +65,15 @@ conclude from either.
 
 `.github/workflows/ci.yml` runs on a push to `main` and on a pull request, so
 a branch commit runs once, through its pull request, not twice. A tag push does
-not start it. `release.yml` calls it (`ci.yml:13`) as its `ci` job, so npm and
-brew publish only after CI passed on the release commit. A newer push to the
+not start it. `release.yml` calls it (its `workflow_call` trigger) as its `ci` job, so npm and
+brew publish only after CI passed on the release commit. Its first job,
+`on-main`, fails the release when the tag's commit is not on `origin/main`.
+Then no job builds or uploads anything. Next, `green` looks for a finished push
+run of `ci.yml` on the same commit. It waits for a running one and counts only
+`success`, and then `ci` does not run: a release does not run the suite twice. No
+such run, or any other outcome, runs `ci` as before. `npm-publish` and
+`brew-formula` need `green` and `ci`, and publish when either answered green.
+A newer push to the
 same ref cancels the run it replaces, except on a release (`concurrency`). Every
 job has a `timeout-minutes`, so a hung test cannot hold a runner for six hours.
 No matrix cancels its other legs when one fails (`fail-fast: false`).
@@ -77,33 +84,58 @@ No matrix cancels its other legs when one fails (`fail-fast: false`).
   empty diff, a base it cannot read, a release or a manual run runs everything.
 - `docs`, prose only: the citations audit, the clarity audit and
   `tests/impacted.py --ref <base>`, which maps a docs page to the docs modules.
-- `test` (`ci.yml:100`) on Python 3.10 and 3.14, the floor and the ceiling.
-  It byte-compiles, lints with ruff from `requirements-dev.txt` (pip cached),
-  audits the docs citations and clarity and runs `TEZGAH_E2E_STRICT=1 python3
-  tests/e2e_plan_flow.py`. A release passes the `release` input and runs one
-  3.10 leg.
-- `test-sharded` (`ci.yml:142`) on Python 3.10 and 3.14 with node 22 (the
+- `test` runs on Python 3.10 and 3.14, the floor and the ceiling. Its first steps
+  are "Byte-compile every script", "Install ruff" (from `requirements-dev.txt`,
+  pip cached) and "Lint". Then come "Every docs citation lands in the symbol it
+  names" and "The docs prose audit". The last two are "The plan and decision
+  rules, in a real project" (`TEZGAH_E2E_STRICT=1 python3 tests/e2e_plan_flow.py`)
+  and "The research checks against their known-truth set" (`python3
+  bin/tezgah-research release-check`). A release passes the `release` input and
+  runs one 3.10 leg.
+- `test-sharded` on Python 3.10 and 3.14 with node 22 (the
   first line that loads the omp `.ts` hook without a flag). On `main` and a
-  release it runs `python3 tests/impacted.py --all`. On a pull request it runs
-  `--ref <base>`: the modules the change maps to, and the whole suite when the
-  map does not know a path. It replaced the serial `unittest discover` step on
+  release its step "Run the suite, sharded" runs `python3 tests/impacted.py --all`.
+  On a pull request "Run the impacted modules, sharded (pull request)" runs
+  `--ref <base>` instead. That runs the modules the change maps to, or the whole
+  suite when the map does not know a path. It replaced the serial `unittest discover` step on
   2026-10-13: both caught the same failures, and the serial step took about 30
   minutes.
-- `apps-e2e` (`ci.yml:175`) on Python 3.12 and node 20: one step,
+- `apps-e2e` on Python 3.12 and node 20: one step, "App MCP handshake
+  (playwright + mobile-mcp)",
   `TEZGAH_E2E_STRICT=1 python3 tests/e2e_analyze_wiring.py`. It completes the
   app-MCP handshake only - no browser, no device - so it stays deterministic;
   strict mode makes a server that cannot start a failure rather than a skip, so
   a broken wire cannot hide behind a skip (`e2e_analyze_wiring.py:4-12`).
-- `artifact-install` (`ci.yml:200`) on Python 3.10 and 3.12: builds the
+- `artifact-install` on Python 3.10 and 3.12: builds the
   tarball, installs from it under a temp prefix, and runs the artifact smoke on
   the installed tree instead of the checkout.
-- `artifact-install-windows` (`ci.yml:243`) on `windows-latest`: the same
+- `artifact-install-windows` on `windows-latest`: the same
   build, install and smoke through `packaging/install.ps1` - the twin a Windows
   user runs - so it is the only place the Windows claim is proven. It then runs
   the opencode plugin's path tests natively, `tezgah update --dry-run`, the
   opencode live probe and `--uninstall` from the installed tree. Any residue
   under the prefix fails it.
 
+Four node harnesses run JavaScript and TypeScript the suite cannot import. Their
+Python modules drive them, so they run wherever those modules run: in
+`test-sharded`, which installs node 22, and locally under `tests/impacted.py`.
+
+- `tests/_opencode_plugin_harness.mjs` loads the opencode plugin
+  (`tests/test_opencode_plugin.py`).
+- `tests/_omp_extension_harness.mjs` loads the omp extension
+  (`tests/test_omp_extension.py`) and `tests/_amp_plugin_harness.mjs` the Amp
+  plugin (`tests/test_amp_plugin.py`). Both need a node that strips types
+  (22.18+).
+- `tests/_workflow_harness.mjs` is a stub of the Workflow runtime. It runs
+  `workflows/graph-review.js`, `workflows/graph-impact.js` and
+  `workflows/graph-map.js` as async function
+  bodies. It answers each `agent()` from a fixture, and `null` is a failed agent.
+  `python3 -m pytest tests/test_graph_workflows.py` runs it.
+
+Without node, or with a node too old for `.ts`, these modules skip rather than
+fail, so a leg with no node passes them silently. `test-sharded` is the leg
+that proves them.
+
 `.github/workflows/neuter.yml` runs two jobs weekly, on demand, and on a push to
 `main` that changes a guard, the matrix or a test module it runs. The matrix is
 CI's, not the local loop's. The first job, `neuter`, asks the question the suite
@@ -125,10 +157,11 @@ row.
 Each mutant first runs alone the test that killed it last time, read from
 `tests/neuter_killers.json`. When that test passes or is gone, the mutant runs
 every module in its own HOME and TMPDIR. The module that reads the mutated file
-goes first. The first failing test becomes its new entry. The
+goes first. With `--update-killers`, the first failing test becomes its new
+entry. Without it, the tracked cache is left as it was. The
 control runs every module, then every cached killer alone, so a killer that
 fails without a mutant voids the run. A session that adds a deny rule checks its
-one mutant with `python3 tests/neuter_matrix.py --only <name>`.
+one mutant with `python3 tests/neuter_matrix.py --only <name> --update-killers`.
 
 The second, `fuzz-shell`, runs the bash-oracle fuzzer (`tests/fuzz_shell.py`)
 under the ubuntu runner's bash 5.x. Locally, macOS ships bash 3.2. A first step

package/docs/vision.md

@@ -117,8 +117,12 @@ conflicting SWE-bench split, the agent cheated in 0 of 132 runs with tezgah and
 no headroom. Hand labels of final messages on those impossible tasks found
 false done claims in 3 of 30 runs with tezgah and 6 of 30 without. The CI of
 that difference includes 0. The Stop rule's claim reader
-flagged far more runs than that. On Turkish replies it counts `doğrulandı`
-(verified) on a partial fix as a claim, a recorded weakness not yet fixed. The
+flagged far more runs than that. On Turkish replies it counted `doğrulandı`
+(verified) on a partial fix as a claim, even beside a `doğrulanmadı`. Commit
+9cb4d1d fixed that shape. Its held-out recall is 0.857, below the 0.9 bar. A
+narrower gap remains. A Turkish partial fix with no admission word
+(`hâlâ başarısız`, `kısmen`) still reads as done and verified. Its English twin
+reads as verification only. The
 numbers, the per-task counts and the instrument flaws are in
 [the results bundle](results/paired-outcome-2026-10.md).
 

package/hooks/hooks.json

@@ -13,7 +13,7 @@
       { "hooks": [ { "type": "command", "command": "TEZGAH_HOST=claude \"${TEZGAH_PYTHON:-python3}\" \"${CLAUDE_PLUGIN_ROOT}/hooks/projects-auto-init.py\"", "timeout": 10 } ] }
     ],
     "PreToolUse": [
-      { "matcher": "Agent|agent|Task|task|Grep|grep|Bash|bash|PowerShell|pwsh|Shell|shell|subagent|Edit|Write|MultiEdit|NotebookEdit|AskUserQuestion", "hooks": [ { "type": "command", "command": "\"${TEZGAH_PYTHON:-python3}\" \"${CLAUDE_PLUGIN_ROOT}/hooks/projects-pretooluse.py\"", "timeout": 5 } ] },
+      { "matcher": "Agent|agent|Task|task|Grep|grep|Bash|bash|PowerShell|pwsh|Shell|shell|Monitor|monitor|subagent|Edit|Write|MultiEdit|NotebookEdit|AskUserQuestion", "hooks": [ { "type": "command", "command": "\"${TEZGAH_PYTHON:-python3}\" \"${CLAUDE_PLUGIN_ROOT}/hooks/projects-pretooluse.py\"", "timeout": 5 } ] },
       { "matcher": "^mcp__(?:.*[^A-Za-z0-9])?(?:append|cancel|clear|click|close|comment|commit|copy|create|delete|deploy|drag|edit|email|evaluate|exec|execute|fill|insert|install|kill|launch|merge|message|mkdir|move|navigate|notify|patch|pause|post|press|print|publish|push|put|release|remove|rename|replace|reply|resume|review|run|save|send|set|share|skip|start|stop|submit|swipe|tag|tap|terminate|type|uninstall|update|upload|write)(?:[^A-Za-z0-9].*)?$", "hooks": [ { "type": "command", "command": "\"${TEZGAH_PYTHON:-python3}\" \"${CLAUDE_PLUGIN_ROOT}/hooks/projects-pretooluse.py\"", "timeout": 5 } ] }
     ],
     "PostToolUse": [

package/hooks/lang/en.json

@@ -1,13 +1,13 @@
 {
  "name": "English",
  "done": [
-  "done|complete[d]?|finished|implemented|fixed|shipped|landed|merged|wired up|wired into|all tests? pass|all checks? pass|(?:tests?|checks?|suite) (?:is |are )?(?:green|passing)|build (?:passes|is green)"
+  "done|complete[d]?|finished|implemented|fixed|(?<!\\bis )(?<!\\bare )(?<!\\bget )(?<!\\bgets )(?<!\\bbe )(?<!\\bbeing )(?<!-)updated(?!-)|shipped|landed|merged|wired up|wired into|(?:all )?(?:tests?|checks?|suite|build) passed|(?:all )?(?:tests|checks) pass|(?:suite|build) passes|(?:tests?|checks?|suite) (?:is |are )?(?:green|passing)|build is green"
  ],
  "verified": [
   "tested|verified|i ran|ran the (?:tests?|suite|build|lint|checks?)"
  ],
  "negated": [
-  "unverified|not verified|could ?n[o']t verify|verification (?:was )?skipped"
+  "unverified|not verified|could ?n[o']t verify|verification (?:was )?skipped|^\\s*(?:untested|not (?:yet )?(?:been )?(?:tested|checked))\\b|(?:^|[.!;]\\s+)(?:(?:this|the) (?:change|fix|patch)|it|i)\\b[^.\\n]{0,24}?(?:not|n't) (?:yet )?(?:been )?tested|not checked yet"
  ],
  "admitted": [
   "contradict|unsatisfiable|(?:can ?not|can't|can ?never|never) pass|impossible"
@@ -36,6 +36,9 @@
  "negation_before": [
   "\\bnot|n't|\\bnever"
  ],
+ "condition_before": [
+  "\\b(?:if|when|once|unless|until|whether)\\b"
+ ],
  "question_particle": [],
  "question_end": [],
  "clause_join": [
@@ -224,6 +227,9 @@
   "plan_build": [
    "\\bplans?\\b[^.?!\\n]{0,40}\\b(?:is ready|ready|written|drafted)\\b|\\b(?:wrote|opened|drafted|added|created) (?:the |a |this )?plans?\\b|\\b(?:build|implement|execute|start on|start) (?:the |this |that )?plans?\\b"
   ],
+  "owner_choice": [
+   "\\bwhich (?:variant|option|approach|design)s?\\b|\\b(?:v\\d+|option [a-h1-9]|variant [a-z0-9]+),? or (?:v\\d+|option [a-h1-9]|variant [a-z0-9]+)\\b|\\b(?:another|other|the other) session\\w*|\\bsession'?s (?:line|plan|branch)\\b|\\bclos\\w*\\b[^?\\n]{0,40}\\bline\\b|--allow-open|--limit\\b|\\.staging\\b|\\bhidden (?:dir|directory|folder)\\b|\\b(?:another|a different) (?:folder|dir|directory)\\b|\\b(?:work ?)?around\\b[^?\\n]{0,40}\\brefusal\\b"
+  ],
   "spend": [
    "spend\\w*|\\bpaid\\b|billing|\\bcost\\w*|\\bbudget\\w*|\\busd\\b|\\$\\s?\\d"
   ],
@@ -236,6 +242,12 @@
   "cheap_answer": [
    "yes|yep|yeah|ok(?:ay)?|sure|go(?: on| ahead)?|continue|proceed|do it|carry on|keep going|approved"
   ],
+  "hand_over": [
+   "\\bplease\\s+(?:run|execute)\\b|\\byour\\s+(?:step|turn|move)\\b(?=\\s*[:.;,!]|\\s*$)|\\bover to you\\b"
+  ],
+  "ran_it": [
+   "\\bi (?:ran|tested|verified|checked|executed)\\b|\\bran the (?:tests?|suite|build|lint|checks?)\\b|\\bwe ran\\b"
+  ],
   "outward": {
    "push": "\\bpush\\w*",
    "release": "\\brelease\\w*|\\btag(?:s|ged|ging)?\\b|version bump|bump the version",
@@ -329,6 +341,8 @@
   "slice_lead": "",
   "ready_lead": "",
   "ask_lead": "",
+  "handed_lead": "",
+  "plan_lead": "",
   "approval_heading": "Approval questions",
   "recommended": "Recommended",
   "grant_examples": "\"push without asking\", \"I approve\""

package/hooks/lang/tr.json

@@ -1,7 +1,7 @@
 {
  "name": "Turkish",
  "done": [
-  "yaptım|tamamladım|tamamlandı|bitirdim|bitirildi|ekledim|eklendi|düzelttim|düzeltildi|hallettim|güncellendi|kuruldu|uygulandı|yayına girdi|kapatıldı|yüklendi|tüm testler geçti|testler geçti|testler yeşil|çalışıyor"
+  "yaptım|tamamladım|tamamlandı|bitirdim|bitirildi|ekledim|eklendi|düzelttim|düzeltildi|hallettim|güncellendi|kuruldu|uygulandı|yayına girdi|kapatıldı|yüklendi|tüm testler geçti|testler geçti|testler geçiyor|testler yeşil|çalışıyor"
  ],
  "verified": [
   "doğruladım|test ettim|kontrol ettim|denetledim|doğrulandı|test edildi"
@@ -89,6 +89,7 @@
  "negation_before": [
   "\\bdeğil"
  ],
+ "condition_before": [],
  "question_particle": [
   "m[ıiuü]|değil"
  ],
@@ -200,7 +201,7 @@
    "ürün(?!\\w*_)\\w*|yol harita\\w*|kuzey yıldız\\w*|aktivasyon\\w*|dönüşüm\\w*|fiyatlandır\\w*|önceliklendir\\w*|kullanıcı araştırma\\w*|ürün keşf\\w*|müşteri geri bildirim\\w*|benimsen\\w*|konumlandır\\w*|segmentasyon\\w*|hedef kitle\\w*|(kullanıcı|müşteri) discovery|keşif (görüşme|çalışma)\\w*|fırsat\\w*|memnuniyet\\w*|anket\\w*|(kullanıcı|müşteri)[ -]?(feedback|geri bildirim)\\w*|(customer|user)[ -]?geri bildirim\\w*|şikayet\\w*|rakip\\w*|rekabet\\w*|pazar pay\\w*|terk oran\\w*|elde tutma\\w*|abonelik\\w*|gelir model\\w*|özellik\\w*|sayfa(?! numara)\\w*|ekran(?! kart)(?!a\\b[^.!?\\n]{0,40}\\b(?:yaz|bas)\\w*)\\w*|arayüz\\w*|arama kutu\\w*|filtre\\w*|tablo(?![^.!?\\n]{0,60}\\b(?:sütun|kolon|sql|index|indeks)\\w*)\\w*|adım(?! sayı)\\w*|kullanıcı liste\\w*|form(u|un|da|daki|lar|ları|unu)\\w*[^.!?\\n]{0,40}\\b(?:incele|denetle|analiz|de[ğg]erlendir|iyile[şs]tir|sadele[şs]tir|kontrol)\\w*"
   ],
   "design": [
-   "(?:(?<![\\w'’] )|(?<=\\bbu )|(?<=\\bşu ))tasar[ıi]m\\w*|(?:dashboard|pano|g[öo]sterge panel|ekran|sayfa|aray[üu]z|landing|logo|ikon)\\w* (?:\\w+ ){0,2}(?:tasarla|tasar[ıi]m|redesign)\\w*|(?:web[ -]?)?site\\w* tasar[ıi]m\\w*|(?:mobil |web )?uygulama\\w* tasar[ıi]m\\w*|(?:web|mobil) tasar[ıi]m\\w*|tasar[ıi]m (?:sistem|token|dil|rehber)\\w*|yeniden tasarla\\w*|ba[şs]tan tasarla\\w*|design [çc]al[ıi][şs]ma\\w*|aray[üu]z\\w*|(?:ui|aray[üu]z|form|buton|d[üu][ğg]me|kart|men[üu]|sayfa|ekran|react|vue)\\w* (?:\\w+ )?bile[şs]en\\w*|bile[şs]en (?:k[üu]t[üu]phane|sistem)\\w*|tipografi\\w*|renk\\w*|tema(?:s[ıi]|y[ıi]|lar\\w*)?|kullan[ıi]labilirlik\\w*|eri[şs]ilebilirli[kğg]\\w*|g[öo]rsel (?:hiyerar[şs]i|tutarl[ıi]l[ıi]k|denetim|ele[şs]tiri)\\w*",
+   "(?:(?<![\\w'’] )|(?<=\\bbu )|(?<=\\bşu ))tasar[ıi]m\\w*|(?:dashboard|pano|g[öo]sterge panel|ekran|sayfa|aray[üu]z|landing|logo|ikon)\\w* (?:\\w+ ){0,2}(?:tasarla|tasar[ıi]m|redesign)\\w*|(?:uygulama(?:y[ıi]|s[ıi]n[ıi])?|site(?:yi|sini)?) redesign\\w*|(?:web[ -]?)?site\\w* tasar[ıi]m\\w*|(?:mobil |web )?uygulama\\w* tasar[ıi]m\\w*|(?:web|mobil) tasar[ıi]m\\w*|tasar[ıi]m (?:sistem|token|dil|rehber)\\w*|yeniden tasarla\\w*|ba[şs]tan tasarla\\w*|design [çc]al[ıi][şs]ma\\w*|aray[üu]z\\w*|(?:ui|aray[üu]z|form|buton|d[üu][ğg]me|kart|men[üu]|sayfa|ekran|react|vue)\\w* (?:\\w+ )?bile[şs]en\\w*|bile[şs]en (?:k[üu]t[üu]phane|sistem)\\w*|tipografi\\w*|renk\\w*|tema(?:s[ıi]|y[ıi]|lar\\w*)?|kullan[ıi]labilirlik\\w*|eri[şs]ilebilirli[kğg]\\w*|g[öo]rsel (?:hiyerar[şs]i|tutarl[ıi]l[ıi]k|denetim|ele[şs]tiri)\\w*",
    {
     "ui_ask": "iyile[şs]tir\\w*|g[üu]zelle[şs]tir\\w*|d[üu]zenle\\w*|kar[ıi][şs][ıi]k\\w*|tutars[ıi]z\\w*|da[ğg][ıi]n[ıi]k\\w*|[çc]irkin\\w*"
    },
@@ -268,6 +269,9 @@
   "plan_build": [
    "\\bplan\\w*[^.?!\\n]{0,40}(?:hazır|yazıldı|yazdım|oluşturdum|oluşturuldu|açtım|açıldı|eklendi|uygula\\w*|başla\\w*|kur\\w*)|(?:yazdığım|açtığım|hazırladığım|oluşturduğum) plan\\w*"
   ],
+  "owner_choice": [
+   "\\b(?:v\\d+|seçenek \\w+|varyant \\w+)(?:'\\w+)? m[ıiuü]\\b,? (?:v\\d+|(?:seçenek |varyant )?\\w+)(?:'\\w+)? m[ıiuü]\\b|\\bhangi (?:varyant|seçenek|opsiyon|yaklaşım|tasarım)\\w*|\\bhangisini seç\\w*|\\b(?:başka|diğer) (?:bir )?oturum\\w*|\\bhatt[ıi]\\w* kapat\\w*|--allow-open|--limit\\b|\\.staging\\b|\\bgizli (?:dizin|klasör)\\w*|\\b(?:başka|farklı) (?:bir )?(?:klasör|dizin)\\w*|\\bred\\w* (?:aş|etrafından)\\w*|\\bengel\\w* (?:aş|etrafından)\\w*"
+  ],
   "spend": [
    "ücret\\w*|ödeme\\w*|harca\\w*|bütçe\\w*|maliyet\\w*|\\bpara\\b|dolar\\w*|\\$\\s?\\d"
   ],
@@ -280,6 +284,12 @@
   "cheap_answer": [
    "evet|tamam|olur|devam(?: et)?|yap|başla|ilerle|okey|onay(?:lıyorum)?"
   ],
+  "hand_over": [
+   "\\b(?:sen|siz)\\b[^.!?\\n]{0,32}?\\bçalıştır(?:ın|ınız)?\\b|\\bsenin adımın\\b|\\badım(?:ı)? sende\\b|\\bsıradaki adım(?:ı)? sen\\b"
+  ],
+  "ran_it": [
+   "\\b(?:test(?:ler)?i|suite'?i|komutu|kontrolü|denetimi)?\\s*(?:çalıştırdım|koştum|çalıştırdık)\\b|\\btest ettim\\b|\\bdoğruladım\\b|\\bkontrol ettim\\b|\\bdenetledim\\b"
+  ],
   "outward": {
    "push": "\\bpush\\w*",
    "release": "versiyon\\w*|sürüm\\w*|\\brelease\\w*|etiket\\w*",
@@ -350,6 +360,8 @@
   "slice_lead": "Durmuş bir dilim var. ",
   "ready_lead": "Hazır adımlar bekliyor. ",
   "ask_lead": "Bu soruyu sorma: kararı ver ya da önerili onay sorusuna çevir. ",
+  "handed_lead": "Bu adımı sen çalıştır, kullanıcıya bırakma. ",
+  "plan_lead": "Plan modunda hiçbir şey koşmadı. ",
   "approval_heading": "Onay için sorular",
   "recommended": "Öneri",
   "grant_examples": "\"bana sormadan pushla\", \"onay veriyorum\""

package/hooks/projects-posttooluse.py

@@ -69,11 +69,19 @@ def result_size(result):
     so a container is measured by its top-level length (O(1) for str, bytes,
     list, dict, set) instead of re-serializing it: `json.dumps` on every
     PostToolUse copied the whole tool response and broke the hook's cost bound
-    ("a sha1 over a short string and a few fields; nothing else"). ponytail: a
-    dict result therefore reports its field count, not its byte length - the
-    host reports no size of its own, and no reader compares the two."""
+    ("a sha1 over a short string and a few fields; nothing else"). A shell
+    result is the exception: Claude's Bash answers `{"stdout", "stderr",
+    "interrupted", ...}`, so its field count is never 0 and a check that
+    printed nothing would read as output (`passing_check`'s silent failure,
+    B-005); its stream strings (`ran_nothing`'s keys) are measured instead.
+    ponytail: any other dict reports its field count, not its byte length."""
     if result is None:
         return None
+    if isinstance(result, dict):
+        streams = [result[k] for k in ("stdout", "stderr", "output")
+                   if isinstance(result.get(k), str)]
+        if streams:
+            return sum(map(len, streams))
     if isinstance(result, (str, bytes, bytearray, list, tuple, dict, set,
                            frozenset)):
         return len(result)

package/hooks/projects-stop.py

@@ -48,7 +48,7 @@ def main():
     if not isinstance(p, dict):
         return
     session_id = p.get("session_id")
-    safe(session_id, bind_session, session_id)  # the switch latch (tezgah_paths.off)
+    safe(session_id, bind_session, session_id, p.get("parent"))  # the switch latch
     cwd = p.get("cwd") or os.getcwd()
     if p.get("hook_event_name") == "SubagentStop" and p.get("agent_id") \
             and root_for(cwd) and not off("slices-off"):
@@ -64,7 +64,8 @@ def main():
     # a core that cannot answer has refused nothing, so the turn ends: the rule
     # never traps a session, and that holds for its own failure too
     reason = safe(session_id, stop_reason, p.get("last_assistant_message"),
-                  session_id, cwd=cwd, after_block=bool(p.get("stop_hook_active")))
+                  session_id, cwd=cwd, after_block=bool(p.get("stop_hook_active")),
+                  mode=p.get("permission_mode"))
     if reason:
         json.dump({"decision": "block", "reason": reason}, sys.stdout)
 

package/hooks/tezgah_agents.py

@@ -245,6 +245,15 @@ def _reviewer_body(host):
         "for those files: account for every listed file as reviewed or skipped\n"
         "with a reason, and still apply everything above - OCR output is input,\n"
         "never a verdict.\n\n"
+        "Plan readiness. When the target is a plan file\n"
+        "(`.tezgah/plans/open/NNN-*.md`) rather than a diff, review whether it\n"
+        "can be built without a question. First restate each section's intent\n"
+        "in one sentence of your own; a section you cannot restate lacks\n"
+        "context, which is a major finding. Then check that every choice the\n"
+        "build needs is made in the plan - schema, API path, dependency,\n"
+        "edge-case handling, the files to change; a choice left to the\n"
+        "implementer is a major finding. A file the plan will create is not a\n"
+        "missing reference. Classify and report exactly as for a diff.\n\n"
         "%s" % (_graph_howto(host), _blast_radius(host), EMPTY_IS_NOT_PROOF,
                 decision, decision, _may_use(host)))
 
@@ -265,14 +274,26 @@ def _worker_body(tier):
                 "report what changed and what each check printed, verbatim. Report\n"
                 "progress, but never redefine the work. Never widen or narrow the brief's\n"
                 "scope, budget or question. If the brief cannot be met as written, say\n"
-                "so and stop rather than answering a different question.\n%s\n"
+                "so and stop rather than answering a different question.\n%s\n%s"
                 "A brief that builds or changes UI: read the `design-contract` skill\n"
                 "(and `design-library` for critique) and derive/check with\n"
                 "`~/.config/tezgah/bin/tezgah-design` before editing.\n"
-                "Never spawn subagents.\n%s" % (tier, tier, scope, WORKER_OUTPUT))
+                "Never spawn subagents.\n%s" % (tier, tier, scope, OWNER_ESCALATE,
+                                                WORKER_OUTPUT))
     return body
 
 
+# A question only the owner can answer climbs past every tier to the user: a
+# worker that settles it itself, frontier included, decided for the owner
+# (plan 136: a line ran under a hidden dir and wrote `chosen:` with no owner
+# choice). One text on every tier.
+OWNER_ESCALATE = ("A question only the owner can answer - choosing a variant or option a\n"
+                  "research, analysis or review recommends; a way around a tezgah\n"
+                  "refusal; deciding about another session's work (its line, plan or\n"
+                  "branch) - is never yours to decide, on any tier: stop and answer\n"
+                  "`ESCALATE: owner` with the options and a recommended default.\n")
+
+
 # The report a consumer reads: the orchestrator re-briefs a report missing one
 # of these fields (_orch_body), so only a role with a reader gets them. One
 # text on every host, since a worker body ignores its host.
@@ -282,7 +303,8 @@ WORKER_OUTPUT = ("End the report, after any other shape asked for, with `Output
                  "- commit: the sha\n"
                  "- checks: each command, its exit code and the last lines of its\n"
                  "  output file, verbatim\n"
-                 "- escalate: the `ESCALATE:` reason (always `none` on tezgah-frontier)")
+                 "- escalate: the `ESCALATE:` reason (on tezgah-frontier only\n"
+                 "  `ESCALATE: owner`, else `none`)")
 
 
 # The specialists beside the tier workers: name -> (what it does, the skills it
@@ -483,6 +505,8 @@ def _orch_body(names):
         "or an ESCALATE, gets one narrower re-brief of the same role naming the\n"
         "missing field or the escalated judgement; only a second miss is\n"
         "restarted on tezgah-frontier with the original brief, never continued.\n"
+        "An `ESCALATE: owner` is neither: its options and default go to the user\n"
+        "in the approval batch, and the orchestrator never answers it itself.\n"
         "Never delegate a task a specialist is not\n"
         "listed for, and never let a subagent spawn its own subagents. Verify each\n"
         "returned claim against the code before acting." % (listed, say()["blocker_tokens"]))