@r1z4x/tezgah 1.9.2 → 1.11.0

package/CHANGELOG.md

@@ -6,6 +6,86 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [1.11.0] - 2026-10-23
+
+### Added
+
+- **A window names the row contract it read.** `tezgah-status --rates` now
+  counts each row's `v` per window. A window that read two contracts prints the
+  split, and a delta whose two windows lean on different contracts says so. The
+  reason is that `claims` is one quantity under `v2` and another under `v3`
+  (plan 135). A `v2` writer recorded every judged reply as a `claim` row. A `v3`
+  writer records a reply that claimed nothing as a `refusal` row. A share
+  compared across that seam is not one number, and the report no longer presents
+  it as one (`rates`, `hooks/tezgah_integrity.py`, `bin/tezgah-status`).
+
+- **The ledger reads a window, not only a lifetime.** `tezgah-status --rates
+  --since DATE --until DATE` folds every real ledger's rows in that span. The
+  fold runs per window and per calendar day. It carries turns, `claim` rows and
+  the Stop classes that blocked them. It also carries the shape flags of each
+  judged reply, and denies by rule (`rates`, `hooks/tezgah_integrity.py`). The
+  rates are blocks per 100 turns and denies per 100 sessions. They also carry
+  the claim block and Stop shape shares, and blocked claims per 100 sessions by
+  class. `--until` is exclusive, so two adjacent windows partition the span. A
+  repeated `--since`/`--until` pair prints the pp delta between adjacent
+  windows. `counters_all()` keeps answering exactly what it answered on the
+  same ledger: the window lives in the new reader. `--json` prints
+  `{"windows": [...]}`, and `docs/status-line.md` carries the reading.
+
+- **Hallmark ships as tezgah's UI generator.** `skills/hallmark` ships whole at revision `7ec8682`. It brings 48 themes, each with a picture, and 20 macrostructures. It also brings 98 reference pages and the zero-dependency `sloplint`. Every file is upstream's bytes, hashed in its own `SOURCE`. Upstream's `LICENSE` sits beside it. `tezgah-design slop --repo . [--render]` runs its gate list and writes `.tezgah/design/slop.json`. It exits 1 on a Floor FAIL. It exits 3 when Node or the skill is missing, which is a check that did not run. The Stop rule counts that verdict where it counts `tezgah-design check`. The UI floor is the union of both.
+
+- **A contract reads Hallmark's locked `design.md`, and one precedence table decides the floor.** A `design.md` or `DESIGN.md` at the repository root now feeds `derive`. It gives the palette and font roles, with `source: design-md`. The palette converts from OKLCH to the hex `check` compares. A token file beside it no longer competes. The contract gains a `precedence` block. It names `ours` (states, components, evidence, facts) and `theirs` (material, motion character). It names `shared` (contrast, focus-visible, reduced-motion, tap-target) and `verbatim: style`. `check` refuses with exit 2 a key named by two classes. It also refuses `facts` handed to a theme or to the user's own words.
+
+
+### Changed
+
+- **Skills reach the session on every armed host.** A UI ask arms a new conditional rule that names `design-contract`, `design-library`, `analyze-app` and `feature-audit`. `design-off` turns it off. The product rule also names `pm-frameworks`. A repeat match keeps the rule's action and its skill names (`ARMED_ACTIONS`), not a bare "Armed again". Every tezgah CLI in the injected text renders as its installed absolute path (`BIN_TOOLS`). Under a tight budget the skill hint now outlives the per-turn lessons and the index line. Shipped skill descriptions open with `Use when`, carry English and Turkish triggers and stay within 160 characters. Their longer text moved to a `## When to use` section, which the collision table now reads. Skill bodies call `~/.config/tezgah/bin/<cmd>`. The local skill hint ranks tezgah's and the project's skills before the hosts' global corpora. It folds Turkish letters, indexes five-letter prefixes and keeps one index per project that ships skills. The 144 vendored library entries are `ENTRY.md`, so codex and Cursor no longer list them as skills. `tezgah-skill` and `codegen` run through their `~/.config/tezgah/bin` symlink. `codegen --help` and `tezgah-research init --help` print their usage and exit zero. Cursor's per-turn text is cut to its 10000-unit hook limit, counted in UTF-16 units as Cursor counts, so Cursor no longer drops it whole. On opencode 2 the installer skips `tui.json` and `compaction.prune`, and the status line is a `cli.json` plugin. `--install --hosts X` keeps the hosts already recorded, and a partial uninstall takes its hosts off the record. A skill the repository ships reaches the hint by its path, marked as repository-provided data and read bounded. A UI build goes to `tezgah-standard`, whose brief loads `design-contract`. Agent briefs and the gate and Stop refusals name the installed CLI path too (plan 126).
+
+### Fixed
+
+- **A runner's flag does not hide its check.** `pnpm --filter mobile test` was
+  read as a plain command. The same held for `npm`, `yarn` and `bun`. A check the
+  turn really ran recorded as `run`. The Stop rule then refused the claim it
+  supported (`no verify_ok`). `VERIFY` now reads a run of flags before the task.
+  It reads the value a flag takes too: `--filter <name>`, `--prefix <dir>`,
+  `-C <dir>` and `--workspace <name>`. `uv run --project <dir> pytest` and
+  `uv run python -m pytest` join the table. So does
+  `pnpm --filter <name> exec <tool>`, which reaches the JS tool entry the same
+  way. A formatter's write mode is still a change. An information form still
+  checks nothing (`hooks/tezgah_integrity.py`, `tests/test_integrity.py`).
+
+- **A turn of reads owes no check, and the shell readers agree with bash**. The Stop rule refused an advice turn of reads in a `for` loop or a `$( )`. The model then answered in self-defence rather than acting. Such a turn now ends without a check. An edit, or a done/tested claim, is still refused. The readers that decide what a command runs now follow bash on these shapes. Both readers delete a backslash-newline exactly where bash deletes it. A `)` closing a substitution is part of the word. A `#` after a backtick, an escaped boundary or a `)` is mid-word. An fd number glued to its redirect is no program word, while `1 <` stays a program. An arm after a negated command stays alive. A `printf -v` or a `set -o` is no read. The opencode port answers the same, and `tests/fuzz_shell.py` draws these shapes so real bash checks the readers.
+
+- **More rules-8 refusals give way.** A registered metric that rewords the lock (`read-path p95 latency` for `p95 latency of the read path`) matches it. A run log above 16 MiB files whole with `source --ack "<the user's words>"`, which the refusal now names. A draw after labels is a `gold ... --redraw --ack "<the user's words>"`, which `check` reads as the draw every rule uses. A gold sample too small to reach the `mde` leaves the instrument `unvalidated`, not `rejected`. `search` takes PubMed, Scopus and ACM DL. Scopus needs `TEZGAH_SCOPUS_KEY`. ACM DL reads through Crossref's ACM member, because its site answers a browser check. `orx runs`'s table is read as runs for the census, since orx 0.2.20 has no `--json`. A quote still matches where an extraction dropped a space (`human-inthe-loop`).
+
+- **Rules-8 checks stop refusing sound lines.** A quote passes when any cited note's capture holds it. Its refusal names the notes it searched. A superseded claim's quotes go unchecked. Normalisation drops inner quotation marks and reads arXiv TeX as rendered. An open-access landing page under 100 body sentences captures as `abstract`, a step instead of a refusal. A receipt naming another id for the work warns instead of refusing. The report's share takes `closed-access`, `not full text` or `abstract-only`. Ledgers keep each version's rows in order, so merged appends pass and `check` refuses a reorder. Receipt and search rows carry their `parser` version. `check` re-derives every row and refuses one from a newer parser. `cite` keeps only 200 answers, and `check --online` compares only those. A `metric:` list no longer splits inside parentheses, digit groups or the locked name, and a word prefix matches the lock both ways. `source` refuses before writing over a metric other than the locked one or an uncommitted arena. The `not_reported` message names the exit that still works before and after the run. Log numbers read with a unit glued on. A label a refile left stale reads unlabelled. A concluded line reads its evaluator as sealed at its conclusion, and `check` also finds it in the checkout it runs in. `commit` with nothing to commit exits 0. `gold` refuses over uncommitted verdict rows. `docs/research.md` covers each change and the formats a new line writes by hand (plan 128).
+
+## [1.10.1] - 2026-10-19
+
+### Fixed
+
+- **The opencode member of a second opinion answers again.** `consult` and the judge ran `opencode run --pure`, whose exit 1 left that member silent. Both argv sites now run `opencode run` the way the user's own CLI does. No 2.x flag replaces `--pure`, so the judge's inline config still denies its tools, and `docs/judge.md` lists the flags each CLI really takes.
+- **A worktree made outside tezgah links the workspace instead of forking it.** `ensure_workspace` made a second `.tezgah` there, with its own `git init`. Research, migrate and the session start all forked the store that way. It now links the main checkout's workspace and returns it, the link a session start already made. A relative `.tezgah/...` write from the worktree lands in the one store. The link is also made on a compaction and on a delegated agent's first call. A worktree Orca or a plain `git worktree add` made stayed without one until a session started there.
+
+## [1.10.0] - 2026-10-19
+
+### Added
+
+- **A repository extends the status line with its own chips.** The repository puts `.tezgah/extension.json` at its top and names a command that prints segments. `health_segments()` walks up to the nearest manifest and runs it once per render, with the repo root as cwd. Each call reaches the child as one JSON object on its stdin: `api`, `event`, `cwd`, `repo_root` and `session_id`. The extension then knows which repository and which session asked it. It appends what comes back after every built-in mark. An extension produces data - `{key, state, glyph, text}` - and tezgah draws it. Color, the narrow-surface drop and the group separators then stay identical. The extension belongs to the user's repo in whatever language, so it runs as a bounded subprocess and never an import. A missing or malformed manifest, an absent command, a non-zero exit, a timeout or a bad shape all cost it its chips. A repo with no manifest pays one `os.path.isfile` per level.
+- **A repository says its workspace is not this harness's.** Tezgah armed every repository under a root, and no project could opt out. A committed `tezgah.owner` at the repository's top now says who owns the workspace, and its two settings turn seams off. `tasks: off` stops the plan and task machine. No active task, no per-turn phase line, and no `tezgah-task` command that writes a record runs - the slice journal and `sweep` included. The gate holds no write to its own plan files. The scope gate, research and lessons keep reading the repository. `harness: excluded` takes the repository out of every root, and nothing runs there. A repository cloned inside a marked one answers for itself, since the file comes from the nearest `.git` top. A file that cannot be …
+
+### Changed
+
+- **The no-plan refusal on a trunk offers no bind route.** On `main` or `master` it used to offer `tezgah-task start NNN --branch <trunk>`. The gate never honoured that binding, so the next write met the same refusal. The text now names the `plan/NNN-slug` route or a non-trunk branch a plan declares. `tezgah-task start --branch main` or `--branch master` now exits 2 and writes nothing.
+- **The impacted run checks a changelog entry's prose.** `tests/impacted.py` now maps `CHANGELOG.md` to `test_clarity.py` too. Before, the impacted run stayed green on an entry the ratchet refuses. The v1.9.1 release CI failed on exactly that.
+- **A linked worktree starts with its main checkout's code graph.** A new worktree had no index, so its slices fell back to text search. The auto-index now copies the main checkout's index into a worktree that has none, before the worker starts. The worker then runs the incremental `codegraph sync` on that copy. On this repository that took 1 s, against 10 s for a full `init`. `tezgah-task start` run inside a worktree does the same when it binds the plan. A copy that fails falls back to `init`.
+
+### Fixed
+
+- **A stopped installer leaves no orphan behind.** A Ctrl-C or a timeout kills the installer's whole process group. On macOS under load, a member caught mid-fork could survive that kill and hold the caller's pipes open. The cleanup now signals the group again until it is empty, for at most 2 s. Under load, 1800 runs gave 0 hangs, against 6 in about 638 before the fix.
+- **A subagent message no longer counts as a product file.** The no-plan rule read `agent://<id>` or `local://x.md` as a checkout file. Two such messages and one real file on `main` met the third-file refusal. A path with a URI scheme other than `file://` now never counts. A `file://` URL now counts as the local file it names, for the no-plan rule and the cross-session write guard alike. A Windows drive path such as `C:/x` still counts. The write guard now matches another URI such as `s3://bucket/key` on its spelling, so two sessions in different directories still race on it.
+- **The replay lists only the writers the race rule refuses on.** The replay named another writer in three cases the live race rule skips. They are a temp file, a shell target whose `$VAR` has no value, and a file an ended subagent of this session wrote. `tezgah-gate replay` and the rule now read one gate helper, so the page lists only writers the live rule would weigh. A live refusal names at most three of them, for its first path.
+
 ## [1.9.2] - 2026-10-17
 
 ### Fixed
@@ -1219,7 +1299,9 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
   the copy could not find `hooks/` and died on import. It now links into the
   installed tree, and also installs the command as `tezgah`.
 
-[Unreleased]: https://github.com/r1z4x/tezgah/compare/v1.9.2...HEAD
+[Unreleased]: https://github.com/r1z4x/tezgah/compare/v1.10.1...HEAD
+[1.10.1]: https://github.com/r1z4x/tezgah/releases/tag/v1.10.1
+[1.10.0]: https://github.com/r1z4x/tezgah/releases/tag/v1.10.0
 [1.9.2]: https://github.com/r1z4x/tezgah/releases/tag/v1.9.2
 [1.9.1]: https://github.com/r1z4x/tezgah/releases/tag/v1.9.1
 [1.9.0]: https://github.com/r1z4x/tezgah/releases/tag/v1.9.0