claude code agent 227
13a333632a
F1: the bug was the color never reaching the DOM (Mantine Avatar's --avatar-bg overrode it); the pure agentGlyphBackground always returned distinct colors, so the existing unit tests would pass even against the broken Avatar. Add a data-testid on the glyph Box and two render tests: one asserts the emoji glyph's applied inline background equals agentGlyphBackground(name); one asserts two palette-distinct agents reach the DOM as different backgrounds. React applies styles via the CSSOM (hsl→rgb), so the assertion normalizes both sides through the same path and compares against the real function output (no frozen literal). Fails against the pre-fix Avatar (no inline background / no glyph testid). F2: the top-level AgentAvatarStack JSDoc and two test titles still described the old z-order (agent glyph in front, human behind); the PR flipped it (human launcher badge in front, zIndex 2 > glyph 1). Updated the JSDoc + both titles to match. vitest: 10 passed (+2). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
React + TypeScript + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Babel for Fast Refresh
- @vitejs/plugin-react-swc uses SWC for Fast Refresh
Expanding the ESLint configuration
If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:
- Configure the top-level
parserOptionsproperty like this:
parserOptions: {
ecmaVersion: 'latest',
sourceType: 'module',
project: ['./tsconfig.json', './tsconfig.node.json'],
tsconfigRootDir: __dirname,
},
- Replace
plugin:@typescript-eslint/recommendedtoplugin:@typescript-eslint/recommended-type-checkedorplugin:@typescript-eslint/strict-type-checked - Optionally add
plugin:@typescript-eslint/stylistic-type-checked - Install eslint-plugin-react and add
plugin:react/recommended&plugin:react/jsx-runtimeto theextendslist