Remove comments from backend and web-player source

Strip //, /* */ and XML doc comments from all backend .cs files, and
JS/TS/CSS/HTML comments from web-player source (.ts, .svelte, .css),
per the project's no-comments convention.

backend/Hosts/Musify.StreamingGateway/Authentication/TicketValidator.cs

@@ -6,10 +6,6 @@ using Musify.StreamingGateway.Configuration;
 
 namespace Musify.StreamingGateway.Authentication;
 
-/// <param name="Prefix">The storage key prefix the ticket authorizes reading from. Empty means the
-/// ticket was missing, malformed, expired, or otherwise invalid.</param>
-/// <param name="MaxBytes">When set, the caller is limited to the first <c>MaxBytes</c> bytes of the
-/// object — the anonymous preview fragment cap carried by the <c>maxBytes</c> claim.</param>
 public sealed record TicketValidationResult(string Prefix, long? MaxBytes)
 {
     public static readonly TicketValidationResult Invalid = new(string.Empty, null);

backend/Hosts/Musify.StreamingGateway/Middleware/TicketValidationMiddleware.cs

@@ -72,12 +72,6 @@ public sealed class TicketValidationMiddleware(
         await next(context);
     }
 
-    /// <summary>Rewrites the request's <c>Range</c> header so nothing past <paramref name="maxBytes"/>
-    /// is ever asked of the filer — this is what actually enforces the anonymous preview length,
-    /// downstream of the ticket carrying that cap. A request with no <c>Range</c> header (a plain,
-    /// whole-file GET) gets one synthesized, so the filer always responds with a bounded 206 instead of
-    /// streaming the full object. Returns false when the requested range starts at or past the cap, in
-    /// which case the caller should answer 416 directly instead of proxying anything.</summary>
     private static bool TryClampRange(HttpContext context, long maxBytes)
     {
         var rangeHeader = context.Request.Headers.Range;