Every pillar's ask-to-live time on the map: median hours from an issue opening to its change live in production, last 7 days #1185

P7 Command: the owner measures every limb by ask-to-live time; the map counts merges per pillar (mergedByPillar) but not how long the asking took.

Done looks like.

• [ ] src/core/pillars.ts computes, per pillar over the same 7-day window, the median and slowest ask-to-live: from the issue's creation to the first production deploy whose commit contains the merge of the pull that closed it.
• [ ] The map page and /api/v1/repos/:o/:r/map show it beside the merged count (askToLive: {medianHours, slowest: {number, hours}}); a pillar with none merged shows a dash.
• [ ] Tests in the pillars test: a known issue/merge/deploy timeline gives the expected numbers.
• [ ] askToLive is in the MCP's map and limb answers, as in the JSON.
• [ ] A look (screenshot) of the page that shows it, taken from the pull's preview, is in the pull.
• [ ] A test that goes red in this pull is fixed in this pull, whoever's it is.

Files. src/core/pillars.ts, src/web/pages/map.ts, its test.

Risks. A deploy record may not name the commits it contains; if not, use the deploy's commit and ancestry (git merge-base --is-ancestor), cached.

Fits. Mason.

Before pushing. bun x tsc --noEmit and the test files named here, quoted in the pull. One pull, green on its first push.

One pillar: this serves exactly the one it is linked under. Done means reachable on the page, through MCP, in a test and by eye (#334).