3 Commits

Author	SHA1	Message	Date
glm-5.1	51f233582d	Align call-protocol.md and api-surface.md with envelope model ... Remove supersession note from response-envelopes.md — both dependent docs now reflect the ResponseEnvelope system. Key changes: - call-protocol.md: CallHandler wraps and publishes (not handlers), call.responded.output uses ResponseEnvelopeSchema, respond() enforces envelope guard, call() resolves ResponseEnvelope, subscribe() yields ResponseEnvelope, references shared result pipeline - api-surface.md: execute() returns Promise<ResponseEnvelope<TOutput>>, OperationEnv functions return Promise<ResponseEnvelope>, CallHandler calls handler directly and applies shared pipeline, respond() requires ResponseEnvelope, added Response Envelope Types and Utilities sections - response-envelopes.md: removed supersession note, added Shared Result Pipeline section (detect→wrap→normalize→validate), unified execute() and CallHandler integration points to reference shared pipeline, updated migration checklist to mark doc changes complete	2026-05-10 08:37:40 +00:00
glm-5.1	81f89e0f6c	Restructure response envelopes architecture: split ADR from spec, add Value.Cast composability, document implementation gaps ... - Split monolithic 680-line response-envelopes.md into focused ADR-005 (decisions/005-response-envelopes.md, 152 lines) and specification (response-envelopes.md, 441 lines) - ADR-005: consolidate 10 inline ADRs into coherent decision record with rationale for data+meta envelope shape, handler responsibility shift, string discriminant detection, and composability analysis - Spec: types, factory functions, integration points, constraints, migration checklist, and open questions - Add MCP outputSchema extraction (2025-06-18+ spec) with FromSchema conversion and<Value.Cast()> normalization for structuredContent - Add current-source-vs-spec implementation gap tables to registry, call, mcp adapter, and openapi adapter integration points - Update adapters.md: from_mcp outputSchema extraction, structuredContent handling, isError non-throw behavior, Value.Cast() for data normalization - Add open questions: serving directionality, JSON.stringify in MCP content, outputSchema extraction completeness, respond() visibility - Note: existing call-protocol.md and api-surface.md describe pre-envelope behavior; this spec supersedes them until updated per migration checklist	2026-05-10 07:56:27 +00:00
glm-5.1	a7e6cc94c7	Add response envelopes architecture spec (ADR-005 through ADR-014) ... Introduce ResponseEnvelope as a first-class concept for uniform operation result handling across MCP, OpenAPI, and local adapters. Key decisions: - ResponseEnvelope<T> wraps every result with typed metadata (LocalResponseMeta, HTTPResponseMeta, MCPResponseMeta) - CallHandler becomes sole publisher of call.responded (handler responsibility shift from publish-to-return) - Envelope detection via closed-set string discriminant (isResponseEnvelope) — no Symbols, JSON-serializable - MCP isError:true no longer throws; wraps in envelope with meta.isError flag preserving error content for consumers - outputSchema validates envelope.data, not the full envelope - PendingRequestMap.respond() validates envelope at runtime - Factory functions (localEnvelope, httpEnvelope, mcpEnvelope) ensure consistent construction - Breaking change: execute() returns ResponseEnvelope<TOutput>, call.responded.output is ResponseEnvelopeSchema - No Client abstraction yet (ADR-014)	2026-05-10 04:58:05 +00:00