Fix lint errors

Author: samkim

app/authzed/concepts/authzed-materialize/page.mdx

@@ -25,6 +25,7 @@ In summary, AuthZed Materialize allows you to:
 ## Limitations
 
 - Your schema can contain any of the following, but they cannot be on the path of your configured Materialize permissions or it will throw an error:
+
   - [Caveats]
   - [Wildcard] subject types
   - [.all intersections]

app/authzed/concepts/restricted-api-access/page.mdx

@@ -275,6 +275,7 @@ If you want to apply a configuration to an existing SpiceDB cluster without down
 2. Prepare the FGAM configuration YAML.
    You'll add the hashes that you generated in the previous step to the `hash` key in the `token` list for each respective token.
    This process heavily depends on what each client needs:
+
    1. You may want to start with FGAM tokens bound to a admin-like Role, since that's what the original PSKs effectively were.
       This is probably lower risk, and then from there you can move to start trimming down permissions.
    2. Or you may want to move directly to downscoped tokens for your individual services, creating the tokens you need.

app/spicedb/concepts/commands/page.mdx

@@ -27,13 +27,12 @@ A database that stores and computes permissions
 
 ### Children commands
 
-- [spicedb datastore](#reference-spicedb-datastore)	 - datastore operations
-- [spicedb lsp](#reference-spicedb-lsp)	 - serve language server protocol
-- [spicedb man](#reference-spicedb-man)	 - Generate man page
-- [spicedb serve](#reference-spicedb-serve)	 - serve the permissions database
-- [spicedb serve-testing](#reference-spicedb-serve-testing)	 - test server with an in-memory datastore
-- [spicedb version](#reference-spicedb-version)	 - displays the version of SpiceDB
-
+- [spicedb datastore](#reference-spicedb-datastore) - datastore operations
+- [spicedb lsp](#reference-spicedb-lsp) - serve language server protocol
+- [spicedb man](#reference-spicedb-man) - Generate man page
+- [spicedb serve](#reference-spicedb-serve) - serve the permissions database
+- [spicedb serve-testing](#reference-spicedb-serve-testing) - test server with an in-memory datastore
+- [spicedb version](#reference-spicedb-version) - displays the version of SpiceDB
 
 ## Reference: `spicedb datastore`
 
@@ -49,11 +48,10 @@ Operations against the configured datastore
 
 ### Children commands
 
-- [spicedb datastore gc](#reference-spicedb-datastore-gc)	 - executes garbage collection
-- [spicedb datastore head](#reference-spicedb-datastore-head)	 - compute the head (latest) database migration revision available
-- [spicedb datastore migrate](#reference-spicedb-datastore-migrate)	 - execute datastore schema migrations
-- [spicedb datastore repair](#reference-spicedb-datastore-repair)	 - executes datastore repair
-
+- [spicedb datastore gc](#reference-spicedb-datastore-gc) - executes garbage collection
+- [spicedb datastore head](#reference-spicedb-datastore-head) - compute the head (latest) database migration revision available
+- [spicedb datastore migrate](#reference-spicedb-datastore-migrate) - execute datastore schema migrations
+- [spicedb datastore repair](#reference-spicedb-datastore-repair) - executes datastore repair
 
 ## Reference: `spicedb datastore gc`
 
@@ -148,8 +146,6 @@ spicedb datastore gc [flags]
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
 
-
-
 ## Reference: `spicedb datastore head`
 
 compute the head (latest) database migration revision available
@@ -181,8 +177,6 @@ spicedb datastore head [flags]
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
 
-
-
 ## Reference: `spicedb datastore migrate`
 
 Executes datastore schema migrations for the datastore.
@@ -222,8 +216,6 @@ spicedb datastore migrate [revision] [flags]
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
 
-
-
 ## Reference: `spicedb datastore repair`
 
 Executes a repair operation for the datastore
@@ -317,8 +309,6 @@ spicedb datastore repair [flags]
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
 
-
-
 ## Reference: `spicedb lsp`
 
 serve language server protocol
@@ -342,20 +332,17 @@ spicedb lsp [flags]
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
 
-
-
 ## Reference: `spicedb man`
 
 Generate a man page for SpiceDB.
- The output can be redirected to a file and installed to the system:
+The output can be redirected to a file and installed to the system:
 
 ```
   spicedb man > spicedb.1
   sudo mv spicedb.1 /usr/share/man/man1/
   sudo mandb  # Update man page database
 ```
 
-
 ```
 spicedb man
 ```
@@ -368,8 +355,6 @@ spicedb man
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
 
-
-
 ## Reference: `spicedb serve`
 
 start a SpiceDB server
@@ -558,8 +543,6 @@ spicedb serve [flags]
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
 
-
-
 ## Reference: `spicedb serve-testing`
 
 An in-memory spicedb server which serves completely isolated datastores per client-supplied auth token used.
@@ -621,8 +604,6 @@ spicedb serve-testing [flags]
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
 
-
-
 ## Reference: `spicedb version`
 
 displays the version of SpiceDB
@@ -644,6 +625,3 @@ spicedb version [flags]
       --log-level string     verbosity of logging ("trace", "debug", "info", "warn", "error") (default "info")
       --skip-release-check   if true, skips checking for new SpiceDB releases
 ```
-
-
-

components/scripts.tsx

@@ -1,14 +1,14 @@
-'use client';
+"use client";
 
-import inEU from '@segment/in-eu';
-import { usePathname, useSearchParams } from 'next/navigation';
-import { Router } from 'next/router';
-import Script from 'next/script';
-import posthog from 'posthog-js';
-import { Suspense, useEffect, useState } from 'react';
+import inEU from "@segment/in-eu";
+import { usePathname, useSearchParams } from "next/navigation";
+import { Router } from "next/router";
+import Script from "next/script";
+import posthog from "posthog-js";
+import { Suspense, useEffect, useState } from "react";
 
-const isProd = process.env.NEXT_PUBLIC_VERCEL_ENV === 'production';
-const baseDir = process.env.NEXT_PUBLIC_BASE_DIR || '';
+const isProd = process.env.NEXT_PUBLIC_VERCEL_ENV === "production";
+const baseDir = process.env.NEXT_PUBLIC_BASE_DIR || "";
 
 function HubSpot() {
   const hsId = process.env.NEXT_PUBLIC_HUBSPOT_ID;
@@ -31,8 +31,8 @@ function HubSpot() {
       if (searchParams && searchParams.toString()) {
         path = path + `?${searchParams.toString()}`;
       }
-      hs.push(['setPath', path]);
-      hs.push(['trackPageView']);
+      hs.push(["setPath", path]);
+      hs.push(["trackPageView"]);
     }
   }, [afterLoad, pathname, searchParams]);
 

instrumentation-client.ts

@@ -1,22 +1,22 @@
-import posthog from 'posthog-js';
-import inEU from '@segment/in-eu';
+import posthog from "posthog-js";
+import inEU from "@segment/in-eu";
 
-const isProd = process.env.NEXT_PUBLIC_VERCEL_ENV === 'production';
+const isProd = process.env.NEXT_PUBLIC_VERCEL_ENV === "production";
 
 const initPostHog = () => {
   if (inEU() || !process.env.NEXT_PUBLIC_POSTHOG_KEY) {
     return;
   }
 
-  posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY ?? '', {
-    api_host: isProd ? '/i' : process.env.NEXT_PUBLIC_POSTHOG_HOST, // See Posthog rewrites in next config
+  posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY ?? "", {
+    api_host: isProd ? "/i" : process.env.NEXT_PUBLIC_POSTHOG_HOST, // See Posthog rewrites in next config
     ui_host: process.env.NEXT_PUBLIC_POSTHOG_HOST,
-    defaults: '2025-11-30',
-    person_profiles: 'always',
+    defaults: "2025-11-30",
+    person_profiles: "always",
     loaded: (posthog) => {
-      if (process.env.NODE_ENV === 'development') posthog.debug();
+      if (process.env.NODE_ENV === "development") posthog.debug();
     },
   });
 };
 
-initPostHog();
+initPostHog();