Skip to content

Fix Workbench command catalog and manual - #9240

Merged
maxliux5 merged 1 commit into
mainfrom
codex/workbench-cli-catalog-fix
Nov 22, 2026
Merged

maxliux5 merged 1 commit into
mainfrom
codex/workbench-cli-catalog-fix

Conversation

@loopx-agent

@loopx-agent loopx-agent commented Nov 22, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

The public command catalog lists loopx workbench start|status|stop as a single example. The existing standalone Core check runs the example through the installed parser, which rejects it with exit code 2. This fails the Package Smoke loopx-core job on #9227 and #9235. The output-budget coverage check also finds Workbench missing from its manifest, and the checked-in manual predates the catalog entry.

Change

  • List the three existing Workbench commands using the catalog’s command separator.
  • Classify Workbench start, status, and stop as operator-invoked commands using the existing cold-path exception. Refresh the generated manual from the canonical catalog.

The published examples now resolve to three commands:

loopx workbench start
loopx workbench status
loopx workbench stop

Verification

  • Base dc79482c88 reproduced the parser error, missing manifest classification and stale manual.
  • Fixed head 5e417ffd6d passed all 58 Package Smoke Core tests with a separately installed Python 3.11 wheel on macOS. On both the source CLI and the installed console, the three subcommand help invocations returned 0. The combined spelling returned 2, and an isolated status read returned stopped.
  • Source output-budget and manual tests passed (51 passed, 1 skipped). The rendered manual lists the same three commands.
  • Standard loopx canary premerge --from-git-diff --git-diff-base origin/main passed.
  • Independent review passed on 5e417ffd6da88d2aeb63b31fda786fa8efa3618e. The reviewer reproduced the baseline failures, resolved all three command examples in the isolated Python 3.11 Core wheel, checked the invalid combined spelling and isolated stopped status, and verified generated-manual parity and the existing cold-path classification.
  • The GitHub Core package smoke and kernel contract job passed on the same commit. The Windows job hit WinError 10038 in the captured research fixture before running the Windows CLI budget check. Both of those steps passed on the native Windows job for #9218.
  • Composing this commit and Read canonical test worker replies through portable pipes #9218 with main 2ab0d1a42b on macOS passed the CLI output differential, seven standalone Core catalog and context cases, and 26 fixture and lease-loss recovery cases. GitHub formal review and hosted validation of the combined tree remain open.

Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.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