docs: brand The Boss README and document UI routing - #5
Conversation
Assisted-by: Codex:GPT-6 [Git, Node.js, Playwright]
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4df8bf9de9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ### Contributor certification | ||
|
|
||
| For a comprehensive overview of the project architecture, tech stack, conventions, and available commands, see [`CLAUDE.md`](CLAUDE.md). | ||
| The inherited contribution policy requires human contributors to certify their right to contribute under [LICENSE](LICENSE). Human certification uses the conventional trailer: |
There was a problem hiding this comment.
This rewrite limits DCO certification to human contributors and warns agents not to manufacture it, but repository policy requires every commit to be cryptographically signed and DCO-signed off. The reviewed Codex commit demonstrates the regression: git verify-commit bc5b59b8… exits 1, the commit has no gpgsig, and its message has no Signed-off-by trailer. State that all contributors must use the configured-author signing workflow, and recreate this commit with both signatures.
AGENTS.md reference: AGENTS.md:L59-L59
Useful? React with 👍 / 👎.
| ## Pull requests | ||
|
|
||
| ## Setting Up Your Development Environment | ||
| Use a focused branch and Conventional Commit messages. Explain the problem, resulting behavior, scope, and actual verification. Follow [.github/pull_request_template.md](.github/pull_request_template.md) and the repository's `gh-create-pr` workflow. Draft PRs may communicate incomplete work, but do not claim that draft status or a passing automated check proves acceptance. |
There was a problem hiding this comment.
The contributor guidance only requests “Conventional Commit messages,” omitting the repository-specific requirement for a concrete kebab-case scope; the reviewed subject, docs: brand The Boss README and document UI routing, consequently repeats the same violation. Document the required type(specific-kebab-case-scope): … form and recreate this commit with an appropriate scope.
AGENTS.md reference: AGENTS.md:L58-L58
Useful? React with 👍 / 👎.
|
|
||
| The [packaged-helper receipt](../../.agent-team/boss-core/ui-routing-packaged-evidence.json) records a macOS offline materialization and helper run with 40 portable skills, preserving 50 native definitions and ten role ownership records. The [pin/sync receipt](../../.agent-team/boss-core/ui-routing-pin-sync-evidence.json) records synchronization and unchanged anti-shadowing implementation. These are source/payload evidence, not installer or Electron acceptance. | ||
|
|
||
| The [mini delivery record](../../resources/prometheus-skills-mini/docs/research/ui-ux-routing/DELIVERY.md) separates macOS/Linux helper evidence and independent skill-contract review from release gaps. Native Windows execution, live invocation across every supported harness, and a full installed Electron run remain unverified for this adoption. The prior Boss repository lint stopped on bundled creator diagnostics; later pipeline stages were not proved. No rendered product UI changed in the routing implementation, so its receipt has no product screenshot acceptance claim. |
There was a problem hiding this comment.
In a fresh or non-recursive clone, this relative link resolves below an unpopulated submodule: the superproject stores resources/prometheus-skills-mini only as a mode-160000 gitlink, and git cat-file -e bc5b59b8:resources/prometheus-skills-mini/docs/research/ui-ux-routing/DELIVERY.md fails. Because scripts/check-doc-links.ts validates links with fs.existsSync, the required pnpm docs:check now reports this new link as broken unless contributors separately initialize the submodule. Link directly to the delivery record in the submodule repository at its pinned revision, or use a tracked superproject copy.
AGENTS.md reference: AGENTS.md:L71-L71
Useful? React with 👍 / 👎.
1 participant
What this PR does
Before this PR: The README presented Cherry Studio branding and upstream product links, and there was no guide to the merged UI/UX catalog and team adoption.
After this PR: The README uses The Boss's tracked
build/logo.png, product links, capabilities and attribution. A new UI/UX guide explains the 97 packaged mini skills, 40 portable UI entries, existing team roles, Node helpers and acceptance limits. Contributor/design docs and the generated documentation index identify The Boss. The release guide's stale source reference now points toIntegrationPage.tsx.Fixes: None. Documentation follow-up to #4.
Why we need it and why it was done in this way
The following tradeoffs were made: Keep upstream attribution, license obligations and technical identifiers while correcting product branding. Describe current source separately from previously published 2.2.2 installers.
The following alternatives were considered: A blanket Cherry identifier rename would change compatibility contracts and exceeds documentation scope. A recreated logo would discard the official asset.
Links to places where the discussion took place: #4. Companion documentation PRs: Full pack, mini, The Boss.
Breaking changes
None. No runtime, dependency, submodule or packaged skill changes.
Special notes for your reviewer
Local results:
pnpm docs:index,pnpm docs:check-structure,pnpm docs:check-frontmatterandpnpm docs:check-indexpassed.pnpm docs:checkremains blocked by existing bundled-reference issues: three Vercel relative links in.agents/skills/vercel-react-best-practices/AGENTS.md, plus a Swift inline-code example misread as a link. Those payloads and the checker are unchanged; aggregate success is not claimed.Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
main/gh-pr-review,gh pr diff, or GitHub UI) before requesting review from othersRelease note