Remove obsolete Cloud infra repository references

[ShenzheZhu]

Target branch

main

Classification

Documentation / repository boundary cleanup

Problem

The public Community repository still described the retired Humanly-Lab/humanly-cloud-infra control plane and retained internal Cloud work-order documents. The private Cloud product now owns its source and deployment workflows directly.

Expected behavior

The public repository contains Community source, Community CI, package publishing, generic Docker assets, and self-hosting tools only. Official Humanly SaaS deployment workflows, credentials, topology, and operational work orders live only in the private Humanly-Lab/humanly-cloud repository.

Scope

• Remove every explicit humanly-cloud-infra reference.
• Remove stale internal Cloud deployment and refactor work orders from Community.
• Document the two-repository ownership boundary in the README.
• Preserve and strengthen Community CI enforcement against official deployment workflows.

Acceptance criteria

• rg humanly-cloud-infra returns no matches in tracked Community files.
• README identifies private humanly-cloud as the managed product and deployment owner.
• No official managed deployment workflow exists under .github/workflows/.
• The Community boundary audit rejects managed deployment paths and deploy workflows.
• Diff checks and the boundary audit pass.

Out of scope

• Changing the frozen writehumanly.net VM.
• Removing generic Community self-hosting assets.
• Product feature or edition-code changes.

File pointers

• README.md
• .github/workflows/ci.yml
• scripts/ci/community-boundary.mjs
• retired docs/EDITIONS_*.md files

References

• Private Cloud migration issue: Humanly-Lab/humanly-cloud#1072