fix(deploy): isolate tracked compose stack

[FZR95]

Summary

• pin production Docker Compose commands to the tracked root docker-compose.yml
• prevent server-local docker-compose.override files from silently reintroducing WorldWeave into the TopicLab stack
• remove legacy project orphan containers during the controlled down/up cycle
• cover the Compose isolation and orphan cleanup contract in the frontend deployment config test

Root cause

The server still has legacy tashan-topiclab-worldweave containers and an untracked override restored from old history. TopicLab main no longer defines those services, but unpinned Compose commands can load a local override and recreate the coupling.

Validation

• WorldWeave proxy deployment config test: 7 passed
• deploy workflow YAML parse: passed
• Docker Compose config: passed
• git diff --check: passed

Safety and merge order

This PR does not remove Docker volumes. Merge only after TashanGKD/worldweave#22 has deployed successfully, https://worldweave.tashan.chat passes its public smoke checks, and TopicLab DEPLOY_ENV points WORLDWEAVE_BASE_URL and WORLDWEAVE_UPSTREAM to that HTTPS origin. The old TopicLab WorldWeave cache volume remains available for an explicit one-time migration if needed.