What you asked for: /asked lists every ask from a person, its age, and whether anything merged #674

Closes #611

/asked: everything a person asked for in the repositories you can write, newest first, with its age, the pulls that close it, and one state word (waiting, building, shipped, closed). An ask with nothing built after three days is flagged.

The path: the owner, from the board's "needs you" or the asks page, wonders whether something he asked for was heard; he opens /asked; the one primary action per row is open the ask; next that issue.

Built so the thought stream (#653) joins as a second source with the same row shape. Work in progress: the page, the MCP asked tool, the API, tests and looks follow.

Ready for review (replaces the description above). Closes #611.

/asked lists what people asked of the crew in the repositories you can write. By default it shows only what has nothing merged yet, oldest first, because the path is "open the oldest unmet ask". Each row has who asked and when, the pull that answers it, when the crew last ran or commented on it (or "crew not on it yet"), and one word: Waiting, Building, Shipped or Closed. An ask still waiting or building after 3 days shows Nothing built instead.

• Views: Not shipped (default), Nothing built, All; a "Show newest first" switch; ?repo=owner/name for one repository.
• The same rows elsewhere: GET /api/v1/asked?show=&order=&repo= (ro token) and the MCP tool asked {repo?, show?, order?}. Both default to unshipped and oldest first.
• Reached from: the feed's header and the board (one quiet "What you asked for" link each), the asks page, and the palette.
• Access: rows only come from repositories the viewer can write. Agents' issues, imported issues and the direction issue are not asks. Each row carries source: "issue" so the thought stream (#653) can join as a second source.

The path: the owner wonders whether something he asked for was heard. From the feed header, the board or /asks he opens /asked. Its one action per row is to open the oldest unmet ask; next is that issue.

What it removes: nothing, because no screen did this job. It adds one page and three small links, and replaces reading the map issue by issue to find out whether an ask was built.

Looks (taken locally at 1280 and 390 px wide, with 6 seeded asks; no horizontal scroll at 390):

• Desktop: the title and the sentence "6 asked · 1 shipped · 2 with nothing built", then tabs Not shipped 4 / Nothing built 2 / All 6 with "Show newest first" on the right. Then four rows, oldest first: two red Nothing built (19d, 4d, no pull yet), one Waiting, one Building ("pull #2 open"). The meta line ends with the crew's activity.
• Phone: the same; titles truncate before a single badge, and the order switch wraps under the tabs.
• Live: the pull's preview (/trevato/forge/app/pull-674/open, then /asked).

Tests: test/asked.test.ts covers the states, the default order and view, the newest-first option, the flag, the crew's last activity, write-only access, the page with its links from the board and home, the API defaults and 422s, and MCP. It is in the gate. main is merged in, including the tsc fix (#693). The full local gate leaves only the gate-list failure already on main (branch_tell and celld test files).

Correction to the gate line above: the full local gate after merging main has 4 failures, none in this change. The gate list (branch_tell and celld files) and studio #230 also fail on a clean main checkout. crew.test "assignment" and following.test "a proposal names only what is actually ahead" fail only under full-gate load and pass alone, on this branch and on main.