llmmsg-srv
MSG-380
[source-integrity] DMs the PM after every deploy for a condition that is true by construction and self-resolves
Done normal
clcoder-llmmsgsrv-cc
pm-llmmsgsrv-cc, 2026-09-11, under Elazar token-cost directive. [source-integrity] DMs hub_blob_differs_from_head after every restart-before-push. In that window the finding is TRUE BY CONSTRUCTION and self-resolves on the push, so the DM is advisory noise charged to the PM on every deploy. The same content already goes to the journal. Scope: keep the journal line, stop the DM - either drop it outright or gate it on the dirty state persisting past a window. The PM ruled explicitly that another disable flag is NOT the fix. Lane: author the diff with proof, hand to pm-llmmsgsrv-cc to gate and deploy. Never applied by me.
Activity
-
Patch ready for gate. /data-venus/llmmsg-srv/diffs/2026-09-11-msg-380-source-integrity-grace.patch (141+/53-, hub/hub.mjs only), rationale .md and harness.sh beside it. Baseline md5 f5036148a2fa4bed466a963c7b200957 (v2.59.7 ea31dc9), git apply --check -p1 clean, post-apply md5 1e6551e4b56adbfe30b8b00dc2112044. 26/26 assertions pass, both mutants red. Supersedes the DESIGN.md (stale baseline).
-
SHIPPED v2.59.8, commit 57494a4, gated + deployed by pm-llmmsgsrv-cc 2026-09-11 13:25 UTC. Dirty boot now defers its DM 900s and re-checks; ahead/unknown keep immediate boot alerts (MSG-307). Verified on the real deploy path: first restart logged 'deferring the alert 900s', killed at ~43s, successor booted state=clean head=57494a4, zero DMs from either. Independent harness re-run 24/26 - the 2 fails are the harness's own line() normalizer, which blanks head= but not 'fetched Ns ago', making c4/c6 timing-dependent; patch behaviour identical.
bug
5w ago by wi-cli-venus
5w ago
2026-09-11 14:11