The MCP explore tool takes q as llms.txt says, and llms.txt names every filter explore reads #9077

Intent: an outside agent that follows /llms.txt gets the filtered list it asked for, not everything.

Today /llms.txt says MCP: the tool "explore" with {"q"}, but src/http/mcp/tools/explore.ts reads only args.query, so {"q":"kind:app"} silently answers the unfiltered list. The search tool takes q. llms.txt also names only kind: and sort:, though explore reads updated:, owner: and archived: too.

Done when:

• [x] The explore tool's inputSchema has q (same as search) and keeps query as an accepted alias; when both are sent, q wins. tools/list shows q first.
• [x] The line in src/web/standards.ts (llms.txt) names all five keys with their values: kind app|person|forge, sort score|forks|ships|likes|use|fresh|name, updated 1d|7d|30d, owner:<name>, archived yes|no.
• [ ] The explore tool's doc and the here manifest's explore action (src/actions/here.ts) say q too.
• [x] A test calls tools/call explore with {"q":"kind:person"} and gets only people; another reads /llms.txt and finds each of the five keys. Both fail on main.

Files: src/http/mcp/tools/explore.ts, src/web/standards.ts, src/actions/here.ts, a test under test/ (mcp explore). Risks: the OpenAPI/MCP contract snapshot, if one pins the tool's schema, must be updated in the same pull and said so. Fits: a builder (torque/scout).

Reviewed pull #9080 at its head: ticked The explore tool's inputSchema has q (same as search) and keeps query as an accepted alias; when both are sent, q wins. tools/list shows q first.; The line in src/web/standards.ts (llms.txt) names all five keys with their values: kind app|person|forge, sort score|forks|ships|likes|use|fresh|name, updated 1d|7d|30d, owner:<name>, archived yes|no.; A test calls tools/call explore with {"q":"kind:person"} and gets only people; another reads /llms.txt and finds each of the five keys. Both fail on main.. left open: The explore tool's doc and the here manifest's explore action (src/actions/here.ts) say q too. — The tool doc says q, but the here manifest action is unchanged because Action has no argument field; that needs its own issue..

Left open after pull #9080 landed: 1 unticked item remains (The explore tool's doc and the here manifest's explore action (src/actions/here.ts) say q too.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.