v0.2.2 Provider Dialects, Schema Output & Context Config

Dogfooding fixes: Tether implemented most of this release itself through its own CLI and a claude -p provider.

Features

• {schema} placeholder (#51) for command providers: constrain output to the act schema (e.g. claude -p --json-schema '{schema}'); replies may be structured objects with cmd/stdin. Measured: with claude -p this adds ~2k prompt tokens per call, so it is a reliability option, not a saving.
• tether misses (#53): list unparsed model replies (nudges) as fixture-ready JSONL for tests/fixtures/dialects.jsonl.

Fixes

• Configurable context budget and fold window (#54): --context-tokens / --fold-after on tether run and tether pipeline, context_tokens / fold_after on MCP tether_run, and per-provider keys in providers.yaml. The 8k context and fold-after-2 defaults made large-context backends re-read the same files forever.
• Table-driven tool-call dialect extractors (#52): built-in <tool_call> JSON, raw JSON, <parameter name="cmd"> blocks and text act(...), extendable with tether.register_dialect or a dialects: regex list in providers.yaml.

Docs: https://igormcsouza.github.io/tether/reference/providers/