8000 test(agentcore): add storage and wire conformance coverage by Fodesu · Pull Request #99 · felinics/twilight · GitHub
[go: up one dir, main page]

Skip to content

test(agentcore): add storage and wire conformance coverage - #99

Merged
Fodesu merged 3 commits into
feat/agent-runtime-integration-testsfrom
feat/agent-runtime-storage-tests
Oct 3, 2026
Merged

Fodesu merged 3 commits into
feat/agent-runtime-integration-testsfrom
feat/agent-runtime-storage-tests

Conversation

@Fodesu
@Fodesu Fodesu commented Oct 3, 2026 •
Copy link
Copy Markdown
Member

Summary

Adds storage and protocol conformance tests for the session, Run wire, settlement, redispatch, PostgreSQL, and filestore layers. The suite makes adapter behavior comparable by driving each implementation through the same public contract.

Coverage

The session-store harness checks commit ordering, idempotent CommitIDs, projection snapshots, inherited history, fencing, replay, and state conflict behavior. Filestore tests apply the same session conformance expectations to its file-backed implementation. PostgreSQL coverage verifies the adapter’s integrated schema and reopen behavior, while the retention tests exercise persisted content and projection retention rules.

Run wire tests cover codec round trips, canonical JSON, snapshots, stable digests, and rejection of malformed or mismatched payloads. Settlement tests verify terminal result handling at the Run boundary. Redispatch tests extend the earlier fold coverage through the adapter-facing test path, including planned-versus-dispatched attempts, given-up state, replay, and epoch fencing.

The harnesses deliberately test invariants at the port boundary: a retry must return the existing result rather than append a duplicate; a stale owner must be fenced; a projection snapshot must reload as the same state; and a dispatch decision recorded before a crash must remain recoverable. The PostgreSQL test additions also verify the concrete adapter’s behavior rather than relying only on the in-memory map implementations.

Scope

This is test-only coverage. It does not alter storage protocols or production state transitions.

@Fodesu
Fodesu added this pull request to stack #105 October 3, 2026 12:27
@Fodesu Fodesu changed the title feat/agent runtime storage tests test(agentcore): add storage and wire conformance coverage Oct 3, 2026
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage-tests branch 2 times, most recently from 9d3ea58 to 25d87f6 Compare October 3, 2026 14:55
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage-tests branch from 25d87f6 to f60d4ec Compare October 3, 2026 15:35
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage-tests branch from f60d4ec to ad0b5ec Compare October 3, 2026 15:47
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage-tests branch from ad0b5ec to 2909d3a Compare October 3, 2026 16:05
@Fodesu
Fodesu removed this pull request from stack #105 October 3, 2026 16:13
@Fodesu
Fodesu added this pull request to stack #107 October 3, 2026 16:16
@Fodesu
Fodesu removed this pull request from stack #107 October 3, 2026 16:34
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage-tests branch from 2909d3a to 219643c Compare October 3, 2026 16:37
@Fodesu
Fodesu added this pull request to stack #108 October 3, 2026 16:37
@Fodesu
Fodesu removed this pull request from stack #108 October 3, 2026 16:51
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage-tests branch from 219643c to dc5cec2 Compare October 3, 2026 16:54
@Fodesu
Fodesu added this pull request to stack #110 October 3, 2026 16:55
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage-tests branch from dc5cec2 to aba312f Compare October 3, 2026 17:04
@Fodesu
Fodesu force-pushed the feat/agent-runtime-storage-tests branch from aba312f to 749df92 Compare October 3, 2026 17:11
@Fodesu
Fodesu marked this pull request as ready for review October 3, 2026 17:20
@Fodesu
Fodesu merged commit 645c4f7 into main Oct 3, 2026
8 checks passed
@Fodesu
Fodesu deleted the feat/agent-runtime-storage-tests branch October 5, 2026 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0