core: an empty or half-written team file is diagnosed as "saved by a newer FlyBot; update FlyBot" #2716

Written-by: Chief

Same audit, same sha. A state.json that parses but carries no version — {}, null, [], "" (0 bytes reads as empty), a truncated file — falls through to the sentence a genuinely newer file gets, so the person is told to update a program that is already current, and the only real recovery ("this file is empty or half written; move it aside") is never said. Fail-closed otherwise: the file is not touched and load() resolves — this is a wrong diagnosis on the very first thing a bad install can hit, not a data risk.

core/src/host/store.js:250, the fall-through of readFileState() (branches above it are version === 1 at :224 and version === STATE_VERSION at :240):

250:    stuck = 'saved by a newer FlyBot; update FlyBot'

Reproduction

cd /data/dsh/bot/workspace/audit48
### 2 empty object {}    (out/1-store-shapes.txt)
readOnly: "The Bot team file … could not be read (saved by a newer FlyBot; update FlyBot). …"
files: [ 'state.json', 'state.lock' ]        # no .broken- copy, file untouched
live : { "readOnly": "… (saved by a newer FlyBot; update FlyBot) …" }
fixed: { "readOnly": "… (the team file has no version: it is incomplete (an empty or half-written file)) …" }

Change scope

Before :250, branch on parsed?.version === undefined and answer "the team file has no version — it is incomplete (an empty or half-written file)". Keep the genuine "newer" sentence for a version above STATE_VERSION (test/store.test.js:209 already covers that). Test: {}, null, [] and a 0-byte file all get the incomplete sentence; {"version": 999} keeps the newer-FlyBot one.

Evidence: /data/dsh/bot/workspace/audit48/EVIDENCE-verify8c82.md (F3), /data/dsh/bot/workspace/audit48/out/1-store-shapes.txt, /data/dsh/bot/workspace/audit48/out/4-controls.txt.