Originally created by: 5dive-bot
5dive ui becomes a plugin in its own repository, 5dive-ai/5dive-ui:
5dive plugin add 5dive-ai/5dive-ui
5dive ui # exactly as before
The presentation leaves — the page, the three routes, the layout, the styling. The data
stays: DIVE-4779's 5dive board is the versioned document the views render, and it is still a
builtin, because the board is a fact about core's own data model and only core can say what is on
it. A contributor who wants to change a screen now clones one small repo instead of 121k lines of
runtime; a contributor who wants a new field still sends core a one-line additive PR, which is
the trade being made deliberately (docs/board-contract.md argues it).
A verb name in core is a case label in main(), and three enumerations are chained to it:
FIVEDIVE_BUILTIN_VERBS (src/cmd_plugin.sh), read at install time;tests/plugin_verb_dispatch_unit.sh T5, which asserts that string is set-equal to main()'s_plugin_verb_is_builtin, which refuses the install of any plugin declaring a name in thatThat refusal is correct: a plugin verb is only ever reached after the builtin table, so a shadowed
one could never run. A "kind" shim that keeps ui as a builtin printing "this moved, install the
plugin" is itself a builtin — so it would have made 5dive plugin add 5dive-ai/5dive-ui fail
rc=3 on every box for as long as the shim existed. The name is therefore released from both
enumerations together, and the notice lives in main()'s *) arm:
$ 5dive ui
note: 'ui' moved out of the core CLI and is now a plugin.
Install it once, and '5dive ui' works exactly as before:
5dive plugin add 5dive-ai/5dive-ui
error: unknown command: ui # exit 2 — non-zero, not a silent nothing
A box that has installed the plugin never reaches that code (_plugin_dispatch_verb execs first).
Retiring the shim later is deleting one table entry.
Background: community/wiki/a-deprecation-shim-that-keeps-the-verb-name-blocks-the-plugin-that-replaces-it.md.
board is in no cut release (v0.47.0 and v0.47.1 carry no src/cmd_board.sh; the box this
was built on runs 0.47.0 and answers unknown command: board). So the first release that carries
the ui removal is also the first that carries board — a box cannot land in a state where ui is
gone and the document it moved to is absent. This repo is not auto-deploying; it ships on a
deliberate release-cut, so the two ride the same cut by construction.
src/cmd_ui.sh deleted; dropped from build.sh's bundle list and from main()'s case table;ui removed from FIVEDIVE_BUILTIN_VERBS.src/main.sh: _moved_verb_repo / _moved_verb_notice, a one-entry table next to main().tests/ui_views_e2e.sh deleted with the file it drove (the plugin repo's harness grades the viewstests/lib/harness-weights.tsv row with it.tests/board_contract_unit.sh section E now grades the release of the name: both enumerations,--help names the plugin and writescat <<USAGE heredoc, so a backticked verb name in there--help — it did, once, during this build). Mutation armdocs/contribute-ui.md is now a pointer to where the page went; README.md, README.zh-CN.md andCONTRIBUTING.md point at the plugin repo and at the board contract.tests/board_contract_unit.sh — 44 arms, 44 pass, including 5 mutation arms (each reverts onetests/plugin_verb_dispatch_unit.sh — 73 pass, 0 fail (T5, the set-equality arm, is the oneplugins/installed.json + plugins/enabled/ui@5dive-ui (the shape T7 uses, because5dive plugin add is root-gated), driven through the built binary —5dive ui --data dispatched to the plugin and its output was identical to5dive board --json modulo generated_at._plugin_verb_is_builtin ui is now false; board and task still true.5dive plugin add 5dive-ai/5dive-ui itself was not run on a box: it is root-gated and installs from
GitHub, and neither branch is merged. What was proven is the dispatch it resolves to, plus the
removal of the install-time refusal that used to block it.
Pairs with 5dive-ai/5dive-ui#<plugin PR> — merge the plugin side first (readers first, delete
last).
🤖 Generated with Claude Code
Ticket changed by: 5dive-bot