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

package/README.md

@@ -361,29 +361,35 @@ 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.
 
-## Structural repo-map
+## Edit blocks
 
-Lite prompts can include a generated structural map from
-`.tania/index/repo-map.json`. The map lists workspace-relative files, language,
-parser provenance, top-level symbols, imports, and exports so cheap providers
-can target likely files before spending turns on blind reads.
+`edit_block` applies bounded search/replace edits without falling back to a
+full-file rewrite:
 
-Tanya indexes TypeScript/JavaScript, Python, Go, Swift, and Kotlin with a
-lightweight ripgrep-style parser and falls back to path-only entries when file
-content cannot be read. Generated, binary, ignored, and oversized files are
-skipped. The repo-map is advisory context only: agents must still read files
-before editing, and the verifier remains the final authority.
+```json
+{
+  "path": "src/example.ts",
+  "search": "const state = \"pending\";",
+  "replace": "const state = \"complete\";",
+  "expectedCount": 1,
+  "matchPolicy": "exact"
+}
+```
 
-Use `TANYA_LITE_PROMPT=1` to inject a ranked repo-map excerpt. Tune the default
-1000-token section budget with `TANYA_REPO_MAP_PROMPT_BUDGET`; the legacy
-`TANIA_*` alias is also accepted. If the prompt budget is tight, the repo-map
-drops before skill packs because it is generated and recoverable.
+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.
 
-Use `inspect_repo_map` when the model needs more structural detail by file,
-symbol, or language without burning prompt tokens on the whole map.
+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/repo-map.md](./docs/repo-map.md) for schema, parser status, ranking,
-budget interaction, and cache invalidation.
+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.
 
@@ -392,7 +398,6 @@ Context files are generic JSON envelopes for caller-supplied task metadata, arti
 - `list_files`
 - `read_file`
 - `search`
-- `inspect_repo_map`
 - `inspect_project_context`
 - `find_reusable_artifacts`
 - `build_task_brief`
@@ -400,6 +405,7 @@ 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`