chore(ops-agent): re-sync max2 baseline — smoke_copilot_media_organizer #43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/ops-agent-baseline-copilot-smoke-max2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Wat
Re-sync van de max2 ops-agent baseline naar de live
/etc/ops-agentconfig. De drift-detector (ops-agent-host-config-disciplinerunbook) meldde 2 gedrifte files:deploy/max2-workflows/ops-agent/baseline/commands.ymldeploy/max2-workflows/ops-agent/baseline/flows/redeploy_media_organizer.ymlReview: was de live-wijziging bedoeld? — Ja
De live change is op 2026-06-19 14:14 toegepast (met
.bak.20260619-141427backups ernaast) en is coherent + functioneel:smoke_copilot_media_organizer:docker exec media-organizer-web→S4M_COPILOT_URL/health(read-only healthcheck, niet-destructief).redeploy_media_organizermeton_failure: continue(non-blocking).Live geverifieerd:
media-organizer-webdraait enS4M_COPILOT_URLis gezet (http://100.118.195.120:8100), dus de smoke werkt echt.Wat deze PR doet
Alleen de repo-baseline bijgewerkt zodat die byte-identiek is aan live — géén live-wijziging. Na merge leest de drift-detector de gemergede baseline en is de detector weer stil.
Conform §2 van de
ops-agent-host-config-disciplinerunbook (double-edit; no self-merge — deze PR wacht op review).