chore(claude): memória dos agentes do redesign + launch.json do dev

Memória registrada durante o trabalho no /stake: colisão dos três verbos
pt-BR (resgatar/sacar/colher), diferenciação visual e a superfície dark
do stake, além dos achados do code review.

launch.json declara o dev server (pnpm dev, :3000) para as ferramentas
de preview subirem sem adivinhar o comando.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: r4topunk

.claude/agent-memory/frontend-engineer/MEMORY.md

@@ -1,3 +1,4 @@
 # Memory Index
 
 - [project_i18n_foundation](project_i18n_foundation.md) — i18n Phase 1 foundation: next-intl installed, [locale] routing wired, proxy.ts merged, 50 message stubs created
+- [feedback_ptbr_verb_collisions](feedback_ptbr_verb_collisions.md) — PT-BR: claim/withdraw/harvest = resgatar/sacar/colher, never two of them as "sacar"

.claude/agent-memory/frontend-engineer/feedback_ptbr_verb_collisions.md

@@ -0,0 +1,19 @@
+---
+name: ptbr-verb-collisions
+description: In PT-BR, claim/withdraw/harvest must stay three distinct verbs (resgatar/sacar/colher) — never collapse them all into "sacar"
+metadata:
+  type: feedback
+---
+
+When translating stake/rewards UI to PT-BR, `claim`, `withdraw` and `harvest` must map to three
+distinct verbs: **claim → resgatar/resgate**, **withdraw → sacar/saque**, **harvest → colher**.
+Do not let two of them land on "sacar".
+
+**Why:** the user flagged that `messages/pt-br/stake.json` already has this collision in the
+`lootbox` and `dlg` blocks (`claim` and `withdraw` both render "Sacar"), which makes two different
+onchain actions indistinguishable in the UI. They explicitly asked not to reproduce it in new keys.
+CLAUDE.md's glossary already says claim → resgate; the existing file drifted from it.
+
+**How to apply:** any new PT-BR string in the stake/rewards area (and any future cleanup of the
+existing `lootbox`/`dlg` keys). Also applies to derived nouns: "Falha no resgate" vs "Falha no saque".
+Related: [[project-i18n-foundation]], `docs/i18n/tone-brief.md`.

.claude/agent-memory/ui-designer/MEMORY.md

@@ -5,3 +5,5 @@
 - [project_design_system.md](./project_design_system.md) — Design system setup: Tailwind v4, shadcn/ui New York, theming tokens, font stack
 - [project_known_issues.md](./project_known_issues.md) — Known UI/accessibility issues found in deep review (2026-03-16)
 - [user_profile.md](./user_profile.md) — r4to's profile and collaboration preferences
+- [project_stake_dark_surface.md](./project_stake_dark_surface.md) — /stake is a committed dark island in a system-theme site: scope it with a `dark` wrapper
+- [feedback_visual_differentiation.md](./feedback_visual_differentiation.md) — Redesign = change the visual language and section weights, not the section order

.claude/agent-memory/ui-designer/feedback_visual_differentiation.md

