fix(hosted): stop duplicating usage errors and align the subcommand list - #428

Merged
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity
Aug 23, 2026
Merged

fix(hosted): stop duplicating usage errors and align the subcommand list#428
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

The problem

webcmd-cloud's parity suite, run against this repo's main, found two ways hosted mode drifted from local after #424/#427. Both are hosted-only; local was already correct.

1. Hosted printed every unknown-option error twice.

local hosted
error: unknown option '--unknown' error: unknown option '--unknown'
help: valid flags for ... error: unknown option '--unknown' ← twice
help: valid flags for ...

src/hosted/runner.ts still passed includeCapturedStderrForUnknownOption: true. Since #424, structuralErrorFromCommander formats the error: line itself, so replaying Commander's captured stderr on top printed it a second time — the exact duplicate #424 removed on the local path.

2. The help: subcommand list was spelled differently on each side.

local: echo, empty, null, scalar, presentation, fail, session-busy, large, local-only, help
hosted: echo, empty, fail, large, null, presentation, scalar, session-busy

Local used Commander's declaration order and included the auto-generated help entry; hosted built its list from the manifest and had neither. Two implementations of one sentence.

What changed

  1. Dropped includeCapturedStderrForUnknownOption at both src/hosted/runner.ts call sites (list, completion).
  2. visibleSubcommandNames now sorts, de-duplicates, and drops Commander's help entry.
  3. The hosted list sorts and de-duplicates the same way.
  4. Four assertions in src/hosted/root-command-surface.test.ts updated — they were pinning the duplicated line and the help entry as expected output.

After this, the only difference left between the two lists is commands hosted mode genuinely cannot run (LOCAL strategy) — a real capability boundary, not drift.

Before / After

# BEFORE — hosted
error: unknown option '-V'
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — hosted, byte-identical to local
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — same order, same shape; only `local-only` differs, and legitimately
local: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, local-only, null, presentation, scalar, session-busy
hosted: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, null, presentation, scalar, session-busy

Tests

npm run typecheck clean. npx vitest run --project unit156 files, 2747 passed, 1 skipped, 0 failed.

Cross-checked against webcmd-cloud by packing this branch and running its parity suite: the two duplicate-line failures are gone. What remains there is digest re-baselining plus the local-only capability delta, handled in the companion cloud PR.

🤖 Generated with Claude Code

Cloud's parity suite caught two ways hosted mode drifted from local after
#424/#427.
Hosted still passed includeCapturedStderrForUnknownOption, so it replayed
Commander's captured stderr on top of the line structuralErrorFromCommander
now formats itself, printing `error: unknown option ...` twice.
The `help:` subcommand list also differed: local used declaration order and
included Commander's auto `help` entry, hosted used manifest order without
it. Both are sorted and drop `help` now, leaving only commands hosted mode
genuinely cannot run (LOCAL strategy) as a difference.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

@ankitranjan7
ankitranjan7 merged commit 54d2dbb into mainAug 23, 2026
52 of 53 checks passed
@ankitranjan7
ankitranjan7 deleted the fix/hosted-usage-error-parity branch August 23, 2026 16:49
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
Sign up for freeto 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

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

fix(hosted): stop duplicating usage errors and align the subcommand list - #428

Merged
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity
Aug 23, 2026
Merged

fix(hosted): stop duplicating usage errors and align the subcommand list#428
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

The problem

webcmd-cloud's parity suite, run against this repo's main, found two ways hosted mode drifted from local after #424/#427. Both are hosted-only; local was already correct.

1. Hosted printed every unknown-option error twice.

local hosted
error: unknown option '--unknown' error: unknown option '--unknown'
help: valid flags for ... error: unknown option '--unknown' ← twice
help: valid flags for ...

src/hosted/runner.ts still passed includeCapturedStderrForUnknownOption: true. Since #424, structuralErrorFromCommander formats the error: line itself, so replaying Commander's captured stderr on top printed it a second time — the exact duplicate #424 removed on the local path.

2. The help: subcommand list was spelled differently on each side.

local: echo, empty, null, scalar, presentation, fail, session-busy, large, local-only, help
hosted: echo, empty, fail, large, null, presentation, scalar, session-busy

Local used Commander's declaration order and included the auto-generated help entry; hosted built its list from the manifest and had neither. Two implementations of one sentence.

