fix(execute): the final report says whether the app was seen with Claude Code's run

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

commands/trekexecute.md

@@ -2140,6 +2140,11 @@ built thing — not in the run. (A ≥ 1.8 plan cannot reach here with its
 `End-to-end:` command missing from `## Verification`: the plan validator
 rejects that as `PLAN_END_TO_END_NOT_VERIFIED`.)
 
+Record `run_seen`: `yes` when the app was seen and driven with Claude Code's
+built-in `run` in this run, else `no — {reason}` (no app to launch, `run` not
+available, not started, and why). The verdict is still the `End-to-end:`
+command.
+
 ### Architecture rules (K5) and the plan-file sweep (K6)
 
 Two whole-run checks, for a trekplan and a session spec alike, in one Bash
@@ -2808,6 +2813,7 @@ Phase 2.3 (validate exit) and Phase 5 (dry-run) intentionally do not write
 **Mode:** {execute | resume | step N}
 **Result:** {COMPLETED | FAILED at step N | STOPPED (escalation) | PARTIAL (N/total passed)}
 **End to end:** {verified | not verified end to end}
+**Seen with `run`:** {yes | no — {reason}}
 
 ### Step Results
 
@@ -2933,6 +2939,7 @@ To continue (multi-session waves): re-run the same /trekexecute command (not --r
     "legacy_plan": false,
     "progress_file": "{path}",
     "end_to_end": "{verified | not-verified | n/a}",
+    "run_seen": "{yes | no — reason}",
     "steps_without_red_proof": 0,
     "stop_class": "{none | 1 | 2 | 3 | 4}",
     "decisions": 0,