Reduce local package/CLI identity conflicts with upstream T3 Code

[badcuban]

Priority: P3 (local-conflict cleanup; not a release blocker)

Current direction

Do not do a sweeping package or CLI rename just for branding. BadCode is a personal local tool for now.

This issue is only about reducing practical conflicts or confusion when BadCode and upstream T3 Code are both installed or run on the same machine.

Narrow scope

• Identify places where the t3 binary, package names, repository metadata, logs, or scripts can conflict with upstream T3 Code in daily local use.
• Decide whether to keep t3 as a compatibility command, add a badcode alias, or document the current behavior.
• Update repository metadata only where it is cheap and low-risk.
• Preserve compatibility where renaming would create avoidable churn.

Acceptance criteria

• List the actual local collision points with upstream T3 Code.
• Decide whether a badcode CLI alias is useful while keeping t3 compatibility.
• Update obviously incorrect repo metadata where it does not affect runtime behavior.
• Verify dev, desktop, and release scripts after any rename or alias work.

[badcuban]

Phase 1 shipped in main and nightly v0.0.18-nightly.20260601.47. Completed the practical local CLI/package identity slice: added the badcode CLI alias while retaining t3 compatibility, updated user-facing local runtime names where low-risk, and verified dev/desktop/release gates. Deeper package-scope renames remain intentionally deferred until the provider/runtime surface is narrower.