kami
7f25dc43e4
A full vision + identity + reconcile cycle ran today against a worker that had
been started before the fix it was supposed to prove. It reproduced the defect
exactly: 46 of 110 boxes past the 900px panel width, coordinates clamping at
1000, the same fingerprint measured before the fix.
vision worker started 12:00:09
worker_vision.py modified 12:11:35
8113bdf, carrying _bbox_to_pixels 12:16:22
Python binds a module once, at process start. Editing the file afterwards
changes nothing until the process restarts, and nothing in the result says so:
the stage reported completed 116/116, the orchestrator recorded no error, and
identity and reconcile ran to completion on top of it. Cost was one cycle plus
a registry reset to undo the 8 characters it minted.
This was already known as advice. The previous handoff said the render worker
"must be restarted by hand to pick up an edit". Advice did not stop it.
check_stale.sh compares every running worker's process start against its
module's mtime and exits non-zero if any is stale, so it can gate a script.
Mutation-tested by touching worker_tts.py, which it caught.
decisions/identity-bbox.md#stale-worker-invalidates carries the evidence and
is committed separately with the rest of the session's notes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011FmkHKFtuhppZE3B4VvNNE