← back to Designerwallcoverings
TK-10933: rotate stale stroheim launchd.err (31 pre-fcffc7f ReferenceError lines + 1 SIGTERM) out of the live log
1b39a0ed25f0ddcf4f0e6f84d1eec61e0d325591 · 2026-09-10 07:37:12 -0700 · Steve Abrams
The log is append-only and never rotated, so it still carried Aug-29 crash text
from before the err->skip fix (fcffc7f). Every agent and the launchd-job-canary
that greps stderr CONTENT kept re-reading that stale signature and re-diagnosing
a crash that no longer exists. Source is clean: zero bare 'err' identifiers,
node --check PASS.
Renamed (not recreated) on purpose: launchd recreates .err on next run, which
keeps runEvidenceMtimeMs correlated to launchd.out ('same-run'). Creating a
fresh empty .err would have set mtime=now and produced the more confusing
'run-newer' / 'older than failing run evidence' warn instead. Verified against
cron-fire-canary/lib/fresh-artifact-classifier.mjs as a pure function.
Reversible: archive kept at launchd.err.stale-pre-fcffc7f.20260910; prior
content also in git blob d373fbb.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QzGkUdf9QjmDmeKrt6raHi
Files touched
R100 scripts/stroheim-onboard/out/launchd.err scripts/stroheim-onboard/out/launchd.err.stale-pre-fcffc7f.20260910
Diff
commit 1b39a0ed25f0ddcf4f0e6f84d1eec61e0d325591
Author: Steve Abrams <steve@designerwallcoverings.com>
Date: Thu Sep 10 07:37:12 2026 -0700
TK-10933: rotate stale stroheim launchd.err (31 pre-fcffc7f ReferenceError lines + 1 SIGTERM) out of the live log
The log is append-only and never rotated, so it still carried Aug-29 crash text
from before the err->skip fix (fcffc7f). Every agent and the launchd-job-canary
that greps stderr CONTENT kept re-reading that stale signature and re-diagnosing
a crash that no longer exists. Source is clean: zero bare 'err' identifiers,
node --check PASS.
Renamed (not recreated) on purpose: launchd recreates .err on next run, which
keeps runEvidenceMtimeMs correlated to launchd.out ('same-run'). Creating a
fresh empty .err would have set mtime=now and produced the more confusing
'run-newer' / 'older than failing run evidence' warn instead. Verified against
cron-fire-canary/lib/fresh-artifact-classifier.mjs as a pure function.
Reversible: archive kept at launchd.err.stale-pre-fcffc7f.20260910; prior
content also in git blob d373fbb.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QzGkUdf9QjmDmeKrt6raHi
---
.../out/{launchd.err => launchd.err.stale-pre-fcffc7f.20260910} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/scripts/stroheim-onboard/out/launchd.err b/scripts/stroheim-onboard/out/launchd.err.stale-pre-fcffc7f.20260910
similarity index 100%
rename from scripts/stroheim-onboard/out/launchd.err
rename to scripts/stroheim-onboard/out/launchd.err.stale-pre-fcffc7f.20260910
← f561cd9 auto-data-snapshot: 2026-09-10T07:33:05 (1 data files) — scr
·
back to Designerwallcoverings
·
TK-10933: add --reset-breaker, the explicit local repair for 6838ced →