Date: 2026-06-01

What was accomplished

Performed a read-only review of /Users/samaguiar/Documents/Projects, the nested GitHub projects repo, the sail-projects-root repo, and the surrounding local environment. Used the folder hygiene guardrail, local Git, GitHub CLI, and Notion export. No cleanup, deletion, rename, commit, push, or destructive change was made.

Key current findings:

• Folder hygiene dry-run reported 7 hard violations and wrote /Users/samaguiar/Documents/Projects/admin/session_logs/folder-hygiene-2026-06-01.md.
• sail-projects-root is private, pushed 2026-06-01T16:50:20Z, and is the GitHub repo for the Projects root.
• projects is private, pushed 2026-06-01T17:16:34Z, and the local nested checkout is on agent/make-life-easier-2026-05-28, ahead 1 with 18 dirty paths.
• Local Projects root is on codex/footer-watchdog-2026-06-01, tracking origin, with 337 dirty paths.
• Several nested repos are dirty: sail-litify about 3587 paths, sail-marketing about 1739, sail-knowledge about 757, sail-infrastructure about 136, ha-law about 86, sail-command-center about 30, and smaller dirty states in others.
• Two local main branches track gone upstream branches: sail-dashboard and sail-marketing-dashboard.
• Root .git has duplicate sync artifacts such as index 2 through index 26 and AUTO_MERGE 2/3, consistent with multi-device filesystem syncing touching Git internals.
• Root hygiene also showed non-allowlisted clutter, names with spaces at root, duplicate marketing and SEO folders, root folders shadowing Repos/sail-*, 50 credential-shaped path hits outside .credentials, Repos naming drift, and a broken launchd reference for desktop_cleanup/run.sh.
• GitHub repo inventory confirms newer canonical repos already exist for this cleanup strategy: sail-projects-root, sail-skills, sail-design-library, and domain repos such as sail-marketing, sail-seo, sail-litify, sail-infrastructure, and sail-templates.

Plan recommended

1. Freeze cleanup as read-only first: snapshot status for each repo, save a manifest, and avoid any move/delete until rollback bundles are created.
2. Protect Git from multi-device sync: stop syncing .git, node_modules, .venv, Playwright browsers, caches, build outputs, and generated QA artifacts through iCloud or similar sync. Use GitHub as the source of truth, not filesystem sync of live repos.
3. Resolve source-control state by repo, not by folder sweep: triage uncommitted changes in sail-litify, sail-marketing, sail-knowledge, root, and projects; create rescue branches or patch bundles before cleanup.
4. Normalize repo layout: keep active code in Repos/sail-*; route root artifacts to admin/inbox, admin/session_logs, admin/rollback, or the relevant domain repo. Use sail-design-library for design assets rather than Design Elements - Current as a mutable local source.
5. Fix hygiene rules and automation: repair the broken desktop_cleanup launchd path, prune stale worktree metadata after confirming no active agents, and update folder hygiene to understand canonical exceptions versus real drift.
6. Add prevention gates: preflight on session start, pre-commit checks for root clutter and credential-shaped files, scheduled repo health summary, and a cloud mirror that records current repo cleanliness by device.