Contributing

Work from the public repository

Clone tokendance-code, inspect the current branch instructions, and make changes against the Rust workspace. The website lives separately in tokendance-code-web.

Verify a source change

The full test suite executes PowerShell. Windows uses powershell.exe; Linux and macOS require PowerShell 7’s pwsh on PATH. The build itself and simulated CLI sessions do not require PowerShell.

The active Rust checks are:

cargo fmt --all -- --check
cargo test --workspace

pnpm verify currently runs those Cargo checks. Wrapper work also has repository helpers such as pnpm release:rust:plan:check and pnpm smoke:rust-wrapper; inspect their current definitions before use. Older TypeScript packaging commands are not a substitute for the Rust release checks.

Keep user-facing claims precise

A new adapter or SDK method needs a separate check at the CLI or consumer entry point that exposes it. Document the version, supported invocation, expected output, and remaining limits. Update English and Chinese guides together when a public contract changes.

Propose a release

Source merges and passing checks do not publish packages. Follow the current release-readiness guide and verify registry availability before documenting an npm install command.