Skip to content

Onboarding documents a positional target, while the parser binds targets only through --target #288

Description

@MicroMilo

Summary

README and DOCUMENTATION repeatedly teach testsprite agent install <target>, but the command declares no positional argument and its action obtains targets only from --target. Thus the advertised form cannot select the requested agent; the checked-in usage is testsprite agent install [options].

Validation source commit: 60d55e47883e924ff1a5f0ab1fe67a25bc3b0877.

Code path

  • README.md:127-133: README onboarding example uses positional target
  • DOCUMENTATION.md:84-89: Complete-loop example uses positional target
  • DOCUMENTATION.md:107-126: Eight positional target examples
  • src/commands/agent.ts:1063-1108: Install grammar has no positional and accepts --target only
  • test/__snapshots__/help.snapshot.test.ts.snap:24-45: Checked-in help usage contains options only
  • test/e2e/agent-install.e2e.test.ts:90-105: E2E path selects targets with --target
  • Repository-local validation artifact: Bounded static witness

Steps to reproduce

This report is based on a source-control-flow validation against the commit above.

  1. Check out the source commit listed in this report.
  2. Inspect the code path and contract anchors listed above.
  3. Exercise the described boundary/state path: Onboarding documents a positional target, while the parser binds targets only through --target.
  4. Compare the observed behavior with the expected contract below.

Validation note: It proves positional examples are present while registration, help, and e2e callers expose target selection only through --target <t>.

Expected behavior

The implementation should preserve the repository contract described by the documentation, public type, parser, serializer, or sibling implementation anchors above.

Actual behavior

README and DOCUMENTATION repeatedly teach testsprite agent install <target>, but the command declares no positional argument and its action obtains targets only from --target. Thus the advertised form cannot select the requested agent; the checked-in usage is testsprite agent install [options].

Existing coverage

I did not find an existing issue or PR title that appears to cover this exact root cause in the pre-submission check.

Suggested fix

Agent install target argument grammar and documentation

Suggested tests

  • Add a regression test for: Onboarding documents a positional target, while the parser binds targets only through --target.
  • Include the boundary value or state transition described above so the old behavior fails before the fix.

Submitted with Codex.

Metadata

Metadata

Assignees

Labels

in-progressAssigned and actively being worked on

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions