Artifact: Outcome-vs-Output Rewrite — Kestrel Feature Tickets

Three Kestrel feature-request tickets rewritten as outcome statements -- exercises co-01. Kestrel is a fictional product; every quoted number, question, or finding here is an illustrative, constructed example, not real data or a real transcript.

Ticket A -- "Add a CSV export button to the schedule page." Rewritten as outcome: managers who currently retype last week's hours into payroll by hand cut payroll prep from about 45 minutes to under 5, and stop making the copy-paste transcription errors that retyping introduces.

Ticket B -- "Add dark mode." Rewritten as outcome: night-shift managers who build tomorrow's schedule around 11pm stop squinting at a bright white screen and stop abandoning the draft schedule early because the glare makes their eyes hurt.

Ticket C -- "Add a 'duplicate shift' button." Rewritten as outcome: managers who run the same weekly shift pattern build next week's full schedule in under 2 minutes, instead of re-entering every individual shift by hand.