Revert "Add IdentityServer 8.0 documentation"

This reverts commit e980773.

# Conflicts:
#	.weave/plans/is8-docs.md

Author: damianh

.weave/plans/is8-docs.md

@@ -14,7 +14,6 @@ redirect_from:
 
 Duende.BFF can be extended in the following areas
 
-- custom logic at the session management endpoints
-- custom logic and configuration for HTTP forwarding
-- custom data storage for server-side sessions and access/refresh tokens
-- [enriching claims returned from the user endpoint](/bff/extensibility/user-endpoint-claims/) using `IUserEndpointClaimsEnricher` (added in v8.0)
+* custom logic at the session management endpoints
+* custom logic and configuration for HTTP forwarding
+* custom data storage for server-side sessions and access/refresh tokens

astro/src/content/docs/bff/extensibility/index.md

@@ -16,8 +16,6 @@ When a user logs in, their identity is established and persisted across requests
 
 When using IdentityServer without ASP.NET Identity, the default cookie scheme is named `"idsrv"`, though we recommend using the constant `IdentityServerConstants.DefaultCookieAuthenticationScheme` in your code if you ever need it.
 
-Starting in **v8.0**, the default cookie name (not the scheme name) has changed to `"__Host-idsrv"` to improve security. The scheme name remains `"idsrv"`. See [Cookie Name Migration (v8.0)](#cookie-name-migration-v80) below for upgrade instructions.
-
 The default cookie scheme is configured by default in `AddIdentityServer()`, which sets up the cookie authentication handler with this scheme name. This cookie is essential for:
 
 - maintaining the user's authenticated session
@@ -41,7 +39,7 @@ services.ConfigureApplicationCookie(options =>
 {
     // The default ("Identity.Application")
     options.Cookie.Name = IdentityConstants.ApplicationScheme;
-
+    
     // Configure other options here...
     options.ExpireTimeSpan = TimeSpan.FromHours(1);
     options.SlidingExpiration = true;
@@ -59,8 +57,6 @@ This allows your login logic to read the claims from the external provider befor
 
 IdentityServer always uses the `"idsrv.external"` scheme here, available in the `IdentityServerConstants.ExternalCookieAuthenticationScheme` constant.
 
-Starting in **v8.0**, the default cookie _name_ for this scheme has changed to `"__Host-idsrv.external"` (previously `"idsrv.external"`). See [Cookie Name Migration (v8.0)](#cookie-name-migration-v80) below for upgrade instructions.
-
 ### Check Session Cookie
 
 IdentityServer session management requires a separate cookie to monitor the session state without sending the large authentication cookie.
@@ -70,59 +66,6 @@ The [User Session Service](/identityserver/reference/services/user-session-servi
 
 Note this cookie is not marked as `HttpOnly`, so it can be accessed in client-side code. The JavaScript code that is required to check user sessions in the background also requires access to this cookie, and needs it to be `HttpOnly`.
 
-## Cookie Name Migration (v8.0)
-
-In IdentityServer v8.0, the default cookie **names** changed to use the `__Host-` prefix:
-
-| Cookie               | Old name (v7.x)  | New name (v8.0)         |
-| -------------------- | ---------------- | ----------------------- |
-| Primary auth cookie  | `idsrv`          | `__Host-idsrv`          |
-| External auth cookie | `idsrv.external` | `__Host-idsrv.external` |
-
-Note: the authentication **scheme names** (`"idsrv"` and `"idsrv.external"`) are unchanged.
-
-### Why `__Host-`?
-
-The `__Host-` prefix is a browser security feature that restricts a cookie to:
-
-- HTTPS-only connections
-- `Path=/` (the entire site)
-- No `Domain` attribute (preventing subdomain sharing)
-
-This provides defense-in-depth against cookie theft and session fixation attacks.
-
-### Migrating Existing Sessions
-
-To avoid invalidating existing user sessions when upgrading, use the migration middleware to
-transparently accept both old and new cookie names. Add it to `Program.cs` **before**
-`UseIdentityServer()`, calling it once per cookie:
-
-```csharp
-// Program.cs — add BEFORE UseIdentityServer()
-app.MigrateIdentityServerCookieName("idsrv", "__Host-idsrv");
-app.MigrateIdentityServerCookieName("idsrv.external", "__Host-idsrv.external");
-app.UseIdentityServer();
-```
-
-When a user visits with an old cookie, the middleware transparently re-issues it under the new
-name. Once all active sessions have been re-issued, you can remove the middleware calls.
-
-### Configuring Cookie Names
-
-Override the default names using `AuthenticationOptions`:
-
-```csharp
-builder.Services.AddIdentityServer(options =>
-{
-    // Restore legacy names if needed (e.g., staged migration)
-    options.Authentication.CookieName = "idsrv";
-    options.Authentication.ExternalCookieName = "idsrv.external";
-});
-```
-
-See the [upgrade guide](/identityserver/upgrades/v7_4-to-v8_0/#cookie-names-changed-to-__host--prefix)
-for full migration instructions.
-
 ## Common Pitfalls
 
 - **Mixing Schemes:** Attempting to `SignOutAsync("idsrv")` when ASP.NET Identity is in use will have no effect on the actual `"Identity.Application"` cookie, leaving the user logged in. Always use the constants or the helper services (like `SignInManager`) that match your configuration.

astro/src/content/docs/bff/extensibility/user-endpoint-claims.md

@@ -33,11 +33,4 @@ systems (APM). They used to have their own different APIs so IdentityServer only
 that could be used to call the APM's APIs. Thanks to OpenTelemetry there is now a standardized
 way to emit diagnostic information from a process. The events may eventually be deprecated and removed.
 
-[Read More](/identityserver/diagnostics/events.md)
-
-## Conformance Report
-
-IdentityServer can generate a conformance report that assesses your configuration against OAuth 2.1
-and FAPI 2.0 specifications.
-
-[Read More](/identityserver/diagnostics/conformance-report/)
+[Read More](/identityserver/diagnostics/events.md)