feat(protocol): AXP Session schemas + optional session_id linkage (D-030)#38
Merged
Merged
Conversation
… (D-030)
New protocol schemas: session.envelope/lifecycle/event v1. Session is a
first-class orchestrator separate from Intent; its lifecycle is bidirectional
(RESOLVED->OPEN), deliberately NOT the forward-only Intent enum (D-031).
Additive, backward-compatible (v1 line unchanged): optional session_id on
intent.lifecycle/event/envelope + message.envelope.v3; parent_intent_id on
intent.lifecycle. No required field added, no enum changed.
New public_api: api.sessions.{create.request,create.response,get.response,
events.list.response,messages.append.request,list.response} v1.
Contract tests + schema-versioning-rules + public-api-schema-index updated.
Coordinated with axme-control-plane PR (protocol filename regex accepts
session.*). Merge this PR first.
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
1 participant
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.
What
Adds the Session entity to the AXP protocol (anti-messenger MVP, plan stage A1).
New protocol schemas
session.envelope.v1.json,session.lifecycle.v1.json,session.event.v1.jsonSession is a first-class orchestrator, separate from Intent. Its lifecycle is bidirectional (
OPEN/WAITING_OWNER/RESOLVED/CLOSED/PRUNED,RESOLVED→OPENon visitor return) and deliberately does not reuse the forward-only Intent enum (D-031).Additive, backward-compatible (v1 line unchanged)
session_idonintent.lifecycle/intent.event/intent.envelope+message.envelope.v3parent_intent_idonintent.lifecycleNew public API schemas
api.sessions.{create.request,create.response,get.response,events.list.response,messages.append.request,list.response}.v1.jsonDocs / tests
docs/schema-versioning-rules.md+docs/public-api-schema-index.mdupdatedtests/test_schema_contracts.py: new Session structural + additive-linkage contract testsVerification
python scripts/validate_schemas.py→ passedpytest tests/test_schema_contracts.py tests/test_validate_schemas.py→ 107 passedvalidate_schemas.py+test_schema_contracts.py/test_public_api_schema_contracts.pyrun against this branch → passedMerge order (coordinated PR train)
Merge this PR first. A companion axme-control-plane PR extends the protocol filename regex to accept
session.*and adds payload contract tests; its CI stays red until this merges (it validates against axp-specmain).