Plan: show Every Code Lab distribution identity

[shiny-code-bot]

Objective

Make the runtime clearly show when a user is running the cbusillo/code build versus upstream just-every/code, without rebranding the product away from Every Code. The desired display tag for this build is Every Code Lab.

Think of Every Code Lab like a beta-style product tag: the product remains Every Code, while the Lab tag tells users they are on the cbusillo/code build/channel. This should reduce confusion in support, screenshots, bug reports, and dogfood sessions without creating a separate identity system.

Finish Line

Users running this repository's build see Every Code Lab in appropriate runtime identity surfaces, alongside enough context to understand it is the cbusillo/code distribution of Every Code. Existing Every Code product naming remains intact where prose refers to the broader product or upstream lineage.

Current Status

State: Implemented locally on branch fix/lab-updater-identity; awaiting review/PR.
Next action: Review the branch diff, then open a PR when ready.
Blocked by: None
Waiting for: Review/PR creation.
Last verified: 2026-05-30 with focused updater tests, git diff --check on touched files, and ./build-fast.sh.

Scope

• In: Treat Every Code Lab as a runtime/build tag appended to the product name, similar to a beta or lab channel label.
• In: Update concrete runtime-facing surfaces where users need to distinguish cbusillo/code from just-every/code: TUI primary header/title, doctor, update diagnostics, and issue-template diagnostics.
• In: Keep code --version parseable in the existing version format; put the Lab tag in diagnostics rather than changing semver output.
• In: Keep docs terminology clear in the naming ledger: Every Code remains the product/upstream lineage, Every Code Lab is this build/channel tag.
• In: Update intentional TUI snapshots or their normalization only after reviewing visual impact.
• Out: A broad distribution identity architecture.
• Out: Renaming crates, packages, repo paths, config directories, environment variable prefixes, or the default code command.
• Out: Rewriting all docs prose just because it says Every Code; only change places where the Lab tag matters.
• Out: A full product rebrand.

Acceptance Criteria

• The TUI makes Every Code Lab visible in the primary title/header area for this build without breaking narrow terminal layout.
• code --version remains parseable as the existing version format.
• doctor, update-check, and update diagnostics distinguish this build as Every Code Lab / cbusillo/code where useful.
• Support/bug-report guidance captures both version and Lab build identity.
• The naming ledger documents the distinction between Every Code, Every Code Lab, upstream just-every/code, and this repository cbusillo/code.
• The assistant remains the Every Code agent with short display name Code; prompt identity is changed only if needed to clarify runtime Lab context.
• Snapshot changes are limited to intentional identity text changes, or snapshot normalization is updated only if it still verifies the UI surface meaningfully.
• The required repository gate passes: ./build-fast.sh.

Relationships

• Related to the renamed-binary updater plan because both should eventually share command/runtime identity helpers where practical.

Validation

• Search for runtime-facing hard-coded Every Code strings and classify each as product lineage, runtime distribution, or docs prose before editing.
• Verify TUI header/title layout at narrow and normal snapshot widths, using focused VT100 snapshot tests if practical.
• Verify code --version stays in the existing parseable version format.
• Verify doctor, update-check, and update output include the distribution identity where intended.
• Run the required repository gate from the root: ./build-fast.sh.

Decisions

• Use Every Code Lab as the cbusillo/code runtime/build tag.
• This is not a rebrand: Every Code remains the product name and upstream lineage term.
• Keep the short agent display name as Code.
• Keep code --version semver/version-format compatible; show the Lab tag in diagnostics instead.
• Avoid a broad identity architecture; use a tiny constant/helper only where it reduces duplication without creating dependency churn.
• Keep broad docs prose unchanged unless the text is specifically about runtime build identity, support diagnostics, or naming policy.

Open Questions

• None currently.

[shiny-code-bot]

Completed in the v0.6.109 release.

Evidence:

• Implementation PR: fix(update): preserve renamed binary identity #241
• Release metadata PR: release: prepare v0.6.109 metadata #243
• Snapshot follow-ups: test(tui): normalize Lab header snapshots #245 and test(tui): stabilize Lab snapshot normalization #247
• Release workflow: https://github.com/cbusillo/code/actions/runs/26697046333
• Published release: https://github.com/cbusillo/code/releases/tag/v0.6.109

Outcome:

• The cbusillo/code build now identifies itself as Every Code Lab in user-facing runtime surfaces where distribution identity matters.
• The product naming ledger documents Every Code Lab as a beta-style build/distribution tag rather than a rebrand.
• Doctor/update/update-check output includes the display identity and repository context so users can tell whether they are on just-every/code or cbusillo/code.