docs: document SonarQube CI setup and scan scope
Document named standing-watch routing and profile selection
docs: explain CI scheduling and full critical-path measurements
Keep only template docs in the wiki TRANSITION-CONTEXT documented one box's migration, and Development mixed that box's PATH/git-identity/tool notes into repo guidance. Both describe a deployment, not the template, so they move to the host's own config repo. Development keeps the CI facts and gains the generated-module drift check. Home states what the wiki deliberately excludes, so the split does not have to be re-derived. The dropped tool claims were also stale: awk and python3 are both installed now.
Add users-vs-sessions doctrine page; link it from Home
Adopt the agent-box rename (Home/Development); mark TRANSITION-CONTEXT historical
Keep only evergreen docs in wiki; session-continuity moves local
Add maintainer continuity notes (session-continuity, transition-context)
Initial Home page