Prepare website repository for public release

[ClaudiuSchuster]

Summary

• release the source code and technical documentation under the MIT License while keeping the OSS Singularity identity and visual assets explicitly protected
• turn the README into a stronger technical showcase and document clear contribution, security, and production boundaries
• add weekly Dependabot updates for pinned GitHub Actions
• update stale private-repository and JavaScript documentation before the public transition
• remove an unnecessary location reference from the preserved design prototype

Validation

• git diff --check HEAD^ HEAD
• ./scripts/check-repository.sh
• complete Git history and image-metadata audit for credentials, private paths, and account-specific data

Publication boundary

This pull request does not change repository visibility, GitHub protection settings, production hosting, credentials, DNS, or deployed files. After merge, the repository can be made public and its public-only security and branch-protection controls can be enabled against the merged commit.