Fix nightly and release-smoke metadata that still says T3 Code

[badcuban]

Priority: P1

Why

Nightly/release metadata and smoke fixtures are part of the release surface. They should describe BadCode releases, not T3 Code releases, unless a fixture intentionally tests legacy compatibility.

Evidence

• scripts/resolve-nightly-release.ts:64 emits T3 Code Nightly ....
• scripts/release-smoke.ts:248 asserts a T3 Code Nightly ... value.
• scripts/release-smoke.ts still uses T3-Code-* updater fixture asset names.
• scripts/notify-discord-release.ts release copy still says T3 Code.

Acceptance criteria

• Update nightly names and release-notification copy to BadCode.
• Update release smoke expected values and fixture names.
• Keep explicit legacy fixtures only if they test backwards compatibility, and name them accordingly.
• Run release smoke after changes.

[badcuban]

Fixed in commit f8250e11 and released in v0.0.7: nightly names, Discord release copy, release-smoke fixtures, and updater fixture names now use BadCode. bun run release:smoke passes locally and the release workflow passed. Release: https://github.com/badcuban/badcode/releases/tag/v0.0.7