run lint with the new tool

Author: sohanmaheshwar

app/spicedb/integrations/_meta.ts

@@ -1,6 +1,5 @@
 export default {
-  "langchain-spicedb":
-    "Use SpiceDB with LangChain & LangGraph for RAG & AI Agent Authorization",
+  "langchain-spicedb": "Use SpiceDB with LangChain & LangGraph for RAG & AI Agent Authorization",
   pinecone: "Access Control in RAG with Pinecone and SpiceDB",
   testcontainers: "Testing RAG Pipelines with Testcontainers",
 };

app/spicedb/integrations/langchain-spicedb/page.mdx

@@ -57,9 +57,9 @@ The retriever fetches documents using your vector store's semantic search, then
 Only documents that `alice` has the `view` permission for are returned.
 
 <Callout type="info">
-  Each document's metadata must include a field (specified by `resource_id_key`)
-  that contains the resource identifier used in SpiceDB. This is how the library
-  knows which SpiceDB resource to check permissions against.
+  Each document's metadata must include a field (specified by `resource_id_key`) that contains the
+  resource identifier used in SpiceDB. This is how the library knows which SpiceDB resource to check
+  permissions against.
 </Callout>
 
 **When to use this approach:**
@@ -194,9 +194,9 @@ The authorization node reads documents from `state["retrieved_documents"]`, chec
 Authorization metrics are automatically included in `state["auth_results"]`.
 
 <Callout type="info">
-  LangGraph is ideal when you need explicit control over each pipeline step,
-  want to maintain state across multiple conversation turns, or need complex
-  branching logic based on authorization results.
+  LangGraph is ideal when you need explicit control over each pipeline step, want to maintain state
+  across multiple conversation turns, or need complex branching logic based on authorization
+  results.
 </Callout>
 
 **When to use this approach:**
@@ -363,9 +363,9 @@ The library checks permissions for `document:123` when evaluating this document.
 If `resource_id_key` doesn't match a field in the document's metadata, that document will be filtered out.
 
 <Callout type="warning">
-  Ensure all documents in your vector store include the resource ID field.
-  Documents missing this field will be silently excluded from results, which can
-  lead to incomplete answers without explicit errors.
+  Ensure all documents in your vector store include the resource ID field. Documents missing this
+  field will be silently excluded from results, which can lead to incomplete answers without
+  explicit errors.
 </Callout>
 
 ## Authorization Metrics
@@ -462,9 +462,9 @@ This flexibility allows you to choose the best vector store for your use case wi
 ### Error Handling
 
 <Callout type="warning">
-  Never fall back to unfiltered results when authorization fails. This creates a
-  path for information leakage during system outages. Instead, return an error
-  to the user or empty results with an explanation.
+  Never fall back to unfiltered results when authorization fails. This creates a path for
+  information leakage during system outages. Instead, return an error to the user or empty results
+  with an explanation.
 </Callout>
 
 ```python

app/spicedb/integrations/pinecone/page.mdx

@@ -50,9 +50,9 @@ In this model, articles have two relations: `viewer` (users who can read) and `e
 The `view` permission is granted to anyone in either relation, while `edit` requires the `editor` relation.
 
 <Callout type="info">
-  Relations define direct relationships between objects, while permissions
-  compute who has access based on those relations. You cannot write
-  relationships directly to permissions—only to relations.
+  Relations define direct relationships between objects, while permissions compute who has access
+  based on those relations. You cannot write relationships directly to permissions—only to
+  relations.
 </Callout>
 
 ## Authorization Strategies: Pre-Filter vs Post-Filter

app/spicedb/integrations/testcontainers/page.mdx

@@ -51,9 +51,9 @@ Each test gets a fresh, isolated SpiceDB container:
 This approach eliminates flaky tests caused by shared state, manual setup, or mock inconsistencies.
 
 <Callout type="info">
-  Testcontainers requires Docker to be running on your system. Install Docker
-  Desktop or Docker Engine before running tests. The framework automatically
-  handles all container lifecycle management.
+  Testcontainers requires Docker to be running on your system. Install Docker Desktop or Docker
+  Engine before running tests. The framework automatically handles all container lifecycle
+  management.
 </Callout>
 
 ## Setting Up Tests with Testcontainers

app/spicedb/tutorials/_meta.ts

@@ -1,5 +1,4 @@
 export default {
-  "ai-agent-authorization":
-    "Tutorial: Authorization for AI Agents using SpiceDB",
+  "ai-agent-authorization": "Tutorial: Authorization for AI Agents using SpiceDB",
   "secure-rag-pipelines": "Tutorial: Securing RAG Pipelines with SpiceDB",
 };