add(resilience): Deprecation + Sunset page (RFC 9745/8594) + ai.txt 410 tombstone#86
Merged
Merged
Conversation
New spec page documenting the Deprecation (RFC 9745) and Sunset (RFC 8594) response headers plus the rel=deprecation / rel=sunset / rel=successor-version link relations, status optional. Ships the worked example in the same PR (the 'ship it before you spec it' rule): functions/_middleware.ts now serves the retired /.well-known/ai.txt as 410 Gone carrying Deprecation (@1780012800 = 2026-05-29), Sunset (Fri, 29 May 2026), and a rel=deprecation Link back to the page — exactly the post-sunset 410 case RFC 8594 describes. Sunset is not earlier than Deprecation, per RFC 9745. Wires relatedSlugs on error-pages and redirects; adds an 'added' changelog entry and the OG images (new page + four count-driven). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
9885ff0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c53d9e78.specification-website.pages.dev |
| Branch Preview URL: | https://standards-scan-deprecation-s.specification-website.pages.dev |
# Conflicts: # public/og-default.png # public/og/checklist.png # public/og/spec.png
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Specs and ships the Deprecation + Sunset convention in one PR.
Spec page — new
resiliencepage, Deprecation and Sunset,status: optional. DocumentsDeprecation(RFC 9745, a structured-field date — past = deprecated then, future = will be),Sunset(RFC 8594, the removal instant;Sunsetmust not be earlier thanDeprecation), and therel="deprecation"/rel="sunset"/rel="successor-version"link relations. Covers the post-sunset410 Gonecase explicitly.Shipped worked example —
functions/_middleware.tsnow serves the retired/.well-known/ai.txtas410 Gonecarrying:Deprecation: @1780012800(2026-05-29, the day it was removed)Sunset: Fri, 29 May 2026 00:00:00 GMTLink: <…/spec/resilience/deprecation-and-sunset/>; rel="deprecation"; type="text/html"This is exactly the post-sunset
410scenario RFC 8594 describes, andSunsetis not earlier thanDeprecationper RFC 9745.ai.txtwas genuinely retired (2026-05-29), so this commits us to nothing new — the dates are historical, and a 410 tombstone is a cleaner retirement than a bare 404.Why this satisfies "ship it before you spec it"
Unlike the OAuth pages, this convention is one the site can and now does implement, so per CLAUDE.md the same PR makes the site emit the headers. The middleware was already the response-mutation layer (it sets
Vary,Server-Timing, does content negotiation); the tombstone slots in as one branch before the existing ones./.well-known/ai.txtis not excluded inpublic/_routes.json, so the worker runs on it.Notes
/.well-known/ai.txtin backticks, not as a Markdown link — it's a middleware-only path that wouldn't resolve in the static Internal-links CI check.Linkheader or api-catalog change: therel="deprecation"link is per-path on the tombstone, not a site-wide discoverable resource.optional— relevant only to sites retiring endpoints. Notrecommended.npm run buildpasses locally (157 pages, integrity green); eslint + prettier pass on the middleware via the pre-commit hook. SKILL.md "140+ pages" still accurate, no digest change.Primary sources: RFC 9745, RFC 8594, IANA Link Relations Registry. Opened as draft by the daily standards scan, following the in-session decision to spec and ship this (option 1: the ai.txt tombstone).
🤖 Generated with Claude Code