add Ko-fi bean

.beans/nuzlocke-tracker-bw1m--errors.md

@@ -1,10 +1,11 @@
 ---
 # nuzlocke-tracker-bw1m
 title: Errors
-status: todo
+status: completed
 type: epic
+priority: normal
 created_at: 2026-03-20T15:19:43Z
-updated_at: 2026-03-20T15:19:43Z
+updated_at: 2026-03-20T15:39:27Z
 ---
 
 Container for crash and blocker beans created by Talos.

.beans/nuzlocke-tracker-d5ht--bug-typescript-build-fails-due-to-optional-propert.md

@@ -0,0 +1,29 @@
+---
+# nuzlocke-tracker-d5ht
+title: 'Bug: TypeScript build fails due to optional property type mismatches in journal components'
+status: todo
+type: bug
+priority: high
+created_at: 2026-03-20T15:39:00Z
+updated_at: 2026-03-20T15:39:00Z
+parent: nuzlocke-tracker-bw1m
+---
+
+The frontend TypeScript build fails with 3 errors due to `exactOptionalPropertyTypes` being enabled.
+
+## Errors
+
+1. `JournalEntryPage.tsx:76` - `bossResults` and `bosses` props passed as `undefined` to `JournalEditor`
+2. `JournalEntryPage.tsx:92` - `bossResult` and `boss` props passed as `undefined` to `JournalEntryView`
+3. `RunEncounters.tsx:1170` - `bossResults` and `bosses` props passed as `undefined` to `JournalSection`
+
+## Root Cause
+
+Optional props in interfaces are declared as `prop?: Type` but callers pass `undefined` values from React Query hooks. With `exactOptionalPropertyTypes: true`, TypeScript requires `prop?: Type | undefined` to allow explicit `undefined` values.
+
+## Fix
+
+Update the interfaces in these files:
+- `JournalEditor.tsx` lines 9-10: change to `bossResults?: BossResult[] | undefined` and `bosses?: BossBattle[] | undefined`
+- `JournalEntryView.tsx` lines 8-9: change to `bossResult?: BossResult | null | undefined` and `boss?: BossBattle | null | undefined`
+- `JournalSection.tsx` lines 9-10: change to `bossResults?: BossResult[] | undefined` and `bosses?: BossBattle[] | undefined`

.beans/nuzlocke-tracker-oar4--ko-fi-integration.md

@@ -0,0 +1,19 @@
+---
+# nuzlocke-tracker-oar4
+title: Ko-fi Integration
+status: draft
+type: feature
+priority: deferred
+created_at: 2026-03-20T15:38:23Z
+updated_at: 2026-03-20T15:38:23Z
+---
+
+Add Ko-fi integration to allow visitors to contribute toward hosting costs. This is not about monetization — it's a way for users who enjoy the tool to optionally help cover server/infrastructure expenses.
+
+## Open Questions
+
+- [ ] Where should the Ko-fi link/button live? (footer, about page, dedicated page, or subtle banner?)
+- [ ] Should it be a simple outbound link to a Ko-fi page, or use Ko-fi's embeddable widget/overlay?
+- [ ] Should there be any acknowledgment for supporters (e.g., a thank-you page, supporter list)?
+- [ ] Should this be gated behind user auth (only shown to logged-in users) or visible to everyone?
+- [ ] Any legal/tax considerations to document?

.beans/nuzlocke-tracker-t90q--crash-backend-journal-entries-model-api-and-migrat.md

@@ -1,11 +1,11 @@
 ---
 # nuzlocke-tracker-t90q
 title: 'Crash: Backend: Journal entries model, API, and migration'
-status: todo
+status: completed
 type: bug
 priority: high
 created_at: 2026-03-20T15:30:02Z
-updated_at: 2026-03-20T15:30:24Z
+updated_at: 2026-03-20T15:39:13Z
 parent: nuzlocke-tracker-bw1m
 blocking:
     - nuzlocke-tracker-vmto
@@ -18,3 +18,7 @@ Manual review required before retrying.
 
 Bean: nuzlocke-tracker-vmto
 Title: Backend: Journal entries model, API, and migration
+
+## Resolution
+
+The underlying bean (nuzlocke-tracker-vmto) was already completed before the crash was detected. All backend work for journal entries is implemented and functional. A separate bug bean (nuzlocke-tracker-d5ht) was created for frontend TypeScript errors discovered during review.