Skip to content

fix(workbench): route catalog review fixes from #211 (usage arity, empty server surfaces, stale-repair e2e) - #222

Merged
ScriptedAlchemy merged 1 commit into
mainfrom
wave5/211-review-fixes
Sep 1, 2026
Merged

fix(workbench): route catalog review fixes from #211 (usage arity, empty server surfaces, stale-repair e2e)#222
ScriptedAlchemy merged 1 commit into
mainfrom
wave5/211-review-fixes

Conversation

@ScriptedAlchemy

Copy link
Copy Markdown
Owner

Folds the three post-merge Codex findings on #211 into fixes, per the #105 stage-2 lane.

Fixes

  1. P1 — stale-catalog repair browser coverage (examples-real.e2e.test.ts): the flagship audiobook-curator routes-catalog journey now breaks src/conversion.ts, rebuilds (epoch stays on the last good build), and asserts the stale route-state plus its diagnostic message in real Chrome; then restores the source, rebuilds, and asserts the catalog returns to current. This closes the AGENTS.md acceptance gap (populated state + stale-diagnostic AND repair flow).
  2. P2 — CLI usage arity (routes-page.tsx commandSummary): positionals now format from both required and repeated and flags carry value operands, matching the generated CLI's own help conventions (cli-entry.ts positionalPlaceholder/optionPlaceholder). library-audit now renders library-audit <sources...> [--concurrency <number>] --report <string> [--strict] instead of advertising the required variadic as optional and --report as valueless.
  3. P2 — empty compiled server surfaces (routes-model.ts): the catalog model now carries every declared server; servers packaged as custom/command/remote (compiled with empty route arrays by design) render as a named section with their packaging mode and an honest explanation instead of vanishing, and the "declares no conventional route modules" empty state no longer fires when such a server exists. routeCatalogServerCount counts declared servers, so an externally packaged server also keeps the MCP page reachable.

Wire contract untouched — no DTO or manifest-client schema changes.

Verification

Correct CLI usage projections, retain externally packaged servers, and cover stale catalog repair in real Chrome.
@changeset-bot

changeset-bot Bot commented Sep 1, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 607ef94

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
agent-bundle Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 1, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-01T22:11:03.619506Z 607ef94 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@ScriptedAlchemy
ScriptedAlchemy merged commit d67f84c into main Sep 1, 2026
9 checks passed
@ScriptedAlchemy
ScriptedAlchemy deleted the wave5/211-review-fixes branch September 1, 2026 22:08

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 607ef9481b

ℹ️ 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".

const placeholder = option.kind === 'boolean'
? ''
: ` <${option.choices === undefined ? option.kind : option.choices.join('|')}>`;
const flag = `--${option.option}${placeholder}`;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Show repetition for variadic named options

When a non-positional CLI option comes from an array schema, its manifest sets repeated: true and the parser accepts multiple occurrences; the generated CLI help also appends ... for this case in packages/agent-bundle/src/cli-entry.ts:217. This summary ignores option.repeated, so a route such as a named --source array is advertised as [--source <string>] rather than indicating that the flag may be repeated. Append the same repetition marker used by the generated help.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in #226 (6901324): cliCommandUsage now appends the same ... repetition marker the generated help prints for value-carrying repeated options — --source <string> ... required, [--tag <string> ...] optional. Unit coverage added for both; booleans are unaffected since the grammar rejects boolean arrays.

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