fixes: what the audit turned up

- POST /api/diary/day finds a day's entry, or starts it at the root of the
  diary, by the server's clock. T, the calendar and a capture all use it, so
  they can no longer write two entries for one day: before, T counted days by
  the browser's midnight and wrote into whichever diary folder was last open.
- A Ctrl-P result opens beside the results, as a / result does, so n and N
  go on from it rather than finding no search.
- A card's description resolves its [[links]] the way a document does, and
  following one leaves the card for what it leads to.
- gf on the board opens a card's notes. Enter was documented for that, but
  Enter turns the card over.
- The pane header and the status line show where the open node is, rather
  than where the list is, so a node from another space shows its own path.

web/src/lib/api.ts

@@ -176,6 +176,8 @@ export interface Card {
   position: number
   created_at: number
   updated_at: number
+  /** Where each `[[title]]` in the description leads, as a document's do. */
+  wikilinks: Record<string, string>
 }
 
 /** A step on a card's checklist. */
@@ -492,6 +494,13 @@ export const api = {
   /** A month's diary entries: `2026-10`. */
   diaryDays: (month: string) => request<DiaryEntry[]>(`/diary/days?month=${encodeURIComponent(month)}`),
 
+  /**
+   * The entry of a day, `2026-10-22`, or of today on the server's clock;
+   * started when there is none, which `created` says.
+   */
+  diaryDay: (day?: string) =>
+    request<{ id: number; created: boolean }>('/diary/day', { method: 'POST', body: body({ day }) }),
+
   /** The entries before and after a diary entry, by date. */
   diaryAround: (id: number) =>
     request<{ prev: DiaryEntry | null; next: DiaryEntry | null }>(`/diary/around/${id}`),