refactor(resource): extract provider protocol crate - #398
Merged
schickling-assistant merged 2 commits intoAug 31, 2026
Merged
Conversation
schickling-assistant
force-pushed
the
schickling-assistant/2026-08-31-resource-protocol-consolidation
branch
from
August 30, 2026 22:46
7762fdb to
dac0662
Compare
schickling-assistant
changed the base branch from
main
to
schickling-assistant/2026-08-31-st2-health-foundation
August 30, 2026 22:47
schickling-assistant
force-pushed
the
schickling-assistant/2026-08-31-resource-protocol-consolidation
branch
2 times, most recently
from
August 30, 2026 23:07
9a3aae2 to
88fbe48
Compare
schickling-assistant
marked this pull request as ready for review
August 30, 2026 23:16
schickling-assistant
force-pushed
the
schickling-assistant/2026-08-31-resource-protocol-consolidation
branch
from
August 31, 2026 00:04
88fbe48 to
232670a
Compare
Base automatically changed from
schickling-assistant/2026-08-31-st2-health-foundation
to
main
August 31, 2026 01:02
agent-identity: dev3.direct.omp.2cshu64q agent-persona: generalist agent-supervisor: unavailable agent-tool: OMP agent-tool-version: 18.0.9 agent-runtime: OMP 18.0.9 tooling-profile: dotfiles@b607597
agent-identity: dev3.direct.omp.2cshu64q agent-persona: generalist agent-supervisor: unavailable agent-tool: OMP agent-tool-version: 18.0.9 agent-runtime: OMP 18.0.9 tooling-profile: dotfiles@b607597
schickling-assistant
force-pushed
the
schickling-assistant/2026-08-31-resource-protocol-consolidation
branch
from
August 31, 2026 01:02
232670a to
66fe50e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Resource wire messages and codecs were owned by the
st2supervisor crate, forcing every native provider runtime to depend on supervisor implementation details and encouraging duplicate protocol copies.Goal
Make one upstream crate the wire authority while preserving the existing
st2API surface and current native session-driver graph authority.Decisions
st2-resource-protocolas a wire-only crate owning resource message types, validation, and JSON-line codecs.st2public imports working through re-exports; no parallel protocol or compatibility shim is introduced.Verification
nix develop -c env CI=1 cargo test -p st2-resource-protocol— 7 passed.7b14815b…) and Admit codex-cli 0.151.0 #394 (af9e20ca…) are ancestors of88fbe48c1092129d059dc79ddd0b242c11127e49.Complexity
No additional runtime process or state owner is introduced. The new crate is a pure wire/codec boundary; the supervisor continues to own graph and session-driver behavior.
Concerns
None known.
Friction & bottlenecks
None.
Follow-ups
The dependent dotfiles stack consumes this exact upstream revision and owns the shared provider runtime plus thin resource adapters.
References
Posted on behalf of @schickling
agent_identitysessionagent_personaagent_supervisoragent_toolagent_tool_versionagent_runtimetooling_profile