What changed

  1. Dropped includeCapturedStderrForUnknownOption at both src/hosted/runner.ts call sites (list, completion).
  2. visibleSubcommandNames now sorts, de-duplicates, and drops Commander's help entry.
  3. The hosted list sorts and de-duplicates the same way.
  4. Four assertions in src/hosted/root-command-surface.test.ts updated — they were pinning the duplicated line and the help entry as expected output.

After this, the only difference left between the two lists is commands hosted mode genuinely cannot run (LOCAL strategy) — a real capability boundary, not drift.

Before / After

# BEFORE — hosted
error: unknown option '-V'
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — hosted, byte-identical to local
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — same order, same shape; only `local-only` differs, and legitimately
local: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, local-only, null, presentation, scalar, session-busy
hosted: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, null, presentation, scalar, session-busy

Tests

npm run typecheck clean. npx vitest run --project unit156 files, 2747 passed, 1 skipped, 0 failed.

Cross-checked against webcmd-cloud by packing this branch and running its parity suite: the two duplicate-line failures are gone. What remains there is digest re-baselining plus the local-only capability delta, handled in the companion cloud PR.

🤖 Generated with Claude Code

Cloud's parity suite caught two ways hosted mode drifted from local after
#424/#427.
Hosted still passed includeCapturedStderrForUnknownOption, so it replayed
Commander's captured stderr on top of the line structuralErrorFromCommander
now formats itself, printing `error: unknown option ...` twice.
The `help:` subcommand list also differed: local used declaration order and
included Commander's auto `help` entry, hosted used manifest order without
it. Both are sorted and drop `help` now, leaving only commands hosted mode
genuinely cannot run (LOCAL strategy) as a difference.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

@ankitranjan7
ankitranjan7 merged commit 54d2dbb into mainAug 23, 2026
52 of 53 checks passed
@ankitranjan7
ankitranjan7 deleted the fix/hosted-usage-error-parity branch August 23, 2026 16:49
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
Sign up for freeto 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

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(hosted): stop duplicating usage errors and align the subcommand list - #428

Merged
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity
Aug 23, 2026
Merged

fix(hosted): stop duplicating usage errors and align the subcommand list#428
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

The problem

webcmd-cloud's parity suite, run against this repo's main, found two ways hosted mode drifted from local after #424/#427. Both are hosted-only; local was already correct.

1. Hosted printed every unknown-option error twice.

local hosted
error: unknown option '--unknown' error: unknown option '--unknown'
help: valid flags for ... error: unknown option '--unknown' ← twice
help: valid flags for ...

src/hosted/runner.ts still passed includeCapturedStderrForUnknownOption: true. Since #424, structuralErrorFromCommander formats the error: line itself, so replaying Commander's captured stderr on top printed it a second time — the exact duplicate #424 removed on the local path.

2. The help: subcommand list was spelled differently on each side.

local: echo, empty, null, scalar, presentation, fail, session-busy, large, local-only, help
hosted: echo, empty, fail, large, null, presentation, scalar, session-busy

Local used Commander's declaration order and included the auto-generated help entry; hosted built its list from the manifest and had neither. Two implementations of one sentence.

What changed

  1. Dropped includeCapturedStderrForUnknownOption at both src/hosted/runner.ts call sites (list, completion).
  2. visibleSubcommandNames now sorts, de-duplicates, and drops Commander's help entry.
  3. The hosted list sorts and de-duplicates the same way.
  4. Four assertions in src/hosted/root-command-surface.test.ts updated — they were pinning the duplicated line and the help entry as expected output.

After this, the only difference left between the two lists is commands hosted mode genuinely cannot run (LOCAL strategy) — a real capability boundary, not drift.

Before / After

# BEFORE — hosted
error: unknown option '-V'
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — hosted, byte-identical to local
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — same order, same shape; only `local-only` differs, and legitimately
local: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, local-only, null, presentation, scalar, session-busy
hosted: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, null, presentation, scalar, session-busy

Tests

npm run typecheck clean. npx vitest run --project unit156 files, 2747 passed, 1 skipped, 0 failed.

Cross-checked against webcmd-cloud by packing this branch and running its parity suite: the two duplicate-line failures are gone. What remains there is digest re-baselining plus the local-only capability delta, handled in the companion cloud PR.

🤖 Generated with Claude Code

Cloud's parity suite caught two ways hosted mode drifted from local after
#424/#427.
Hosted still passed includeCapturedStderrForUnknownOption, so it replayed
Commander's captured stderr on top of the line structuralErrorFromCommander
now formats itself, printing `error: unknown option ...` twice.
The `help:` subcommand list also differed: local used declaration order and
included Commander's auto `help` entry, hosted used manifest order without
it. Both are sorted and drop `help` now, leaving only commands hosted mode
genuinely cannot run (LOCAL strategy) as a difference.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

