Frontend asset handling & Functioning profile page

[Driedoutjerky]

Summary

• Adds frontend asset handling for the Memory Egg equipment flow.

Added

• Created an asset registry to map stable asset keys to frontend image files.
• Added real profile page data from existing mock hooks.
• Added shop item preview images for backgrounds and decorations.
• Added inventory item preview images for backgrounds and decorations.
• Added equipped cosmetic rendering on the dashboard egg.
• Added equipped background rendering on the dashboard window scene.
• Updated mock shop item data to include asset_key.
• Updated mock egg recalculation to store equipped asset keys.

Asset handling decision

• The backend should not return actual frontend file paths such as FlowerCrown.png.

Instead, backend/database should store and return stable keys such as:

{
  "asset_key": "flower_crown"
}

Testing

Tested locally with

npm run dev

To get will_balance,

const user = JSON.parse(localStorage.getItem("memory_egg_user"));

localStorage.setItem(
  "memory_egg_user",
  JSON.stringify({
    ...user,
    will_balance: 9999,
  })
);

location.reload();

Expected output

[ ] Run npm run build
[ ] Run npm run lint
[ ] View profile page to see if it's properly showing the user's profile data rather than placeholders
[ ] Buy a decoration from Shop
[ ] Equip the decoration in Inventory
[ ] Confirm the cosmetic appears on the Dashboard egg
[ ] Buy a background from Shop
[ ] Equip the background in Inventory
[ ] Confirm the Dashboard window background changes
[ ] Confirm owned items do not show “Not enough Will”

[A1VERMAN]

Nicely done, thank you for writing all of the info of the cosmetics, that probably took a long time.