p2a-visual-experiencelisted

# Plan2Agent Visual Experience Define and approve the visual behavior of a screen-bearing product before UI tasks are authored. This is a conditional Gate B track, not a separate gate or frontend harness. ## Activation Read `spec_json.visual_experience` and choose exactly one path: - `none`: no visual artifact or review contract. - `minimal`: use product flows, acceptance criteria, and existing conventions; no candidates. - `reuse`: cite existing design-system references and create an experience artifact only for composition or exceptions needing approval. - `full + deferred_iteration`: record deferral and keep visual design out of current tasks. - `full + current_iteration`: read `references/full-visual-procedure.md`. Gate B remains draft until at least two candidates are compared and one direction is explicitly approved, unless constrained reuse justifies one. ## Ownership Candidate authorship belongs to read-only `p2a-visual-designer`. The harness owner is the only writer and owns file persistence, hashes, schema validation, and verbatim approval evidence. If the agent is unavailable, preserve the same author/writer boundary locally. ## Progressive reference routing The canonical conditions live in `.agents/context-routes.json`. 1. Required, conditional; stages: visual, gate-b — `references/full-visual-procedure.md` — The Gate B visual decision is full with current-iteration timing. 2. Required, conditional; stages: visual — `references/implementation-feedback-and