@ankitranjan7
ankitranjan7 merged commit 54d2dbb into mainAug 23, 2026
52 of 53 checks passed
@ankitranjan7
ankitranjan7 deleted the fix/hosted-usage-error-parity branch August 23, 2026 16:49
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
Sign up for freeto 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

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(hosted): stop duplicating usage errors and align the subcommand list - #428

Merged
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity
Aug 23, 2026
Merged

fix(hosted): stop duplicating usage errors and align the subcommand list#428
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

The problem

webcmd-cloud's parity suite, run against this repo's main, found two ways hosted mode drifted from local after #424/#427. Both are hosted-only; local was already correct.

1. Hosted printed every unknown-option error twice.

local hosted
error: unknown option '--unknown' error: unknown option '--unknown'
help: valid flags for ... error: unknown option '--unknown' ← twice
help: valid flags for ...

src/hosted/runner.ts still passed includeCapturedStderrForUnknownOption: true. Since #424, structuralErrorFromCommander formats the error: line itself, so replaying Commander's captured stderr on top printed it a second time — the exact duplicate #424 removed on the local path.

2. The help: subcommand list was spelled differently on each side.

local: echo, empty, null, scalar, presentation, fail, session-busy, large, local-only, help
hosted: echo, empty, fail, large, null, presentation, scalar, session-busy

Local used Commander's declaration order and included the auto-generated help entry; hosted built its list from the manifest and had neither. Two implementations of one sentence.

What changed

  1. Dropped includeCapturedStderrForUnknownOption at both src/hosted/runner.ts call sites (list, completion).
  2. visibleSubcommandNames now sorts, de-duplicates, and drops Commander's help entry.
  3. The hosted list sorts and de-duplicates the same way.
  4. Four assertions in src/hosted/root-command-surface.test.ts updated — they were pinning the duplicated line and the help entry as expected output.

After this, the only difference left between the two lists is commands hosted mode genuinely cannot run (LOCAL strategy) — a real capability boundary, not drift.

Before / After

# BEFORE — hosted
error: unknown option '-V'
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — hosted, byte-identical to local
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — same order, same shape; only `local-only` differs, and legitimately
local: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, local-only, null, presentation, scalar, session-busy
hosted: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, null, presentation, scalar, session-busy

Tests

npm run typecheck clean. npx vitest run --project unit156 files, 2747 passed, 1 skipped, 0 failed.

Cross-checked against webcmd-cloud by packing this branch and running its parity suite: the two duplicate-line failures are gone. What remains there is digest re-baselining plus the local-only capability delta, handled in the companion cloud PR.

🤖 Generated with Claude Code

Cloud's parity suite caught two ways hosted mode drifted from local after
#424/#427.
Hosted still passed includeCapturedStderrForUnknownOption, so it replayed
Commander's captured stderr on top of the line structuralErrorFromCommander
now formats itself, printing `error: unknown option ...` twice.
The `help:` subcommand list also differed: local used declaration order and
included Commander's auto `help` entry, hosted used manifest order without
it. Both are sorted and drop `help` now, leaving only commands hosted mode
genuinely cannot run (LOCAL strategy) as a difference.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

@ankitranjan7
ankitranjan7 merged commit 54d2dbb into mainAug 23, 2026
52 of 53 checks passed
@ankitranjan7
ankitranjan7 deleted the fix/hosted-usage-error-parity branch August 23, 2026 16:49
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
Sign up for freeto 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

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

fix(hosted): stop duplicating usage errors and align the subcommand list - #428

Merged
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity
Aug 23, 2026
Merged

fix(hosted): stop duplicating usage errors and align the subcommand list#428
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

The problem

webcmd-cloud's parity suite, run against this repo's main, found two ways hosted mode drifted from local after #424/#427. Both are hosted-only; local was already correct.

1. Hosted printed every unknown-option error twice.

local hosted
error: unknown option '--unknown' error: unknown option '--unknown'
help: valid flags for ... error: unknown option '--unknown' ← twice
help: valid flags for ...

src/hosted/runner.ts still passed includeCapturedStderrForUnknownOption: true. Since #424, structuralErrorFromCommander formats the error: line itself, so replaying Commander's captured stderr on top printed it a second time — the exact duplicate #424 removed on the local path.

