@matheuskrumenauer/tanya 0.14.0-beta.0 → 0.15.0-beta.0

package/README.md

@@ -296,6 +296,24 @@ up to `TANYA_ESCALATION_CAP` per session.
 See [docs/routing.md](./docs/routing.md) for schema, examples, context-window
 guards, per-tool model overrides, and sub-agent model pins.
 
+## Live status
+
+Interactive `tanya chat` sessions show a compact status footer derived from the
+same events already sent to the human sink:
+
+```text
+[deepseek:deepseek-chat | tool_call | $0.04 | 2 tools | 1 child]
+[awaiting permission: run_shell]
+[escalated deepseek:deepseek-chat->openai:gpt-4.1-mini: parse_failure]
+```
+
+The footer is TTY-only. Piped output, JSONL output, and Cosmo bridge streams stay
+byte-stable and receive no ANSI cursor control bytes. Disable it with
+`TANYA_LIVE_STATUS=0` or the legacy `TANIA_LIVE_STATUS=0` alias.
+
+See [docs/live-status.md](./docs/live-status.md) for the surfaced fields,
+streaming strategy, and TTY fallback behavior.
+
 `--verify` adds required verification commands to the run context. Tanya must run and report each exact command before finishing the coding task.
 
 `tanya benchmark run --all` currently exercises 27 executable low-to-medium regression fixtures: targeted edits, new files, dependency/lockfile updates, framework-style migrations, failing-test repair, frontend smoke checks, artifact/context reuse, streaming long-tool execution, compaction-boundary recovery, run-history logging, dirty worktrees, report repair, and the CosmoHQ mobile/backend smoke profiles.
@@ -361,36 +379,6 @@ Tanya trims model-visible tokens while keeping state reversible and auditable.
 
 See [docs/token-economy.md](./docs/token-economy.md) for the full model, cache locations, and tool-definition knobs.
 
-## Edit blocks
-
-`edit_block` applies bounded search/replace edits without falling back to a
-full-file rewrite:
-
-```json
-{
-  "path": "src/example.ts",
-  "search": "const state = \"pending\";",
-  "replace": "const state = \"complete\";",
-  "expectedCount": 1,
-  "matchPolicy": "exact"
-}
-```
-
-Exact mode is the default and fails closed when the block is missing, ambiguous,
-or appears a different number of times than expected. Fuzzy mode is opt-in via
-`matchPolicy: "fuzzy"` and requires an explicit M3 permission allow rule. Fuzzy
-recovery only accepts whitespace-normalized or nearby-context candidates with
-confidence >= 0.95; otherwise Tanya returns a structured error and asks the
-model to re-read the file.
-
-Successful edit blocks emit before/after hashes and a unified diff. Fuzzy
-successes also add candidate metadata to the audit log. The final verifier still
-reads the changed workspace independently; edit-block success is not a verifier
-pass.
-
-See [docs/edit-blocks.md](./docs/edit-blocks.md) for the full tool reference,
-permission model, confidence threshold, and failure modes.
-
 Context files are generic JSON envelopes for caller-supplied task metadata, artifacts, instructions, and verification commands.
 
 ## Current Tools
@@ -405,7 +393,6 @@ Context files are generic JSON envelopes for caller-supplied task metadata, arti
 - `write_file`
 - `apply_patch`
 - `search_replace`
-- `edit_block`
 - `copy_file`
 - `copy_dir`
 - `apply_artifact`