feat(amicode): the harmonic wave working indicator, and two transcript cleanups

[aarontrowbridge]

The chat had two "working" indicators that looked identical — the thinking line and the tool-group header — because both were shimmering text with no glyph. This replaces that with one brand motif, and fixes two transcript problems found while verifying it in the dev host.

The harmonic wave

A standing wave in quadrature: two identical sine curves, the companion a quarter period out of phase, so one is at full swing whenever the other crosses zero. That is what stops the glyph reading as a blink at 12px — a single standing line passes through zero amplitude twice per cycle. Three curves cross-fade so the harmonic index climbs.

Geometry and timing live in wave-geometry.ts, pure and DOM-free, following the thinking.ts / run-series.ts convention. All animation is CSS — two keyframes, transform and opacity only, no rAF — since this sits on screen for minutes at a time.

Two correctness traps are written down in the code because both are invisible on inspection:

• Per-mode animation-delay magnitudes must descend for the visible sequence to ascend. The intuitive -1×/-2× ordering silently plays mode 1 → 3 → 2. The delays are therefore computed by a tested function and passed as inline style, so the CSS cannot reintroduce it. There is a regression test that fails if the ordering inverts.
• No SVG <defs> and no id attributes. Several indicators mount at once (one per in-flight tool call) and SVG ids are document-global, so ids would collide and every instance would resolve to the first definition. A story mounts 8 at once as the guard.

Repeated receipt cards collapse

Four amicode_* calls against one entity rendered four identical cards. Runs of consecutive receipts sharing (problem, entity, action) now render as one card with a count, opening the highest seq. Conservative by design — a differing action, entity or problem, an interrupting part, or an unparseable sentinel all prevent merging, so no state change can hide. INLINE_KINDS entities are excluded entirely: they can resolve to a live InlineEntityView via a reactive currency check the pure module cannot see, so collapsing them risked dropping a render path.

Skill activations

ui.tool.skill ("Skill") was reachable only as a fallback for a missing input.name, which never happens — so an activated skill rendered as a bare word, indistinguishable from any other tool. Skills now say what they are and wear the Amico chip, since amicode's skills are Amico's repertoire. An opened skill file gets a bounded, tinted panel instead of dumping markdown into the transcript, because [data-component="tool-output"] carries no surface of its own.

Notes for review

• tool-status-title.tsx is a stock opencode component. The change is logged in AMICODE-PATCHES.md. Only the shimmer went; the active→done word morph is deliberately preserved.
• --v2-icon-icon-accent is the ink role, resolved by oc-2.json to grey-800 on light and #FFF676 on dark. Do not add a scheme selector for it. In particular, :root:not([data-theme="light"]) is dead CSS — the block containing it in v2/styles/theme.css is inside a /* */ comment, and data-theme holds a theme id rather than a scheme. An earlier revision built on it and shipped a lemon-on-white glyph at ~1.1:1.
• Storybook cannot exercise the scheme switch by setting data-color-scheme on a wrapper; its preview loads only the v1 theme bundle. amico-wave.stories.tsx resolves tokens through resolveThemeVariantV2() instead, which is the only reason the contrast bug above was caught before a user saw it.
• The H-mark in .amc-lane's head is now static, since two animated brand marks side by side compete with each other.

Testing

bun test src in packages/ui: 432 pass / 0 fail. bun turbo typecheck clean. oxlint packages/ui/src at 505 warnings / 0 errors — identical to the base, no new warnings. Verified in the extension dev host on both light and dark themes.

Not included

