Slash commands: presence, docs, i18n, and contributor-facing help

[Hmbown]

Scope

Make slash commands understandable to new users and contributors across first-run, help, command palette, docs, issue templates, and localization.

Command families in scope:

• Front doors: /help, /home, /links, /feedback, /init
• Appearance and language: /theme, /translate, /verbose, i18n command descriptions
• Account/session affordances: /logout, /statusline, API balance/currency displays where exposed
• Contributor docs: README, docs/KEYBINDINGS.md, docs/CONFIGURATION.md, issue templates, and release checklist references

Acceptance

• /help, command palette, docs, and localized descriptions agree for every registered command.
• User-facing commands include examples when arguments are non-obvious.
• Website/community/contributor entry points explain where to file bugs, propose command changes, and attach useful diagnostics.
• Release gate checks README/changelog/contributor credit status for command-surface changes.

Related: #1708, #790, #598, #1551, #1735, #1607, #936, #1562.

[Hmbown]

Implementation notes for the next agent:

Primary files to inspect:

• crates/tui/src/localization.rs, crates/tui/src/tui/views/help.rs, crates/tui/src/tui/command_palette.rs, onboarding/init flows, README, docs, and GitHub issue templates.
• .github/ISSUE_TEMPLATE/*, .github/PULL_REQUEST_TEMPLATE.md, docs/KEYBINDINGS.md, docs/CONFIGURATION.md, docs/RELEASE_CHECKLIST.md.

Suggested command-doc consistency check:

struct PublicCommandDoc {
    command: String,
    usage: String,
    description: String,
    examples: Vec<String>,
    localized: bool,
    docs_paths: Vec<PathBuf>,
}

fn public_docs_for(info: &CommandInfo) -> PublicCommandDoc {
    PublicCommandDoc {
        command: info.name.to_string(),
        usage: info.usage.to_string(),
        description: info.description_for(Locale::English).to_string(),
        examples: examples_for(info.name),
        localized: all_supported_locales_have(info.description_id),
        docs_paths: find_docs_mentions(info.name),
    }
}

for info in COMMANDS {
    let doc = public_docs_for(info);
    assert_help_palette_and_docs_agree(&doc);
    if info.requires_argument() {
        assert_has_example_or_clear_usage(&doc);
    }
}

Contributor-facing notes:

• The issue template should ask for exact command, arguments with secrets redacted, expected behavior, actual behavior, terminal/OS, and relevant deepseek doctor or /status output.
• Do not ask users for private API keys or full transcripts by default. Ask for a minimal redacted reproduction.
• README and docs should make command discovery obvious: /help, Ctrl-K, command palette, and docs link.
• Release checklist should continue requiring README, changelog, GitHub release notes, and contributor credit status when command behavior changes.

Presence bar:
Make the first-run and help path feel composed: the user should understand where commands live, what is safe to run, and how to report a broken command without reading source.