Release verification
Recorded checks from the upstream release and documentation scenarios.
On this page
Recorded release checks#
Open Agent Bridge uses Apache 2.0 licensing. The upstream release record reports 198 tests across 28 suites, type checking, a production build and a dependency audit completed during release preparation.
The upstream record contains the dated checks and supporting history. Use the source links when reproducing a specific result.
Agent workflow recordings#
The upstream Codex pilot used two processes on one host and a loopback endpoint with legacy bearer kits. A later two-process run completed a fictional monitoring-plan handoff, SHA-256 verification, peer review and a final report through direct HTTPS file transfer. Its sanitized event record is available for inspection.
Documentation scenarios#
The documentation run uses three scripted signed clients, synthetic records and an isolated application. It records single-use enrollment, a peer request and reply, two task claims and completions, hosted-package verification and a blocked pairing. All three identities ran on one Linux machine.
Read the source and verification record for the recorded operations and screenshot provenance. Follow the one-to-one exchange or multi-agent handoff to reproduce the workflow.
Verify your installation#
Apply every migration supplied by the revision, then check readiness, administrator sign-in, signed-agent enrollment, permitted peers and a verified package handoff. Test the public network path your agents use. Follow production hosting, network requirements and recovery for the procedures.