docs(cli): advertise open --foreground and snapshot --actions in the workflow card - #1682
Merged
Merged
Conversation
Size Report
Startup median (7 runs, lower is better):
Top changed chunks:
|
Member
Author
|
Re-reviewed exact head
|
…workflow card open --foreground (#1670/#1671) and snapshot -i --actions (#1665) shipped with no mention in the compact `help workflow` card, so a planning model never discovers either. Add one terse line each: the foreground fast-path in Bootstrap, and the merged-element custom-action guidance in Validation and evidence. Stays under the 9,000-byte compact-card budget (8493 -> 8908 bytes). Adds two help-conformance bench cases per the repo's changed-guidance rule: foreground-attach-single-sim (correct plan starts with `open --foreground` in an unambiguous single-sim scenario, fail-closed alternative forbidden) and merged-card-actions-not-directly-invokable (a merged Bluesky-style feed card's actions list is evidence, not a selector). Both use a real pinned sample rebuilt through the production snapshot renderer.
…matcher Flag order after `open` isn't semantically meaningful (`open --platform ios --foreground` is exactly as correct as `open --foreground --platform ios`), but startsWithForegroundOpen required --foreground to be the literal next token after `open`. Rescoring the completed repeat=3 bench report shows this docked codex:gpt-5.4-mini on all 3 trials even though its plan was config-order noise, not a real deviation -- the no-positional/no-device guarantee already comes from the forbidden checks. Loosened to require --foreground anywhere on the open line; foreground-attach-single-sim now scores 54/54 across both runners.
thymikee
force-pushed
the
claude/card-advertise-foreground-actions
branch
from
August 8, 2026 07:29
12cf904 to
adc8366
Compare
thymikee
added
the
ready-for-human
Member
Author
|
Resolved all three findings at exact head |
|
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
1 participant
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.
Summary
Advertise two shipped iOS simulator workflows in the compact
agent-device help workflowcard:open --foregroundattaches to the sole running app and returns its initial interactive snapshot; if capture fails, the session remains open and recovery issnapshot -i.snapshot -i --actionsexposes custom-action names hidden in merged elements while making clear those names are evidence, not direct targets.The conformance harness now rejects explicit foreground app targets from parsed positionals regardless of flag order, pins degraded-open recovery, and builds the merged-actions sample through the real
snapshot -ioutput route. Scope is 10 help/conformance files; runtime behavior is unchanged.Validation
open --foreground --platform ios com.example.app; the new parsed-positionals check rejects it.snapshotCliOutput({ interactiveOnly: true })restores the production flattened output.pnpm check:affected --run: every runnable local check passed, including format, lint, typecheck, layering, Fallow, build/package, affected coverage, provider integration, Node integration, progress, and replay compatibility.No device run is required: this changes help text and its planning/conformance fixtures, not device-facing runtime behavior.