@pyric/cli 0.1.0-alpha.9

package/dist/serve/docs-ui/llms.txt

@@ -0,0 +1,308 @@
+# Pyric
+
+> Pyric is Firebase for agents: a Firebase-shaped SDK and toolchain
+> (in-browser sandbox, rules tooling, replay verification, deploy)
+> that lets developers and AI agents work against Firebase semantics
+> without touching a live project.
+
+Every page below is also served as raw markdown at the linked `.md` URL.
+
+## Overview
+
+- [Run Firebase locally, ship unchanged](/__pyric/ui/docs/overview.md): Understand what Pyric is and what you get, in one short read.
+
+## Run locally
+
+- [Run Firebase locally](/__pyric/ui/docs/start-building.md): Start a new Firebase application or add Pyric to an existing Vite application without connecting development to production.
+- [How firebase/* imports resolve locally and in production](/__pyric/ui/docs/how-the-swap-works.md): Understand how your firebase imports reached a local backend, and why production is untouched.
+- [Connect an agent to the sandbox](/__pyric/ui/docs/set-up-your-agent.md): Connect Claude Code, Cursor, Codex, or any MCP client to your backend in minutes.
+- [Run the same backend in tests and scripts](/__pyric/ui/docs/test-in-node.md): Run your rules and data logic in a Node test suite, with no browser and no emulator.
+
+## Develop with Firebase APIs
+
+- [Run Firebase Authentication locally](/__pyric/ui/docs/sign-in-and-manage-users.md): Keep Firebase Authentication code unchanged while identities, sessions, and provider flows stay in the local sandbox.
+- [Run Cloud Firestore locally](/__pyric/ui/docs/store-and-query-data.md): Keep Cloud Firestore application code unchanged while data, listeners, transactions, and Security Rules stay local.
+- [Run Realtime Database locally](/__pyric/ui/docs/sync-realtime-data.md): Keep Realtime Database application code unchanged while the data tree, listeners, and Security Rules stay local.
+- [Run Cloud Storage locally](/__pyric/ui/docs/store-files.md): Keep Cloud Storage application code unchanged while objects, metadata, and Security Rules stay local.
+- [Receive Firebase Cloud Messaging locally](/__pyric/ui/docs/receive-messages.md): Keep Firebase Cloud Messaging receive code unchanged while tokens and deliveries stay in the local sandbox.
+- [Run Firebase AI Logic locally](/__pyric/ui/docs/run-ai-logic-locally.md): Keep Firebase AI Logic application code unchanged while model responses stay deterministic or come from a local model.
+- [Run an RTDB onValueCreated function locally](/__pyric/ui/docs/pyric-cli-how-to-run-rtdb-onvaluecreated.md): Use pyric dev to run an existing Node firebase-functions/v2/database.onValueCreated export against the same local Realtime Database as your app and Pyric Studio. The function source keeps its production imports and needs no credentials or deployment.
+- [Choose a Firebase database](/__pyric/ui/docs/which-data-service.md): Make the Firestore or Realtime Database decision from Firebase's production model, then check the corresponding Pyric boundary.
+
+## Inspect and correct
+
+- [Watch every read, write, and denial live](/__pyric/ui/docs/see-whats-happening.md): See every operation your backend performs, with its rules verdict, without writing a log line.
+- [Read a Security Rules denial](/__pyric/ui/docs/read-a-denial.md): See which rule denied an operation, on what path, with what data, the moment it happens.
+- [Seed, snapshot, reset, and replay the backend](/__pyric/ui/docs/shape-your-data.md): Put the backend in any state you want, capture the good ones, and get them back on demand.
+- [Watch the agent work, then check it](/__pyric/ui/docs/watch-and-review.md): See every operation your agent performs, live, with the verdict that decided it.
+- [Prove a user can access only their own data](/__pyric/ui/docs/secure-it-with-rules.md): Write a rule, simulate a request against it, read the verdict, and deploy knowing what it allows.
+- [Simulate and lint Security Rules before deployment](/__pyric/ui/docs/simulate-and-lint.md): Get a rules verdict and a lint report locally, before production answers with an unexplained 400 or 403.
+- [Apply production-tested Firestore Rules patterns](/__pyric/ui/docs/rules-patterns.md): Learn the five moves that turn "rules can't do that" into a ruleset that deploys.
+- [Build Firestore Rules from tested modules](/__pyric/ui/docs/rules-standard-library.md): Compose security rules from tested modules, with an import system that compiles away before Firebase ever sees it.
+- [Write Realtime Database rules in TypeScript](/__pyric/ui/docs/rtdb-rules-in-typescript.md): Compose RTDB rules from typed constraints, prove them in-process, and deploy the compiled JSON.
+- [Firestore Rules compiler and evaluator limits](/__pyric/ui/docs/firestore-rules-limits.md): Use measured production compiler and evaluator limits before a ruleset reaches Firebase.
+- [Case studies in pure security rules](/__pyric/ui/docs/whats-possible.md): See working, deployed rulesets that enforce chess, checkers, connect four, and US tax math, built from the patterns this wing teaches.
+- [Work with the sandbox through an agent](/__pyric/ui/docs/what-your-agent-can-do.md): Every backend capability, callable as a tool: inspect, query, simulate, shape, ship, verify.
+- [Give an agent methods for Firebase tasks](/__pyric/ui/docs/skills.md): Packaged expert procedures for the problems that need a method, not more tools.
+
+## Verify the boundary
+
+- [How to verify your rules against a captured session](/__pyric/ui/docs/pyric-cli-how-to-verify-against-a-captured-session.md): pyric verify replays a captured sandbox session against candidate rules and reports service-labelled divergences. It works for Firestore and Realtime Database captures. It answers the question that makes "build in the sandbox, swap to prod" safe: will the rules I'm about to ship break what I built?
+- [Write a Security Rules test suite](/__pyric/ui/docs/write-a-rules-test-suite.md): A suite of allow/deny cases that runs in-process, gates CI, and can escalate to Google's own engine.
+- [Audit Security Rules and data before production](/__pyric/ui/docs/audit-your-rules.md): Get an evidence-backed answer to who can access what, with every serious finding proven by a simulation.
+
+## Ship unchanged
+
+- [The same code goes live](/__pyric/ui/docs/ship-to-production.md): Deploy rules, indexes, hosting, and functions, and learn what would change before production does.
+- [Prepare the Firebase project](/__pyric/ui/docs/set-up-the-project.md): Configure the real Firebase services that production will use, without confusing project setup with local development.
+
+## Conformance
+
+- [How does Pyric know it works like Firebase?](/__pyric/ui/docs/how-we-know-it-matches-firebase.md): See the production evidence behind Pyric's conformance claims, the gaps those claims leave open, and the checks to make before shipping.
+- [What's experimental](/__pyric/ui/docs/whats-experimental.md): Know exactly which parts of Pyric are v1 and which are still earning it.
+- [Conformance scores](/__pyric/ui/docs/pyric-conformance-scores.md): Public runtime surface, public type surface, and behavior fidelity answer different questions. How does Pyric know it works like Firebase? explains the evidence and its limits.
+- [pyric/app compatibility matrix](/__pyric/ui/docs/pyric-app-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Public surface:</strong> runtime 90% (9/10) <span aria-hidden="true">·</span> types 66.7% (4/6)</p> <p class="compat-stat-figure"> <span class="compat-stat-pct">85.2%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">23 of 27 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 23 conform, 2 documented divergences, 0 bugs, 1 unsupported, 1 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 23" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="diverged" style="flex-grow: 2" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="unsupported" style="flex-grow: 1" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="unverified" style="flex-grow: 1" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>23</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>2</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>1</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>1</strong> unverified</span></li> </ul> <p class="compat-stat-note">Public surface measures whether exports exist. Fidelity measures whether tracked behavior matches production.</p> </div> Read how the axes differ.
+- [pyric/firestore compatibility matrix](/__pyric/ui/docs/pyric-firestore-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Public surface:</strong> runtime 63.5% (66/104) <span aria-hidden="true">·</span> types 38.5% (30/78)</p> <p class="compat-stat-figure"> <span class="compat-stat-pct">87.6%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">141 of 161 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 141 conform, 20 documented divergences, 0 bugs, 0 unsupported, 0 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 141" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="diverged" style="flex-grow: 20" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>141</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>20</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>0</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>0</strong> unverified</span></li> </ul> <p class="compat-stat-note">Public surface measures whether exports exist. Fidelity measures whether tracked behavior matches production.</p> </div> Read how the axes differ.
+- [pyric/auth compatibility matrix](/__pyric/ui/docs/pyric-auth-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Public surface:</strong> runtime 82.4% (70/85) <span aria-hidden="true">·</span> types 39.1% (25/64)</p> <p class="compat-stat-figure"> <span class="compat-stat-pct">81.8%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">99 of 121 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 99 conform, 16 documented divergences, 0 bugs, 5 unsupported, 1 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 99" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="diverged" style="flex-grow: 16" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="unsupported" style="flex-grow: 5" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="unverified" style="flex-grow: 1" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>99</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>16</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>5</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>1</strong> unverified</span></li> </ul> <p class="compat-stat-note">Public surface measures whether exports exist. Fidelity measures whether tracked behavior matches production.</p> </div> Read how the axes differ.
+- [pyric/database compatibility matrix](/__pyric/ui/docs/pyric-database-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Public surface:</strong> runtime 79.5% (35/44) <span aria-hidden="true">·</span> types 53.3% (8/15)</p> <p class="compat-stat-figure"> <span class="compat-stat-pct">76.6%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">154 of 201 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 154 conform, 9 documented divergences, 0 bugs, 26 unsupported, 12 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 154" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="diverged" style="flex-grow: 9" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="unsupported" style="flex-grow: 26" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="unverified" style="flex-grow: 12" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>154</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>9</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>26</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>12</strong> unverified</span></li> </ul> <p class="compat-stat-note">Public surface measures whether exports exist. Fidelity measures whether tracked behavior matches production.</p> </div> Read how the axes differ.
+- [pyric/storage compatibility matrix](/__pyric/ui/docs/pyric-storage-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Public surface:</strong> runtime 72.2% (13/18) <span aria-hidden="true">·</span> types 52.9% (9/17)</p> <p class="compat-stat-figure"> <span class="compat-stat-pct">86%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">86 of 100 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 86 conform, 6 documented divergences, 0 bugs, 8 unsupported, 0 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 86" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="diverged" style="flex-grow: 6" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="unsupported" style="flex-grow: 8" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>86</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>6</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>8</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>0</strong> unverified</span></li> </ul> <p class="compat-stat-note">Public surface measures whether exports exist. Fidelity measures whether tracked behavior matches production.</p> </div> Read how the axes differ.
+- [pyric/rules compatibility matrix](/__pyric/ui/docs/pyric-rules-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Surface:</strong> native <span>(no upstream Firebase public API; measured against Pyric's own surface)</span></p> <p class="compat-stat-figure"> <span class="compat-stat-pct">86.2%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">50 of 58 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 50 conform, 8 documented divergences, 0 bugs, 0 unsupported, 0 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 50" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="diverged" style="flex-grow: 8" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>50</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>8</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>0</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>0</strong> unverified</span></li> </ul> <p class="compat-stat-note">Public surface measures whether exports exist. Fidelity measures whether tracked behavior matches production.</p> </div> Read how the axes differ.
+- [pyric messaging compatibility matrix](/__pyric/ui/docs/pyric-messaging-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Public surface:</strong> runtime 100% (5/5) <span aria-hidden="true">·</span> types 100% (8/8)</p> <p class="compat-stat-figure"> <span class="compat-stat-pct">100%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">17 of 17 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 17 conform, 0 documented divergences, 0 bugs, 0 unsupported, 0 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 17" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>17</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>0</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>0</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>0</strong> unverified</span></li> </ul> <p class="compat-stat-note">Public surface measures whether exports exist. Fidelity measures whether tracked behavior matches production.</p> </div> Read how the axes differ.
+- [pyric/ai compatibility matrix](/__pyric/ui/docs/pyric-ai-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Public surface:</strong> runtime 69.1% (38/55) <span aria-hidden="true">·</span> types 66.5% (109/164)</p> <p class="compat-stat-figure"> <span class="compat-stat-pct">92.3%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">72 of 78 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 72 conform, 6 documented divergences, 0 bugs, 0 unsupported, 0 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 72" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="diverged" style="flex-grow: 6" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>72</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>6</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>0</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>0</strong> unverified</span></li> </ul> <p class="compat-stat-note">Public surface measures whether exports exist. Fidelity measures whether tracked behavior matches production.</p> </div> Read how the axes differ.
+- [Firebase Functions RTDB integration compatibility](/__pyric/ui/docs/pyric-cli-functions-rtdb-compat.md): <div class="compat-stat"> <p class="compat-stat-surface"><strong>Surface:</strong> integration contract <span>(unchanged upstream source; breadth is the signed row inventory)</span></p> <p class="compat-stat-figure"> <span class="compat-stat-pct">92.3%</span> <span class="compat-stat-label">of tracked behaviors conform</span> </p> <p class="compat-stat-denom">12 of 13 tracked behaviors</p> <div class="compat-stat-bar" role="img" aria-label="Behavior distribution: 12 conform, 0 documented divergences, 0 bugs, 0 unsupported, 1 unverified."> <span class="compat-stat-seg" data-status="ok" style="flex-grow: 12" aria-hidden="true"></span> <span class="compat-stat-seg" data-status="unverified" style="flex-grow: 1" aria-hidden="true"></span> </div> <ul class="compat-stat-key" aria-label="Behavior state counts"> <li class="compat-stat-item"><span class="compat-dot" data-status="ok" aria-hidden="true"></span><span><strong>12</strong> conform</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="diverged" aria-hidden="true"></span><span><strong>0</strong> documented divergences</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="bug" aria-hidden="true"></span><span><strong>0</strong> bugs</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unsupported" aria-hidden="true"></span><span><strong>0</strong> unsupported</span></li> <li class="compat-stat-item"><span class="compat-dot" data-status="unverified" aria-hidden="true"></span><span><strong>1</strong> unverified</span></li> </ul> <p class="compat-stat-note">The signed row inventory defines this integration contract. Fidelity measures how many tracked behaviors match production.</p> </div> Read how the axes differ.
+
+## @pyric/cli
+
+- [@pyric/cli](/__pyric/ui/docs/pyric-cli.md): The pyric CLI and programmatic helpers for local sandbox development, verification, artifact generation, and agent bridges — organised by the four Diátaxis quadrants: learn, do, look up, understand.
+- [Run your firebase-admin app on the pyric sandbox](/__pyric/ui/docs/pyric-cli-tutorials-server-adoption.md): You have an existing Node server that uses firebase-admin: Realtime Database, Auth, Storage. By the end of this tutorial it runs against the pyric in-browser sandbox with zero code changes: no pyric imports, no config edits, no emulator suite, no Firebase project.
+- [Wire Claude Code to your pyric sandbox (manual MCP wiring)](/__pyric/ui/docs/pyric-cli-tutorials-wire-claude-code.md): By the end of this tutorial you will have:
+- [Build a standalone pyric binary](/__pyric/ui/docs/pyric-cli-how-to-build-a-standalone-binary.md): Ship pyric as a single self-contained executable: no Node, no npm, no node_modules. Built with bun build --compile.
+- [How to promote sandbox state to a committable fixture](/__pyric/ui/docs/pyric-cli-how-to-promote-sandbox-state-to-a-fixture.md): You have been working in the sandbox interactively (signing in test users, creating documents) and you want to commit that state so teammates, tests, and CI all start from the same place. pyric snapshot promotes the lived sandbox state into a single fixture file that pyric verify and pyric dev --seed can consume.
+- [Persistence and multi-tab with pyric dev](/__pyric/ui/docs/pyric-cli-how-to-serve-persistence-and-multi-tab.md): When you run pyric dev, your app's firebase/* imports are served from an in-browser pyric sandbox instead of real Firebase. This guide covers how that sandbox keeps (or doesn't keep) data, the flags that control it, and what to do if the SharedWorker that backs it acts up.
+- [Use the Vite plugin (@pyric/cli/vite)](/__pyric/ui/docs/pyric-cli-how-to-use-the-vite-plugin.md): The pyricSandbox() Vite plugin gives a source-driven app the same firebase/ → pyric-sandbox swap that pyric dev gives a static app, without leaving your normal vite dev loop (HMR, source maps, your own router/UI stack). Your app's firebase/ imports stay exactly as written; the plugin swaps them at Vite's module-resolution layer. A plain vite build keeps the real firebase package; only vite dev and an explicit sandbox build (vite build --mode development) run the swap. See Two build flavors.
+- [pyric CLI reference](/__pyric/ui/docs/pyric-cli-reference-cli.md): The complete command + flag surface of the pyric binary. This is the authoritative source for flags, defaults, and exit codes: guides and tutorials link here rather than restating them.
+- [Package exports and resolution](/__pyric/ui/docs/pyric-cli-reference-package-and-resolution.md): Install @pyric/cli as a development dependency. It provides the pyric binary and a small set of explicit programmatic subpaths; the package root is not an import target.
+- [Verify API](/__pyric/ui/docs/pyric-cli-reference-verify.md): @pyric/cli/verify verifies captured sandbox sessions from code. It uses the same fixture format and replay behavior as pyric verify.
+- [@pyric/cli/bridge](/__pyric/ui/docs/pyric-cli-bridge.md): Bridge between an external MCP client (Claude Code, Cursor) and a browser-resident pyric sandbox.
+
+## pyric
+
+- [The versioning and compatibility policy](/__pyric/ui/docs/pyric-explanation-versioning-and-compatibility.md): Pyric mirrors Firebase's observable behavior. Users need one honest way to ask "which Firebase does this pyric behave like," and pyric needs one honest way to answer. This document is that answer. It defines what the claim means, where it appears, and what has to be true before it can move.
+
+## pyric / firestore
+
+- [pyric/firestore](/__pyric/ui/docs/pyric-firestore.md): pyric/firestore is the sandbox implementation of Firebase's modular Firestore surface. It provides reads, writes, queries, listeners, transactions, batches, converters, aggregates, sentinels, and local scalar value classes without loading the production Firebase SDK.
+- [Write a sandbox-backed demo](/__pyric/ui/docs/pyric-firestore-tutorials-01-write-a-sandbox-demo.md): Build a tiny notes app with pyric/firestore against the sandbox backend. By the end you'll have set rules, seeded data, written, read, watched a query, and seen a denial, all in-process.
+- [Run canonical imports against Firebase](/__pyric/ui/docs/pyric-firestore-tutorials-02-swap-to-prod-backend.md): In this lesson you will take the canonical-import demo from the previous tutorial, remove sandbox activation, and observe Firebase becoming the backend without changing the Firestore calls.
+- [How to run an existing Firebase application in the Firestore sandbox](/__pyric/ui/docs/pyric-firestore-how-to-migrate-from-firebase-firestore.md): Keep the application's Firebase imports unchanged. Add a Pyric activation seam around the application instead of replacing imports with pyric/firestore.
+- [How to select sandbox or production Firestore](/__pyric/ui/docs/pyric-firestore-how-to-pick-a-backend.md): Keep canonical Firebase imports in application source and select the backend by activating, or not activating, Pyric's package-resolution seam.
+- [How to run a transaction](/__pyric/ui/docs/pyric-firestore-how-to-run-a-transaction.md): Read a document and write based on its current value, atomically, with runTransaction. It works the same against either backend.
+- [How to use onSnapshot](/__pyric/ui/docs/pyric-firestore-how-to-use-onsnapshot.md): Keep your UI live by registering snapshot listeners on documents and queries, in the modular Web SDK shape.
+- [How to use sandbox-only operations](/__pyric/ui/docs/pyric-firestore-how-to-use-sandbox-ops.md): Load rules, seed data, snapshot documents, and inspect Firestore state in one local sandbox.
+- [Feature matrix: pyric/firestore](/__pyric/ui/docs/pyric-firestore-reference-feature-matrix.md): The generated compatibility matrix is the authoritative list of supported, diverged, unsupported, and unverified Firestore behaviour. It is generated from packages/conformance/registry/firestore.ts; do not maintain a second row-by-row status table here.
+- [getFirestore](/__pyric/ui/docs/pyric-firestore-reference-getfirestore.md): Constructs a Firestore handle owned by the Pyric sandbox mirror.
+- [Query constraints](/__pyric/ui/docs/pyric-firestore-reference-query-constraints.md): pyric/firestore mirrors firebase/firestore's constraint factories. Compose them via query(...).
+- [Sandbox-only operations](/__pyric/ui/docs/pyric-firestore-reference-sandbox-ops.md): Firestore-specific controls are top-level exports from pyric/sandbox/firestore. They operate on the owning local Sandbox, not on a Firestore data-plane handle.
+- [Tool factories](/__pyric/ui/docs/pyric-firestore-reference-tool-factories.md): createFirestoreDataTools(deps) wraps the modular Firestore data plane as @inbrowser/agent tool handlers.
+- [Why rules tooling lives on a sibling subpath](/__pyric/ui/docs/pyric-firestore-explanation-rules-tooling-is-separate.md): pyric/firestore is the Firebase-compatible sandbox data plane. The rules parser, linter, simulator, validator, modules resolver, and value wrappers live under pyric/rules. Firestore-specific sandbox controls live under pyric/sandbox/firestore. The separation preserves clear package ownership.
+- [The TARGET_SYMBOL opacity contract](/__pyric/ui/docs/pyric-firestore-explanation-target-symbol-opacity.md): The public Firestore type has exactly one property:
+- [Why package resolution owns backend selection](/__pyric/ui/docs/pyric-firestore-explanation-two-backends-one-surface.md): Pyric and Firebase expose the same canonical module name in different environments. The environment chooses the package before either implementation loads:
+
+## pyric / rules
+
+- [pyric/rules](/__pyric/ui/docs/pyric-rules.md): Pyric-native Firestore Security Rules tooling. A browser-safe parser, linter, modules resolver, in-process simulator, and Rules Test API client, packaged so the data-plane swap-in (pyric/firestore) stays minimal.
+- [How to compare two rulesets for weakening](/__pyric/ui/docs/pyric-rules-how-to-compare-rulesets-for-weakening.md): When you ship a rules change, the most dangerous mistake is silently removing a security predicate to make a failing test pass. Here's how to catch that before it deploys.
+- [How to inspect rules through the AST](/__pyric/ui/docs/pyric-rules-how-to-inspect-rules-via-the-ast.md): Parse rules into a typed AST and walk the tree for custom analysis: bespoke lint rules, generated documentation, or structural facts the built-in linter doesn't surface.
+- [How to lint a rules source](/__pyric/ui/docs/pyric-rules-how-to-lint-rules-source.md): Lint a Firestore rules source, read the result, and gate a deploy on it. Everything here runs in-process.
+- [How to pin request.time for deterministic tests](/__pyric/ui/docs/pyric-rules-how-to-pin-request-time.md): A rule that reads request.time evaluates against wallclock by default. That makes any date-gated test flaky: the same FirestoreCase run twice can decide ALLOW once and DENY the next. Pin time and the verdict is reproducible.
+- [How to register rules tools with an agent](/__pyric/ui/docs/pyric-rules-how-to-register-tools-with-an-agent.md): Expose the rules surface as tool handlers for an @inbrowser/agent registry, so an LLM-driven agent can lint, simulate, and test rules through structured tool calls.
+- [How to resolve 2+modules imports](/__pyric/ui/docs/pyric-rules-how-to-resolve-module-imports.md): Write rules that import reusable helper functions, then resolve them into a standard Firestore rules source.
+- [How to simulate rules locally](/__pyric/ui/docs/pyric-rules-how-to-simulate-rules-locally.md): Evaluate Firestore rules in-process against a list of test cases, without deploying or contacting Google's servers.
+- [How to test rules against the Firebase Rules Test API](/__pyric/ui/docs/pyric-rules-how-to-test-rules-against-firebase.md): Evaluate Firestore rules against Google's live Rules Test API. Use this when the local simulator returns UNSUPPORTED, or when you need parity with what production will actually decide.
+- [AST](/__pyric/ui/docs/pyric-rules-reference-ast.md): The AST is the typed tree produced by parseToAST / parseToASTOrError. These functions and the shapes below are exported from pyric/rules/internal, an internal, unstable surface not covered by the public pyric/rules contract: it may change without notice. Most callers reach the AST through the public front door instead: firestoreRules(source).toJSON() returns the same FirestoreRules tree without touching the parser directly. This page documents the shape for callers (and tooling like Inspect rules via the AST) that need to walk it directly.
+- [Firestore rules gaps: where pyric and Firebase disagree](/__pyric/ui/docs/pyric-rules-reference-conformance-gaps.md): A gap is a rule that gets one answer from pyric and a different answer from Firebase. You write the rule once. pyric allows the request and Firebase denies it, or the other way round. The rule you tested is not the rule you shipped.
+- [Errors](/__pyric/ui/docs/pyric-rules-reference-errors.md): pyric/rules throws exactly three error classes on its public surface. Everything below the public surface (the parser, evaluator, and handlers on pyric/rules/internal) has its own error vocabulary; those types still apply, but only to the internal engine now.
+- [Lint rules](/__pyric/ui/docs/pyric-rules-reference-lint-rules.md): This page lists every lint rule emitted by lint(source) and firestoreRules(source).lint(), both from pyric/rules. Each rule surfaces as a RuleIssue with origin: 'lint' and code set to the rule name below. Each entry gives the rule code, default severity, what it detects, and the suggested fix.
+- [Simulator context and result states](/__pyric/ui/docs/pyric-rules-reference-simulator-context.md): The simulator evaluates expressions against a SimulationContext. This page describes its shape and the three result states a test case can land in. SimulationContext and evaluate are engine-internal, reached through pyric/rules/internal; the public front door is firestoreRules(source).simulate(cases) / .explain(oneCase), which builds and consumes this context internally and returns a CaseResult / Explanation instead. This page documents the internals for callers who need them directly, and to explain what the public result fields mean underneath.
+- [Standard library modules](/__pyric/ui/docs/pyric-rules-reference-stdlib-modules.md): Fifteen modules ship with pyric/rules. Each module is a .rules file living under src/rules/modules/stdlib/; imports resolve automatically without any configuration.
+- [FirestoreCase schema](/__pyric/ui/docs/pyric-rules-reference-test-case-schema.md): FirestoreCase is the unit of work for firestoreRules(source).simulate(cases) and firestoreRules(source).explain(oneCase), both from pyric/rules. It's structurally identical to the engine-internal TestCase type (pyric/rules/internal), re-exported under the public name so callers never need to reach into the engine seam. A Zod schema for the same shape, TestCaseSchema, is available on pyric/rules/internal for callers that want runtime validation; it is not part of the public contract.
+- [Validator findings](/__pyric/ui/docs/pyric-rules-reference-validator-findings.md): The validator runs as part of lint(source) and firestoreRules(source).lint(), both from pyric/rules. Each finding surfaces as a RuleIssue with origin: 'validate'. The validator's own internal shape, ValidationFinding, still exists on pyric/rules/internal (via validateFirestoreRules(ast)) for callers that need the raw four-level severity scale:
+- [Value wrappers](/__pyric/ui/docs/pyric-rules-reference-value-wrappers.md): The simulator and the sentinel expression engine model Firestore's runtime types as TypeScript classes. Every wrapper extends RulesValue, exposes equals, toJSON, and toString, and dispatches method calls via callMethod. These classes are engine-internal, importable from pyric/rules/internal.
+- [Agent failure modes the linter catches](/__pyric/ui/docs/pyric-rules-explanation-agent-failure-modes.md): Most of the linter's compilation and budget rules came from production: we hit the limit, learned the number, encoded it. A separate set of rules came from somewhere different. We watched LLM-driven agents try to write rules and fail in characteristic ways.
+- [Lint vs validate vs simulate vs test](/__pyric/ui/docs/pyric-rules-explanation-lint-vs-validate-vs-simulate-vs-test.md): The package offers four distinct ways to look at a rules source. Their names suggest they overlap. They don't, and the distinction matters when you're building a CI pipeline or an agent loop.
+- [The runtime budget and shared gates](/__pyric/ui/docs/pyric-rules-explanation-runtime-budget-and-shared-gates.md): Firestore rules have two kinds of limits. Compilation limits fail loudly: a 400 INVALID_ARGUMENT at deploy. The runtime evaluation budget fails silently: a 403 PERMISSION_DENIED that looks identical to a denied rule.
+- [The sentinel expression engine ($expr)](/__pyric/ui/docs/pyric-rules-explanation-sentinel-expression-engine.md): Firestore writes are usually concrete: { count: 5, owner: 'alice' }. But sometimes you want a write whose value depends on the document at write time: "increment count by one if it's less than 100", "set lastSeen to the current request time", "merge this list with the existing one and dedupe". The Firestore SDK offers a handful of FieldValue sentinels for the most common cases (increment, arrayUnion, serverTimestamp), but anything outside that small set requires a transaction.
+- [Simulator vs Rules Test API](/__pyric/ui/docs/pyric-rules-explanation-simulator-vs-rules-test-api.md): Two surfaces evaluate rules against test cases. Underneath, they share a case shape and a result vocabulary; they disagree on tradeoffs. Choosing between them is a deliberate decision, not an implementation detail.
+- [The 2+modules extension](/__pyric/ui/docs/pyric-rules-explanation-the-2-plus-modules-extension.md): Firestore rules don't have imports. The DSL has functions, but every function has to be defined in the same file as the match block that calls it. This means real-world rules either repeat the same helper code across files (and drift) or live in one giant file (and become unreadable).
+- [Value wrapper design](/__pyric/ui/docs/pyric-rules-explanation-value-wrappers-design.md): Firestore rules have a small but real type system. request.time is a timestamp. request.path is a path. bytes[0:10] is a bytes value. is duration, is timestamp, is reference are type tests. None of these have first-class JavaScript representations (Timestamp is not a primitive, Path is not a primitive), so the simulator has to model them somehow.
+- [Why this package exists](/__pyric/ui/docs/pyric-rules-explanation-why-this-package-exists.md): Firestore Security Rules is a small DSL that sits between every read and write your app makes. In Pyric we have two distinct needs around that DSL:
+
+## pyric / sandbox
+
+- [pyric/sandbox](/__pyric/ui/docs/pyric-sandbox.md): An in-process Firebase sandbox, the foundation every other @pyric/* data-plane package plugs into. It holds documents, rules, and listener state for a single isolated environment. It is identity-agnostic by design: every operation flows through a SandboxContext that names the auth identity it should evaluate under.
+- [Your first sandbox session](/__pyric/ui/docs/pyric-sandbox-tutorials-01-your-first-sandbox-session.md): Create a sandbox, deploy a tiny set of rules, write a document as one user, deny a read as another, and inspect the result. By the end you'll have seen the three core ideas (Sandbox, SandboxContext, SandboxError) work together in one short script.
+- [How to run multiple isolated sandboxes in parallel](/__pyric/ui/docs/pyric-sandbox-how-to-multiple-isolated-sandboxes.md): Keep multiple sandboxes alive at once, for fleet tests, multi-tenant simulations, or any workload that needs more than one isolated environment.
+- [How to observe sandbox events](/__pyric/ui/docs/pyric-sandbox-how-to-observe-events.md): One subscription covers everything observable. sandbox.onEvent(cb) fires a SandboxEvent for every rule evaluation, every committed write, every snapshot delivered to a listener callback, every suppressed re-eval, every listener attach / detach / errored, and every reset / dispose boundary. Filter on event.kind to recover whichever slice your code cares about.
+- [How to pick between pyric-admin and pyric/firestore](/__pyric/ui/docs/pyric-sandbox-how-to-pick-an-adapter.md): Two adapter packages sit on top of pyric/sandbox. Both expose Firestore. They look the same from a distance and shape differently up close. This guide helps you pick.
+- [How to replay a captured event stream](/__pyric/ui/docs/pyric-sandbox-how-to-replay-events.md): The sandbox captures every SandboxEvent it emits. Hand the captured stream to replay(events, rules) from pyric/sandbox and the engine re-issues every write against a fresh sandbox, classifying the differences against an optional snapshot of the original state.
+- [How to reset between tests](/__pyric/ui/docs/pyric-sandbox-how-to-reset-between-tests.md): Keep one sandbox alive across many tests without state leakage.
+- [How to seed initial data and rules](/__pyric/ui/docs/pyric-sandbox-how-to-seed-data-and-rules.md): Bring a fresh sandbox up to a known state (rules deployed, documents in place) before your test code runs.
+- [How to switch users with withAuth](/__pyric/ui/docs/pyric-sandbox-how-to-switch-users.md): Evaluate rules under different auth identities against the same sandbox.
+- [How to use admin reads to assert in tests](/__pyric/ui/docs/pyric-sandbox-how-to-use-admin-reads.md): Use sandbox.admin to verify state in tests without writing rules that permit your test fixture.
+- [Divergence](/__pyric/ui/docs/pyric-sandbox-reference-divergences.md): What replay(events, rules, opts, originalState) returns when the replayed state doesn't perfectly match the captured state. A discriminated union; filter on kind to handle each case.
+- [SandboxError codes](/__pyric/ui/docs/pyric-sandbox-reference-error-codes.md): Every error the sandbox raises is a SandboxError carrying a code. Catch with instanceof SandboxError, switch on code.
+- [The /internal adapter protocol](/__pyric/ui/docs/pyric-sandbox-reference-internal-protocol.md): The pyric/sandbox/internal sub-path is the adapter-only surface. Service-adapter packages (pyric-admin, pyric/firestore, future pyric/auth) consume it to reach the underlying LocalEnvironment and related primitives.
+- [Sandbox, SandboxContext, AuthState](/__pyric/ui/docs/pyric-sandbox-reference-sandbox-and-context.md): The three core types. Every other surface in the package builds on them.
+- [SandboxEvent](/__pyric/ui/docs/pyric-sandbox-reference-sandbox-event.md): The discriminated union sandbox.onEvent(cb) delivers. Filter on kind to recover any individual event family. The unified channel replaces the prior onRequest / onDenial / onSnapshotError triplet.
+- [SandboxSnapshot and admin reads](/__pyric/ui/docs/pyric-sandbox-reference-snapshot-and-admin.md): Two related surfaces. SandboxSnapshot is the shape returned by Sandbox.snapshot(). SandboxAdmin is the rule-bypass read surface exposed on Sandbox.admin.
+- [Every operation is a request](/__pyric/ui/docs/pyric-sandbox-explanation-every-op-is-a-request.md): The sandbox started with one observation channel, onDenial, and it surfaced the wrong subset of the truth. We expanded the surface to onRequest, then to a per-channel triplet (onRequest / onDenial / onSnapshotError), and finally collapsed them into one unified onEvent. This page explains the conceptual arc, what it implies about how to think about sandbox traffic, and the trade-offs we made along the way.
+- [Identity is a context, not a sandbox](/__pyric/ui/docs/pyric-sandbox-explanation-identity-is-a-context.md): The most-visible architectural decision in pyric/sandbox is that Sandbox does not carry an identity. To do anything as a user, you derive a SandboxContext via sandbox.withAuth(...). This page explains why.
+- [The /internal adapter protocol](/__pyric/ui/docs/pyric-sandbox-explanation-internal-adapter-protocol.md): pyric/sandbox ships a second sub-path: pyric/sandbox/internal. The public entry stays narrow: Sandbox, SandboxContext, SandboxError, listener channels, lifecycle. Anything an adapter needs but a consumer shouldn't reach for lives behind the /internal gate.
+- [Listener re-evaluation on deployRules](/__pyric/ui/docs/pyric-sandbox-explanation-listener-re-evaluation.md): A snapshot listener attached before a deployRules call gets re-evaluated under the new rules. This is a deliberate departure from production Firestore behaviour. The reasoning matters; this page lays it out.
+- [A local backend, not Firestore offline persistence](/__pyric/ui/docs/pyric-sandbox-explanation-local-backend-vs-firestore-offline.md): A natural worry when you see pyric dev keep data across refreshes and sync across tabs is: "are you reimplementing Firestore's offline + multi-tab persistence?" That feature is one of the largest parts of the Firestore SDK, and reimplementing it would be a massive undertaking.
+- [Why service adapters live in sibling packages](/__pyric/ui/docs/pyric-sandbox-explanation-why-adapters-are-siblings.md): pyric/sandbox doesn't ship the data-plane API. The functions you actually call (getDoc, setDoc, collection, onSnapshot, runTransaction) live in pyric-admin (Admin-SDK-shaped) and pyric/firestore (modular Web-SDK-shaped). This page explains why.
+- [Why this package exists](/__pyric/ui/docs/pyric-sandbox-explanation-why-this-package-exists.md): The Firebase Emulator Suite is a Google-provided tool that runs a local copy of Firestore (and other services) in a sub-process. It's the canonical answer to "I want to test without hitting production." It works, but only in environments that can spawn an emulator. pyric/sandbox is what happens when you can't.
+
+## pyric / storage
+
+- [pyric/storage](/__pyric/ui/docs/pyric-storage.md): Firebase Storage mirror for the Pyric sandbox. Its modular Web-SDK shape (getStorage, ref, uploadBytes, getBytes, getDownloadURL, listAll, deleteObject) is backed by IndexedDB. Production selection happens outside this package: normal builds resolve firebase/storage, while Pyric development swaps that import to this sandbox mirror.
+- [How to enforce Storage rules](/__pyric/ui/docs/pyric-storage-how-to-enforce-rules.md): This guide shows you how to wire Storage rules into a sandbox-backed handle and watch them gate uploads, reads, and deletes.
+- [How to list and delete objects](/__pyric/ui/docs/pyric-storage-how-to-list-and-delete.md): This guide shows you how to enumerate objects under a prefix and remove them.
+- [Select the Storage runtime](/__pyric/ui/docs/pyric-storage-how-to-switch-backends.md): Keep application imports canonical:
+- [How to test rule expressions independently](/__pyric/ui/docs/pyric-storage-how-to-test-rule-expressions.md): This guide shows you how to verify a Storage rule expression without uploading anything. Useful when iterating on a complex rule or building a rules-test harness.
+- [Storage rules gaps: where pyric and Firebase disagree](/__pyric/ui/docs/pyric-storage-reference-conformance-gaps.md): A gap is a rule that gets one answer from pyric and a different answer from Firebase. You write the rule once. pyric allows the request and Firebase denies it, or the other way round. The rule you tested is not the rule you shipped.
+- [Error codes](/__pyric/ui/docs/pyric-storage-reference-error-codes.md): Operations through pyric/storage throw errors with Firebase-aligned code properties, 'storage/<noun>'. Catch by code.
+- [Storage rules subset](/__pyric/ui/docs/pyric-storage-reference-rules-subset.md): The Storage rules grammar in the v1 scope. Anything not listed is out of scope and will produce a parse error.
+- [StorageOptions](/__pyric/ui/docs/pyric-storage-reference-storage-options.md): The options bag for getStorageSandbox(target, options?).
+- [Implementation scope and deferred features](/__pyric/ui/docs/pyric-storage-explanation-implementation-scope.md): pyric/storage is a deliberate v1 scope. The scope is what the session-archive use case needed; anything beyond that is deferred. This page is the canonical list of what's not in the package and why.
+- [The session-archive driver](/__pyric/ui/docs/pyric-storage-explanation-session-archive-use-case.md): pyric/storage was scoped around one use case: storing completed agent sessions so a user can come back to them later. This page explains the use case and how it shaped the package.
+- [Why IndexedDB](/__pyric/ui/docs/pyric-storage-explanation-why-indexeddb.md): pyric/storage's sandbox backend persists blobs and metadata in IndexedDB. This page explains why, and what the choice implies.
+
+## pyric / auth
+
+- [pyric/auth](/__pyric/ui/docs/pyric-auth.md): Sandbox-only modular Web SDK Auth mirror. It implements firebase/auth's tree-shakable shape (getAuth, signInAnonymously, signInWithEmailAndPassword, onAuthStateChanged, signInWithPopup, GoogleAuthProvider) in process, with no network.
+- [Feature matrix: pyric/auth coverage of firebase/auth](/__pyric/ui/docs/pyric-auth-reference-feature-matrix.md): Coverage of the modular Web SDK Auth surface when package resolution swaps canonical firebase/auth imports to the Pyric sandbox mirror. Production installs no swap and continues using Firebase.
+- [Sandbox test driver: pyric/auth/sandbox.*](/__pyric/ui/docs/pyric-auth-reference-sandbox-test-driver.md): The sandbox export is pyric/auth's test-driver namespace. It mirrors pyric/firestore's sandbox.setRules / sandbox.seedDocuments pattern: methods exist only for sandbox-backed Auth handles and throw failed-precondition against a prod handle.
+
+## pyric / database
+
+- [Realtime Database](/__pyric/ui/docs/pyric-database.md): Pyric's Realtime Database surface has three deliberately separate parts:
+- [Author your first RTDB rules with constraints](/__pyric/ui/docs/pyric-database-tutorials-01-author-rtdb-rules-with-constraints.md): This tutorial creates a small Realtime Database rules document in memory, checks it, and simulates one write before you hand the generated JSON to deploy tooling.
+- [API reference: RTDB rules constraints](/__pyric/ui/docs/pyric-database-reference-constraints.md): Typed builders that produce Realtime Database security-rule expressions, plus the assembly layer that places them in a path tree and compiles the tree to Firebase rules JSON. Everything on this page is importable directly from pyric/rules, the public front door. The dedicated constraints-only subpaths that used to exist (pyric/rules/rtdb/constraints, pyric/rules/rtdb-constraints) no longer do; there is one place to import the DSL from now. The engine that compiles and simulates against it (the parser, linter, simulator, and tool factories) lives on the internal pyric/rules/internal/rtdb subpath instead.
+- [RTDB rules tooling](/__pyric/ui/docs/pyric-database-reference-rules-tooling.md): The RTDB constraints DSL (defineRtdbRules and the combinators) is public, re-exported directly from pyric/rules. The engine underneath it (expression parser, validator, linter, compile/simulate/serialize, and replay) is engine-internal, on the pyric/rules/internal/rtdb subpath. That subpath isn't covered by the public pyric/rules contract and may change without notice.
+- [Why RTDB rules authoring and deploy are separate](/__pyric/ui/docs/pyric-database-explanation-rules-authoring-and-deploy-are-separate.md): Pyric keeps Realtime Database rules authoring in pyric/rules (the constraints DSL, public). Shipping those rules to a real Firebase project is a separate concern: use firebase-tools or the Firebase Console.
+
+## pyric-admin / app
+
+- [pyric-admin/app](/__pyric/ui/docs/pyric-admin-app.md): This subpath owns the sandbox admin app registry. initializeApp returns a branded PyricAdminApp, and every other pyric-admin/* subpath uses that app's sandbox.
+
+## pyric-admin / firestore
+
+- [pyric-admin](/__pyric/ui/docs/pyric-admin-firestore.md): Admin-SDK-shaped Firestore adapter for the Pyric sandbox. Mirrors firebase-admin/firestore (db.collection(p).doc(p).get(), db.batch(), db.runTransaction()) over pyric/sandbox's in-process substrate. Streaming reads are covered too: a production-shaped onSnapshot ships as both a free function and a chainable .onSnapshot(...) method on refs and queries.
+- [Your first admin-shaped Firestore session](/__pyric/ui/docs/pyric-admin-firestore-tutorials-01-first-admin-session.md): In this tutorial you will use pyric-admin to write, read, batch, transact, and watch documents in a sandbox. By the end you will have seen every piece of the surface in action.
+- [How to run a transaction](/__pyric/ui/docs/pyric-admin-firestore-how-to-run-a-transaction.md): This guide shows you how to use runTransaction on a sandbox Firestore handle.
+- [How to seed and set rules](/__pyric/ui/docs/pyric-admin-firestore-how-to-seed-and-set-rules.md): This guide shows you how to use the sandbox-only setRules and seed methods on the Firestore handle.
+- [How to translate denials with denialContext](/__pyric/ui/docs/pyric-admin-firestore-how-to-translate-denials.md): This guide shows you how to read the structured denial frame attached to every permission-denied error from pyric-admin operations.
+- [How to use onSnapshot to watch a doc or query](/__pyric/ui/docs/pyric-admin-firestore-how-to-use-onsnapshot.md): This guide shows you how to register a snapshot listener and react to changes.
+- [How to write a batch](/__pyric/ui/docs/pyric-admin-firestore-how-to-write-a-batch.md): This guide shows you how to use WriteBatch for atomic multi-document writes.
+- [onSnapshot overloads](/__pyric/ui/docs/pyric-admin-firestore-reference-onsnapshot.md): The Web-SDK-shaped streaming surface. Four overload groups mirror firebase/firestore's onSnapshot exactly, so existing call sites copied from production code typecheck unchanged.
+- [Re-exported types](/__pyric/ui/docs/pyric-admin-firestore-reference-re-exported-types.md): pyric-admin/firestore re-exports a large surface of types from the sandbox admin-firestore implementation and pyric/sandbox so most consumers can import the Firestore admin surface from one place. This page lists what comes from where and why.
+- [SandboxFirestore surface](/__pyric/ui/docs/pyric-admin-firestore-reference-sandbox-firestore.md): The handle returned from getFirestore(ctx). Extends Firestore from firebase-admin/firestore (via the simulator's compat impl) and adds three sandbox-only methods.
+- [Error translation and instanceof SandboxError](/__pyric/ui/docs/pyric-admin-firestore-explanation-error-translation.md): Every operation through a SandboxFirestore handle that fails throws a SandboxError. The underlying simulator throws FirestoreSimError; the admin handle wraps every method, catches those, and re-throws as SandboxError with structured denialContext. This page explains the layer.
+- [Per-call delegate construction](/__pyric/ui/docs/pyric-admin-firestore-explanation-per-call-delegate.md): Every production-shaped method on SandboxFirestore constructs a fresh Firestore delegate from pyric/sandbox/admin-firestore per call. This page explains why and what it costs.
+- [Why mirror the admin SDK shape](/__pyric/ui/docs/pyric-admin-firestore-explanation-why-mirror-admin-shape.md): pyric-admin re-implements the firebase-admin/firestore API. Same chainable style, same method names, same arguments, same return types. The behaviour is sandbox-aware (it talks to pyric/sandbox instead of Google's servers), but the surface is faithful.
+
+## pyric-admin / auth
+
+- [pyric-admin/auth](/__pyric/ui/docs/pyric-admin-auth.md): Admin-shape Auth with swappable backends. getAuth(app) mirrors firebase-admin/auth and dispatches on the app handle from pyric-admin/app:
+
+## pyric-admin / database
+
+- [pyric-admin/database](/__pyric/ui/docs/pyric-admin-database.md): Admin-shape Realtime Database with swappable backends. getDatabase(app) mirrors firebase-admin/database and dispatches on the app handle from pyric-admin/app:
+
+## pyric-admin / storage
+
+- [pyric-admin/storage](/__pyric/ui/docs/pyric-admin-storage.md): Admin-shaped Cloud Storage for a sandbox. getStorage(app) reads the sandbox handle from pyric-admin/app:
+
+## @pyric/ui
+
+- [@pyric/ui](/__pyric/ui/docs/ui.md): Per-component reference. Each page is one-screen — import, minimal example, props table, common gotchas.
+- [<Badge>](/__pyric/ui/docs/ui-primitives-badge.md): Headless pill / tag. An inline <span> carrying data-pyric-badge and an optional data-pyric-badge-kind so consumers style categories with attribute selectors.
+- [<ConfirmDialog> + useConfirm](/__pyric/ui/docs/ui-primitives-confirmdialog.md): Headless confirmation dialog. Two ways to use:
+- [<CopyButton>](/__pyric/ui/docs/ui-primitives-copybutton.md): Clipboard button that exposes a data-copied attribute on the underlying <button> so consumers can style the success state. Ships no visual treatment of its own.
+- [<JsonView>](/__pyric/ui/docs/ui-primitives-jsonview.md): Headless collapsible JSON tree — one structural step above a <pre> dump. Object/array nodes are independently expandable; there's no editing and no syntax-color theme, just data-pyric-* hooks.
+- [<SegmentedControl>](/__pyric/ui/docs/ui-primitives-segmentedcontrol.md): Headless single-select chip group — reads as one widget, wired as an ARIA radiogroup.
+- [<ToastProvider> + useToast](/__pyric/ui/docs/ui-primitives-toast.md): Imperative toast queue. One <ToastProvider> per scope; any descendant calls useToast() to push toasts. Renders to document.body via portal.
+- [<VirtualList>](/__pyric/ui/docs/ui-primitives-virtuallist.md): Thin wrapper around @tanstack/react-virtual. Renders a scrollable container with absolutely-positioned rows; only the rows in view (plus overscan neighbors) mount to the DOM.
+- [<CollectionList>](/__pyric/ui/docs/ui-firestore-collectionlist.md): Headless list renderer for collections under a parent. The component is purely presentational — fetching is the consumer's job (via useCollectionList or otherwise).
+- [<DeleteWithConfirm>](/__pyric/ui/docs/ui-firestore-deletewithconfirm.md): Composition of useConfirm + useRecursiveDelete for safe deletion of a document or collection with progress tracking.
+- [<DocumentEditor>](/__pyric/ui/docs/ui-firestore-documenteditor.md): Compound component over useDocumentEditor. The hook owns a reducer-backed normalized field tree; the component renders the tree with per-type Edit widgets and add/remove affordances.
+- [<DocumentList>](/__pyric/ui/docs/ui-firestore-documentlist.md): Headless list renderer for documents in a collection. Above virtualizeThreshold (default 100), switches to virtualized rendering via <VirtualList>; below, renders a plain <ul>.
+- [<DocumentPreview>](/__pyric/ui/docs/ui-firestore-documentpreview.md): Read-only renderer for a Firestore document. Iterates top-level fields in lexicographic order; dispatches each value through the field-editor registry on its inferred type.
+- [<QueryBuilder>](/__pyric/ui/docs/ui-firestore-querybuilder.md): Single-level where/orderBy/limit query builder. Composes state into a real Firestore Query via the hook's buildQuery(base).
+- [<ReferencePicker>](/__pyric/ui/docs/ui-firestore-referencepicker.md): Pick a DocumentReference by typing a path OR by browsing the tree. Improvement over firebase-tools-ui's plain text input.
+- [<DeleteSelectionWithConfirm>](/__pyric/ui/docs/ui-storage-deleteselectionwithconfirm.md): Bulk + recursive delete behind the confirm-dialog primitive, with toasts on outcome — the storage counterpart of the Firestore half's <DeleteWithConfirm>. Objects delete via deleteObject; folders walk recursively (default impl: listAll-driven, including the create-folder placeholder sweep). Requires <ConfirmProvider> and <ToastProvider> ancestors.
+- [<ObjectBrowser>](/__pyric/ui/docs/ui-storage-objectbrowser.md): Headless row list for a storage path — folders first, then objects, from useStorageList's entries. Folder rows navigate, object rows select. Above virtualizeThreshold (default 100), switches to virtualized rendering via <VirtualList>; below, renders a plain <ul>.
+- [<ObjectInspector>](/__pyric/ui/docs/ui-storage-objectinspector.md): Headless inspector for one storage object: metadata fields + a content-type-driven preview. Previews come from a registry — image/ (blob-URL <img>) and text/ + application/json (text panel, 256KB cap, JSON pretty-printed) ship built in; consumers extend by prepending their own matchers. Bytes load lazily and only when the matched preview asks; blob URLs are revoked on path change/unmount.
+- [<PathBreadcrumb>](/__pyric/ui/docs/ui-storage-pathbreadcrumb.md): Headless breadcrumb for a storage path. Renders a root crumb plus one crumb per segment; every crumb (including the current one) is a real <button> firing onNavigate with that ancestor's absolute path.
+- [@pyric/ui/storage](/__pyric/ui/docs/ui-storage.md): Headless components + hooks for browsing AND administering Firebase Storage — list/navigate/select (the read path), upload, inspect, metadata editing, and bulk delete (the write path), plus rules-aware affordances (the gate pre-evaluates rules so denied actions warn BEFORE the click). Same one-handle contract as the Firestore half: every hook takes the sandbox FirebaseStorage handle from pyric/storage.
+- [<UploadDropzone>](/__pyric/ui/docs/ui-storage-uploaddropzone.md): Headless drop target for file and folder uploads. Slot-based — the children render the chrome; the component owns the drag wiring, flattens the drop (folders traverse recursively via webkitGetAsEntry), and emits DroppedFile { file, relativePath }[] ready for useObjectUpload.
+- [Rules-aware affordances](/__pyric/ui/docs/ui-storage-rules-aware-affordances.md): The M7 differentiator: the storage UI knows what the rules will say before the click. One hook — useStorageRulesGate — evaluates the current identity against paths with the same evaluator the sandbox enforces with; the components annotate themselves from its verdicts. No emulator-UI equivalent exists.
+- [useStorageRulesGate](/__pyric/ui/docs/ui-storage-usestoragerulesgate.md): Pre-flight rules evaluation — evaluate the current identity against storage paths before the click, so the UI can mark denied affordances (data-pyric-denied rows, disabled-with-reason buttons) instead of letting the user discover a denial through a thrown storage/unauthorized. Built on the pure evaluator exports from pyric/storage (parseStorageRules + evaluateStorageRules) — the same evaluator the sandbox enforces with.
+- [@pyric/ui/traffic](/__pyric/ui/docs/ui-traffic.md): Headless components + hooks for observing rule-eval traffic — a Chrome DevTools Network-panel-style log and a per-rule heatmap, plus stats and grouping. Decoupled from pyric/sandbox: the data hook takes a source function, so the same components work against the sandbox or a production log feed.
+- [<RuleHeatmap>](/__pyric/ui/docs/ui-traffic-ruleheatmap.md): Per-rule fire / deny rollup — one row per rule, busiest first. Pairs with useRuleHeatmap, which does the aggregation.
+- [<TrafficDetail>](/__pyric/ui/docs/ui-traffic-trafficdetail.md): The drill-in panel for one traffic event — header, a consumer classification slot, then JSON sections for auth / request / resource before+after, the reasons list, triggeredBy, and groupId.
+- [<TrafficLog> · <TrafficRow> · <TrafficGroupRow>](/__pyric/ui/docs/ui-traffic-trafficlog.md): The event stream — a Chrome DevTools Network-panel-style list. Below 100 rows it's a plain <ul>; above, it virtualizes via <VirtualList>. Pass items (from useTrafficGroups) instead of events for collapsible group rows.
+- [<TrafficStats>](/__pyric/ui/docs/ui-traffic-trafficstats.md): The aggregation panel — totals, deny rate, and count breakdowns by method / origin / path. Pairs with useTrafficStats.
+- [<AuthSignInHelper> + useAuthFlowHelper](/__pyric/ui/docs/ui-auth-authsigninhelper.md): Emulator-style sign-in helper for sandbox auth: when an app calls signInWithPopup / signInWithRedirect against a sandbox Auth handle, the flow parks on a helper request; this pair renders an account picker + add-account form and settles the app's promise.
+- [Auth users admin — useAuthUsers, <AuthUserList>, <AuthUserForm>](/__pyric/ui/docs/ui-auth-authusers.md): Emulator-style user administration for a sandbox Auth handle: a live users table, an add/edit form with emulator-grade validation, and confirm-gated destructive actions.
+
+## API reference
+
+- [API reference](/__pyric/ui/docs/api-reference.md): Published declarations for every supported Pyric package entry point.
+- [API reference: create-pyric](/__pyric/ui/docs/create-pyric-reference-api.md): Published declarations for create-pyric.
+- [API reference: pyric-admin/app](/__pyric/ui/docs/pyric-admin-app-reference-api.md): Published declarations for pyric-admin/app.
+- [API reference: pyric-admin/auth](/__pyric/ui/docs/pyric-admin-auth-reference-api.md): Published declarations for pyric-admin/auth.
+- [API reference: pyric-admin/database](/__pyric/ui/docs/pyric-admin-database-reference-api.md): Published declarations for pyric-admin/database.
+- [API reference: pyric-admin/firestore](/__pyric/ui/docs/pyric-admin-firestore-reference-api.md): Published declarations for pyric-admin/firestore.
+- [API reference: pyric-admin/storage](/__pyric/ui/docs/pyric-admin-storage-reference-api.md): Published declarations for pyric-admin/storage.
+- [API reference: pyric/ai](/__pyric/ui/docs/pyric-ai-reference-api.md): Published declarations for pyric/ai.
+- [API reference: pyric/ai/scripting](/__pyric/ui/docs/pyric-ai-scripting-reference-api.md): Published declarations for pyric/ai/scripting.
+- [API reference: pyric/app](/__pyric/ui/docs/pyric-app-reference-api.md): Published declarations for pyric/app.
+- [API reference: pyric/auth](/__pyric/ui/docs/pyric-auth-reference-api.md): Published declarations for pyric/auth.
+- [API reference: @pyric/cli/assurance/browser](/__pyric/ui/docs/pyric-cli-assurance-browser-reference-api.md): Published declarations for @pyric/cli/assurance/browser.
+- [API reference: @pyric/cli/assurance](/__pyric/ui/docs/pyric-cli-assurance-reference-api.md): Published declarations for @pyric/cli/assurance.
+- [API reference: @pyric/cli/bridge/client](/__pyric/ui/docs/pyric-cli-bridge-client-reference-api.md): Published declarations for @pyric/cli/bridge/client.
+- [API reference: @pyric/cli/bridge](/__pyric/ui/docs/pyric-cli-bridge-reference-api.md): Published declarations for @pyric/cli/bridge.
+- [API reference: @pyric/cli/credentials/node](/__pyric/ui/docs/pyric-cli-credentials-node-reference-api.md): Published declarations for @pyric/cli/credentials/node.
+- [API reference: @pyric/cli/discover](/__pyric/ui/docs/pyric-cli-discover-reference-api.md): Published declarations for @pyric/cli/discover.
+- [API reference: @pyric/cli/register](/__pyric/ui/docs/pyric-cli-register-reference-api.md): Published declarations for @pyric/cli/register.
+- [API reference: @pyric/cli/remote](/__pyric/ui/docs/pyric-cli-remote-reference-api.md): Published declarations for @pyric/cli/remote.
+- [API reference: @pyric/cli/serve/worker](/__pyric/ui/docs/pyric-cli-serve-worker-reference-api.md): Published declarations for @pyric/cli/serve/worker.
+- [API reference: @pyric/cli/verify](/__pyric/ui/docs/pyric-cli-verify-reference-api.md): Published declarations for @pyric/cli/verify.
+- [API reference: @pyric/cli/vite](/__pyric/ui/docs/pyric-cli-vite-reference-api.md): Published declarations for @pyric/cli/vite.
+- [API reference: pyric/database](/__pyric/ui/docs/pyric-database-reference-api.md): Published declarations for pyric/database.
+- [API reference: pyric/firestore](/__pyric/ui/docs/pyric-firestore-reference-api.md): Published declarations for pyric/firestore.
+- [API reference: pyric/firestore-values](/__pyric/ui/docs/pyric-firestore-values-reference-api.md): Published declarations for pyric/firestore-values.
+- [API reference: pyric/messaging](/__pyric/ui/docs/pyric-messaging-reference-api.md): Published declarations for pyric/messaging.
+- [API reference: pyric/messaging/sw](/__pyric/ui/docs/pyric-messaging-sw-reference-api.md): Published declarations for pyric/messaging/sw.
+- [API reference: pyric/rules](/__pyric/ui/docs/pyric-rules-reference-api.md): Published declarations for pyric/rules.
+- [API reference: pyric/sandbox/database](/__pyric/ui/docs/pyric-sandbox-database-reference-api.md): Published declarations for pyric/sandbox/database.
+- [API reference: pyric/sandbox/firestore](/__pyric/ui/docs/pyric-sandbox-firestore-reference-api.md): Published declarations for pyric/sandbox/firestore.
+- [API reference: pyric/sandbox](/__pyric/ui/docs/pyric-sandbox-reference-api.md): Published declarations for pyric/sandbox.
+- [API reference: pyric/storage](/__pyric/ui/docs/pyric-storage-reference-api.md): Published declarations for pyric/storage.
+- [API reference: @pyric/ui/agents](/__pyric/ui/docs/pyric-ui-agents-reference-api.md): Published declarations for @pyric/ui/agents.
+- [API reference: @pyric/ui/auth/hooks](/__pyric/ui/docs/pyric-ui-auth-hooks-reference-api.md): Published declarations for @pyric/ui/auth/hooks.
+- [API reference: @pyric/ui/auth](/__pyric/ui/docs/pyric-ui-auth-reference-api.md): Published declarations for @pyric/ui/auth.
+- [API reference: @pyric/ui/events/hooks](/__pyric/ui/docs/pyric-ui-events-hooks-reference-api.md): Published declarations for @pyric/ui/events/hooks.
+- [API reference: @pyric/ui/events](/__pyric/ui/docs/pyric-ui-events-reference-api.md): Published declarations for @pyric/ui/events.
+- [API reference: @pyric/ui/firestore/hooks](/__pyric/ui/docs/pyric-ui-firestore-hooks-reference-api.md): Published declarations for @pyric/ui/firestore/hooks.
+- [API reference: @pyric/ui/firestore](/__pyric/ui/docs/pyric-ui-firestore-reference-api.md): Published declarations for @pyric/ui/firestore.
+- [API reference: @pyric/ui/primitives](/__pyric/ui/docs/pyric-ui-primitives-reference-api.md): Published declarations for @pyric/ui/primitives.
+- [API reference: @pyric/ui/rtdb](/__pyric/ui/docs/pyric-ui-rtdb-reference-api.md): Published declarations for @pyric/ui/rtdb.
+- [API reference: @pyric/ui/rules/hooks](/__pyric/ui/docs/pyric-ui-rules-hooks-reference-api.md): Published declarations for @pyric/ui/rules/hooks.
+- [API reference: @pyric/ui/rules](/__pyric/ui/docs/pyric-ui-rules-reference-api.md): Published declarations for @pyric/ui/rules.
+- [API reference: @pyric/ui/storage/hooks](/__pyric/ui/docs/pyric-ui-storage-hooks-reference-api.md): Published declarations for @pyric/ui/storage/hooks.
+- [API reference: @pyric/ui/storage](/__pyric/ui/docs/pyric-ui-storage-reference-api.md): Published declarations for @pyric/ui/storage.
+- [API reference: @pyric/ui/traffic/hooks](/__pyric/ui/docs/pyric-ui-traffic-hooks-reference-api.md): Published declarations for @pyric/ui/traffic/hooks.
+- [API reference: @pyric/ui/traffic](/__pyric/ui/docs/pyric-ui-traffic-reference-api.md): Published declarations for @pyric/ui/traffic.

package/dist/serve/entries/ai.d.ts

@@ -0,0 +1,4 @@
+import { getAI as pyricGetAI } from 'pyric/ai';
+export { AIError, AIErrorCode, Backend, BackendType, GoogleAIBackend, VertexAIBackend, AIModel, ChatSession, ChatSessionBase, GenerativeModel, AnyOfSchema, ArraySchema, BooleanSchema, IntegerSchema, NumberSchema, ObjectSchema, Schema, StringSchema, BlockReason, FinishReason, FunctionCallingMode, HarmBlockMethod, HarmBlockThreshold, HarmCategory, HarmProbability, HarmSeverity, ImageConfigAspectRatio, ImageConfigImageSize, Language, Modality, Outcome, POSSIBLE_ROLES, ResponseModality, SchemaType, ThinkingLevel, URLRetrievalStatus, getGenerativeModel, } from 'pyric/ai';
+export declare const getAI: typeof pyricGetAI;
+//# sourceMappingURL=ai.d.ts.map

package/dist/serve/entries/ai.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ai.d.ts","sourceRoot":"","sources":["../../../src/serve/entries/ai.ts"],"names":[],"mappings":"AA6BA,OAAO,EAAE,KAAK,IAAI,UAAU,EAAE,MAAM,UAAU,CAAC;AAU/C,OAAO,EACL,OAAO,EACP,WAAW,EACX,OAAO,EACP,WAAW,EACX,eAAe,EACf,eAAe,EACf,OAAO,EACP,WAAW,EACX,eAAe,EACf,eAAe,EACf,WAAW,EACX,WAAW,EACX,aAAa,EACb,aAAa,EACb,YAAY,EACZ,YAAY,EACZ,MAAM,EACN,YAAY,EACZ,WAAW,EACX,YAAY,EACZ,mBAAmB,EACnB,eAAe,EACf,kBAAkB,EAClB,YAAY,EACZ,eAAe,EACf,YAAY,EACZ,sBAAsB,EACtB,oBAAoB,EACpB,QAAQ,EACR,QAAQ,EACR,OAAO,EACP,cAAc,EACd,gBAAgB,EAChB,UAAU,EACV,aAAa,EACb,kBAAkB,EAClB,kBAAkB,GACnB,MAAM,UAAU,CAAC;AA+IlB,eAAO,MAAM,KAAK,EA+Bb,OAAO,UAAU,CAAC"}