MCP `asked` draws a card in MCP Apps hosts: what you asked the crew, its state and the pull that closes it

Intent: the owner checks on their asks inside the harness, flagged ones first, and taps through to the pull.

Done:

[ ] src/web/studio/cards.ts gains an asked card kind and CARD_OF_TOOL.asked = "asked", built from the answer asked already returns: status N waiting · M flagged, one row per ask (flagged first): its words cut to 80 characters → waiting, building, shipped or closed, linked to the closing pull when there is one, else the issue, on this forge only; at most 20 rows.
[ ] The tool's doc string and text answer stay as they are, so docs/MCP.md does not change.
[ ] A test calls asked through the MCP route with two asks (one flagged) and checks the card's order, states and links.

Files: src/web/studio/cards.ts, src/http/mcp/tools/asked.ts (only if the card needs more than the answer), a new test.

Waits for the pulls card only because both add a kind to the same lists in cards.ts.

MCP `asked` draws a card in MCP Apps hosts: what you asked the crew, its state and the pull that closes it #7376