Skip to content

Agent Control 3.9.0

Choose a tag to compare

View all tags
@lozknowles lozknowles released this 05 Sep 14:07
· 115 commits to main since this release
v3.9.0
4966c97
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Agent Control 3.9.0

Agent Control 3.9.0 adds a qualified, cross-platform resilient execution lifecycle for governed Work Parcels.

Highlights

  • Persistent Work Parcel execution context with immutable goals, durable events, bounded baton views, and governed retrieval.
  • Resilient execution and recovery with controller-restart reconciliation that does not unsafely replay external work.
  • Bounded retry/backoff, cancellation, cleanup verification, and durable terminal-state handling.
  • Qualified Linux execution plus the tested production Windows cancellation and timeout path.
  • Qualified Android wireless-ADB lifecycle on the tested Pixel, including service-identity and intended-target verification, direct DNS-SD fallback, and bounded reconnect handling.
  • Dashboard and runtime resilience improvements with authoritative execution, recovery, and telemetry projections.
  • Sanitized artifact contracts for cross-node qualification and recovery evidence.
  • Independent cache outcome-quality verification across matched experiment arms.

Qualification boundary

  • Windows qualification applies to the tested production Windows execution path.
  • Android qualification applies to the tested Pixel wireless-ADB lifecycle. Other Android/ADB builds and unsupported execution or recovery substrates require their own qualification.
  • Cache outcome quality was demonstrated: both matched arms passed independent verification and scored 6/6.
  • No cache token, latency, or economic saving was demonstrated or claimed; the cache candidate used more tokens and took longer in the matched experiment.
  • Explicit Responses cache controls remain disabled and deferred.

Release integrity

  • Release commit: 4966c97505d05e5be3a2f8cae092113ad44d636e
  • Qualified candidate: 9e7696fd223a1eb80f5f83c94935b5b5ba8ef20e
  • Qualified package SHA-256: 51861afe80bdf2bd0ba1c184ca4eecde9b9d4f40b5e721ea07bf9e9ad0bf1d5d
  • Published package SHA-256: 4203e083d7c633f68febecdbc3d03470ac7517e6569ace8cfa7bdec2595ca3cb
  • Published package size: 20,536,323 bytes
  • Final validation: 829/829 tests; 3/3 neutrality checks; 45/45 implementation-status entries; 610 local Markdown links across 127 files.
  • Clean package installation reports agent-control 3.9.0; production dependency audit reports zero known vulnerabilities.

The published package differs from the qualified package in exactly three non-runtime files: two documentation examples now use the repository-supported no-lock install command, and one test supplies a fixed timestamp so its determinism assertion cannot race the wall clock. No runtime implementation file differs.

See the tracked Agent Control 3.9 qualification report. The attached evidence archive and manifest preserve the accepted sanitized cross-platform qualification set.

Install and verify

npm install --no-package-lock --ignore-scripts
npm run check
npm pack --dry-run
agent-control --version

No deployment is performed by this release publication.

Assets 5
Loading