Remove upstream identity from desktop release artifact metadata

[badcuban]

Priority: P0

Why

Release artifacts should not carry upstream identity unless deliberately preserved as compatibility metadata. The current desktop artifact metadata is partially BadCode and partially T3 Code.

Evidence

• scripts/build-desktop-artifact.ts:573 already uses BadCode app ID metadata.
• scripts/build-desktop-artifact.ts:575 already emits BadCode-${version}-${arch}.${ext} artifact names.
• scripts/build-desktop-artifact.ts:784 still writes staged package metadata with name: "t3code".
• scripts/build-desktop-artifact.ts:787 still uses t3codeCommitHash.
• scripts/build-desktop-artifact.ts:790 still sets author: "T3 Tools".

Acceptance criteria

• Replace upstream package metadata where it is user/release visible.
• Rename internal metadata keys if they are not compatibility-sensitive.
• Keep explicit fork attribution separately from product artifact identity.
• Update tests and release smoke fixtures to match BadCode metadata.

[badcuban]

Diagnostics follow-up from May 26, 2026:

The active packaged app is running from C:\Users\Will\AppData\Local\Programs\t3code\BadCode (Alpha).exe, and server stack traces in Diagnostics also resolve through C:\Users\Will\AppData\Local\Programs\t3code\resources\app.asar\....

That makes this issue user-visible beyond package metadata: the Windows install directory still carries the upstream t3code identity even though the product name is BadCode.

[badcuban]

Fixed in commit f8250e11 and released in v0.0.7: staged desktop package metadata now uses BadCode identity (name: badcode, author: BadCode, badcodeCommitHash), and tests/release smoke were updated for the BadCode metadata surface. Release: https://github.com/badcuban/badcode/releases/tag/v0.0.7