A note's status says "Shipped in <release>", or "Shipped on <date>" until a release includes it #5789

A closed note whose fix was merged now reads "Shipped in <release>" once a release holds the fix, and "Shipped on <date>" while none does. test/apps-feedback.test.ts passes (17 tests) and bun x tsc --noEmit is clean. I did not run the rest of the suite or design-lint.

• How a note finds its release: the merged pull whose description says "Closes #N" is the one that shipped the note's issue. Its release is the newest healthy row in src/release/record.ts with that pull number. The new helpers are mergedPullClosing in src/core/pulls.ts and releaseOfPull in record.ts. statusOf in src/actions/app_notes.ts uses them, and the toolbar panel already prints the label, so proxy.ts is untouched.
• The date: it is the pull's merge date. A note closed by hand with no merged pull keeps the old behaviour, the issue's close date.
• Release name: the release table stores a commit, not a version. A release's "name" is therefore its 12-character commit id, the same one the Releases page shows. Mapping a pull to a version such as 0.7.251 would mean searching git history on every status read. I left that out; if you want the version, it's a follow-up.
• Only the forge's own repository has release rows. For any other app the note always says "Shipped on <date>".
• Test: the new test closes one note whose pull is in a release and one whose pull is merged but unreleased. It fails without the change. It uses its own app, because the other tests had used up the shared app's daily note limit.

Phone layout (#5222) can proceed.

Closes #5412

A closed note whose fix was merged now reads "Shipped in <release>" once a release holds the fix, and "Shipped on <date>" while none does. test/apps-feedback.test.ts passes (17 tests) and bun x tsc --noEmit is clean. I did not run the rest of the suite or design-lint.

• How a note finds its release: the merged pull whose description says "Closes #N" is the one that shipped the note's issue. Its release is the newest healthy row in src/release/record.ts with that pull number. The new helpers are mergedPullClosing in src/core/pulls.ts and releaseOfPull in record.ts. statusOf in src/actions/app_notes.ts uses them, and the toolbar panel already prints the label, so proxy.ts is untouched.
• The date: it is the pull's merge date. A note closed by hand with no merged pull keeps the old behaviour, the issue's close date.
• Release name: the release table stores a commit, not a version. A release's "name" is therefore its 12-character commit id, the same one the Releases page shows. Mapping a pull to a version such as 0.7.251 would mean searching git history on every status read. I left that out; if you want the version, it's a follow-up.
• Only the forge's own repository has release rows. For any other app the note always says "Shipped on <date>".
• Test: the new test closes one note whose pull is in a release and one whose pull is merged but unreleased. It fails without the change. It uses its own app, because the other tests had used up the shared app's daily note limit.

Phone layout (#5222) can proceed.