etwenandClaude Opus 5
a5b7c4757b
EN_Cold_Warm_boot = 1 opens Logs\Blanton_Reboot_Cycle_<ts>.log and prints a "Reboot Cycle : N" banner each round; = 2 opens Blanton_Power_Cycle_<ts>.log and prints "Power Cycle : N". Three sites branch on the flag now: the log name, the banner, and the boot itself. Two things follow from it. With EN_Cold_Warm_boot = 0 there is no longer a logopen either, so the run that already hangs at wait "Booting in blind mode" now also leaves no log to show where it stopped. EN_log = 1 on its own no longer produces a log from this macro. And anything that parses these logs has to accept both banners. The cycle banner is the record separator the check-point and per-segment timing reports are built on, so a parser that only greps "Reboot Cycle :" finds zero cycles in a power-cycle log and reports nothing without complaining. The logopen timestamp flag stays a literal 1 rather than EN_timestamp the way Script A does it. That is the right call here - the per-segment timing analysis is derived from those timestamps and there is no other way to recover them - but it does mean this macro ignores EN_timestamp = 0. Recorded under V1.2.2 in Script A's history; the header version is unchanged because V1.2.2 has not been tagged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM