Skip to content

Decide public command name before package distribution #187

@shiny-code-bot

Description

@shiny-code-bot

Objective

Track the public distribution decision for whether the code binary remains the canonical command or gets a unique public command such as ecode while preserving compatibility aliases.

Current Status

State: Waiting
Next action: Revisit before intentional public npm/Homebrew/package-manager distribution, not during current internal dogfood cleanup.
Blocked by: Public distribution strategy decision.
Last verified: 2026-05-28.

Finish Line

Public distribution has an explicit �[?2004h�[?1007h�[?1004h�[?1049h vs unique command decision

Acceptance Criteria

  • Compare keeping code vs introducing a unique command such as ecode.
  • Decide alias/symlink behavior for local dogfood, direct releases, npm, and Homebrew if re-enabled.
  • Document migration and collision handling.
  • Keep this decision separate from prompt/docs taxonomy cleanup.

Relationships

Sub-issue of #179.
Related to #121 and #122 package-manager distribution blockers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:waitingPlan is waiting on non-issue evidence or decision

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions