[mgratzer]

People kept asking after a finished run how to start the change and what to look at (the session audit's hand count is about 19 sessions in colorburst and tandler), so Try it now answers that and the end-of-run summary repeats it.

Notes

• No new section or setting. ## Exercised already had a Try it line, but the six recent colorburst and tandler PRs I sampled all filled it with a bun test command, and neither summary showed it.
• A test command is still allowed when nothing a person can reach changed, such as an internal refactor.
• This doesn't start the app for anyone. The summary says how, and the person can ask.
• forge-land and the lens don't read this line, so verdicts and views are unaffected.

Exercised

Snapshots of this branch and of its base, each running forge-ship --unattended in mgratzer/forge-e2e-sandbox on the same task, adding GET /notes/:id/preview. Both PRs are closed and their branches deleted.

• New, sandbox#50: the Ship Summary has Try it: PORT=3999 npm start, then curl -H 'Authorization: Bearer test-token-red' http://127.0.0.1:3999/notes/n-1/preview and look for the "Release checklist" page, and the PR body has the same line
• Old, sandbox#51: the Ship Summary has no Try it; the PR body's line is the same start command and curl, with nothing to look for
• Everything else matched in kind: exercised intended, 11 of 11 tests, no review findings
• Not exercised: forge-implement's own summary (one added phrase, not run on its own); a run with no recipe, where the summary should leave the line out; the test-command habit itself, because the sandbox's easy recipe produced a run command in the control too, so only real PRs can show whether that habit changes
• Try it: scripts/check-skills.sh, then run forge-ship on a task in a sandbox and look for Try it under ### Implementation in the summary

[Copilot]

Copilot was unable to review this pull request due to rate limiting. Please try again later. See Usage limits for GitHub Copilot for details.