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

package/README.md

@@ -296,26 +296,6 @@ 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.
 
-## Reasoning models
-
-Reasoning routes such as `deepseek-reasoner`, `qwen3-thinking-*`, and
-`grok-3-reasoning` are handled as a separate stream. Tanya archives reasoning to
-`.tania/runs/<runId>/reasoning.jsonl`, emits `reasoning_chunk` events, and keeps
-assistant history reasoning-free so replay and verifier inputs stay stable.
-
-Reasoning tokens appear separately in `/cost` and `/budget`. Route rules can set
-`reasoningCap.maxTokens`; built-in defaults are 2k for planning-like turns and
-8k for synthesis/verification/reasoning turns. If the cap is exceeded, Tanya
-emits `reasoning_truncated` and asks the model to finish.
-
-Use `/memory --reasoning <runId>` to inspect archived reasoning. Use
-`TANYA_HIDE_REASONING=1` to hide reasoning from the human UI while preserving
-JSONL/Cosmo events. Verifier reasoning annotations are off by default; enable
-them with `--verbose-verifier` or `TANYA_VERIFIER_INCLUDE_REASONING=1`.
-
-See [docs/reasoning.md](./docs/reasoning.md) for provider notes, billing math,
-budget defaults, and UX modes.
-
 `--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.
@@ -381,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
@@ -388,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`