outcome-httlisted

<purpose> Log the outcome of a delivered pitch. Captures what happened, what resonated, what didn't, user reflections, and next steps. Pushes learnings back to audience profiles (in shared/people/) and the professional profile. Updates goal status. </purpose> <steps> <step id="load-config" number="1"> <description>Load Configuration</description> <load-config> Resolve the user's home directory (run `echo $HOME` via Bash). Use this absolute path for all file operations below -- never pass `~` to the Read tool. 1. Read `<home>/.things/config.json` <if condition="config-missing">Tell the user: "Run `/things:setup-things` first." Then stop.</if> </load-config> </step> <step id="select-campaign" number="2"> <description>Select Campaign and Goal</description> <if condition="campaign-id-in-arguments"> Read `<home>/.things/heres-the-thing/campaigns/<campaign-id>/campaign.json`. </if> <if condition="no-campaign-id"> Scan `<home>/.things/heres-the-thing/campaigns/*/campaign.json`. List active campaigns with goals that have status `active` or `delivered`. Use AskUserQuestion to select one. </if> <if condition="goal-id-in-arguments"> Select the matching goal. </if> <if condition="no-goal-id-and-multiple-goals"> Use AskUserQuestion to select a goal. </if> <if condition="single-active-goal"> Auto-select it. </if> Show the goal summary: description, audience, medium, target da