PR #50's content was merged out-of-band (squash commit 2dfc3e1, 2026-08-30 12:16 UTC) while the PR itself stayed open, which double-applied the ## Execution section in infrastructure-monitoring.prose.md.
Master currently carries two identical ## Execution blocks (lines 104 and 177), each with its own ### check-health + Phases 1-4.
Change
Delete the second (duplicate) copy of the ## Execution block — 73 lines removed.
The RUN LIVE, NEVER ECHO rule — kept exactly as written.
No changes to any other contract, registry, or script.
The gpu-light model-row conflict (Qwen3.5-9B vs gemma-4-12b) — needs live verification against .110 first; will follow up separately with @abiba-bot.
Verification
scripts/prose-lint.sh passed locally before push (15 pre-existing warnings, 0 errors).
Post-dedup structure verified: check-health ×1, Phase 1: GPU Exporters ×1, RUN LIVE, NEVER ECHO ×1.
Relates to dangling PR #50 (should be closed once this lands). Tagging @abiba-bot for the CRITICAL-adjacent review per AGENTS.md authorization table.
## Problem
PR #50's content was merged out-of-band (squash commit `2dfc3e1`, 2026-08-30 12:16 UTC) while the PR itself stayed **open**, which double-applied the `## Execution` section in `infrastructure-monitoring.prose.md`.
Master currently carries **two identical `## Execution` blocks** (lines 104 and 177), each with its own `### check-health` + Phases 1-4.
## Change
- Delete the second (duplicate) copy of the `## Execution` block — 73 lines removed.
- Result: single canonical flow `## Execution → ### check-health (RUN LIVE, NEVER ECHO probes) → Phases 1-4 → ## Verification Commands`.
## Intentionally NOT changed
- The `check-health` probe content itself (Zulip ping, pm2 jlist, :9400 exporters, Prometheus, Grafana, LiteLLM metrics) — Abiba's wording is kept verbatim.
- The `RUN LIVE, NEVER ECHO` rule — kept exactly as written.
- No changes to any other contract, registry, or script.
- The gpu-light model-row conflict (Qwen3.5-9B vs gemma-4-12b) — needs live verification against .110 first; will follow up separately with @abiba-bot.
## Verification
- `scripts/prose-lint.sh` passed locally before push (15 pre-existing warnings, 0 errors).
- Post-dedup structure verified: `check-health` ×1, `Phase 1: GPU Exporters` ×1, `RUN LIVE, NEVER ECHO` ×1.
Relates to dangling PR #50 (should be closed once this lands). Tagging @abiba-bot for the CRITICAL-adjacent review per AGENTS.md authorization table.
PR #50's content was squash-merged out-of-band (2dfc3e1, 2026-08-30) while
the PR itself stayed open, double-applying the check-health/Execution
section. This drops the second copy; keeps one canonical
Execution -> check-health -> Phases 1-4 -> Verification Commands flow.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
PR #50's content was merged out-of-band (squash commit
2dfc3e1, 2026-08-30 12:16 UTC) while the PR itself stayed open, which double-applied the## Executionsection ininfrastructure-monitoring.prose.md.Master currently carries two identical
## Executionblocks (lines 104 and 177), each with its own### check-health+ Phases 1-4.Change
## Executionblock — 73 lines removed.## Execution → ### check-health (RUN LIVE, NEVER ECHO probes) → Phases 1-4 → ## Verification Commands.Intentionally NOT changed
check-healthprobe content itself (Zulip ping, pm2 jlist, :9400 exporters, Prometheus, Grafana, LiteLLM metrics) — Abiba's wording is kept verbatim.RUN LIVE, NEVER ECHOrule — kept exactly as written.Verification
scripts/prose-lint.shpassed locally before push (15 pre-existing warnings, 0 errors).check-health×1,Phase 1: GPU Exporters×1,RUN LIVE, NEVER ECHO×1.Relates to dangling PR #50 (should be closed once this lands). Tagging @abiba-bot for the CRITICAL-adjacent review per AGENTS.md authorization table.