Automate deploy

[Anulo2]

I'm not knowleadgeble about the deploy practices in wikimedia/wikipedia but I'm pretty sure https://github.com/WikiEducationFoundation/topic-builder/blob/main/mcp_server/deploy_landing.sh this is now a great way to do deployments. Should probably evaluate switching to building through ci/cd and doing an automated deploy on a release/tag

[Anulo2]

Related deployment drift for the same operations cleanup:

• docs/operations.md:15 documents a single service at 127.0.0.1:8000; deploy.sh:52-58,212 actually installs the template unit topic-builder@.service with two instances (8000 + 8001) and no non-templated counterpart (the legacy topic-builder.service is actively stopped, disabled, and rm'd at L44-L49).
• Worse than stale prose: the runbook recovery command systemctl restart topic-builder (docs/operations.md:111) targets a unit that does not exist. An operator following it mid-incident gets "unit not found"; reality is topic-builder@8000.service / topic-builder@8001.service.
• Same line wipes only exports/*.csv, and the per-file revoke recipe (docs/operations.md:115) likewise ignores *-rubric.txt sidecars, which can also carry topic data (see Anonymous MCP callers can export any topic's CSV to a public URL #11).

Deploy automation and runbook corrections can be separate tasks under this umbrella.

Correction note: an earlier version of this comment also claimed deploy_landing.sh publishes the whole repository (including benchmark reports) to the static dir. That was wrong — the script is 19 lines and scp's exactly one file, landing.html → static/index.html; and deploy.sh's app copy is an explicit allowlist, not a repo-wide copy. Bullet removed.