USR369 said start working on real housekeeping scheduling after confirming (via ask_user_input) automatic trash deletion is fine given the 8-day recoverable buffer. Checked TASKGATE first, matched SOP-CLEAN.md (6th false match pattern this session, not separately logged given the pattern is already well-documented at K238/K239/K241). Before building anything, checked whether the existing daily health check was actually running - found MAINTENANCE-LOG.md completely empty, zero entries, despite SOP-HEALTH-CHECK.md documenting a daily requirement since 08/02/26. Same failure class as SOP-INDEX pre-D675 - a real procedure nobody enforces just stops happening. Wrote SOP-HOUSEKEEPING-SCHEDULE.md: consolidates all cadenced duties in one table with real status (not assumed), poses the real-cron-feasibility question to Server before building a workaround for a problem that might have a real fix, specs the weekly CLEAN/CLEANBACKUPS sweep with full automatic trash-lifecycle enforcement through actual deletion (USR369-approved, no per-run gate), and specs a fallback session-open enforcement gate (non-blocking, same severity as the tokens STALE check) if real cron isn't available. Added to SOP-INDEX.md. Filed T-HOUSEKEEPING-SCHEDULE (!high) and sent Server a full work order (inbox 801) covering both the cron question and the health-check enforcement gap together rather than as two separate future tickets.