Zero monotonic sentinel suppresses the first corrupt-memory diagnostic on a young host

[Calmingstorm]

Severity: P3

Verified at v4.10.0, 55c15761845b00931ab2ea4aa184a7797dfd0614.

Locations

src/tools/executor.py:249,1433-1436

Failure scenario / benefit and affected installs

Machineuptime<300sec andunreadablememory. Lastlogged0interpretedrecent, emptymemorydegradationfirstwarning suppressed.

Verification

Independently traced timestampinitialization/rategate; reviewerStoreCorruptError clock100 noerrorlog.

Correction and tests

Distinguishneverloggedfromrealzeroandregressfirstwarning; hostuptimenotprocessage.

Duplicate screening

Checked original open/closed inventory and fresh GitHub title/body search. No matching root. Full-path traces and harmless mocks only; mutation strings were never executed.

[Calmingstorm]

Validated as fixed on campaign/v4.10.0-review (PR #629) at a978f193: the fix was reviewed against the final code, and its regression tests pass on the branch and in CI. It is not merged to master yet. Closing per the maintainer's instruction; reopen if a later change regresses it.