refactor: rebrand Gator TUI to Term / NemoClaw #130

Problem Statement

The TUI is currently branded as "Gator" throughout the codebase — CLI subcommand, UI title bar, docs, and agent skills. It needs to be rebranded: the CLI subcommand becomes nemoclaw term, the title shown in the TUI changes from "Gator" to "NemoClaw", and all other code/doc references change from "Gator" to "Term" or "TUI" as appropriate. This is a naming cleanup to move to a generic, consistent brand.

Technical Context

The TUI is implemented in the navigator-tui crate and launched via a clap-derived Commands::Gator enum variant in navigator-cli. The variant name directly determines the subcommand string (nemoclaw gator). The visible brand text "Gator" is rendered in a single Span::styled call in ui/mod.rs. Beyond the source code, the name is embedded in architecture docs, mise task files, and agent skill files. The crate name itself (navigator-tui) does not contain "gator" and needs no change.

Affected Components

Technical Investigation

Architecture Overview

The TUI is a ratatui-based terminal application in the navigator-tui crate. It is launched as a subcommand of the nemoclaw binary. The CLI uses clap's derive macro — the Commands enum has a Gator variant which clap auto-lowercases to the gator subcommand. The main function dispatches Commands::Gator to call navigator_tui::run(). Inside the TUI, the brand is rendered in the title bar via a single Span::styled(" Gator", ...) call.

Code References

Current Behavior

• nemoclaw gator launches the TUI. The clap variant Commands::Gator is lowercased automatically.
• The TUI title bar renders " Gator" as a styled span in the top-left corner.
• mise run gator and mise run gator:dev are convenience tasks defined in tasks/gator.toml.
• Architecture docs and agent skills refer to the TUI as "Gator" throughout.

What Would Need to Change

Source code (3 files, 6 changes):

• main.rs: Rename enum variant Gator → Term, update doc comment and match arm
• lib.rs: Update doc comment from "Gator" to "NemoClaw"
• ui/mod.rs: Change rendered string from " Gator" to " NemoClaw"
• Cargo.toml: Update package description

Mise tasks (1 file rename + content changes):

• Rename tasks/gator.toml → tasks/term.toml
• Update task names [gator] → [term], [gator:dev] → [term:dev]
• Update run commands from nemoclaw gator to nemoclaw term

Architecture docs (1 file rename + content changes in 3 files):

• Rename architecture/gator.md → architecture/tui.md
• Update ~25 "Gator" references in the renamed file
• Update 2 references in system-architecture.md
• Update 3 references in sandbox-connect.md
• Note: gator.md:151 references plans/gator-tui.md which does not exist (dead link — remove or fix)

Agent skill files (content changes in 3 files):

• .agents/skills/tui-development/SKILL.md: ~14 line updates
• .agents/skills/nemoclaw-cli/cli-reference.md: 3 line updates
• .agents/skills/nemoclaw-cli/SKILL.md: 1 line update

Alternative Approaches Considered

The renaming rules are straightforward, but there are a few judgment calls:

• Architecture doc filename: architecture/tui.md (generic) vs architecture/term.md (matches CLI subcommand). Recommend tui.md since the doc describes the TUI component, not the CLI subcommand.
• Skill trigger keywords: Replace gator with both term and tui to cover both terms users might type.

Patterns to Follow

This is a find-and-replace refactor. The naming convention to apply:

• CLI subcommand: term (lowercase, matches clap variant convention)
• Rendered UI text: NemoClaw (product brand)
• Prose/docs: "the TUI" or "NemoClaw TUI" (never "Term" as a proper noun in prose)
• Task/file names: term (lowercase, matches CLI subcommand)

Proposed Approach

Rename the clap enum variant from Gator to Term to change the CLI subcommand, update the single rendered title string to "NemoClaw", then sweep through docs, mise tasks, and agent skills replacing "Gator" references with "Term", "TUI", or "NemoClaw" as context dictates. File renames for tasks/gator.toml and architecture/gator.md to match. This is a mechanical refactor with no behavioral changes.

Scope Assessment

• Complexity: Low
• Confidence: High — clear path, purely mechanical renaming
• Estimated files to change: 10 (+ 2 file renames)
• Issue type: refactor

Risks & Open Questions

• Dead link: architecture/gator.md:151 references plans/gator-tui.md which doesn't exist. Decide whether to remove the link or create the plan doc.
• External references: Any external docs, wikis, or READMEs outside the repo that reference nemoclaw gator will break. Verify no external tooling depends on the gator subcommand name.
• Git branch: There's an existing branch feat(gator) in .git/config — this is historical and doesn't need changing.

Test Considerations

• No existing tests reference "gator" directly, so no test changes needed
• After the rename, verify cargo build succeeds (the enum variant rename is the only code change that could cause a compile error)
• Verify nemoclaw term launches the TUI and the title bar shows "NemoClaw"
• Verify mise run term and mise run term:dev work

Created by spike investigation. Use build-from-issue to plan and implement.