Skip to content

[codex] Align neo TUI docs with runtime behavior#1

Closed
IYENTeam wants to merge 1 commit into
mainfrom
codex/align-neo-tui-docs-runtime
Closed

[codex] Align neo TUI docs with runtime behavior#1
IYENTeam wants to merge 1 commit into
mainfrom
codex/align-neo-tui-docs-runtime

Conversation

@IYENTeam
Copy link
Copy Markdown

What changed

  • Aligned packages/neo-tui README/AGENTS/screenshot docs with the current Rust runtime instead of the older scaffold plan.
  • Added actual docs/theme-spec.md and docs/keymap-spec.md based on the current Rust parsers and bundled assets.
  • Cleaned stale Rust/TS comments and test names that still referenced old T-phase plans, stubs, or missing files.
  • Fixed senpi --neo -- ... parsing so flags after the sentinel reach senpi-neo-tui as documented.
  • Added a regression test for the sentinel parser path and a changelog entry.

Code vs docs decisions

  • Missing theme/keymap spec docs: added docs, because the parser/runtime already exist.
  • Missing qa.sh, qa-scenarios.json, snapshot fixtures, copied dist assets: corrected docs, because current scripts/assets are the source of truth.
  • ColorSupport detection and leader-key sequences: documented current behavior; did not implement new features.
  • Ctrl+D/history behavior: corrected docs to match runtime semantics.
  • Screenshot pipeline mismatch: corrected docs to match the demo-scene script; did not rewrite capture flow.
  • senpi --neo -- --list-themes runtime failure: fixed code, because docs and splitNeoArgs already defined this supported contract.

Validation

  • cargo fmt --package senpi-neo-tui -- --check
  • cargo test --package senpi-neo-tui
  • cargo clippy --package senpi-neo-tui --all-targets -- -D warnings
  • npx tsx ../../node_modules/vitest/dist/cli.js --run test/suite/regressions/neo-tui-arg-parse.test.ts test/suite/regressions/neo-tui-arg-forwarding.test.ts
  • npm run check
  • npm run build
  • cargo build --release --package senpi-neo-tui --bins
  • Runtime smoke in tmux:
    • direct Rust demo mode rendered
    • faux backend echoed hello faux
    • Node launcher forwarded --list-themes through senpi --neo -- --list-themes

Not tested

  • Full screenshot PNG regeneration. The script syntax validates, but local aha is not installed and running the script would overwrite checked-in PNG artifacts.

The Rust native TUI docs still described earlier scaffold plans, missing spec files, copied assets, and nextest-only workflows. Runtime verification also showed the documented sentinel forwarding path was real in neo-mode but blocked by the Node parser before dispatch. This change updates the documentation and stale code comments to match the current implementation, adds theme/keymap specs based on the actual parsers, and lets `senpi --neo -- ...` pass through to the Rust binary.\n\nConstraint: Keep existing TUI behavior except for unblocking the documented sentinel forwarding path.\nRejected: Implement leader-key dispatch and ColorSupport detection | the current runtime intentionally only parses that metadata/hint, so documenting the actual behavior is lower risk.\nRejected: Make screenshot capture use the faux backend | the current script intentionally captures the demo scene; docs were the stale side.\nConfidence: high\nScope-risk: narrow\nTested: cargo fmt --package senpi-neo-tui -- --check\nTested: cargo test --package senpi-neo-tui\nTested: cargo clippy --package senpi-neo-tui --all-targets -- -D warnings\nTested: npx tsx ../../node_modules/vitest/dist/cli.js --run test/suite/regressions/neo-tui-arg-parse.test.ts test/suite/regressions/neo-tui-arg-forwarding.test.ts\nTested: npm run check\nTested: npm run build\nTested: cargo build --release --package senpi-neo-tui --bins\nTested: tmux runtime smoke for Rust demo, faux backend echo, and Node --neo -- --list-themes\nNot-tested: Full screenshot PNG regeneration because it would overwrite checked-in image artifacts and local aha is not installed
@IYENTeam
Copy link
Copy Markdown
Author

Superseded by upstream split PRs: code-yeongyu#22, code-yeongyu#23, code-yeongyu#24, code-yeongyu#25.

@IYENTeam IYENTeam closed this May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants