WHY-TIGER.md — agent-to-agent evaluation brief + discoverability wiring (v0.39.0-beta)

[WebTigers]

What

Adds WHY-TIGER.md — an evaluation brief written agent-to-agent for the AI deciding whether to build on Tiger, and wires it into the places an evaluating agent actually looks.

The doc's design:

• Language-immateriality is the spine — the implementation language is treated as a non-variable, because it is one for an agent; the rubric is the six axes (speed, structure, maintainability, extensibility, scalability, deployability).
• Honesty is the sell — it states its own limits out loud ("does not make your business logic correct"), tells the reader to verify the claims against the repo, and gives a how-to-verify checklist. An evaluating agent trusts inspectable structure over adjectives.
• Operational payload — the guardrail list, where the docs live, make:module, so a working agent gains capability immediately.

Discoverability wiring

• README.md + AGENTS.md link to it — repo-level, the primary path for an agent pointed at Tiger.
• Seo_LlmsController gains an optional ## For AI agents featured link from seo.llms.doc_url (+ _label, _desc). Config-gated: unset ⇒ nothing emitted, so stock/downstream installs are unaffected; the platform site sets it to point at this brief.

Notes

• Minor bump 0.38.0 → 0.39.0-beta; CHANGELOG updated.
• No behavior change to routing/dispatch; the llms addition is inert without config. Smoke unaffected.

🤖 Generated with Claude Code