2. The help: subcommand list was spelled differently on each side.

local: echo, empty, null, scalar, presentation, fail, session-busy, large, local-only, help
hosted: echo, empty, fail, large, null, presentation, scalar, session-busy

Local used Commander's declaration order and included the auto-generated help entry; hosted built its list from the manifest and had neither. Two implementations of one sentence.

What changed

  1. Dropped includeCapturedStderrForUnknownOption at both src/hosted/runner.ts call sites (list, completion).
  2. visibleSubcommandNames now sorts, de-duplicates, and drops Commander's help entry.
  3. The hosted list sorts and de-duplicates the same way.
  4. Four assertions in src/hosted/root-command-surface.test.ts updated — they were pinning the duplicated line and the help entry as expected output.

After this, the only difference left between the two lists is commands hosted mode genuinely cannot run (LOCAL strategy) — a real capability boundary, not drift.

Before / After

# BEFORE — hosted
error: unknown option '-V'
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — hosted, byte-identical to local
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — same order, same shape; only `local-only` differs, and legitimately
local: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, local-only, null, presentation, scalar, session-busy
hosted: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, null, presentation, scalar, session-busy

Tests

npm run typecheck clean. npx vitest run --project unit156 files, 2747 passed, 1 skipped, 0 failed.

Cross-checked against webcmd-cloud by packing this branch and running its parity suite: the two duplicate-line failures are gone. What remains there is digest re-baselining plus the local-only capability delta, handled in the companion cloud PR.

🤖 Generated with Claude Code

Cloud's parity suite caught two ways hosted mode drifted from local after
#424/#427.
Hosted still passed includeCapturedStderrForUnknownOption, so it replayed
Commander's captured stderr on top of the line structuralErrorFromCommander
now formats itself, printing `error: unknown option ...` twice.
The `help:` subcommand list also differed: local used declaration order and
included Commander's auto `help` entry, hosted used manifest order without
it. Both are sorted and drop `help` now, leaving only commands hosted mode
genuinely cannot run (LOCAL strategy) as a difference.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

@ankitranjan7
ankitranjan7 merged commit 54d2dbb into mainAug 23, 2026
52 of 53 checks passed
@ankitranjan7
ankitranjan7 deleted the fix/hosted-usage-error-parity branch August 23, 2026 16:49
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
Sign up for freeto 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

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(hosted): stop duplicating usage errors and align the subcommand list - #428

Merged
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity
Aug 23, 2026
Merged

fix(hosted): stop duplicating usage errors and align the subcommand list#428
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

The problem

webcmd-cloud's parity suite, run against this repo's main, found two ways hosted mode drifted from local after #424/#427. Both are hosted-only; local was already correct.

1. Hosted printed every unknown-option error twice.

local hosted
error: unknown option '--unknown' error: unknown option '--unknown'
help: valid flags for ... error: unknown option '--unknown' ← twice
help: valid flags for ...

src/hosted/runner.ts still passed includeCapturedStderrForUnknownOption: true. Since #424, structuralErrorFromCommander formats the error: line itself, so replaying Commander's captured stderr on top printed it a second time — the exact duplicate #424 removed on the local path.

2. The help: subcommand list was spelled differently on each side.

local: echo, empty, null, scalar, presentation, fail, session-busy, large, local-only, help
hosted: echo, empty, fail, large, null, presentation, scalar, session-busy

Local used Commander's declaration order and included the auto-generated help entry; hosted built its list from the manifest and had neither. Two implementations of one sentence.

What changed

  1. Dropped includeCapturedStderrForUnknownOption at both src/hosted/runner.ts call sites (list, completion).
  2. visibleSubcommandNames now sorts, de-duplicates, and drops Commander's help entry.
  3. The hosted list sorts and de-duplicates the same way.
  4. Four assertions in src/hosted/root-command-surface.test.ts updated — they were pinning the duplicated line and the help entry as expected output.

After this, the only difference left between the two lists is commands hosted mode genuinely cannot run (LOCAL strategy) — a real capability boundary, not drift.

Before / After

# BEFORE — hosted
error: unknown option '-V'
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — hosted, byte-identical to local
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — same order, same shape; only `local-only` differs, and legitimately
local: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, local-only, null, presentation, scalar, session-busy
hosted: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, null, presentation, scalar, session-busy

Tests

npm run typecheck clean. npx vitest run --project unit156 files, 2747 passed, 1 skipped, 0 failed.

