Establish an independent open-source identity for HotMem

[valiantone]

Context

The merged documentation sanitization removed internal EMOS, YC, OKF, and process-specific material. A follow-up audit found that HotMem still has institutional and operational ties to the KnowGuardAI ecosystem.

Scope

Define and implement an independent open-source identity for HotMem:

• Confirm the independent GitHub organization/repository identity.
• Choose the public documentation domain.
• Choose the container/OCI registry and image name.
• Define project-owned security and conduct contacts.
• Confirm the copyright holder and licensing presentation.
• Replace or remove KnowGuard-specific branding, logos, palette guidance, and ecosystem language.
• Update repository, docs, package, Docker, workflow, badge, and adapter metadata consistently.
• Preserve the sanitized-content boundary: no EMOS internals, private processes, or proprietary ecosystem references.

Acceptance criteria

• All public URLs, badges, package metadata, image references, contacts, and branding point to the approved independent identity.
• Repository-wide scans find no unintended KnowGuardAI, EMOS, or internal-process references.
• A clean documentation build and the full test suite pass.
• GitHub Actions passes on the migration PR and the resulting public docs/image endpoints are verified.
• Any intentional attribution or historical references are explicitly documented and approved.

Related: #82