D109 established context_pct field. Schema not yet applied to Server [40] and Builder [02] system DBs. Confirm which tables need the column and deploy.

Independently reported by Finance (K147), Server itself (K143), and Master's own session today, plus Server's own ZIP-intake note describing a sustained 15-minute window affecting all endpoints that resolved on its own. Consistent pattern across all reports: COMMS api, memory-pipeline api, and inbox api time out intermittently while each system's own data api and static file reads stay mostly healthy. Not random - same few endpoints repeatedly across separate sessions and separate systems. Elevating from scattered knowledge entries to a formal task since the pattern is now well-evidenced. Likely PHP-FPM worker pool or resource contention given static files sometimes fail too during the worst windows, but no server-level diagnostic access to confirm root cause from this side.

Lightbox opens but image is tiny on mobile (layout bug). Rotate buttons present but not functioning. Delete untested. Token fix applied 07/26/26 but issue persists. Needs full debug and retest on Android Firefox. Photo editor standard requires these controls work in-lightbox.

Two '95-travel' folders exist on ikre84i@yttcom.net Drive under same parent (canonical: created 07/23, has Backup/ + ES2026/JT2026 history; duplicate: created 07/25 today, holds the working SD2026 Notes/Expenses/Daily Log files + a stray extra Daily Log copy). Canonical copies of Notes/Expenses/Daily Log now placed in canonical 95-travel/SanDiego-072526-072826/. No Drive delete tool available to this session — needs manual trash of duplicate folder tree (id 17qmjFNht9Q1laOpFB8YuNQvNAyQD3Ihk) and its contents.

Two command reference lists have drifted apart: EXEC_OPEN_Master template COMMANDS section vs ORIENT-REG.md COMMANDS section. Neither confirmed to match the live commands-directory access-control whitelist per D270 security protocol. Server 40 to pull the live allow-list, reconcile ORIENT-REG to match it, then update the EXEC_OPEN template to match ORIENT-REG. Filed by Master 01 session 07/27/26.

The legacy-file gate in CLOSE only special-cases Builder for using system code naming, defaults to decade code for every other system. Daily's own gov-file audit (07/29) confirmed system-code naming (05-suffix) is authoritative, decade-code naming (50-suffix) is a stale duplicate being deprecated. Fix is ready and verified (brace/paren balanced, single line) but I cannot write to the protected commands directory directly per D270. Please add Daily system code to the same special-case list Builder already has. Low urgency, soft warn only, but will misfire every Daily close until fixed. Ask Master for the exact line if needed.

Samsung Fit 3 syncs to Samsung Health app. Export path: Samsung Health CSV export. Goal: import exercise data into Gym Logger. Needs scoping by Health [07] and Builder [02]. Route via Master [01].

USR369 said a report on a new photo center should have been sent to Master. Searched Master's full inbox (589 messages) and knowledge.db for 'photo center', 'photo', 'media' - no such report exists. Found related but not equivalent items: a Photo Standard note in Travel's knowledge-95.md (lightbox pattern for photo grids, dated 07/26/26), T342/message 595 (Lightbox photo editor broken on mobile, high priority, already open), and D352 (media.db established as a Server[40] research scratch pad, not primary photo storage). Whichever system built the photo center needs to actually send Master the report - it never arrived.

Admin[00] self-logged (knowledge-00.md 07/24/26): kill-switch.html close button calls CLOSE.php directly, skipping full D079 sequence (SYNC->outbound-pending->LOG->DELIVER->RECORD->DROP). Session shows closed on dashboard but no close report ever reaches Master[01] inbox - creates a silent gap David has to catch manually. Fix: either (a) wire kill-switch to POST a close-report stub to inbox-api targeting Master[01] right after calling CLOSE.php, or (b) add explicit on-screen warning that kill-switch is emergency-only and full close protocol must be run manually after. File location not found via file-reader in this session - needs Builder[02] to locate (likely backend/tools/ or backend/ root) and confirm before patching.

Each system COMMANDS file should fire automatically at session open step 3b (ORIENT) — not just on manual URL call. Server [40] to update OPEN.php and/or REFRESH.php to call each system's COMMANDS-[decade].php automatically. Include jurisdiction_check (T034) as part of that auto-fire sequence.

Health [07] needs Gym Logger sessions synced to 70-app.db. Builder [02] owns the HTML/JS side. Server [40] owns any PHP/DB api changes needed. Health [07] verifies data lands correctly.

Add cmd=jurisdiction_check to each system's COMMANDS file. Queries jurisdiction.db for all items owned by that system. Fires at ORIENT (session open step 3b). Auto-reports to Master [01]. D290.

USR369 asked how much room is available for saving multimedia/books. Tried the standard bootstrap pattern (tmp b64 payload -> boot script in systems/10-master/toolbox/ -> execute -> read result) 3 times with increasing simplification. Every GET to the ad-hoc toolbox boot file returned a genuine 404 from LiteSpeed (confirmed via -i, real HTTP 404 not a JSON error), even though file_write_web.php reported successful writes at the exact same path. Backup-status-api.php also 404'd at its known path. Strong signal this is WAF/whitelist blocking un-whitelisted ad-hoc PHP execution in toolbox/, consistent with the platform's own WAF-whitelist-required-for-new-command-PHPs pattern. Could not get real disk_free_space/disk_total_space numbers as a result. FIX NEEDED: Server[40] add a disk_usage action to an already-whitelisted endpoint (e.g. backup-status-api.php or records-api.php) reporting disk_free_space()/disk_total_space() plus size of backend/web/media and backups/ dirs.

Already in Server todo. Check systems/10-master/history/ systems/20-builder/history/ systems/40-server/history/ — what files are there, are they current or legacy, should they be cleaned.

master-tool.php deployed 07/22/26. Actions: read/scan/grep/exec_php/wipe all live. COPY action stubbed but needs verify. COMMANDS-01.php should reference master-tool.php so it appears in session orient. Low priority — tool is usable now.

These three frontend pages still use baked-in JS data arrays. Data should be migrated to 30-app.db (new tables as needed) and pages converted to DB-driven like windows.html and android.html.

New endpoint at backend/api/critical/backup-status-api.php. Action: get_backup_status. Scans backup dirs per BACKUP-REG.md groups and returns per group: name, level, newest file, timestamp, age_hours, age_label, health (ok/warn/stale), plus file list with individual timestamps. CRITICAL groups: platform-commands, platform-api, platform-tools-api, platform-root-infra, platform-governance. STANDARD: platform-html-pages, platform-debug. Health thresholds: ok=under 24h, warn=1-3d, stale=3d+. Full spec in Builder [02] inbox msg 363. Report back to inbox system=02 when live. Depends on T653 (BACKUP-REG.md registry update).