fix(api): restack unsupported exchange method short-circuit on current main - #206
fix(api): restack unsupported exchange method short-circuit on current main#206seonghobae wants to merge 5 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Superseded by fresh protected-main successor #214 after exact byte/scope comparison. Fresh identities immediately before this closure decision:
Preservation proof:
Closing #206 unmerged removes the stale parallel writer without discarding unique API behavior or tests. #214 remains the sole current-main owner; its branch is otherwise left untouched in this invocation because its head moved during the fresh writer-state sweep. |
Fresh protected-main successor for #101 on exact base
1a8a77d67f61a2c61e88974be9206a91d19acdf4. No predecessor checks, reviews, scanner output, model judgment, or production evidence transfers.Current test-first RED head
74ee8801620e5189ee3ac0c8ededd049c638365dadds only the executable/exchangemethod contract. Current protectedsrc/entrypoint.tsenters OIDC envelope/body and GitHub egress-configuration handling before rejecting unsupported methods; the regression requires GET/HEAD/PUT/PATCH/DELETE/OPTIONS to return the public 405 contract before credential egress configuration and distributed limiter side effects, with HEAD bodyless.Selected bounded GREEN after RED is proven: short-circuit unsupported methods at the outer
/exchangeentrypoint while preserving POST behavior, security/cache/trace headers, and every credential-bearing path.Historical #101 remains open until this current-main successor proves and preserves the complete two-file contract.