USR369 reported Health couldn't reach Gym Logger at the gym 08/08/26, worked around with a manual spreadsheet. Investigated live: confirmed Gym Logger's real store (save.php/load.php, profile=david) has 17 sessions through 08/08 -- the app itself is fine. Root cause is T480 (Wire Gym Logger to 70-app.db, Builder 20, open since before 07/19), never completed -- Health's own 70-app.db is a stale disconnected copy (11 sessions, 06/13-07/16). Also found 3 stale/empty profile keys (IWH/usr369/main) that could compound confusion. Escalated T480 to Builder with concrete evidence (msg 888). Built Health-Gym-Log.xlsx, backfilled with full existing history (133 rows/17 sessions, not just a scaffold) as an immediate stopgap. Wrote SOP-HEALTH-LOG.md v1.0. Registered in BACKUP-REG.md and SOP-INDEX.md v2.5. Updated Health's own todo-70.md -- escalated T480 with evidence, added the new dual-write task, and flagged that an existing standing instruction (write to 70-app.db at close) has been faithfully followed but doesn't actually reach the app's real data store, so it shouldn't be mistaken for equivalent.