Document the Dispatch plugin in the in-app docs (docs audit) - #960
Merged
Conversation
The official plugin (#952) shipped with a README section and nothing else — no in-app docs section and no ambient tip, so the only place a user learns it exists is the GitHub README. - New docs-pane section "Plugin" covering trust (unsigned/unsandboxed, no executable components, how to verify), the two-step marketplace + install flow on Claude Code and Codex, the eleven skills and what each fires on, and update mechanics (Codex has no update subcommand). - Ambient tip pointing at plugin#plugin-install, since 0.34.1 (the plugin landed after the v0.34.0 release commit). - README's plugin blurb named 8 skills; the tree has 11 — personas, personalities and ui-validation were missing. Same fix in plugins/dispatch/README.md's intro paragraph. - README's "user-facing documentation" list was missing browser feedback, service resources and the new plugin section, and said "jobs" where the section is templates and jobs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nightly docs audit. Slice: the deep-dive area carried in
next_focus— the official Dispatch plugin (#952), which shipped with a README section and no in-app docs coverage at all.The diff since the last audited SHA (
037f4601..HEAD) was three PRs, all of which were either the previous audit's own docs work or dead-code deletion, so nothing was diff-driven this run.What changed
docs-sections/plugin.tsx) — trust first (unsigned/unsandboxed, ships no executable components,claude plugin detailsas the verification), then the two-step marketplace + install flow on both Claude Code and Codex, the eleven skills and the situation each fires on, and update mechanics (auto-update off by default on Claude Code; Codex has no update subcommand so upgrading means re-runningcodex plugin add).dispatch-plugin→plugin#plugin-install,since: 0.34.1. The plugin commit (fe8a46ba) is not an ancestor ofRelease v0.34.0; the nearest release after it is v0.34.1.plugins/dispatch/skills/has 11 —personas,personalitiesandui-validationwere missing. Same fix inplugins/dispatch/README.md's intro paragraph (its own table below was already correct).Validation
pnpm run format:write,pnpm run check,apps/webtips unit tests, and a Playwright render of/settings/help/pluginon an isolated dev stack (nav entry present, section renders, 0 console errors).Deferred to next run
next_focus→ audit docs-pane Automations (templates & jobs) againstapps/web/src/components/app/automations-*andapps/server/src/jobs/— it has three open backlog items (defaultArgs has no UI, the vestigial "Show in command palette" toggle,JobNotifyConfig) and hasn't been deep-dived.descriptionfield (both.claude-plugin/plugin.jsonand.codex-plugin/plugin.json, plus.claude-plugin/marketplace.json) still names the same 8 skills. Left alone here because those strings are published marketplace metadata and changing them is a version-bump call, not a docs fix.