Skip to content

v5.0.0-alpha.4 - API agents and mission preflight

Pre-release
Pre-release

Choose a tag to compare

View all tags
@godhiraj-code godhiraj-code released this 20 Sep 17:53
v5.0.0-alpha.4
edcab0c

Starlight 5.0.0-alpha.4 — API agents and mission preflight

Missions can now read JSON APIs through a reusable agent, verify domain results, and hand them to subsequent steps. Plans can also be checked before any agents are loaded or executed.

  • HTTP JSON agent: createHttpJsonAgent supports GET requests to explicitly allowed HTTP(S) origins, request deadlines, bounded decoded response sizes, cancellation, HTTP evidence, and optional verification. Redirects and automatic retries are disabled.
  • Service-health workflow: starlight demo --example service-health starts a temporary local fixture endpoint, fetches and verifies three health records, then writes and reads back a Markdown report. It demonstrates real HTTP against sample data without credentials.
  • Mission preflight: starlight validate mission.json and SDK validateMission normalize and validate a mission without loading agents, making requests, or creating run files.

Requires Node.js 22+. Wire protocol 1.0 remains unchanged. Existing agents, the default file-report demo, run storage, and mission APIs remain supported.

Try the exact release

Download the attached archive and verify it against SHA256SUMS:

npm install ./starlight-protocol-starlight-5.0.0-alpha.4.tgz
npx starlight demo --example service-health --events --timeout-ms 10000
npx starlight runs --status completed --limit 10

The attached archive is the release distribution; these commands do not assume a registry publication.

Verification and scope

The release gate passes 79 tests, 19 protocol conformance cases, lint, TypeScript declarations, schema and documentation checks, authenticated multi-process execution, demo scenarios, and website builds. Installed-package checks exercise both demos, run history, report inspection, and mission validation. The dependency audit reports zero vulnerabilities.

HTTP regressions cover blocked origins, redirects, malformed data, compressed and streamed response limits, configured credentials, failed verification, request deadlines, and cancellation of stalled streams.

Agents remain trusted code. URL origin restrictions are not a network sandbox or DNS policy. API credentials belong in agent configuration, and domain validation remains agent-defined. Preflight checks plan structure, not endpoint health or future execution success. This remains an alpha release.

API agents and mission validation · Website · Changelog

Assets 4
Loading