Pin TinyTools advisory recovery contract

[senamakel]

Pin the published TinyTools recovery contract so hosts can consume its advisory evaluator and validation through TinyAgents' existing TinyTools dependency tree. The pin also incorporates already merged TinyTools sanitization and web-fetch updates since the previous pin. This changes only the TinyTools gitlink; the harness retains its current argument normalization, unknown-tool suggestions, execution and accounting behavior.

Dependency: tinyhumansai/tinytools#61 must land first. This PR remains draft until that dependency is merged.
Part of tinyhumansai/openhuman#7341.

Validation: fresh cargo test -p tinyagents-harness arg_recovery (6 passed), unknown_tool (18 passed), and tools_args_recovery (6 passed), all exit 0. The new gitlink object is published on the canonical TinyTools remote.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}

[senamakel]

Closing this Jev-assisted tool-recovery implementation at the maintainer's request, together with tinyhumansai/openhuman#7341 and its implementation PRs: tinyhumansai/openhuman#7345, #375, and tinyhumansai/tinytools#61.

The investigation did not establish an incremental recovery or task-completion benefit from this adviser for the observed workload. The maintainer's recent local sessions used native structured tool calls. Observed failures primarily involved command execution, missing runtime state, unavailable services, and a declared JSON Schema anyOf requirement that local validation did not enforce. Recognized schema failures also take the existing deterministic recovery path before this adviser. These findings call for focused validation and state-handling changes rather than proceeding with this decision-model integration.

This is a decision not to pursue this implementation; it does not claim that decision-assisted recovery can never be useful. The existing deterministic safeguards and independently merged compatibility fixes remain in place.