A transcript rail (a vertical spine bracketing Amico's stretch of a turn) was built and reverted. The design held up, but it stalled on a dev-host webview serving a stale content-hashed document, which meant no CSS or JS change reached the screen at all and looked exactly like a broken feature. Worth knowing independently of this PR: a new vendored binary needs a full dev-host restart, not Cmd+R — the webview can stay pinned to the old asset hash.

[aarontrowbridge]

The chat had two "working" indicators that looked identical — the thinking line and the tool-group header — because both were shimmering text with no glyph. This replaces that with one brand motif, and fixes two transcript problems found while verifying it in the dev host.

The harmonic wave

A standing wave in quadrature: two identical sine curves, the companion a quarter period out of phase, so one is at full swing whenever the other crosses zero. That is what stops the glyph reading as a blink at 12px — a single standing line passes through zero amplitude twice per cycle. Three curves cross-fade so the harmonic index climbs.

Geometry and timing live in wave-geometry.ts, pure and DOM-free, following the thinking.ts / run-series.ts convention. All animation is CSS — two keyframes, transform and opacity only, no rAF — since this sits on screen for minutes at a time.

Two correctness traps are written down in the code because both are invisible on inspection:

• Per-mode animation-delay magnitudes must descend for the visible sequence to ascend. The intuitive -1×/-2× ordering silently plays mode 1 → 3 → 2. The delays are therefore computed by a tested function and passed as inline style, so the CSS cannot reintroduce it. There is a regression test that fails if the ordering inverts.
• No SVG <defs> and no id attributes. Several indicators mount at once (one per in-flight tool call) and SVG ids are document-global, so ids would collide and every instance would resolve to the first definition. A story mounts 8 at once as the guard.

Repeated receipt cards collapse

Four amicode_* calls against one entity rendered four identical cards. Runs of consecutive receipts sharing (problem, entity, action) now render as one card with a count, opening the highest seq. Conservative by design — a differing action, entity or problem, an interrupting part, or an unparseable sentinel all prevent merging, so no state change can hide. INLINE_KINDS entities are excluded entirely: they can resolve to a live InlineEntityView via a reactive currency check the pure module cannot see, so collapsing them risked dropping a render path.

Skill activations

ui.tool.skill ("Skill") was reachable only as a fallback for a missing input.name, which never happens — so an activated skill rendered as a bare word, indistinguishable from any other tool. Skills now say what they are and wear the Amico chip, since amicode's skills are Amico's repertoire. An opened skill file gets a bounded, tinted panel instead of dumping markdown into the transcript, because [data-component="tool-output"] carries no surface of its own.

Notes for review

• tool-status-title.tsx is a stock opencode component. The change is logged in AMICODE-PATCHES.md. Only the shimmer went; the active→done word morph is deliberately preserved.
• --v2-icon-icon-accent is the ink role, resolved by oc-2.json to grey-800 on light and #FFF676 on dark. Do not add a scheme selector for it. In particular, :root:not([data-theme="light"]) is dead CSS — the block containing it in v2/styles/theme.css is inside a /* */ comment, and data-theme holds a theme id rather than a scheme. An earlier revision built on it and shipped a lemon-on-white glyph at ~1.1:1.
• Storybook cannot exercise the scheme switch by setting data-color-scheme on a wrapper; its preview loads only the v1 theme bundle. amico-wave.stories.tsx resolves tokens through resolveThemeVariantV2() instead, which is the only reason the contrast bug above was caught before a user saw it.
• The H-mark in .amc-lane's head is now static, since two animated brand marks side by side compete with each other.

Testing

bun test src in packages/ui: 432 pass / 0 fail. bun turbo typecheck clean. oxlint packages/ui/src at 505 warnings / 0 errors — identical to the base, no new warnings. Verified in the extension dev host on both light and dark themes.

Not included

A transcript rail (a vertical spine bracketing Amico's stretch of a turn) was built and reverted. The design held up, but it stalled on a dev-host webview serving a stale content-hashed document, which meant no CSS or JS change reached the screen at all and looked exactly like a broken feature. Worth knowing independently of this PR: a new vendored binary needs a full dev-host restart, not Cmd+R — the webview can stay pinned to the old asset hash.

[aarontrowbridge]

The chat had two "working" indicators that looked identical — the thinking line and the tool-group header — because both were shimmering text with no glyph. This replaces that with one brand motif, and fixes two transcript problems found while verifying it in the dev host.

The harmonic wave

A standing wave in quadrature: two identical sine curves, the companion a quarter period out of phase, so one is at full swing whenever the other crosses zero. That is what stops the glyph reading as a blink at 12px — a single standing line passes through zero amplitude twice per cycle. Three curves cross-fade so the harmonic index climbs.

Geometry and timing live in wave-geometry.ts, pure and DOM-free, following the thinking.ts / run-series.ts convention. All animation is CSS — two keyframes, transform and opacity only, no rAF — since this sits on screen for minutes at a time.

Two correctness traps are written down in the code because both are invisible on inspection:

• Per-mode animation-delay magnitudes must descend for the visible sequence to ascend. The intuitive -1×/-2× ordering silently plays mode 1 → 3 → 2. The delays are therefore computed by a tested function and passed as inline style, so the CSS cannot reintroduce it. There is a regression test that fails if the ordering inverts.
• No SVG <defs> and no id attributes. Several indicators mount at once (one per in-flight tool call) and SVG ids are document-global, so ids would collide and every instance would resolve to the first definition. A story mounts 8 at once as the guard.

Repeated receipt cards collapse

Four amicode_* calls against one entity rendered four identical cards. Runs of consecutive receipts sharing (problem, entity, action) now render as one card with a count, opening the highest seq. Conservative by design — a differing action, entity or problem, an interrupting part, or an unparseable sentinel all prevent merging, so no state change can hide. INLINE_KINDS entities are excluded entirely: they can resolve to a live InlineEntityView via a reactive currency check the pure module cannot see, so collapsing them risked dropping a render path.

Skill activations

ui.tool.skill ("Skill") was reachable only as a fallback for a missing input.name, which never happens — so an activated skill rendered as a bare word, indistinguishable from any other tool. Skills now say what they are and wear the Amico chip, since amicode's skills are Amico's repertoire. An opened skill file gets a bounded, tinted panel instead of dumping markdown into the transcript, because [data-component="tool-output"] carries no surface of its own.

Notes for review

• tool-status-title.tsx is a stock opencode component. The change is logged in AMICODE-PATCHES.md. Only the shimmer went; the active→done word morph is deliberately preserved.
• --v2-icon-icon-accent is the ink role, resolved by oc-2.json to grey-800 on light and #FFF676 on dark. Do not add a scheme selector for it. In particular, :root:not([data-theme="light"]) is dead CSS — the block containing it in v2/styles/theme.css is inside a /* */ comment, and data-theme holds a theme id rather than a scheme. An earlier revision built on it and shipped a lemon-on-white glyph at ~1.1:1.
• Storybook cannot exercise the scheme switch by setting data-color-scheme on a wrapper; its preview loads only the v1 theme bundle. amico-wave.stories.tsx resolves tokens through resolveThemeVariantV2() instead, which is the only reason the contrast bug above was caught before a user saw it.
• The H-mark in .amc-lane's head is now static, since two animated brand marks side by side compete with each other.

Testing

bun test src in packages/ui: 432 pass / 0 fail. bun turbo typecheck clean. oxlint packages/ui/src at 505 warnings / 0 errors — identical to the base, no new warnings. Verified in the extension dev host on both light and dark themes.

Not included

A transcript rail (a vertical spine bracketing Amico's stretch of a turn) was built and reverted. The design held up, but it stalled on a dev-host webview serving a stale content-hashed document, which meant no CSS or JS change reached the screen at all and looked exactly like a broken feature. Worth knowing independently of this PR: a new vendored binary needs a full dev-host restart, not Cmd+R — the webview can stay pinned to the old asset hash.

[aarontrowbridge]

The chat had two "working" indicators that looked identical — the thinking line and the tool-group header — because both were shimmering text with no glyph. This replaces that with one brand motif, and fixes two transcript problems found while verifying it in the dev host.

The harmonic wave

A standing wave in quadrature: two identical sine curves, the companion a quarter period out of phase, so one is at full swing whenever the other crosses zero. That is what stops the glyph reading as a blink at 12px — a single standing line passes through zero amplitude twice per cycle. Three curves cross-fade so the harmonic index climbs.

Geometry and timing live in wave-geometry.ts, pure and DOM-free, following the thinking.ts / run-series.ts convention. All animation is CSS — two keyframes, transform and opacity only, no rAF — since this sits on screen for minutes at a time.

Two correctness traps are written down in the code because both are invisible on inspection:

• Per-mode animation-delay magnitudes must descend for the visible sequence to ascend. The intuitive -1×/-2× ordering silently plays mode 1 → 3 → 2. The delays are therefore computed by a tested function and passed as inline style, so the CSS cannot reintroduce it. There is a regression test that fails if the ordering inverts.
• No SVG <defs> and no id attributes. Several indicators mount at once (one per in-flight tool call) and SVG ids are document-global, so ids would collide and every instance would resolve to the first definition. A story mounts 8 at once as the guard.

Repeated receipt cards collapse

Four amicode_* calls against one entity rendered four identical cards. Runs of consecutive receipts sharing (problem, entity, action) now render as one card with a count, opening the highest seq. Conservative by design — a differing action, entity or problem, an interrupting part, or an unparseable sentinel all prevent merging, so no state change can hide. INLINE_KINDS entities are excluded entirely: they can resolve to a live InlineEntityView via a reactive currency check the pure module cannot see, so collapsing them risked dropping a render path.

Skill activations

ui.tool.skill ("Skill") was reachable only as a fallback for a missing input.name, which never happens — so an activated skill rendered as a bare word, indistinguishable from any other tool. Skills now say what they are and wear the Amico chip, since amicode's skills are Amico's repertoire. An opened skill file gets a bounded, tinted panel instead of dumping markdown into the transcript, because [data-component="tool-output"] carries no surface of its own.

Notes for review

• tool-status-title.tsx is a stock opencode component. The change is logged in AMICODE-PATCHES.md. Only the shimmer went; the active→done word morph is deliberately preserved.
• --v2-icon-icon-accent is the ink role, resolved by oc-2.json to grey-800 on light and #FFF676 on dark. Do not add a scheme selector for it. In particular, :root:not([data-theme="light"]) is dead CSS — the block containing it in v2/styles/theme.css is inside a /* */ comment, and data-theme holds a theme id rather than a scheme. An earlier revision built on it and shipped a lemon-on-white glyph at ~1.1:1.
• Storybook cannot exercise the scheme switch by setting data-color-scheme on a wrapper; its preview loads only the v1 theme bundle. amico-wave.stories.tsx resolves tokens through resolveThemeVariantV2() instead, which is the only reason the contrast bug above was caught before a user saw it.
• The H-mark in .amc-lane's head is now static, since two animated brand marks side by side compete with each other.

Testing

bun test src in packages/ui: 432 pass / 0 fail. bun turbo typecheck clean. oxlint packages/ui/src at 505 warnings / 0 errors — identical to the base, no new warnings. Verified in the extension dev host on both light and dark themes.

Not included

A transcript rail (a vertical spine bracketing Amico's stretch of a turn) was built and reverted. The design held up, but it stalled on a dev-host webview serving a stale content-hashed document, which meant no CSS or JS change reached the screen at all and looked exactly like a broken feature. Worth knowing independently of this PR: a new vendored binary needs a full dev-host restart, not Cmd+R — the webview can stay pinned to the old asset hash.

[aarontrowbridge]

The chat had two "working" indicators that looked identical — the thinking line and the tool-group header — because both were shimmering text with no glyph. This replaces that with one brand motif, and fixes two transcript problems found while verifying it in the dev host.

The harmonic wave

A standing wave in quadrature: two identical sine curves, the companion a quarter period out of phase, so one is at full swing whenever the other crosses zero. That is what stops the glyph reading as a blink at 12px — a single standing line passes through zero amplitude twice per cycle. Three curves cross-fade so the harmonic index climbs.

Geometry and timing live in wave-geometry.ts, pure and DOM-free, following the thinking.ts / run-series.ts convention. All animation is CSS — two keyframes, transform and opacity only, no rAF — since this sits on screen for minutes at a time.

Two correctness traps are written down in the code because both are invisible on inspection:

• Per-mode animation-delay magnitudes must descend for the visible sequence to ascend. The intuitive -1×/-2× ordering silently plays mode 1 → 3 → 2. The delays are therefore computed by a tested function and passed as inline style, so the CSS cannot reintroduce it. There is a regression test that fails if the ordering inverts.
• No SVG <defs> and no id attributes. Several indicators mount at once (one per in-flight tool call) and SVG ids are document-global, so ids would collide and every instance would resolve to the first definition. A story mounts 8 at once as the guard.

Repeated receipt cards collapse

Four amicode_* calls against one entity rendered four identical cards. Runs of consecutive receipts sharing (problem, entity, action) now render as one card with a count, opening the highest seq. Conservative by design — a differing action, entity or problem, an interrupting part, or an unparseable sentinel all prevent merging, so no state change can hide. INLINE_KINDS entities are excluded entirely: they can resolve to a live InlineEntityView via a reactive currency check the pure module cannot see, so collapsing them risked dropping a render path.

Skill activations

ui.tool.skill ("Skill") was reachable only as a fallback for a missing input.name, which never happens — so an activated skill rendered as a bare word, indistinguishable from any other tool. Skills now say what they are and wear the Amico chip, since amicode's skills are Amico's repertoire. An opened skill file gets a bounded, tinted panel instead of dumping markdown into the transcript, because [data-component="tool-output"] carries no surface of its own.

Notes for review

• tool-status-title.tsx is a stock opencode component. The change is logged in AMICODE-PATCHES.md. Only the shimmer went; the active→done word morph is deliberately preserved.
• --v2-icon-icon-accent is the ink role, resolved by oc-2.json to grey-800 on light and #FFF676 on dark. Do not add a scheme selector for it. In particular, :root:not([data-theme="light"]) is dead CSS — the block containing it in v2/styles/theme.css is inside a /* */ comment, and data-theme holds a theme id rather than a scheme. An earlier revision built on it and shipped a lemon-on-white glyph at ~1.1:1.
• Storybook cannot exercise the scheme switch by setting data-color-scheme on a wrapper; its preview loads only the v1 theme bundle. amico-wave.stories.tsx resolves tokens through resolveThemeVariantV2() instead, which is the only reason the contrast bug above was caught before a user saw it.
• The H-mark in .amc-lane's head is now static, since two animated brand marks side by side compete with each other.

Testing

bun test src in packages/ui: 432 pass / 0 fail. bun turbo typecheck clean. oxlint packages/ui/src at 505 warnings / 0 errors — identical to the base, no new warnings. Verified in the extension dev host on both light and dark themes.

Not included

A transcript rail (a vertical spine bracketing Amico's stretch of a turn) was built and reverted. The design held up, but it stalled on a dev-host webview serving a stale content-hashed document, which meant no CSS or JS change reached the screen at all and looked exactly like a broken feature. Worth knowing independently of this PR: a new vendored binary needs a full dev-host restart, not Cmd+R — the webview can stay pinned to the old asset hash.

[aarontrowbridge]

The chat had two "working" indicators that looked identical — the thinking line and the tool-group header — because both were shimmering text with no glyph. This replaces that with one brand motif, and fixes two transcript problems found while verifying it in the dev host.

The harmonic wave

A standing wave in quadrature: two identical sine curves, the companion a quarter period out of phase, so one is at full swing whenever the other crosses zero. That is what stops the glyph reading as a blink at 12px — a single standing line passes through zero amplitude twice per cycle. Three curves cross-fade so the harmonic index climbs.

Geometry and timing live in wave-geometry.ts, pure and DOM-free, following the thinking.ts / run-series.ts convention. All animation is CSS — two keyframes, transform and opacity only, no rAF — since this sits on screen for minutes at a time.

Two correctness traps are written down in the code because both are invisible on inspection:

• Per-mode animation-delay magnitudes must descend for the visible sequence to ascend. The intuitive -1×/-2× ordering silently plays mode 1 → 3 → 2. The delays are therefore computed by a tested function and passed as inline style, so the CSS cannot reintroduce it. There is a regression test that fails if the ordering inverts.
• No SVG <defs> and no id attributes. Several indicators mount at once (one per in-flight tool call) and SVG ids are document-global, so ids would collide and every instance would resolve to the first definition. A story mounts 8 at once as the guard.

Repeated receipt cards collapse

Four amicode_* calls against one entity rendered four identical cards. Runs of consecutive receipts sharing (problem, entity, action) now render as one card with a count, opening the highest seq. Conservative by design — a differing action, entity or problem, an interrupting part, or an unparseable sentinel all prevent merging, so no state change can hide. INLINE_KINDS entities are excluded entirely: they can resolve to a live InlineEntityView via a reactive currency check the pure module cannot see, so collapsing them risked dropping a render path.

Skill activations

ui.tool.skill ("Skill") was reachable only as a fallback for a missing input.name, which never happens — so an activated skill rendered as a bare word, indistinguishable from any other tool. Skills now say what they are and wear the Amico chip, since amicode's skills are Amico's repertoire. An opened skill file gets a bounded, tinted panel instead of dumping markdown into the transcript, because [data-component="tool-output"] carries no surface of its own.

Notes for review

• tool-status-title.tsx is a stock opencode component. The change is logged in AMICODE-PATCHES.md. Only the shimmer went; the active→done word morph is deliberately preserved.
• --v2-icon-icon-accent is the ink role, resolved by oc-2.json to grey-800 on light and #FFF676 on dark. Do not add a scheme selector for it. In particular, :root:not([data-theme="light"]) is dead CSS — the block containing it in v2/styles/theme.css is inside a /* */ comment, and data-theme holds a theme id rather than a scheme. An earlier revision built on it and shipped a lemon-on-white glyph at ~1.1:1.
• Storybook cannot exercise the scheme switch by setting data-color-scheme on a wrapper; its preview loads only the v1 theme bundle. amico-wave.stories.tsx resolves tokens through resolveThemeVariantV2() instead, which is the only reason the contrast bug above was caught before a user saw it.
• The H-mark in .amc-lane's head is now static, since two animated brand marks side by side compete with each other.

Testing

bun test src in packages/ui: 432 pass / 0 fail. bun turbo typecheck clean. oxlint packages/ui/src at 505 warnings / 0 errors — identical to the base, no new warnings. Verified in the extension dev host on both light and dark themes.

Not included

A transcript rail (a vertical spine bracketing Amico's stretch of a turn) was built and reverted. The design held up, but it stalled on a dev-host webview serving a stale content-hashed document, which meant no CSS or JS change reached the screen at all and looked exactly like a broken feature. Worth knowing independently of this PR: a new vendored binary needs a full dev-host restart, not Cmd+R — the webview can stay pinned to the old asset hash.

[aarontrowbridge]

The chat had two "working" indicators that looked identical — the thinking line and the tool-group header — because both were shimmering text with no glyph. This replaces that with one brand motif, and fixes two transcript problems found while verifying it in the dev host.

The harmonic wave

A standing wave in quadrature: two identical sine curves, the companion a quarter period out of phase, so one is at full swing whenever the other crosses zero. That is what stops the glyph reading as a blink at 12px — a single standing line passes through zero amplitude twice per cycle. Three curves cross-fade so the harmonic index climbs.

Geometry and timing live in wave-geometry.ts, pure and DOM-free, following the thinking.ts / run-series.ts convention. All animation is CSS — two keyframes, transform and opacity only, no rAF — since this sits on screen for minutes at a time.

Two correctness traps are written down in the code because both are invisible on inspection:

• Per-mode animation-delay magnitudes must descend for the visible sequence to ascend. The intuitive -1×/-2× ordering silently plays mode 1 → 3 → 2. The delays are therefore computed by a tested function and passed as inline style, so the CSS cannot reintroduce it. There is a regression test that fails if the ordering inverts.
• No SVG <defs> and no id attributes. Several indicators mount at once (one per in-flight tool call) and SVG ids are document-global, so ids would collide and every instance would resolve to the first definition. A story mounts 8 at once as the guard.

Repeated receipt cards collapse

Four amicode_* calls against one entity rendered four identical cards. Runs of consecutive receipts sharing (problem, entity, action) now render as one card with a count, opening the highest seq. Conservative by design — a differing action, entity or problem, an interrupting part, or an unparseable sentinel all prevent merging, so no state change can hide. INLINE_KINDS entities are excluded entirely: they can resolve to a live InlineEntityView via a reactive currency check the pure module cannot see, so collapsing them risked dropping a render path.

Skill activations

ui.tool.skill ("Skill") was reachable only as a fallback for a missing input.name, which never happens — so an activated skill rendered as a bare word, indistinguishable from any other tool. Skills now say what they are and wear the Amico chip, since amicode's skills are Amico's repertoire. An opened skill file gets a bounded, tinted panel instead of dumping markdown into the transcript, because [data-component="tool-output"] carries no surface of its own.

Notes for review

• tool-status-title.tsx is a stock opencode component. The change is logged in AMICODE-PATCHES.md. Only the shimmer went; the active→done word morph is deliberately preserved.
• --v2-icon-icon-accent is the ink role, resolved by oc-2.json to grey-800 on light and #FFF676 on dark. Do not add a scheme selector for it. In particular, :root:not([data-theme="light"]) is dead CSS — the block containing it in v2/styles/theme.css is inside a /* */ comment, and data-theme holds a theme id rather than a scheme. An earlier revision built on it and shipped a lemon-on-white glyph at ~1.1:1.
• Storybook cannot exercise the scheme switch by setting data-color-scheme on a wrapper; its preview loads only the v1 theme bundle. amico-wave.stories.tsx resolves tokens through resolveThemeVariantV2() instead, which is the only reason the contrast bug above was caught before a user saw it.
• The H-mark in .amc-lane's head is now static, since two animated brand marks side by side compete with each other.

Testing

bun test src in packages/ui: 432 pass / 0 fail. bun turbo typecheck clean. oxlint packages/ui/src at 505 warnings / 0 errors — identical to the base, no new warnings. Verified in the extension dev host on both light and dark themes.

Not included

A transcript rail (a vertical spine bracketing Amico's stretch of a turn) was built and reverted. The design held up, but it stalled on a dev-host webview serving a stale content-hashed document, which meant no CSS or JS change reached the screen at all and looked exactly like a broken feature. Worth knowing independently of this PR: a new vendored binary needs a full dev-host restart, not Cmd+R — the webview can stay pinned to the old asset hash.

[aarontrowbridge]

The chat had two "working" indicators that looked identical — the thinking line and the tool-group header — because both were shimmering text with no glyph. This replaces that with one brand motif, and fixes two transcript problems found while verifying it in the dev host.

The harmonic wave

A standing wave in quadrature: two identical sine curves, the companion a quarter period out of phase, so one is at full swing whenever the other crosses zero. That is what stops the glyph reading as a blink at 12px — a single standing line passes through zero amplitude twice per cycle. Three curves cross-fade so the harmonic index climbs.

Geometry and timing live in wave-geometry.ts, pure and DOM-free, following the thinking.ts / run-series.ts convention. All animation is CSS — two keyframes, transform and opacity only, no rAF — since this sits on screen for minutes at a time.

Two correctness traps are written down in the code because both are invisible on inspection:

• Per-mode animation-delay magnitudes must descend for the visible sequence to ascend. The intuitive -1×/-2× ordering silently plays mode 1 → 3 → 2. The delays are therefore computed by a tested function and passed as inline style, so the CSS cannot reintroduce it. There is a regression test that fails if the ordering inverts.
• No SVG <defs> and no id attributes. Several indicators mount at once (one per in-flight tool call) and SVG ids are document-global, so ids would collide and every instance would resolve to the first definition. A story mounts 8 at once as the guard.

Repeated receipt cards collapse

Four amicode_* calls against one entity rendered four identical cards. Runs of consecutive receipts sharing (problem, entity, action) now render as one card with a count, opening the highest seq. Conservative by design — a differing action, entity or problem, an interrupting part, or an unparseable sentinel all prevent merging, so no state change can hide. INLINE_KINDS entities are excluded entirely: they can resolve to a live InlineEntityView via a reactive currency check the pure module cannot see, so collapsing them risked dropping a render path.

Skill activations

ui.tool.skill ("Skill") was reachable only as a fallback for a missing input.name, which never happens — so an activated skill rendered as a bare word, indistinguishable from any other tool. Skills now say what they are and wear the Amico chip, since amicode's skills are Amico's repertoire. An opened skill file gets a bounded, tinted panel instead of dumping markdown into the transcript, because [data-component="tool-output"] carries no surface of its own.

Notes for review

• tool-status-title.tsx is a stock opencode component. The change is logged in AMICODE-PATCHES.md. Only the shimmer went; the active→done word morph is deliberately preserved.
• --v2-icon-icon-accent is the ink role, resolved by oc-2.json to grey-800 on light and #FFF676 on dark. Do not add a scheme selector for it. In particular, :root:not([data-theme="light"]) is dead CSS — the block containing it in v2/styles/theme.css is inside a /* */ comment, and data-theme holds a theme id rather than a scheme. An earlier revision built on it and shipped a lemon-on-white glyph at ~1.1:1.
• Storybook cannot exercise the scheme switch by setting data-color-scheme on a wrapper; its preview loads only the v1 theme bundle. amico-wave.stories.tsx resolves tokens through resolveThemeVariantV2() instead, which is the only reason the contrast bug above was caught before a user saw it.
• The H-mark in .amc-lane's head is now static, since two animated brand marks side by side compete with each other.

Testing

bun test src in packages/ui: 432 pass / 0 fail. bun turbo typecheck clean. oxlint packages/ui/src at 505 warnings / 0 errors — identical to the base, no new warnings. Verified in the extension dev host on both light and dark themes.

Not included

A transcript rail (a vertical spine bracketing Amico's stretch of a turn) was built and reverted. The design held up, but it stalled on a dev-host webview serving a stale content-hashed document, which meant no CSS or JS change reached the screen at all and looked exactly like a broken feature. Worth knowing independently of this PR: a new vendored binary needs a full dev-host restart, not Cmd+R — the webview can stay pinned to the old asset hash.