Agent surface lane: tanstack family merge

[omridevk]

Parent

#579

What to build

The two overlapping tanstack tool families (browser verb tools and server adapter tools) merge into one set of metered procedures. Starts with a verb-by-verb matrix: canonical schema, binding (client verb vs server adapter), card renderer, and compatibility impact per operation; genuinely distinct operations survive distinctly. Reads (router state, route tree, caches) classify free or sensitive per the spec; navigation and invalidation mutations ask.

Spec: docs/superpowers/specs/2026-08-22-agent-api-surface-design.md (facade collapse — tanstack; loader/query-cache reads are sensitive).

Acceptance criteria

• Verb-by-verb matrix agreed in the PR before implementation
• One procedure per operation; no duplicated family remains
• Loader data and query cache reads classified sensitive
• Card renderers preserved for the surviving procedures

Blocked by

• Agent surface lane: gate core #583 (gate core)