Skip to content

docs(ui): core keeps a one-line pointer; the contributor page lives in 5dive-ai/5dive-ui (DIVE-4784) - #1079

Open
5dive-bot wants to merge 1 commit into
mainfrom
dive-4784-page-to-5dive-ui
Open

5dive-bot wants to merge 1 commit into
mainfrom
dive-4784-page-to-5dive-ui

Conversation

@5dive-bot

Copy link
Copy Markdown
Collaborator

Core keeps the pointer; the page moves to the repo the code is in

Main ruled on 2026-09-21 that the UI contributor page lands in the extracted 5dive-ai/5dive-ui and
that core's README and CONTRIBUTING keep a one-line pointer, not the page. PR #1071 merged the
whole page into core instead, so core has been carrying a map that sends a first-time contributor at
src/cmd_ui.sh — the copy that goes away when core releases the ui verb name, and the copy any
PR against it is orphaned by.

Companion PR, which carries the page: 5dive-ai/5dive-ui#8.

What changed

  • docs/contribute-ui.md → the pointer. It names ui/bin/ui as the file to work in, links
    5dive-ai/5dive-ui's CONTRIBUTING.md, and says why a PR against core's copy is orphaned. Kept as
    a forwarding stub rather than deleted, so an external link to this path does not 404.
  • README.md:439, README.md:583, CONTRIBUTING.md:21 — the three in-repo links now go to
    5dive-ai/5dive-ui's CONTRIBUTING.md.
  • docs/ui-today.png deleted: its only consumer is the page, which moved, and the identical blob
    (a449c8ce94aad0ce55f7188a9c655dc6fa914200) is added in the companion PR. grep -rn 'contribute-ui|ui-today' over the tree finds no other reference — no test, no workflow, no doc.

What this PR does not do

It does not touch src/cmd_ui.sh, which is still live: src/main.sh:1254 dispatches ui)
cmd_ui and ui is still in FIVEDIVE_BUILTIN_VERBS, so every installed box runs core's copy and
5dive plugin add 5dive-ai/5dive-ui is still refused by the verb-collision check. Retiring it behind
the moved-verb shim is DIVE-4783. Until that lands, both copies are live and the docs say which one
to work in.

Docs only — no src/ change, so no bundle rebuild is involved.

DIVE-4784

🤖 Generated with Claude Code

…n 5dive-ai/5dive-ui (DIVE-4784)

Main ruled on 2026-09-21 that the UI contributor page lands in the extracted
5dive-ai/5dive-ui repo and that core's README and CONTRIBUTING keep a pointer,
not the page. PR #1071 merged the whole page into core instead, so core carried
a map that sends a first-time contributor at src/cmd_ui.sh — the copy that goes
away when core releases the `ui` verb name.

- docs/contribute-ui.md is reduced to the pointer, naming ui/bin/ui as the file
  to work in and saying why a PR against core's copy is orphaned.
- The two README links and the one CONTRIBUTING link now go to
  5dive-ai/5dive-ui's CONTRIBUTING.md, which carries the page.
- docs/ui-today.png moves with the page (identical blob is added there).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@5dive-bot

Copy link
Copy Markdown
Collaborator Author

Merge order: 5dive-ai/5dive-ui#8 first, then this one. The three links this PR repoints (README ×2, CONTRIBUTING ×1) target 5dive-ai/5dive-ui/blob/main/CONTRIBUTING.md, which exists only once #8 is on that repo's main. Merged the other way round, core's public README carries three dead links until #8 lands. (DIVE-4784)

5dive-push Bot pushed a commit that referenced this pull request Sep 21, 2026
…r page (DIVE-4783)

main's #1077 repointed docs/contribute-ui.md's issue links while this branch was
in flight; DIVE-4784's #1079 replaces the same page with a transitional pointer
that says core still ships src/cmd_ui.sh — a sentence this branch falsifies by
deleting that file. The merge keeps this branch's pointer, which is the text that
is true once the verb is released.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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