[prakashNalla]

What does this change?

405 responses now include Allow: POST, OPTIONS, the same methods the preflight sends in Access-Control-Allow-Methods. Both paths are covered: fetchChatResponse in http.ts (Vercel, Cloudflare, and the session endpoint, which is routed after the method check) and the 405 branch in the Express adapter. The 405 row in protocol.mdx mentions the header, and there's a patch changeset for @chatcops/server.

Closes #431

How I tested this

The existing "returns 405" tests in tests/adapters/vercel.test.ts, cloudflare.test.ts and express.test.ts now also check the Allow header. With the two source changes reverted, those 3 tests fail.

• pnpm -r build and pnpm -r typecheck: pass
• pnpm test: 129 files passed (5 skipped), 1748 tests passed
• pnpm test:coverage: passes
• pnpm lint: passes
• pnpm docs:check: 132 TypeScript blocks checked

AI assistance

Claude helped me w/ understand the issue

Checklist

• This PR targets dev
• I was assigned the linked issue
• pnpm -r build, pnpm test and pnpm -r typecheck pass locally
• Tests added or updated where it makes sense
• For a bug fix: the new test fails without my change
• Changeset added (pnpm changeset) if this changes core, widget or server
• Docs updated if behavior or options changed

[anurag629]

Thanks, this is right. Both 405 paths get the header, and it matches the preflight's methods. I merged it with current dev locally: build, typecheck, test:coverage, lint (same warnings as dev) and docs:check pass, and the three adapter tests fail with the two source lines reverted. Merging once CI is green on the updated branch.

[anurag629]

Merged, thanks @prakashNalla. It goes out with the next server release.