diff --git a/docs/integrations/openai-compatible-chat.md b/docs/integrations/openai-compatible-chat.md index 79c01c0..c05176d 100644 --- a/docs/integrations/openai-compatible-chat.md +++ b/docs/integrations/openai-compatible-chat.md @@ -70,7 +70,9 @@ and numeric `usage`; unrelated fields and account limits are ignored. This is only a minimal identifying subset of OpenRouter's documented [current-key response](https://github.com/OpenRouterTeam/docs/blob/main/api_reference/limits.mdx#checking-your-limits), not validation of the full account document. Other statuses and unrecognized -200 responses do not establish acceptance. +200 responses do not establish acceptance. A 200 response exceeding the bounded +recognition allowance reports `authentication_response_limit_exceeded`, leaving +credential acceptance unknown; see the [public reason](../../smoke_diagnostics.go). Diagnostic HTTP evidence describes the last request observed at Promptkit's RoundTripper boundary and any response associated with it. It includes the diff --git a/docs/roadmap/implementation.md b/docs/roadmap/implementation.md index 84e9fea..e67a0bf 100644 --- a/docs/roadmap/implementation.md +++ b/docs/roadmap/implementation.md @@ -860,6 +860,23 @@ post-change measurements are recorded without new performance guarantees, and no unapproved feature/policy/dependency changes or temporary harnesses are left in the repository. Follow normal commit policy; release preparation remains separate. +Completion: all catalog entries are covered by the implementation and focused +evidence recorded above, including comparable measurements for the selected +optimizations. With Go 1.27.3, `GOTOOLCHAIN=local`, and `GOWORK=off`, the full +offline `go test -race ./...` and `go vet ./...` passed. Tracked Go files are +formatted; the diff has no whitespace errors; local Markdown targets and headings +in changed documentation were checked. No benchmark overlays were retained in +the repository. Release preparation, version selection, tagging, and publication +remain separate work. + +Migration summary: successful artifact readers transfer returned mutable storage; +convenience sources use ConfigKit's supported value forms; JSON Schemas must be +self-contained; authentication overflow has an explicit diagnostic reason; and +opaque prompt definition hashes may change, requiring cross-version caches or +comparisons to be refreshed. See the [consumer guide](../consumers/pkg-promptkit.md), +[migration guidance](../consumers/configuration-migration.md), and +[format reference](../formats.md) for the applicable contracts. + ## Catalog Coverage | Catalog finding | Owning stages |