[P3.2] Purge scratch artifacts and fix no-op or personalized ops scripts

[frankbria]

Filed by the SaaS launch review. Priority P3.2 — severity low, category hygiene.

Problem

The public AGPL repo that prospective customers clone contains 38 dated AI session-scratch files in claudedocs/, a root-level test_config_manual.py print-assert script outside pytest collection, tests/test_issues.md, demo-pr888.md, and a committed Playwright test-results/.last-run.json that overrides its own .gitignore and permanently reports 'failed'. scripts/deploy.sh prints '✅ Deployment simulation successful' and exits 0 without deploying — anyone wiring it into a pipeline gets a passing step and no deployment — and seed-staging.sh targets the removed v1 API while faking success. The systemd units hardcode User=frankbria and /home/frankbria paths, scripts/test-websocket.py hardcodes a personal LAN host and targets the removed /ws endpoint, and deploy.yml installs root PM2 deps with unpinned npm install.

Evidence

• claudedocs/sprint4-p0-BREAKTHROUGH.md:1
• test_config_manual.py:2
• test-results/.last-run.json:1
• scripts/deploy.sh:19
• scripts/seed-staging.sh:57
• systemd/codeframe-staging.service:9
• .github/workflows/deploy.yml:560

Acceptance criteria

• test_config_manual.py, tests/test_issues.md, demo-pr888.md, test-results/.last-run.json and claudedocs/ are removed or relocated under legacydocs/, with the docs table updated
• scripts/deploy.sh and scripts/seed-staging.sh either do real work or are deleted; no script exits 0 after printing simulated success
• scripts/fix_workspace_env.py and scripts/test-websocket.py removed
• systemd units parameterize user/paths; no personal username or /home/ path in tracked files
• deploy.yml uses npm ci against a committed lockfile

---

Atomic by construction: one developer, one focused session.