Do not open a public issue for security-sensitive bugs.

Use GitHub private vulnerability reporting for this repository if it is enabled. If it is not enabled yet, open a private security advisory draft or contact the maintainer through a private channel before sharing details publicly.

When you report an issue, include:

• whether the issue affects create-bight, the docs deployment, or both
• the impact
• reproduction steps
• any package names or generated output involved

This repository covers the create-bight CLI and the public docs site. Runtime issues in @bight-ts/core or the official extras packages belong in their respective repositories unless the bug clearly originates in scaffolding or docs tooling.