USR369 said he had no visibility into the schedule and couldn't drill down. Made each duty's name clickable -- expands to show the SOP link (what the duty actually does) and the 3 most recent MAINTENANCE-LOG.md entries for that owner system, reusing the same parsing logic as maintenance-log.html, cached once per page load so opening multiple duties doesn't re-fetch. For Tools Index, added a read-only 'View Code' link per tool pointing to file-reader.php?path=<the tool's own real path> -- confirmed file-reader.php's auth (cai_check_token) already checks the PHP session cookie before falling back to a URL token, so this works for a real logged-in browser without needing to embed a token in the page (my earlier curl-based 403 test was a false negative from curl having no session cookie, not a real limitation).