[Hackathon] Add "testsprite ci": one-shot run + gate + GitHub-native output

[Andy00L]

Discord Username / User ID

interferon0

What does this improvement do?

A single command teams paste into one CI step: it runs a project's suite (wrapping the existing batch path), gates the job on the exit code, and when GITHUB_ACTIONS is set appends a Markdown results table to $GITHUB_STEP_SUMMARY, emits one ::error:: workflow-command line per failed test (title + dashboard link) so failures annotate the PR checks tab, and writes a stable machine summary to stdout or --summary-file. It auto-detects the runner and degrades to plain output off-CI. This collapses "run + gate + PR feedback + dashboard artifact" into one call, the exact shape gh, Cypress, and Playwright converged on.

Details / implementation notes

The batch --all --wait path already computes {passed, failed, timedOut, total} plus per-test runId/dashboardUrl/error (src/commands/test.ts:5743), so ci is a presenter over data the CLI already assembles, with zero new wire calls. The backend already stamps source: 'github_action' (src/lib/runs.types.ts:249), so the provenance loop is pre-wired. New src/commands/ci.ts + registration in src/index.ts + a dry-run sample; reads GITHUB_STEP_SUMMARY/GITHUB_ACTIONS from process.env, writes via fs. No new dependency. Tests: summary/annotation/machine-summary formats; off-CI plain fallback. PR to follow once assigned.

Confirmations

• I have searched existing issues and this is not a duplicate.
• I have provided my Discord identity above for reward coordination.

[zeshi-du]

Triage: sequenced behind #95 — most of the value here (run + gate + CI artifact) lands with --report junit on the existing batch path. Once PR #96 merges we will reassess whether a separate top-level ci command still earns its surface area (a new top-level command is a long-term maintenance commitment).

[zeshi-du]

Direction update: the #95 JUnit prerequisite shipped a while back, so this is no longer blocked — but the CI close-out direction has since been decided as an official GitHub Action (wrapping the CLI: run + gate + annotations + JUnit artifact) plus a CircleCI orb, rather than a new testsprite ci top-level command in the CLI itself. The one-shot UX this issue proposes is exactly what that Action's interface will deliver. Keeping the issue open until the Action ships, then we'll close it against that release.

[Andy00L]

/assign

[testsprite-hob]

Assigned to @Andy00L. Thanks for taking this on. (0 more slots available.)

Your open assigned issues (3/3):

• [Hackathon] Read ~/.testsprite/config for persistent defaults (output, endpoint, project) #100 — [Hackathon] Read ~/.testsprite/config for persistent defaults (output, endpoint, project)
• [Hackathon] TESTSPRITE_PROJECT_ID env default for --project #76 — [Hackathon] TESTSPRITE_PROJECT_ID env default for --project

[zeshi-du]

Direction reminder for anyone watching this issue (and @Andy00L after #264): per the 07-18 note above, the one-shot CI entrypoint ships as the official GitHub Action, so a testsprite ci subcommand is out of scope. What is in scope CLI-side — and welcome as PRs — is the CI-native output layer: GitHub annotations + step-summary rendering attached to test run (see the reshape requested on #264). This issue stays open until the Action ships.

[zeshi-du]

@Andy00L — heads-up on the Season 3 CLI Improvement Bonus coordination step: please join the TestSprite Discord and reach out to Kairui | TestSprite by 2026-07-29 23:59 UTC. Slots not claimed by then may be reallocated.

https://discord.com/invite/GXWFjCe4an