yttcom.net
Backend / Tools / DB Viewer
yttcom.net
Domains / DB Viewer
v2.0 · 07.11.26
◇ 20-sys.db
systems/20-builder/data/
records.db inbox.db transfers.db knowledge.db jurisdiction.db
20-sys sessions Row #33
Tables
decisions
77
domain
0
events
0
gov_archive
0
gov_archive_fts
0
gov_archive_fts_config
1
gov_archive_fts_data
2
gov_archive_fts_docsize
0
gov_archive_fts_idx
0
items
5
sessions
47
sqlite_sequence
4
transfers_log
2
sessions — Row #33
20-sys.db · systems/20-builder/data/
id
33
package
—
duration_minutes
89
decision_ids
system
02
date
08/01/26
decisions_count
0
transfers_in
0
transfers_out
0
context_pct
—
context_bucket
—
_rowid
33
summary
Diagnosed and fixed corrupted live Gym Logger (index.html), verified working, backed up, logged D626, flagged registry/diary drift for follow-up.
work_done
Investigated Gym Logger working copy per David's request; found index.html truncated/corrupted on server (98KB vs expected, no closing tags, confirmed 3x). Located last known-good backup via X-plore (David's device) at backups/70-health/apps/gym-logger/gym-logger-v5.39-07-17-26-1800.html (222KB). Verified backup integrity, restored to live index.html, re-verified post-restore (tag balance, node --check syntax, live save.php/load.php round-trip with real session data, 48 sessions through 07/18/26). Backed up both the corrupted pre-fix copy and the verified-good restored copy. Logged decision D626 with verification. Updated handoff-02.md in full. Flagged for follow-up: DEFAULTS-REG.md's Gym Logger PRIMARY APP pointer is wrong (points to stale v5.25 gym-logger-CURRENT.html, not the real live index.html); BUILD-DIARY.md stale since 07/13/26; v5.40/v5.41 changes not yet recovered.
▼ Show timestamps
created_at
2026-08-01 08:40:19
Backend Domains Panel DB Viewer Transfers
Backend Tools DB Viewer DB Admin Server Map File Editor Backend Tools DB Viewer DB Admin Server Map File Editor