2.6 KiB
2.6 KiB
Deferred items
Out-of-scope discoveries made while executing phase 19.7 plans. Nothing here was changed by the plan that recorded it.
Deferred Items
- Pre-existing
gofmtdrift in cabana (found during 19.7-01 Task 1) status: open What:gofmt -l modules/cabanalistsaccount_tokens.go,account_tokens_test.go,field_trigger_smoke_test.go,token_postgres_smoke_test.go,token_routes_test.goandtoken_scopes_test.goas unformatted before this plan touched the module (alignment of map literals and struct tags). Left as is: reformatting would add diff noise unrelated to the plan (a whole-filegofmt -wontoken_routes_test.gorewrote 132 lines and was reverted). A one-linegofmt -won those six files in astyle(cabana)commit of its own fixes it. AdminRecordAction.Promptacceptance grep counted twoprompt,omitemptytags inschema_types.go(found during 19.7-01 Task 4) status: resolved What: the second match is the pre-existingFormField.PromptJSON tag atschema_types.go:376, not a duplicate of the newRecordAction.Prompt; the criterion's "prints 1" was written without that line in mind. No change needed.- Stateful pier sessions cannot carry the SDK's protocol-version context value (found during 19.7-02 Task 3)
status: open
What: go-sdk v1.8.0's
StreamableHTTPHandler.ServeHTTPstores theMcp-Protocol-Versionheader under an unexported context key that the transport'sservePOST/serveGETread; pier's own session router (needed for Redis-shared sessions, D-25) servesStreamableServerTransportdirectly and cannot set that key, so stateful streams run with the SDK's 2025-03-26 defaults for stream close/reconnect hints and the JSON-RPC batch rule (lenient, spec-compliant for older clients; 2026-07-28 clients go through the SDK's own stateless handler). Revisit if a later SDK exports the key or a transport-level setter; plan 05 may add a test pinning the behaviour. notifications/initializedlanding on another instance thaninitialize(found during 19.7-02 Task 3) status: open What: the session state is persisted afterinitializeand again after the client'sinitializednotification; when a load balancer sends the notification to a second instance, the first instance's local copy keepsInitializedParamsnil and refuses calls until that copy is dropped (session end, revocation or process restart) while the second instance serves them. Sticky sessions or a per-request re-read of the storedinitializedflag would close the gap; not needed for the single-instance demo.