SystemControl was rendered as two per-system panels (Trump / Macro) that both
flipped the SAME global auto_trade, and its copy claimed a "qualifying Macro
Vibes signal auto-opens a trade". Both are wrong: bot_engine.process_post
early-returns for System 2, so the auto_trade gate only ever fires for Trump
(System 1). Macro Vibes is manage-only — it never auto-opens.
- Macro (`system="btc"`) panel: replaced the misleading Auto-Trade ON/OFF
toggle with a manage-only explainer (open on HL → /adopt via Telegram → bot
manages exits) and a note that the Trump-page switch has no effect here.
- Trump (`system="trump"`) panel: relabeled the switch "TRUMP (System 1)" and
rewrote all copy/status lines to say Trump-only auto-open (was "GLOBAL
(Trump + BTC)" / "both Trump & BTC").
- CLAUDE.md: corrected "No global store (no Redux/Zustand)" — the app DOES use
a small Zustand store (store/dashboard.ts / useDashboardStore); documented
what it holds and the guidance to keep it small.
Note (not a bug): dashboard adopt/release is intentionally Telegram-only —
there are no positions/adopt|hl|release client calls and the UI correctly
points to the Telegram /adopt command. No dashboard wiring is "broken".
tsc + next build clean.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Pre-launch audit findings (frontend):
- trades: unlock private history in-page. TradesPageClient only read a CACHED
view envelope, so a connected user who hadn't visited Settings first saw
"load settings once to unlock" with no way forward. Added an explicit
"Unlock trade history" button that mints the view envelope via
getOrCreateViewEnvelope (one signature, no gas) and reloads — no detour.
- wagmi: broaden connector from injected({target:'metaMask'}) to generic
injected(). The MetaMask pin made Rabby / Coinbase ext / Brave / Frame / OKX
and non-MetaMask browsers fail to connect. wagmi v2 EIP-6963 discovery covers
all injected wallets; still uses the native provider path (not the MM SDK).
- sitemap: drop /settings. It was emitted in sitemap.xml while robots.ts
disallows it — a self-contradicting crawler signal. Private pages stay out
of both.
- docs: note the app runs on port 3001 (package.json), not 3000. The CLAUDE.md
verify sweep targeted 3000 and would have reported every page as down.
- routing: COMMIT the Next.js 16 migration that was sitting uncommitted —
delete middleware.ts, add root proxy.ts (next-intl createMiddleware), update
next-env.d.ts. Vercel deploys from git, so leaving proxy.ts untracked would
have shipped the old routing. `next build` confirms "Proxy (Middleware)" is
active and all routes compile. tsc clean.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Convention file every new Claude session reads first when opening this
repo. Documents:
- Next.js 16 quirks (proxy.ts replaces middleware.ts, async params,
i18n shelved).
- Full route + component map.
- API layer + auth model (EIP-191 signed envelopes).
- Design system tokens (oklch colors, .macro-* classes, dark mode).
- "Looks like a bug but isn't" section — including the /en/btc → /en/macro
rename + the isZh=false i18n-shelved pattern.
- SEO/GEO surface (layout.tsx JSON-LD + public/llms.txt + sitemap) that
must be kept in sync when renaming features.
- Cross-repo coupling points with the backend.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
k