The Waiting-on-you card links each ask to its pull or issue, so the owner can look deeper without losing the place #5748

Intent: in a harness, every row of the ui://forge/decision card (MCP asks) opens the pull or issue it is about on this forge, as the Plan card's ready rows already do.

Done looks like:

• [ ] In src/web/studio/cards.ts, each decision row whose ask names a repository (owner/name) and a number carries link: <origin>/<owner>/<name>/pulls/<n> for an ask about a pull, <origin>/<owner>/<name>/issues/<n> for one about an issue.
• [ ] A row gets no link when the origin is not http(s), the repo is not owner/name, or the number is not a positive integer (same rule as the map and pull cards); a row with no pull or issue (e.g. paused) has none.
• [ ] asks rows carry whatever the card needs to tell a pull from an issue, beside the repo and number they already carry, and nothing a reader of that ask could not already see.
• [ ] A test in test/mcp.test.ts (or beside the card tests) calls asks with one pull ask and one issue ask and asserts each row's link, and that a bad origin gives no link; it fails without the change.
• [ ] docs/MCP.md's Cards paragraph says the decision card's rows link to their pull or issue.

Files: src/web/studio/cards.ts, src/http/mcp.ts (asks rows, only if a field is missing), test/mcp.test.ts, docs/MCP.md. Risks: links built from unvalidated text; keep the ^https?:// and owner/name checks. No change to the inbox page itself. Brief: a builder (scout).