Phase 2 auth boundary obligation. The v0.1 chassis (extended local sixis dashboard HTTP server) is localhost-trusted with no way to distinguish your manual clicks from Claude-driven browser-control from a future API client. v0.1 itself does not need to build auth — but before phase 2 (Claude browser-control) begins, the dashboard must explicitly design an X-Sixis-Agent header (or equivalent) so the substrate's audit chain can attribute every wizard-step event to its actual initiator. Without this, phase 2 will silently break the 'who initiated which step' lineage. Surfaced by Deepseek in poll 69965acc as a hidden-obligation finding, accepted into the convergence and queued as a discrete amendment that must clear before phase 2 work opens.