Repository navigation
Sunset header and feature-flagged retirement for legacy routes #266
Description
Problem Statement. Legacy /ai/* paths exist alongside /v1/ai/*. The webhook in
swagger.config.ts says "deprecated" but no Sunset header is emitted.
Why it matters. Consumers (the mobile + frontend) get no machine-readable signal to
migrate.
Technical Context. RFC 8594 Sunset and Deprecation headers.
Expected Outcome.
- Legacy handlers emit
Sunset: <RFC 1123 date>(e.g.Sunset: Wed, 01 Oct 2026 00:00:00 GMT) andDeprecation: true. - A configurable
LEGACY_RETIREMENT_DATEenv renders the header.
Acceptance Criteria.
- A test asserts both headers on every
/ai/*route. - Backwards compatibility preserved (still 308s to /v1/ai/*).
Files or modules likely to be affected.
app/ai-service/main.py.
Difficulty. Easy
Estimated effort. XS
Backlog item #58 from `docs/maintainer-issue-backlog.md.
Activity
AugistineCreates commentedon Jul 15, 2026
I would like to work on this issue because i am confident i can resolve the issue, having worked on and resolved similar issues. my eta is 4 hours
grantfox-oss commentedon Jul 15, 2026
🦊 GrantFox — @AugistineCreates has been assigned to this issue as part of the Official Campaign | FWC26 campaign!
Next steps:
Closes #266)Good luck! Track your progress on GrantFox.
grantfox-oss commentedon Jul 17, 2026
🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!
@AugistineCreates's PR #331 was approved and merged by @kilodesodiq-arch.
🏆 @AugistineCreates: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,914 total points). Track your full progress on GrantFox.
👏 Great work, @AugistineCreates! Keep contributing to ChainForgee.