[diangogav]

Summary

• GET /me/emote-bar returns the player's 8 slots. A player without a saved bar gets the default bar.
• PUT /me/emote-bar with body { "slots": string[8] } replaces the whole bar.
  • A default id is always accepted.
  • A pack ref is accepted only if the pack is an active EMOTE_PACK that the player can use (same rule as equipping) and <key>.json exists in the pack.
  • An invalid or unknown ref returns 400 and names the ref.
  • A pack the player cannot use returns 403.
• Each slot is { ref, packId, assetUrl, packUrl, assetsExpiresAt }.
  • For pack emotes these are short-lived signed URLs for <key>.json and pack.json.
  • For default emotes they are all null, because the client bundles those animations.
• A saved slot whose pack is no longer usable reads as a default emote. Storage is not rewritten.
• Both routes use banGuard and Cache-Control: private, no-store, like the other signed-asset routes.

Chain context

This is part of the emote packs feature: emote packs become cosmetics, and each player builds an 8-slot emote bar from the default emotes and the emotes of packs they own. The duel server already relays any emote id up to 48 bytes (diangogav/EDOpro-server-ts#418).

This is a stacked chain into main. Merge the PRs in order. After each merge, retarget the next PR to main.

main
└── #109 EMOTE_PACK cosmetic type and pack validation
  └── #110 emote bar domain and persistence
    └── #111 GET and PUT /me/emote-bar 📍
      └── #112 emote bar fixes

• Starts from: feat(emotes): add emote bar domain and persistence #110.
• Ends at: players can read and save their bar.
• Follow-up: fix(emotes): keep emote bar reads distinct, lenient and atomic on save #112 fixes three defects found in review of this PR: repeated defaults when slots go stale, a non-atomic first save, and strict reads of stored bars. Do not deploy the API between merging this PR and fix(emotes): keep emote bar reads distinct, lenient and atomic on save #112.
• Out of scope: the public bar for opponents, the client and the backoffice.

Size

765 changed lines: 272 production, 493 tests. The maintainer accepted a size exception because the excess over the budget is tests.

Verification

• bun test, bun run lint and bun run build --noEmit all pass on the top of the chain.