v1.5.0: Social & Retention — contracts, leaderboards, achievements, daily streak

[NeverEndingCode]

Implements v1.5, the final phase of the v1.2–v1.5 expansion. Spec and 12-task plan are in the first two commits; the remaining ten are the implementation, one per task.

What's in it

• Daily contracts — three a day, rotating at midnight UTC, generated deterministically from the date so everyone gets the same three types, with targets scaled to each player's own output and level.
• Global leaderboards — six boards aggregated server-side from canonical saves behind a ~60s cache, with avatars, usernames and badge mini-icons.
• Achievements — 19, pure prestige, unlocked automatically (including from offline accrual), shown as a badge case with an unlock toast.
• Daily streak — 7-day escalating claim in the header banner; a missed UTC day resets it.
• social.* tunables — all the numbers above are Balancing-tab editable and event-overlayable.

Design points worth a look

• Type ids aren't stored in the save. They're re-derived from dateKey, which is what guarantees client and server agree without a sync step. Targets and baselines are stored — a rate-scaled target recomputed on every read would recede as fast as the player approached it. tests/contracts.test.js and the e2e suite both pin this.
• Locked-lane substitution. Three of the six contract types need Cold Storage. Rather than hand a new player two dead contracts, locked picks are deterministically swapped for base-lane ones — two locked players still match each other exactly.
• The achievement sweep runs in two places, because the two ways state advances are disjoint: after every successful action (applyAction), and after evaluate() on the load path. The second is what catches lifetime-FLOPS thresholds crossed while a player was offline, which no action touches.

A real bug the e2e suite caught

The global boards are cache-fronted, so opting out left a player visible for up to 60 seconds. The per-event board has always been immediate — v1.4 went out of its way to make opt-out live rather than a join-time snapshot ("hard requirement 1") — and this control must not quietly mean something weaker on the newer boards. PUT /api/me/leaderboard-opt-out now invalidates the cache, with a unit regression test pinning it. This is exactly the class of thing the whole-branch review has historically caught, so it's worth a second pair of eyes.

Two pre-existing tests needed updating

Adding unlockedAchievements to successful action results broke one toEqual assertion, and the sweep's goalCtx call broke two tests that hand-built a runtime-fields-only config. Both fixed at the assertion/fixture level rather than by suppressing the sweep.

The one judgment call, flagged again

social.contractFlopsMin is a floor on the FLOPS contract target (no upper clamp, so it stays a pure rate scale above it). Without it a zero-output player — fresh save, or the instant after a Migrate — gets a target of 0, which is already met, and the contract auto-completes free. Set it to 0 in the Balancing tab to restore the unguarded behaviour. Documented in spec §5.1 and the README.

Verification

• npm test — 415 passed, 28 files (was 318 on main)
• cd client && npm run build — clean
• tests/e2e/smoke-v15.mjs — 7/7 PASS, all seven checklist items
• tests/e2e/smoke-v14.mjs — 9/9 PASS, no regressions from the shared-code changes

Not tagged or pushed as a release — per the usual ritual that's merge, then tag main, then push the tag.

🤖 Generated with Claude Code

https://claude.ai/code/session_013HLPH7zGymsz31RarDnNKS