Skip to content

feat(test): assert warm runtime identity in contract matrix #337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ScriptedAlchemy merged 2 commits into from
Sep 3, 2026
Merged

feat(test): assert warm runtime identity in contract matrix #337

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
36f52c5
feat(test): assert warm runtime identity in contract matrix
ScriptedAlchemy Sep 2, 2026
28124ce
fix(test): scope runtime identity to event owner
ScriptedAlchemy Sep 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/warm-runtime-contract-identity.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'agent-bundle': patch
---

Assert stable warm-runtime identity and compiled state catalogs at packed and installed-host contract-matrix boundaries.
19 changes: 13 additions & 6 deletions packages/agent-bundle/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -428,7 +428,9 @@ idempotent commit replay, and typed budget rejection. A caller-supplied
same-store `restart` callback adds durability evidence at that boundary;
without one the check is honestly `not-applicable`. Packed callers should wire
that callback into the existing packed journey's restart rather than creating
a second pack/build/install path.
a second pack/build/install path. A lifecycle fixture's optional
`state.catalog` assertion pins its declared id and lifetime to the compiler
manifest used by that same mounted-state replay.

**`runInstalledHostContractMatrix` (`host-install`)** runs against an
already-open session from `openInstalledHostMcpServer`. The opener reads the
Expand All @@ -440,12 +442,16 @@ running-process versions separately and fails closed when any value is missing
or differs. Metadata records the host binary version when observed, adapter
revision, manifest/schema digest, and framework version. Module-backed checks
remain honestly not-applicable because loading project modules would cross back
into the source/build tree.
into the source/build tree. When the compiled manifest contains event routes,
the packed and installed-host boundaries sample the read-only event-runtime
status before and throughout sequential matrix events. The
`runtime-instance-identity` check fails if the warm `instanceId` changes, the
artifact epoch drifts, or availability degrades to `runtime-restarted` /
`runtime-unavailable`.

No matrix boundary proves browser App HTML, artifact-rebuild replay,
state-lifetime catalog identity, or running-process identity beyond what the
live MCP session reports; deeper runtime-instance introspection depends on
#269.
No matrix boundary proves browser App HTML or artifact-rebuild replay.
In-memory runs and compiled artifacts without event routes report runtime
identity as honestly `not-applicable`.

When the advertised input schema declares `additionalProperties: false`, plain
`z.object` tool routes may still strip unknown keys without a protocol failure.
Expand All @@ -472,6 +478,7 @@ await runContractMatrix({

// Packed: pass an already-open session and a manifest compiled before source removal.
await runPackedContractMatrix({
eventRuntime: { endpointId: packedEventRuntimeEndpointId },
session: packedSession,
manifest: compiledManifest,
fixtures: { /* same shape */ },
Expand Down
Loading
Loading