T-YFUN-ink-tui-over-the-same-ops
State: closed/done · Impact: medium · Complexity: medium
Build an Ink-based TUI over the same op surface the dashboard and CLI already use. Its first screens are simple-dispatch’s Ink TUI, folded in as design input (see sdlc-0.8-plan.md, “Folded in: simple-dispatch” and simple-dispatch-plan.html’s “Dispatch TUI” phase): a PR table and a Tasks page, described below.
Approach
Section titled “Approach”- Build the PR page first: shared list/table components (sort, filter, multi-select, status line), columns for verdict/behind-ahead/checks/new comments/author/age/session-present, and actions on selected/filtered/all PRs (update via pr-update, respond by routing to the live session or opening a new one, open a session).
- Build the Tasks page: from
task next/task inflight— status, impact, complexity, lease phase, open PR, rank — with the ability to select tasks to run or run the whole orchestration routine. - Extend to the rest of the dashboard’s new views (mirroring them where it makes sense) against the existing op registry, no new backend logic.
- Wire it as
sdlc tui(or similar).
| Area | Note |
|---|---|
solutions/ontological/cli/ | New tui entry |
solutions/ontological/lib/services/ | Op registry it consumes |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: sdlc tui (or its chosen entry point) launches and renders at least the roadmap/task view against a live project.
- AC-2: It uses only existing ops, no duplicated business logic.
Out of scope
Section titled “Out of scope”- none
Dependencies
Section titled “Dependencies”- none