Allow AFK prototype tickets

skills/prototype/LOGIC.md

@@ -76,14 +76,17 @@ If the host project has no task runner, put the command at the top of the protot
 
 Done when a fresh user can launch the prototype with one documented command.
 
-### 6. Hand it over
+### 6. Evaluate it
 
-Give the user the run command.
+In HITL mode, give the user the run command.
 They drive it themselves.
 The interesting moments are when they say "wait, that shouldn't be possible" or "huh, I assumed X would be different" because those expose bugs in the idea.
 Add actions when the feedback needs them.
 
-Done when the user can exercise the model and the prototype exposes every state transition needed to reach a verdict.
+In AFK mode, run the command yourself and drive the hard cases that answer the stated question.
+Record the observations that support the verdict.
+
+Done when the evaluator can exercise the model and the prototype exposes every state transition needed to reach a verdict.
 
 ## Production mapping
 

skills/prototype/SKILL.md

@@ -7,6 +7,9 @@ description: Build a throwaway prototype to answer a design question. Use when t
 
 A prototype is **throwaway code that answers one question**.
 The question decides the branch.
+The interaction mode decides who reaches the verdict.
+Use AFK mode when the question has objective observable criteria the agent can test end to end.
+Use HITL mode when the verdict depends on human judgment, taste, or UX feel.
 
 ## 1. Pick a branch
 
@@ -39,11 +42,13 @@ Done when exactly one branch and one design question govern the prototype.
 
 ## 2. Build and reach a verdict
 
-Follow the selected branch through its handover step and iterate on the prototype in response to the user's feedback.
+Follow the selected branch through its evaluation step.
+In HITL mode, hand the prototype to the user and iterate in response to their feedback.
+In AFK mode, run the prototype yourself and evaluate the objective observations against the question.
 Do not treat a runnable prototype as the result.
 The result is the verdict that answers the design question.
 
-Done when the user has reached an explicit verdict or stated that the prototype did not resolve the question.
+Done when the verdict is explicit, or when the prototype establishes that it did not resolve the question.
 
 ## 3. Capture the primary source
 

skills/prototype/UI.md

@@ -99,12 +99,15 @@ Put the switcher in a single shared component so both sub-shapes can reuse it. L
 
 Done when mouse and keyboard controls cycle through every shareable variant without intercepting text-editing keys, and the switcher cannot render in production.
 
-### 5. Hand it over
+### 5. Evaluate it
 
-Surface the URL and the `?variant=` keys.
+In HITL mode, surface the URL and the `?variant=` keys.
 The user flips through the variants and may combine elements rather than choosing one unchanged.
 
-Done when the user can compare every variant in its host context and the prototype exposes enough contrast to reach a verdict.
+In AFK mode, open the URL yourself, compare every variant against the stated objective criteria, and record the observations that support the verdict.
+Use HITL instead when the decision depends on taste, product judgment, or UX feel.
+
+Done when the evaluator can compare every variant in its host context and the prototype exposes enough contrast to reach a verdict.
 
 ## Production mapping
 

skills/wayfinder/ARTIFACTS.md

@@ -97,7 +97,8 @@ tags:
 Use one of these tags:
 
 - `ticket/research`
-- `ticket/prototype`
+- `ticket/prototype/afk`
+- `ticket/prototype/hitl`
 - `ticket/grill`
 - `ticket/task/afk`
 - `ticket/task/human`

skills/wayfinder/SKILL.md

@@ -36,8 +36,10 @@ The agent never speaks for the human's side.
 
 - **Research** (AFK): Investigate documentation, third-party APIs, or resources outside the current working directory through `research`.
   The called skill completes the Research ticket artifact in place.
-- **Prototype** (HITL): Raise the fidelity of a logic, state-model, or UI decision through `prototype`.
+- **Prototype** (AFK or HITL): Raise the fidelity of a logic, state-model, or UI decision through `prototype`.
-  The called skill completes the Prototype ticket artifact in place after the human reaches a verdict.
+  Use AFK when the question has objective observable criteria the agent can test end to end.
+  Use HITL when the verdict depends on human judgment, taste, or UX feel.
+  The called skill completes the Prototype ticket artifact in place after the verdict is reached.
 - **Grill** (HITL): Resolve a decision through `grill`.
   This is the default ticket type.
 - **Task** (AFK or HITL): Perform prerequisite work that must happen before a decision can be made.