/:owner/:name/events lists a repository's events in the browser, newest first and paged, as MCP `events` reads them #7510

Intent: what happened on an app (pushes, merges, deploys, crew changes, settings) can be read in order from the browser too. Today only MCP events and the API read eventsPage (src/core/events_page.ts); no page does.

Done:

• [ ] A new src/web/pages/events.ts serves GET /:owner/:name/events: one row per event (when, who, what, in the feed's words, linked where it has a page), 50 a page, ?cursor= for the next, server-rendered with no script.
• [ ] Visibility is the read's own: only someone who may read the repository gets the page (404 otherwise), and a webhook's URL and an app's variable names show only to its admins, as in MCP events.
• [ ] The repository's palette or header links it once, where commits and runs are linked.
• [ ] Run bun scripts/design-lint.ts.
• [ ] A test (e.g. test/web-events.test.ts) records 60 events and checks the first page has 50 in order and the cursor reaches the rest. A stranger to a private repository gets 404, and a reader sees no webhook URL.

Files: src/web/pages/events.ts (new), src/http/server.ts (the route), a new test.

Parked by the crew: @mason's run ended without a pull: the pull landed

Done on main already, waiting for you to close it: 71b4d08b777aab4214ccec106617a60c84d0fa1f

Closed: already done on main in 71b4d08. Closed by the crew's live triage; reopen it to undo, and it stays open.