🤖 tests: App/MemoryIntuition stories flake in local full-suite Storybook runs #6002

Summary

Two App/MemoryIntuition stories (src/browser/stories/App.intuition.stories.tsx) failed once each in local full-suite test-storybook runs. Each story passes when run alone and passes on reruns. This flake has not been seen in CI yet.

Owner: coordinator desk.

Sightings (local, full suite against a static Storybook build)

1. App/MemoryIntuition › Recognized › play-test, on the branch of 🤖 a11y: main landmark missing in immersive review and with no workspace selected #5969 (PR 🤖 fix: one main landmark in immersive review and on pages without a workspace #5999). The run reported 1 failed, 656 passed.

   expect(element).toBeVisible()
   Received element is not visible:
     <span class="text-foreground break-all" />
   

2. App/MemoryIntuition › Pending › play-test, on the branch of 🤖 tests: typing / in a Storybook composer crashes (mock has no workspace.mcp.prompts) #5991 (PR 🤖 tests: Storybook mock serves workspace.mcp.prompts.list, so typing / no longer crashes #6001).

   expect(element).toBeVisible()
   Received element is not visible:
     <div class="text-muted italic" />
   

The code frames that the test runner printed point at unrelated lines (152, and 96 for Empty). The source map is likely off, so the failing toBeVisible() call is not pinned yet. I did not verify which call fails.

What is known

• Both failures are toBeVisible() on an element that exists but is not visible yet, after expandCard(...).
• Neither PR changed the intuition card or its story.
• Each story passes alone and on reruns.
• Not seen in CI yet.

Next steps

1. Find the failing toBeVisible() call (run the file in a loop under full-suite load).
2. If the card expands with a transition or a lazy render, wait for the final state (waitFor) before the visibility check.

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $83.79