fix: the command name is not part of the goal, and a report must name the ref it used

[linhdmn]

Follows #35, which added /product.

/product had unit tests and had never been driven. This is what running it found.

The command name is not part of the goal

$ /product a slugify(text) function that lowercases text and joins its words with hyphens…
$   →  feat: /product a slugify(text) function that lowercases text and joins its wo…

The composer submits a command's return value as the turn with the command name still attached. Everything downstream names work after the goal — branch, commit subject, PR title — so the slash command went into a commit message.

Both launchers are peeled now, in order: the app name (headless Say OK.) and then the command name. A bare /product with nothing after it has no goal, and falls through to the deployment's goal rather than naming the run after the command.

A report that named the wrong branch

The branch is re-derived at ship time from the session log — that fix is in #33. But the diagnostic printed sandbox.branch, which is the value captured back at containment time:

dsh-feature-loop: ship — branch=fl/create-tmp-fl-headless-proof-txt-contain-run   ← reported
$ git branch --contains HEAD
* fl/a-slugify-text-function-that-lowercases-run                                    ← where it actually landed

One value now feeds both the work and the report. A report naming the wrong ref is worse than no report: it reads as a fact, and this one was confidently wrong for three rounds of diagnosis in the round before it was written.

Proven end to end

phase research  → prd        docs/0-research.md written and checked
phase prd       → implement  docs/PRD.md written and checked
phase implement → test       working tree shows changed files
phase test      → ship       npm test exits 0
ship — branch=fl/a-slugify-text-function-that-lowercases-run
       the branch is pushed; gh pr create ran and was refused — origin is a local bare repo

682 unit tests pass (679 at #35).