-
Notifications
You must be signed in to change notification settings - Fork 10
Extract @domscribe/protocol package (RCP versioning unit) #32
Copy link
Copy link
Open
Labels
enhancementNew feature or requestNew feature or requestpriority:P0Urgent — security, data loss, or critical regressionUrgent — security, data loss, or critical regressionrcpRuntime Context Protocol — public spec workstreamsRuntime Context Protocol — public spec workstreamstech-debtInternal refactor / architecture work driven by a strategic bet, not user-reportedInternal refactor / architecture work driven by a strategic bet, not user-reported
Milestone
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestpriority:P0Urgent — security, data loss, or critical regressionUrgent — security, data loss, or critical regressionrcpRuntime Context Protocol — public spec workstreamsRuntime Context Protocol — public spec workstreamstech-debtInternal refactor / architecture work driven by a strategic bet, not user-reportedInternal refactor / architecture work driven by a strategic bet, not user-reported
Type
Fields
Give feedbackNo fields configured for issues without a type.
Sprint 2371 — task T1 (Batch A)
Implements decision in RFC 0001: extract the agent-facing contract into a new
@domscribe/protocolpackage, versioned independently from implementation packages, so RCP v1.0.0 can be published with a meaningful SemVer stamp.Scope
@domscribe/protocolunderpackages/ManifestEntry,RuntimeContext,Annotation, error envelopes (currently in@domscribe/core)relay,runtime,mcpto depend on@domscribe/protocolfor shapes and names@domscribe/corekeeps utilities (PII redaction, ID generation, error system)TECHNICAL_SPEC.md §2.3module boundariesAcceptance
packages/protocol/exists with its ownpackage.json, builds independently vianx build protocol@domscribe/coreno longer exports the relocated schemasrelay,runtime,mcp, plugins) import from@domscribe/protocolpnpm run build:allpasses@domscribe/protocolbeyond the relocated surface (no scope creep)Blocks
T2 (tool-name normalization lands in this package), T4 (spec doc references this package).
Out of scope
FrameworkAdapterSDK extraction — separate follow-on RFC per RFC 0001 explicit deferral