fe: Instructions file for Codex

Codex Instructions

• After making code changes, do not run npm run build or npx tsc unless the user explicitly asks for it.
• If verification is useful, prefer lighter checks that are relevant to the changed files, or ask before running expensive project-wide commands.
• After modifying source files, run ./node_modules/.bin/prettier --write on the changed files and verify them with ./node_modules/.bin/prettier --check before delivery. Follow .prettierrc.json; do not leave formatting-only violations in changed files.
• Prefer native type-checking APIs over lodash for type narrowing: use Array.isArray instead of _.isArray, typeof x === 'number' instead of _.isNumber, x == null instead of _.isNil, etc. Lodash type guard functions are not recognized by TypeScript when @types/lodash is unavailable, leaving unknown types un-narrowed.

页面修改原则

• 所有页面修改都要检查视觉美观与周边协调，包括按钮间距、水平/垂直对齐、颜色、图标与文字的实际可见间距；不能只检查控件外框或功能是否可用。
• 提示浮窗按内容调整宽度：不超过 20 个字的短句尽量保持一行，避免过窄造成无意义换行；长文案与窄视口仍须合理换行，不能溢出屏幕。背景与箭头使用系统 Tooltip 的主题、颜色及透明度，与“筛选”旁的提示一致，不单独硬编码不透明背景。
• 所有修改都要控制影响范围，优先采用页面或组件局部作用域；检查相关状态、共用组件调用方与集成入口，避免修复一处却让其他位置回归，并完成与改动相关的验证。

React Router Routes and Deployment Prefixes

• This project uses React Router's basename for subpath deployments. Use Router-provided paths for in-app routes. For example, with a /flashcat basename, useLocation().pathname and React Router's history.location.pathname are /dial-analysis, while window.location.pathname or global location.pathname is the full browser path /flashcat/dial-analysis.
• When building in-app navigation, calling React Router's history.push or history.replace, or preserving the current route, use Router-relative paths such as useLocation() or history.location. Do not use global location.pathname as a Router path or prepend basename to a Router path; either can duplicate the prefix and produce a URL such as /flashcat/flashcat/polaris.
• useLocation() is a snapshot for the current render. If an asynchronous callback needs the latest path or query string when it runs, read history.location from the corresponding Router history instead of relying on a stale value captured by a closure.
• Use window.location or global location only when browser-level URL semantics are needed, such as a full-page navigation, reload, or generating a browser URL that includes the deployment prefix. Their paths have different semantics from Router paths. The native History API on window.history is also different from React Router's history.
• For copied, shared, saved, or custom-generated URLs, first distinguish a Router path, an app-relative URL, and a fully qualified URL. Use the existing URL helpers (getAppBaseUrl and addAppBasePrefix in src/utils/appUrl.ts) instead of concatenating basePrefix ad hoc. The helper leaves absolute URLs untouched and avoids duplicating an existing prefix.
• $local_url is a fully qualified app base URL, including origin and deployment prefix. After expanding it, do not prepend basePrefix again. Likewise, window.location.pathname already includes the browser prefix, while useLocation().pathname does not.
• The Vite prefix plugin rewrites recognized URL sinks such as direct window.open calls; it does not rewrite URLs copied to the clipboard, displayed in inputs, stored in config/data objects, or passed through custom components. Handle those values explicitly with the URL helpers.