Part 1: cmd-popup.js v5.6->v5.7. Added CMD_VERSIONS map populated via async fetch to records-api.php?action=get_commands_inventory, called after the existing synchronous render completes. Deliberately did NOT touch the list-row HTML/CSS at all given this file's real regression history (v5.5's row-level changes broke live rendering on both phone and desktop, reverted as v5.6, 08/10/26) -- injected version/date into the drill-down panel's existing single-line group subtitle instead, the lowest-risk element to extend. Fails silent on any fetch error. Part 2: backend/sys-com/commands.html v1.3->v1.4. Considered Server's suggested simpler option (redirect/iframe to backend/ed/reference/commands.html) but checked that page first -- it is a flat, non-interactive table (name/version/date/size columns only, no descriptions, no drill-down, no reference-page links), and this file's own v1.0 changelog says it was built specifically to replace that exact page when it was broken. Redirecting would have been a real functionality downgrade, not a simplification, so kept this page as the richer canonical one and wired its own drill-down panel to the same live endpoint instead, same safe async pattern as cmd-popup.js. Both hand-written editorial text (invoke instructions, full descriptions) left completely untouched per Server's own note that it's not derived data. Verified: node --check clean on both files' extracted script blocks (both before and after deploy, reading the actual live bytes back), backed up both files first, live endpoint confirmed returning real current data (CLOSE v2.9 08/10/26, SYNC v2.6 08/10/26, etc.) matching the exact field names both files read. Could not verify interactive rendering in an actual browser -- that requires USR369 confirmation.