@@ -0,0 +1,50 @@
+---
+name: visual-differentiation-over-reordering
+description: A redesign that only reorders sections reads as "practically identical" — change the language (headers, weights, accent discipline), not the order
+metadata:
+  type: feedback
+---
+
+When asked to redesign a page, reordering sections and reusing the existing panel
+/ eyebrow / accent language is not a redesign. The first `/stake/preview`
+prototype did exactly that and was rejected as "practically identical" to
+production.
+
+**Why:** section order is invisible in a screenshot comparison. What a reviewer
+actually reads as "different" is the visual language: surface recipe, header
+pattern, type scale, accent discipline, and — most of all — **section weights**.
+Uniform slabs stacked at equal weight is the failure mode; it makes every section
+claim the same importance, so the page has no reading order.
+
+**How to apply:** on a redesign brief, commit to ONE recipe per role (one panel,
+one row, one muted tier pair, one accent) and then deliberately vary weight:
+a 56px inline strip for reference data, a medium panel for the user's own data,
+a nearly frameless block for the page's hero visual. Reserve the accent for
+primary CTAs, selected states and key numbers; secondary actions get a quiet
+`bg-white/[0.06]` treatment, and a second brand colour (e.g. Morpheus green) may
+appear as *data* only — never as button, border or glow chrome.
+
+**Corrections the owner made on the next pass (these are taste rules, not
+one-offs — they apply to any surface here):**
+
+- **No section-number eyebrows** (`01 Pick your rider`). Numbering sections is a
+  known AI tell; an eyebrow names a topic in plain language or it doesn't exist.
+  The first fix for uppercase eyebrows was mono `01`–`05` indices, and that got
+  rejected too. Consistent headers are the rhythm.
+- **No sub-cards inside a card.** Rows in a panel are transparent and separated by
+  ONE hairline on the container (`divide-y`), never a lighter fill per row and
+  never `border-t` + `border-b` in the same gap.
+- **Zero decorative dots.** A coloured dot is only allowed when it encodes real
+  state (milestone done/pending). A dot that repeats what the unit text already
+  says ("● 84.21 MOR") dies. Same for `·` chains: max one middle dot per line —
+  separators between list items are CSS borders, not literal characters.
+- **Zero em-dashes and en-dashes in user-facing copy** (both locales). Restructure
+  with period, comma, colon or parentheses. Applies to i18n strings AND to hard
+  coded visible strings like page metadata titles. Code comments are exempt.
+- **No fake precision.** Placeholder numbers drawn as measurement (filled meter
+  tracks, "Overall 87") get deleted rather than restyled; variable rates print
+  with `≈`.
+- **Panel fills were too dark at `bg-white/[0.03]`** — the site's own `--card`
+  step over `--background` is about twice that. `bg-white/[0.06]` is the recipe.
+
+Related: [[stake-dark-surface]]

.claude/agent-memory/ui-designer/project_stake_dark_surface.md

@@ -0,0 +1,38 @@
+---
+name: stake-dark-surface
+description: The /stake family is a committed dark surface inside a system-theme site — scope it with a `dark` wrapper before using white/alpha tokens
+metadata:
+  type: project
+---
+
+The stake pages (production `/stake`, `/stake/[rider]`, and the `/stake/preview`
+prototype) are designed as a **dark arcade island**: hardcoded dark panels, white
+alpha text (`text-white/50`, `text-white/35`), gold accent. The rest of the site
+follows `next-themes` with `defaultTheme="system"` (see `src/app/[locale]/layout.tsx`).
+
+**Why:** a light-theme visitor otherwise gets white/alpha text on a light page —
+the pre-existing production stake components already had this bug (near-black
+`text-foreground` labels sitting on hardcoded dark panels). Fixing it by switching
+to `muted-foreground` would throw away the committed dark direction the art
+depends on.
+
+**How to apply:** when a stake surface uses white-alpha tokens, wrap the subtree in
+`className="dark bg-background text-foreground"` (Tailwind v4 here defines
+`@custom-variant dark (&:is(.dark *))`, and `.dark {}` sets the CSS variables, so
+the wrapper both flips shadcn tokens for Buttons/Dialogs inside it and paints its
+own dark background). `/stake/preview`'s island in `StakePreview.tsx` does exactly
+this. Verify any stake UI change in BOTH color schemes — Playwright
+`newContext({ colorScheme: "light" })` catches it in one shot.
+
+**Gotcha:** a spec that says the island is `bg-white/[0.02]` cannot be taken
+literally on one element — a 2% white fill is a *tint over an assumed dark page*,
+and on a light-theme page it lands on white. Use two nested elements: outer
+`dark bg-background` for a guaranteed dark base, inner `bg-white/[0.02]
+ring-1 ring-white/[0.06]` (same radius) for the lift. Same trap for any
+white-alpha "surface" value inherited from a dark mockup.
+
+Also: the island's h1 and hero paragraph belong OUTSIDE it, on the page's normal
+theme tokens (`text-muted-foreground`, not `text-white/50`), so the page opens
+like Treasury/Auctions do.
+
+Related: [[design_system_overview]], [[stake-preview-visual-language]]

.claude/launch.json

@@ -0,0 +1,12 @@
+{
+  "version": "0.0.1",
+  "configurations": [
+    {
+      "name": "gnars-dev",
+      "runtimeExecutable": "pnpm",
+      "runtimeArgs": ["dev"],
+      "port": 3000,
+      "autoPort": true
+    }
+  ]
+}