Make Piggy part of the product rather than a guest in it

Piggy arrived as a chat panel bolted onto a CRM and then grew a workspace
around it. The layout was already right — the audit found the approval card
to be the best-designed object in the repo, and the account page's empty
panels less finished than anything in the workspace. What was wrong was
vocabulary: nobody had written the small things down, so both halves kept
inventing them.

Piggy was drawn with five different marks — a pig in the dock, a sparkle in
the sidebar and again on the model picker, a speech bubble on the Ask
buttons, and a stock robot glyph on every assistant message, which is the
one people look at most. There is now one mark. The composer, which is the
first control in the product since sign-in lands on /piggy, was the only
un-adapted shadcn field left: 6px radius against a 12px Send button it sat
8px from. A stat tile had been reinvented six times at three numeral scales,
and the same uppercase micro-label existed in five variants, two of them one
tab apart in the same rail. There were 63 hand-written font sizes: not a
scale, sixty-three opinions.

Underneath that, the focus ring was invisible. The global rule used
ring-accent, which Tailwind deliberately aliases onto the hover tint, so the
ring measured 1.01:1 against the light canvas — no visible focus indicator
anywhere in the product, for any accent, in either theme. It is ring-brand
now and measures 17:1. The warning, positive and info tones were darkened
until each clears 4.5:1 on a card, on inset and on its own chip, and the
light canvas moved to 98% so a card lifts without leaning on its shadow.

The mobile work is the part worth reading. A landscape phone gave the
transcript 28% of the viewport and a keyboard-up phone 16%, against a 45%
floor — and the fixed tab bar painted over the composer, covering the safety
sentence and half the Send button, because two source comments asserted the
bar stood down on short viewports and it never had. Both fixed and measured
by hit-testing rather than by screenshot. The composer itself was 64px tall
for a blank second line nobody typed, because the auto-resize effect sizes
to scrollHeight and scrollHeight counts rows — a CSS height could not win
against an inline style, so the attribute was the honest lever.

Verified across both themes driven through the app's own control: no
horizontal overflow on 15 routes at four viewports, 672 stat values that fit,
297 labels at exactly 11px/500, Escape returning focus to its opener rather
than the body on every overlay, and a rejected write no longer reporting
"Succeeded" with a green check.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

apps/web/src/components/piggy/reasoning.tsx

@@ -1,6 +1,7 @@
 import { useEffect, useRef, useState } from 'react';
-import { Brain, ChevronRight } from 'lucide-react';
+import { Brain } from 'lucide-react';
 import { cn } from '@/components/ui';
+import { Disclosure } from '@/components/ui/disclosure';
 
 /**
  * How long after the last reasoning token the panel folds itself away.
@@ -81,10 +82,11 @@ export function PiggyReasoning({ text, streaming }: { text: string; streaming: b
   if (!started && !streaming) return null;
 
   return (
-    <details
+    <Disclosure
       open={open}
-      onToggle={(event) => setOpen(event.currentTarget.open)}
+      onOpenChange={setOpen}
       className="mb-2 text-xs text-muted"
+      summaryClassName="pr-2 text-xs"
       /*
        * The transcript around this is `role="log" aria-live="polite"`, and a
        * live region announces its whole subtree. Auto-opening the panel
@@ -93,30 +95,29 @@ export function PiggyReasoning({ text, streaming }: { text: string; streaming: b
        * overrides the inherited politeness for this subtree only.
        */
       aria-live="off"
+      /*
+       * On the `<details>` rather than on the summary, because that is where
+       * the primitive's own props land — and a click anywhere in this panel,
+       * summary or body, is the user attending to it, which is exactly the
+       * signal the automatic open and close must stand down for.
+       */
+      onClick={() => {
+        touched.current = true;
+      }}
+      summary={
+        <span className="flex min-w-0 items-center gap-2">
+          <Brain className={cn('size-4 shrink-0', streaming && 'animate-pulse')} aria-hidden />
+          {streaming ? 'Thinking' : reasoningLabel(durationMs)}
+        </span>
+      }
     >
-      <summary
-        // `list-none` and the WebKit rule between them remove the native
-        // triangle, which a flex summary drops in Chrome but keeps in Firefox —
-        // so without both the disclosure marker exists in one browser only.
-        className="flex min-h-11 cursor-pointer list-none items-center gap-2 py-2 pr-2 font-medium transition-colors hover:text-fg [&::-webkit-details-marker]:hidden"
-        onClick={() => {
-          touched.current = true;
-        }}
-      >
-        <ChevronRight
-          className={cn('size-3.5 shrink-0 transition-transform', open && 'rotate-90')}
-          aria-hidden
-        />
-        <Brain className={cn('size-4 shrink-0', streaming && 'animate-pulse')} aria-hidden />
-        {streaming ? 'Thinking' : reasoningLabel(durationMs)}
-      </summary>
       {/* Withheld until the first token so the gap between "Thinking" and
           anything to read is empty space rather than an empty rail. */}
       {started ? (
         <div
           ref={bodyRef}
           className={cn(
-            'ml-1 animate-in fade-in border-l border-border py-1 pl-3',
+            'ml-1 animate-in fade-in border-l border-border py-1 pl-3 duration-2 ease-enter',
             // Capped only while it writes. An auto-opened panel is one the user
             // did not ask for, so it must not push the answer off screen; a
             // panel they opened themselves is one they mean to read to the end.
@@ -126,7 +127,7 @@ export function PiggyReasoning({ text, streaming }: { text: string; streaming: b
           <p className="whitespace-pre-wrap leading-5">{text}</p>
         </div>
       ) : null}
-    </details>
+    </Disclosure>
   );
 }