Persist Currents run URLs for ATVM watcher notes

atvm/docs/automation/run-learnings.md

@@ -259,6 +259,15 @@ This file stores run-specific examples only when a run produced a new learning r
 - Action for future runs:
   - Render ATVM status output in that section order for both local output and Mattermost posts.
 
+## Run Learning: 2026-03-27 (Persist the Currents run URL outside the transient runner log)
+- Observed failure mode:
+  - The watcher can include the Currents run URL in `NOTES:`, but only if it can still read the URL from live runner output or a consolidated run log.
+  - In practice, `/tmp/<build-name>.log` is not guaranteed to exist, and the host reporter artifacts do not preserve the final Currents run URL.
+- Action for future runs:
+  - Persist the Currents `Recorded Run` URL as soon as `run-sorry-cypress.py` sees it.
+  - Store it under the watcher state directory for the parent build so it survives runner exit and missing log files.
+  - Prefer the persisted Currents URL store over transient log scraping when building the final `NOTES:` section.
+
 ## Run Learning: 2026-03-27 (Default ATVM approval should include the watcher)
 - Observed requirement:
   - The operator wants `approve` to mean run with watcher by default.

atvm/docs/automation/status-template.md

@@ -71,6 +71,7 @@ Use this as the default ATVM automation run-status template for:
   - `⏭️ SKIP`
 - Keep `Detail` concise.
 - Put broader context under `NOTES:`, not in the host table.
+- When available, put the persistent Currents run URL in `NOTES:` so operators can open the exact recorded run directly.
 - `COVERAGE:` should describe what the run was intended to cover without listing target hosts.
 - `TEST FLOW:` should describe the template-specific numbered run flow once for the whole test, not per host.
 - The watcher resolves `TEST FLOW:` from the run template name.