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

package/README.md

@@ -267,6 +267,35 @@ schema-invalid tool responses before they reach model history.
 See [docs/mcp.md](./docs/mcp.md) for the full schema, transports, server tools,
 and security model.
 
+## Multi-model routing
+
+Tanya can route each agent step to a different provider/model. Planning and
+simple tool-call turns can use cheap chat models, while synthesis,
+verification, and reasoning turns can use stronger models only when needed.
+
+Default route profile:
+
+| Step | Route | Fallback |
+| --- | --- | --- |
+| `planning` | `deepseek/deepseek-chat` | `qwen/qwen3-coder-plus` |
+| `tool_call` | `deepseek/deepseek-chat` | `groq/llama-3.3-70b-versatile` |
+| `synthesis` | `deepseek/deepseek-reasoner` | `openai/gpt-4.1-mini` |
+| `verification` | `deepseek/deepseek-reasoner` | `openai/gpt-4.1-mini` |
+| `reasoning` | `deepseek/deepseek-reasoner` | `qwen/qwen3-coder-plus` |
+
+Project routes live in `.tania/routes.json`; user-global routes live in
+`~/.tanya/routes.json` with a legacy read fallback from `~/.tania/routes.json`.
+Use `/route` in the REPL to inspect the effective table, `/route show
+<stepType>` to inspect one step, `/route set <stepType> <provider>/<model>` for
+a session-only patch, and `/route reset` to clear session patches.
+
+Escalations are visible: if a cheap route exhausts the malformed tool-call
+repair budget, Tanya emits `escalation_event` and uses the route fallback once,
+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.
+
 `--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.
@@ -332,6 +361,30 @@ 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
+
+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.
+
+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.
+
+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.
+
+Use `inspect_repo_map` when the model needs more structural detail by file,
+symbol, or language without burning prompt tokens on the whole map.
+
+See [docs/repo-map.md](./docs/repo-map.md) for schema, parser status, ranking,
+budget interaction, and cache invalidation.
+
 Context files are generic JSON envelopes for caller-supplied task metadata, artifacts, instructions, and verification commands.
 
 ## Current Tools
@@ -339,6 +392,7 @@ 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`