v0.1.6

release: fix workflow — separate build and publish jobs, include inst…

v0.1.5

feat: improve install UX with auto PATH and Windows support

- install.sh: auto-add ~/.local/bin to shell PATH
- install.ps1: native Windows PowerShell installer
- README: rewrite Global install section
- CLI --help: simplify output

v0.1.4

test: harden import and routing coverage

v0.1.3

Clarify docs, sanitize screenshots, and add td alias install support

Keep the CLI command surface English-only while splitting the documentation into English and Chinese entry points. Sanitize the demo screenshots and make installation create a td shortcut so the shorter shell trigger works by default.

Constraint: Open-source docs and assets must avoid leaking real account identifiers or tokens.
Constraint: The user wants English CLI commands but a bilingual documentation experience.
Rejected: Keep Chinese command aliases in the parser | unnecessary once docs are bilingual and commands are confirmed to stay English-only.
Rejected: Require users to create td manually after install | extra friction for the preferred shell trigger.
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep screenshots synthetic/sanitized and keep README.md as the English default with README.zh-CN.md as an explicit secondary document.
Tested: gofmt -w ./cmd ./internal; go build ./cmd/token-dance; INSTALL_DIR=/tmp/token-dance-bin VERSION=v0.1.2 bash scripts/install.sh; /tmp/token-dance-bin/td help
Not-tested: Windows shell alias behavior beyond release asset generation

v0.1.2

Stabilize release uploads after adding installer assets

Adjust the release workflow so matrix jobs always upload their own binaries but only one job publishes the shared install script. This avoids asset deletion races while keeping the installer available from tagged releases.

Constraint: GitHub release automation must stay tag-driven and succeed across the build matrix.
Rejected: Keep uploading install.sh from every matrix leg | causes asset deletion races in action-gh-release.
Rejected: Remove install.sh from releases entirely | would weaken the global install story the user asked for.
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Shared release assets must be uploaded by a single job only; matrix jobs should own only their unique artifacts.
Tested: go build -o /tmp/token-dance-check ./cmd/token-dance; /tmp/token-dance-check 帮助; go run ./cmd/token-dance 列表 --json; go run ./cmd/token-dance 用量 --json; INSTALL_DIR=/tmp/token-dance-bin VERSION=v0.1.0 bash scripts/install.sh; inspected failed v0.1.1 workflow logs to confirm root cause
Not-tested: v0.1.2 release workflow before tag push

v0.1.1

Improve operator ergonomics with Chinese aliases and install flows

Add Chinese command aliases for the primary agent and human flows, document global installation paths, and ship a release install script plus README screenshots so the project is easier to adopt from GitHub.

Constraint: The CLI must remain agent-first while also being usable by Chinese-speaking operators from the terminal.
Rejected: Gate Chinese support behind a separate locale mode | adds friction to common command paths.
Rejected: Delay installation support until a later release | user explicitly asked for global install in the first public flow.
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep aliases additive only; do not break the stable English commands or --json contract when extending command parsing.
Tested: go build -o /tmp/token-dance-check ./cmd/token-dance; /tmp/token-dance-check 帮助; go run ./cmd/token-dance 列表 --json; go run ./cmd/token-dance 用量 --json; go run ./cmd/token-dance 自动切换 --json; INSTALL_DIR=/tmp/token-dance-bin VERSION=v0.1.0 bash scripts/install.sh
Not-tested: release workflow after adding install.sh asset on a new tag

v0.1.0

Establish an agent-first Codex account switcher MVP

Build token-dance as a small Go CLI with JSON-safe command output, import/switch/usage flows, and a minimal near-exhaustion auto-switch rule. Add a tag-driven GitHub release workflow so the first version can ship from nova-infra immediately.

Constraint: First version must be agent-first, human-usable, and published under nova-infra.
Rejected: Continue with the initial TypeScript scaffold | user preferred a Go CLI prototype and single-binary release path.
Rejected: Add watcher/TUI in v1 | unnecessary complexity before validating command and release flows.
Confidence: medium
Scope-risk: moderate
Reversibility: clean
Directive: Keep core flows non-interactive and preserve --json output stability before adding any TUI layer.
Tested: go build ./cmd/token-dance; go run ./cmd/token-dance help; go run ./cmd/token-dance import-current --json; go run ./cmd/token-dance list --json; go run ./cmd/token-dance usage --json; go run ./cmd/token-dance autoswitch --json
Not-tested: multi-account switching with imported snapshots; GitHub Actions release execution before first tag push