Cross-checked against webcmd-cloud by packing this branch and running its parity suite: the two duplicate-line failures are gone. What remains there is digest re-baselining plus the local-only capability delta, handled in the companion cloud PR.

🤖 Generated with Claude Code

Cloud's parity suite caught two ways hosted mode drifted from local after
#424/#427.
Hosted still passed includeCapturedStderrForUnknownOption, so it replayed
Commander's captured stderr on top of the line structuralErrorFromCommander
now formats itself, printing `error: unknown option ...` twice.
The `help:` subcommand list also differed: local used declaration order and
included Commander's auto `help` entry, hosted used manifest order without
it. Both are sorted and drop `help` now, leaving only commands hosted mode
genuinely cannot run (LOCAL strategy) as a difference.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

@ankitranjan7
ankitranjan7 merged commit 54d2dbb into mainAug 23, 2026
52 of 53 checks passed
@ankitranjan7
ankitranjan7 deleted the fix/hosted-usage-error-parity branch August 23, 2026 16:49
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
Sign up for freeto 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

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

fix(hosted): stop duplicating usage errors and align the subcommand list - #428

Merged
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity
Aug 23, 2026
Merged

fix(hosted): stop duplicating usage errors and align the subcommand list#428
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

The problem

webcmd-cloud's parity suite, run against this repo's main, found two ways hosted mode drifted from local after #424/#427. Both are hosted-only; local was already correct.

1. Hosted printed every unknown-option error twice.

local hosted
error: unknown option '--unknown' error: unknown option '--unknown'
help: valid flags for ... error: unknown option '--unknown' ← twice
help: valid flags for ...

src/hosted/runner.ts still passed includeCapturedStderrForUnknownOption: true. Since #424, structuralErrorFromCommander formats the error: line itself, so replaying Commander's captured stderr on top printed it a second time — the exact duplicate #424 removed on the local path.

2. The help: subcommand list was spelled differently on each side.

local: echo, empty, null, scalar, presentation, fail, session-busy, large, local-only, help
hosted: echo, empty, fail, large, null, presentation, scalar, session-busy

Local used Commander's declaration order and included the auto-generated help entry; hosted built its list from the manifest and had neither. Two implementations of one sentence.

What changed

  1. Dropped includeCapturedStderrForUnknownOption at both src/hosted/runner.ts call sites (list, completion).
  2. visibleSubcommandNames now sorts, de-duplicates, and drops Commander's help entry.
  3. The hosted list sorts and de-duplicates the same way.
  4. Four assertions in src/hosted/root-command-surface.test.ts updated — they were pinning the duplicated line and the help entry as expected output.

After this, the only difference left between the two lists is commands hosted mode genuinely cannot run (LOCAL strategy) — a real capability boundary, not drift.

Before / After

# BEFORE — hosted
error: unknown option '-V'
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — hosted, byte-identical to local
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — same order, same shape; only `local-only` differs, and legitimately
local: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, local-only, null, presentation, scalar, session-busy
hosted: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, null, presentation, scalar, session-busy

Tests

npm run typecheck clean. npx vitest run --project unit156 files, 2747 passed, 1 skipped, 0 failed.

Cross-checked against webcmd-cloud by packing this branch and running its parity suite: the two duplicate-line failures are gone. What remains there is digest re-baselining plus the local-only capability delta, handled in the companion cloud PR.

🤖 Generated with Claude Code

Cloud's parity suite caught two ways hosted mode drifted from local after
#424/#427.
Hosted still passed includeCapturedStderrForUnknownOption, so it replayed
Commander's captured stderr on top of the line structuralErrorFromCommander
now formats itself, printing `error: unknown option ...` twice.
The `help:` subcommand list also differed: local used declaration order and
included Commander's auto `help` entry, hosted used manifest order without
it. Both are sorted and drop `help` now, leaving only commands hosted mode
genuinely cannot run (LOCAL strategy) as a difference.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

@ankitranjan7
ankitranjan7 merged commit 54d2dbb into mainAug 23, 2026
52 of 53 checks passed
@ankitranjan7
ankitranjan7 deleted the fix/hosted-usage-error-parity branch August 23, 2026 16:49
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
Sign up for freeto 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

@ankitranjan7
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

fix(hosted): stop duplicating usage errors and align the subcommand list - #428

Merged
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity
Aug 23, 2026
Merged

