BT411

Files

T

arcattackandClaude Opus 5 becaddb662 console logs ROTATE instead of truncate -- tonight's evidence loss cannot repeat

Two destroyers, both in btoperator.py:
  * Start Session zeroed operator_relay.log -- took the whole 23:08 session
    (the reservoir-crash round's relay trace) minutes after it happened;
  * Launch local instances os.remove()'d operator_N.log -- took the pod's
    [crash] self-report block before it could be copied.

Both now rotate the previous file to <name>.1 (btrelay_park's pattern: drop
the old .1, os.replace, never block on a locked file).  One generation of
history is exactly what post-mortems needed twice tonight.  All four console
suites pass; picks up on the console's next restart.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-07-27 00:13:06 -05:00

__pycache__

gauge-complete P4b: AggregateHeatSink 0xBBE -> HeatSink/AmbientTemperature bound (last config NULL cleared)

2026-07-07 20:10:11 -05:00

btconsole.py

seat identity swap (SAURON played as 'Draco'): the LEFT handler ate the pref of a re-seating player

2026-07-27 00:11:59 -05:00

btoperator.py

console logs ROTATE instead of truncate -- tonight's evidence loss cannot repeat

2026-07-27 00:13:06 -05:00

btrelay_park.py

parked relay: a supervisor that keeps it alive + a REMOTE restart the operator can actually reach