feat: integrate goals redesign across components

GOALS_FIGMA_MAKE_PROMPT.md

@@ -0,0 +1,41 @@
+# Figma Make prompt: Papyrus Goals
+
+Design a new Goals experience for **Papyrus**, a cross-platform book library and reader for physical and digital books. The purpose is to help people understand their reading progress and build a reading habit. Make it feel like a thoughtful part of a reading app: clear, calm, approachable, and easy to use.
+
+Focus on the visual design and overall experience. You have freedom to rethink the composition, hierarchy, and interactions. Do not turn this into a dense dashboard or an exhaustive feature specification.
+
+## Design style
+
+Use **modern, minimal product design grounded in Material Design 3**, with the warmth and restraint of a well-designed reading app. Favor clean sans-serif typography, clear hierarchy, generous but deliberate spacing, subtle surface differences, and consistent rounded controls. Use simple outline icons from one coherent icon family.
+
+The result should feel polished and practical. Avoid decorative gradients, glass effects, oversized statistics, excessive shadows, motivational slogans, and unnecessary visual clutter. Let typography, alignment, and spacing do most of the work.
+
+Choose a cohesive layout rather than forcing every piece of content into a card. Where you use repeated cards or controls, keep their proportions and alignment consistent. Buttons should fit their purpose and labels; short inputs should not stretch across a large desktop panel. Keep activity information easy to scan without repeating long book titles unnecessarily.
+
+## Colors and themes
+
+Provide **Light and Dark** versions using the same visual language and layout. Use Papyrus’s existing palette:
+
+| Role | Light | Dark |
+| --- | --- | --- |
+| Primary accent | `#5654A8` | `#C3C0FF` |
+| Text on primary | `#FFFFFF` | `#272377` |
+| Background | `#FFFBFF` | `#1C1B1F` |
+| Main text | `#1C1B1F` | `#E5E1E6` |
+| Secondary text | `#47464F` | `#C8C5D0` |
+| Subtle borders | `#C8C5D0` | `#47464F` |
+| Soft accent surface | `#E2DFFF` | `#3E3C8F` |
+
+Use purple sparingly to guide attention and indicate selection. Keep most surfaces neutral and maintain readable contrast. Also show how the design adapts to a high-contrast, grayscale e-ink display with solid surfaces and minimal motion.
+
+## Cross-platform design
+
+This is a **Flutter application for Android, iOS, web, Windows, macOS, and Linux**. Design it as one coherent product that adapts naturally to phones, tablets, and desktops, rather than a desktop dashboard squeezed onto a phone.
+
+Show representative phone, tablet, and desktop layouts. Account for touch, mouse, keyboard, visible focus, larger text, and system safe areas. Use bottom navigation on phones and sidebar navigation on wide screens as surrounding app context. Adapt secondary interactions to suitable mobile sheets and desktop dialogs or panels. Keep essential actions easy to reach without consuming excessive space.
+
+## Deliverable
+
+Create a visually convincing, interactive prototype of the Goals experience, including a representative overview, an activity/history view, and a secondary interaction that demonstrates the shared component style. Use concise, natural copy and realistic sample content, including a long book title, to demonstrate a balanced layout.
+
+Prioritize visual coherence, readability, and a strong responsive composition over the number of features shown. Establish a reusable typography, spacing, surface, and control system that could also guide the rest of Papyrus.

GOALS_INTEGRATION.md

@@ -0,0 +1,44 @@
+# Goals integration
+
+The coordinated `feat/goals-redesign` branches target `development` in reader,
+server, client, and this workspace. No component version changes are included.
+
+The reader exposes generic observations; the client owns durable foreground
+tracking, goal projections, and the adaptive Goals interface; the server validates
+owned immutable activity and synchronizes rule/period history. Detailed contracts
+and local validation commands live in:
+
+- `reader/docs/integration.md`
+- `client/docs/goals-tracking.md`
+- `server/docs-tracking.md`
+
+Merge the reader change before the client uses its committed revision. Merge the
+server alongside the client, and deploy its migration/publication/PowerSync streams
+and advertised tracking capability before the integrated client release. Merge
+workspace pins after their component PRs. Use the established development-to-master
+release workflow when ready; this work does not trigger a version-based release.
+
+## Coordinated changes
+
+- [Reader #5](https://github.com/PapyrusReader/reader/pull/5): generic activity observations, committed revision `bc617deeaf2ae684f20c1000ed7cd52f9a61d0a7`.
+- [Server #12](https://github.com/PapyrusReader/server/pull/12): owned ledger and tracking capability, committed revision `91a1612a0c650f07ce0d7e3fe5266efe3969eeaa`.
+- [Client #40](https://github.com/PapyrusReader/client/pull/40): Goals and durable foreground tracking, committed revision `6fa232c0b4eeacd293d17126907cd932b843a05e`.
+
+## Validation evidence
+
+Final client integration: 1,541 tests passed, 19 skipped; final focused identity,
+tracker, and persistence checks: 11 passed. Final goal replacement, deadline, UI,
+projection, and persistence regressions: 41 passed. Analysis, formatting, bootstrap tests,
+and production web build passed. Android and Chromium host checks exercised real
+EPUB/PDF reading, durable checkpoints, exposed coverage, and pause/exit behavior.
+Light/dark/e-ink Goals and fixed-footers were inspected at phone, tablet, desktop,
+and enlarged text sizes. Screenshots are in the client tracking documentation.
+
+Reader package: 145 tests passed; package/example checks, web build, browser
+smoke checks, and worker drift passed. Server: 39 focused route/service/migration
+checks and the final 12 aggregation/ownership regressions passed; Ruff, formatting,
+and Mypy passed. Migration tests preserve pre-existing data.
+
+Shared aggregation fixtures cover concurrent-device overlap and coverage. Live
+two-device PowerSync transport was not exercised; this remains an opt-in check
+with configured services, rather than a claim implied by local database tests.