Skip to content

Register the edgecommons CLI as a tool; add docsPath for monorepo entries - #9

Merged
mbreissi merged 1 commit into
mainfrom
feat/cli-tool-entry
Jul 23, 2026
Merged

Register the edgecommons CLI as a tool; add docsPath for monorepo entries#9
mbreissi merged 1 commit into
mainfrom
feat/cli-tool-entry

Conversation

@mbreissi

Copy link
Copy Markdown
Contributor

The CLI is the tool people reach for first, and it was not in the catalog — registry list --category tool did not list the binary you are typing, and the docs site had no tool entry for it.

  • docsPath (optional): where an entry's docs/ lives inside its repo, for entries shipping from a monorepo. The CLI is at cli/docs inside the library repo, whose root docs/ holds the library's own internal design docs — syncing that would pull entirely the wrong thing.
  • The edgecommons entry: category: tool, docsPath: cli/docs. platforms deliberately omitted — it means deployment targets, and the CLI is not deployed to anything.

Verified: components.json validates (0 errors).

⚠️ Merge this before edgecommons#65 (which adds cli/docs and rewrites the Getting Started page). Registry-first is safe — the entry exists and its docs are skipped with a warning until they land. The reverse order would break the docs-site build, because the rewritten page links into /tools/edgecommons/.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LsX7cWVGLszurNYMVwMJGo

…ries

The CLI is the tool people reach for first and it was not in the
catalog: `registry list --category tool` did not show the binary you are
typing, and the docs site had no tool entry for it.

- `docsPath` (optional): where an entry's docs/ lives inside its repo,
  for entries shipping from a monorepo. The CLI is at `cli/docs` inside
  the library repo, whose root docs/ holds the library's own internal
  design docs - syncing that would pull entirely the wrong thing.
- The `edgecommons` entry itself: category `tool`, docsPath `cli/docs`.
  `platforms` is deliberately OMITTED - it means deployment targets, and
  the CLI is not deployed to anything.

Verified: components.json validates (0 errors).

Ordering note: merge this BEFORE the edgecommons PR that adds cli/docs
and rewrites the Getting Started page. Registry-first is safe (the entry
exists, its docs are skipped with a warning until they land); the
reverse would break the docs-site build on the new page's links.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsX7cWVGLszurNYMVwMJGo
@mbreissi
mbreissi merged commit a6a9eaa into main Jul 23, 2026
1 check passed
@mbreissi
mbreissi deleted the feat/cli-tool-entry branch July 23, 2026 15:50
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.

1 participant