…ailing checks (#950)

Trigger: PR #945 hit a heuristic FAIL on scenario 02 because the TS SDK
flattened `outpost.publish.event(...)` to `outpost.publish(...)` in v1.3.0
(commit d875c66), but the eval check + scenario criterion + prompt were
never updated. Prior runs masked it: the agent often echoed the literal
"publish.event" from the prompt in comments, accidentally satisfying the
string-presence check. This run stuck to the SDK README wording and the
check exit-1'd with no clue in the GH Actions log — only in the artifact.

Impact: PR #945 (docs only) was blocked by an unrelated stale check. After
this fix the heuristic matches the current SDK shape, and any future
heuristic/LLM failure prints the failing check id and detail directly in
the main CI log.

Changes:
- scoreScenario02 regex now matches `.publish(` and keeps `publish.event`
  as a fallback for older transcripts.
- run-agent-eval logs each failing heuristic check + LLM criterion on
  pass=false (was: silent exit 1).
- Scenario 02 success criterion lists `outpost.publish` not `publish.event`.
- Prompt's TS counter-example uses `outpost.publish({ ... })`.
- Trajectory SDK hint pattern renamed `ts_publish` with `/\.publish\s*\(/`.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>