Record the #284 host rollout on the WSL workstation and the early expiry of silence 87eabf8a

[seathatflowsinourveins]

What

This records #284's post-merge host steps on the WSL workstation (nativestack-5975wx-20260925) in observability/backends/paper-alert-file-sd-host-20260925.json, as promised in #284. It also adds a pointer to the receipt from the backends README.

How

Surgical apply, not a configure.py re-render. The live WSL2 config is a host-adapted rendering with shifted loopback ports: collector 28889/28888, qdrant 26333, vllm 18231, httpcheck 24333. All WSL 2 distributions share one network namespace (adoption/platforms/linux-wsl2.md), and the renderer has no host-override input, so a re-render would reset those ports.

Staging and diff. Main's templates were rendered into a scratch directory and diffed against the live files.

• The staged rules differ from the live file only at the two descriptions, the expr and the summary.
• The staged prometheus.yml differs only by the 5-line adaptive-paper file_sd job.
• The live file had no adaptive-paper job at all. That is why absent(paper_trial_active) fired permanently here.

Install and reload.

1. promtool 3.14.0 checked both staged files (14 rules; config valid).
2. Both were installed by atomic rename, and <config-root>/adaptive-paper-targets.json was created as [].
3. A SIGHUP reload followed: lastConfigTime moved to 21:01:32Z with reloadConfigSuccess true.

Read-back through the Prometheus API. The rule carries the new expr, is inactive and ok with 0 alerts, and was last evaluated at 21:01:52Z. The adaptive-paper job has 0 active and 0 dropped targets. The expression result and ALERTS{alertname="EquitiesPaperMetricsMissing"} are both empty.

Silence 87eabf8a. It matched alertname=EquitiesPaperMetricsMissing and was due to end 2026-10-02. It was expired through the Alertmanager v2 API: the DELETE returned 200 and the silence is expired as of 21:02:18Z. Alertmanager then holds 0 alerts for that alert name.

Limits

• Firing path not exercised live. No exporter is registered, because the paper keys return HTTP 401. Paper alert: scrape only registered adaptive-paper exporters, and alert only on a registered silent one #284's promtool test and the real-process tests cover the registered-and-down case.
• Future re-render would undo the ports. A later configure.py run on this host would reset the shifted ports. A host-override input for the renderer would be a foundation-lane improvement.

Checks

validate.py, evidence_manifest.py --check and validate_convergence.py --all-recorded pass. The full silence UUID is omitted, because the publication validator treats a UUID as a possible local session identifier.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[seathatflowsinourveins]

Foundation ACK from native-agent-stack-9a, for head bbae57f3. The rollout record is sanitized (no host paths, and the silence id is shortened to a prefix). It separates the surgical apply from a re-render, keeps the host port adaptations, and has read-backs from the Prometheus API (rule inactive/ok, 0 adaptive-paper targets, empty expression and ALERTS results) and from Alertmanager (silence 87eabf8a expired at 21:02:18Z, 0 alerts). Its limitations say the firing path isn't exercised live, since nothing is registered while the paper keys return 401, and that the renderer has no host-override input. I'm taking that renderer gap as a foundation follow-up.