Breadboard Analysis

Find design smells in a breadboard and fix them. Use the canonical schema and validation rules in ../breadboarding/SKILL.md; the extended guide is background material, not a competing format.

Correct the requested breadboard within its existing scope. Reflection does not authorize refactoring the implementation: for an existing system, report a code/design mismatch and distinguish a faithful map correction from a proposed implementation change. For a proposed system, validate the intended wiring without claiming it already exists in code.

Finding Smells

Entry Point: Trace User Stories Through the Wiring

Take a user story from the requirements or frame. Trace it through the breadboard wiring. Ask: does the path tell a coherent story that produces the expected effect?

Example: "User says 'add Tokyo after Detroit' → Tokyo appears after Detroit in the table, and persists across restarts."

Trace: U4 (input) → N1 → N2 (LLM) → N3 (dispatch) → N4 (handle) → ... → S1 (locales updated) → N12 (persist) → S4 (config written).