docs: shorten sidebar titles and add moat.yaml

[dpup]

Summary

• Shorten doc frontmatter title fields so the docs site sidebar fits a narrower nav (drops "Credentials"/"Variable"/"Usage"/"Support" suffixes, RFC parenthetical on Token Exchange, etc.)
• Disambiguate Concepts > Sources from Reference > Source types
• Add moat.yaml for Moat sandbox config

Test plan

• Render the docs site locally and verify sidebar labels fit and are still meaningful
• Confirm moat.yaml is picked up by Moat as expected

[claude]

Claude finished @dpup's task in 53s —— View job

---

Code Review

• Gather context and read changed files
• Review moat.yaml
• Review doc title changes
• Post final review

---

This PR is docs-only (frontmatter title shortening) plus a new moat.yaml config. No security, logic, or Go code changes — review is scoped accordingly.

moat.yaml

memory: 12192 (line 10) — 12,192 MB is an odd number. Clean 12 GB would be 12,288 MB. Assuming this is intentional (a headroom calculation or platform-specific limit), but worth double-checking it's not a typo.

CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS: 1 — Experimental flag; fine for a dev sandbox, but worth a comment that this may need revisiting as the feature stabilizes.

Everything else in moat.yaml looks reasonable: runtime, grants, and dependency list all make sense for this repo.

Doc title changes

Most renames are clean improvements (dropping "Credentials" suffix from cloud provider guides, "Usage" from Go Library, etc.). Two titles warrant a second look:

• concepts/02-credential-injection.md: "Injection" — Loses significant context. In isolation (e.g., browser tab title, search result) "Injection" is ambiguous. If sidebar breadcrumbs show "Concepts > Injection" that's still readable, but consider "Credential Injection" if the nav section label already supplies enough context.

• concepts/03-credential-sources.md: "Sources" — Same concern, though the corresponding reference page being renamed "Source types" does help differentiate them. If the goal is sidebar fit, "Sources" works fine under a "Concepts" parent.

Dropping the RFC 8693 parenthetical from the Token Exchange title is fine — it's preserved in the description field and the keywords, so it'll still surface in search.

Overall: Clean, low-risk PR. No security or correctness issues. The memory value in moat.yaml is the only thing worth a quick sanity check before merge.