fix(hosted): stop duplicating usage errors and align the subcommand list#428
ankitranjan7 merged 1 commit into
mainfrom
fix/hosted-usage-error-parity

Conversation

@ankitranjan7

Copy link
Copy Markdown
Contributor

The problem

webcmd-cloud's parity suite, run against this repo's main, found two ways hosted mode drifted from local after #424/#427. Both are hosted-only; local was already correct.

1. Hosted printed every unknown-option error twice.

local hosted
error: unknown option '--unknown' error: unknown option '--unknown'
help: valid flags for ... error: unknown option '--unknown' ← twice
help: valid flags for ...

src/hosted/runner.ts still passed includeCapturedStderrForUnknownOption: true. Since #424, structuralErrorFromCommander formats the error: line itself, so replaying Commander's captured stderr on top printed it a second time — the exact duplicate #424 removed on the local path.

2. The help: subcommand list was spelled differently on each side.

local: echo, empty, null, scalar, presentation, fail, session-busy, large, local-only, help
hosted: echo, empty, fail, large, null, presentation, scalar, session-busy

Local used Commander's declaration order and included the auto-generated help entry; hosted built its list from the manifest and had neither. Two implementations of one sentence.

What changed

  1. Dropped includeCapturedStderrForUnknownOption at both src/hosted/runner.ts call sites (list, completion).
  2. visibleSubcommandNames now sorts, de-duplicates, and drops Commander's help entry.
  3. The hosted list sorts and de-duplicates the same way.
  4. Four assertions in src/hosted/root-command-surface.test.ts updated — they were pinning the duplicated line and the help entry as expected output.

After this, the only difference left between the two lists is commands hosted mode genuinely cannot run (LOCAL strategy) — a real capability boundary, not drift.

Before / After

# BEFORE — hosted
error: unknown option '-V'
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — hosted, byte-identical to local
error: unknown option '-V'
help: valid flags for `webcmd completion`: -f, --format, --json
# AFTER — same order, same shape; only `local-only` differs, and legitimately
local: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, local-only, null, presentation, scalar, session-busy
hosted: help: valid subcommands for `webcmd parity`: echo, empty, fail, large, null, presentation, scalar, session-busy

Tests

npm run typecheck clean. npx vitest run --project unit156 files, 2747 passed, 1 skipped, 0 failed.

Cross-checked against webcmd-cloud by packing this branch and running its parity suite: the two duplicate-line failures are gone. What remains there is digest re-baselining plus the local-only capability delta, handled in the companion cloud PR.

🤖 Generated with Claude Code

Cloud's parity suite caught two ways hosted mode drifted from local after
#424/#427.
Hosted still passed includeCapturedStderrForUnknownOption, so it replayed
Commander's captured stderr on top of the line structuralErrorFromCommander
now formats itself, printing `error: unknown option ...` twice.
The `help:` subcommand list also differed: local used declaration order and
included Commander's auto `help` entry, hosted used manifest order without
it. Both are sorted and drop `help` now, leaving only commands hosted mode
genuinely cannot run (LOCAL strategy) as a difference.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🟠 Maintainer review suggested — low confidence

The automated review could not reach a fully supported conclusion.

Limitations

  • The automated review returned an invalid structured result.

This review is advisory and does not block merging.

@ankitranjan7
ankitranjan7 merged commit 54d2dbb into mainAug 23, 2026
52 of 53 checks passed
@ankitranjan7
ankitranjan7 deleted the fix/hosted-usage-error-parity branch August 23, 2026 16:49
Agnik47 added a commit to Agnik47/webcmd that referenced this pull request Aug 28, 2026
…gentrhq#317)
`browser --help` listed its session commands and its adapter-authoring commands
in one flat block, so the two unrelated surfaces read as one. Group them from
the shared catalog: `tabs`, `bind`, `run`, `snapshot`, and `close` under
"Browser session commands", `init` and `verify` under "Adapter authoring
commands". Local and hosted help draw from the same catalog, so they stay
aligned.
`browser fork` is also removed here. It ran the same action as the adapter
command and only existed as a hidden re-registration, which agentrhq#361 superseded;
`adapter override` gains a `fork` alias so the local spelling survives.
Rebased onto 0.7.10. Three upstream changes landed in the same lines and are
kept: the structured-help imports from agentrhq#425/agentrhq#428, `BROWSER_RUN_HELP_TEXT`, and
the `adapter override` description and hosted artifact-download paragraph. The
alias is additive to that description rather than replacing it.
Sign up for freeto 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

@ankitranjan7