Agent Control 3.8.2
Agent Control 3.8.2
Agent Control 3.8.2 aligns the repository-review provider-facing structured-output schema with the stricter application validation contract exposed by the 3.8.1 video qualification. The historical providers returned completed, transport-valid JSON; Agent Control then rejected values admitted by its looser wire schema. This release declares the same literals, enums, non-empty values, line constraints and confidence range at both boundaries while retaining independent fail-closed application validation.
New failures retain bounded safe constraint paths such as $.findings[0].category:enum. Rejected values and raw provider responses remain ephemeral and are not added to evidence merely for diagnostics.
The dashboard adds human-readable Execution history for Saved Job Runs and Lanes. This bounded redacted projection derives from existing durable Job Run, associated Work Parcel, token-governor, baton and verification records. It distinguishes operator, system, provider, tool/action, governor, baton and error activity and keeps current context separate from cumulative token/cost accounting with authoritative, estimated and unavailable labels. It is not a raw transcript store and does not expose hidden reasoning.
Handoff semantics remain evidence-based. A threshold can produce HANDOFF_RECOMMENDED without a transfer; baton creation is not destination acceptance or execution; only a durable successful BATON_AND_HANDOFF outcome is shown as completed. This release does not claim that its 3.8.2 physical qualification performed an actual baton transfer.
The HTTP redaction boundary now permits the safe numeric contextTokens and contextLimitTokens fields while continuing to redact credential-like token fields. Clean package installations can report their exact source release with agent-control --version without contacting a controller.
Physical qualification used the normal Controller Account A Saved Job path. Run a0d646b0-77ae-41b3-85ed-a02a86f4880e and Work Parcel parcel-bccb41f1-c1b1-4ff2-8f1d-b3d8c61c2c07 returned a schema-valid PASS, passed independent verification, exposed 21 correctly associated history entries and reconciled 13,092 input plus 194 output tokens to 13,286 total at calculated USD 0.026960.
Provenance and integrity
- Release commit:
b51623dae1b764a31198424e8fc6ea9076d04089 - Qualified RC evidence checkpoint:
fa112f3f9e470041d22a0e91b93543ba946cbd62 - Qualified implementation commit:
9be253fb06f97ae0c010d2c26f0f74a263338ee4 - Package SHA-256:
d4c755aed3c73def1eb60275f58ae84b9ec26796e7bb744da4be901a74d362ef - Package SHA-512:
08c790a52791bd067756f09444599c61b09ab548d5a512f4a6bf516aa845f994f4d8d16b555ba8aba5a470b2b3eadf13a975ea070ed2281b0eb92fb5e8ab1395 - History qualification video SHA-256:
bb885f3b3a427c2ac49d50e7fd7143f6862a9987ccd4c44298da51d318421e2e - Candidate identity video SHA-256:
e02fb8790242642b76597212e4db4c094d6b61ea0470bc3e3348d491936ed93a - Full release regression: 718/718 passed
- Markdown links: 120 files, zero broken local links
Upgrade
git fetch --tags
git checkout v3.8.2
npm install --no-package-lock --ignore-scripts
npm run check
agent-control --versionInstalling this source package starts no service, changes no live configuration, authenticates no provider and enables neither Spark nor a Saved Job. The immutable v3.8.1 tag remains the previous source rollback point; restore the operator's pre-upgrade state backup before running the older version.