[alistairjcbrown]

The site's half of the public profile work. The Worker's half is clusterflick/api-profiles on the same branch name. Deploy order: Worker, then Firestore rules, then this site. If the rules and site go out first, a reader could hide a section the old Worker still sends.

Settings: /personalise/profile/

• One draft, one Save. Address, about you, favourite films and what it shows sit on one page, saved with one button in a bar stuck to the bottom of the screen. A new handle is claimed in the same write. The bar says what stops a save, asks before a rename frees the old address, and leaving with unsaved changes asks first.
• Live preview. It sits beside the settings from 1100px. Narrower, it's a full-screen dialog opened from the save bar. It draws the profile page's own hero and sections, so the two can't differ.
• Handle checked as it's typed, and again on saving.
• Publishing is a moment, not a switch. It first lists what goes public and what stays hidden, then saves the draft and public: true in one write. The card then lights up with the address, Copy link and Share. Making it private never waits for anything.
• Account bar. Its Public profile panel now only says where the profile stands and links to the settings page.

Profile page: /u/<handle>/

• Favourites as the hero. Up to four, fanned over a blurred wash of their posters. A favourite that's showing links to its film page.

• Taste line under the name, e.g. "Mostly drama · Big on the 2000s · 2 Wong Kar-wai films". It only appears with the stats, and each part only when it's true enough to say.

• Owner: Edit profile and Copy link.

• Watchlist: leads with what's showing this week and links to the planner. Its buttons speak of the owner by name.

• Comparison, offered not shown. A signed-in visitor gets a card ("You have 4 films in common with Siobhán") with Compare, which opens groups as poster stacks:

  • both want to see, with "Plan together";
  • both seen;
  • each one's films the other has seen.

  Signed out, the card invites the visitor to start their own lists. Either card can be dismissed for the day. Only lists the owner shows are compared.

Data and rules

• New fields on users/{uid}/meta/profile:
  • sections, required before public: true;
  • displayName, stripped of HTML and JSON-significant, control and bidirectional characters;
  • links;
  • favourites.
• Validation in three places. Each field is checked in @/lib/user-profile, again in firestore.rules (held to the module by rules-copy.test.ts), and again by the Worker.
• Revoked capability. Without it, switching the profile off is the only change allowed.

Testing

• npm run lint is clean.
• Unit tests: pass under src/lib, covering the draft, comparison, taste line, favourites, identity and day-long dismissals.
• Firestore rules: npm run test:rules passes all 101 tests against the emulator.
• Storybook: the profile, settings and personalise page stories pass locally, but only against stand-in data, because the real releases couldn't be downloaded in my session. Two existing Import stories on /personalise fail the same way on main with that stand-in data. CI runs them against the real data.
• Not yet seen with real data:
  • the poster wash behind the hero;
  • "Plan together" and the "showing this week" line;
  • a long comparison group closed to a pile.

---

Generated by Claude Code