fix: yarn lock

.mcp.json

@@ -0,0 +1,12 @@
+{
+  "mcpServers": {
+    "falcon": {
+      "args": [
+        "mcp",
+        "serve"
+      ],
+      "command": "falcon",
+      "type": "stdio"
+    }
+  }
+}

.roo/mcp.json

@@ -0,0 +1,12 @@
+{
+  "mcpServers": {
+    "falcon": {
+      "args": [
+        "mcp",
+        "serve"
+      ],
+      "command": "falcon",
+      "type": "stdio"
+    }
+  }
+}

.roo/rules/falcon.md

@@ -0,0 +1,15 @@
+## RepoFalcon Code Knowledge Graph
+
+This repository has a pre-built code knowledge graph. You MUST use the `falcon_*` MCP tools to understand the codebase before making changes.
+
+**Mandatory workflow:**
+1. At the start of every task, call `falcon_architecture` to understand the project structure
+2. Before modifying any file, call `falcon_file_context` with its path to see what depends on it
+3. Before renaming or refactoring a symbol, call `falcon_symbol_lookup` to find all usages
+4. To understand a package's role, call `falcon_package_info` instead of reading files one by one
+5. Use `falcon_search` instead of grep/glob for finding symbols, files, or packages by name
+6. After major refactoring (renamed packages, moved files), call `falcon_refresh` to re-index
+
+These tools are faster and more accurate than grep — they use a pre-computed dependency graph with full symbol resolution.
+
+If the MCP tools are unavailable, read `.falcon/CONTEXT.md` for a static architecture summary as a fallback.

CLAUDE.md

@@ -0,0 +1,17 @@
+<!-- BEGIN FALCON -->
+## RepoFalcon Code Knowledge Graph
+
+This repository has a pre-built code knowledge graph. You MUST use the `falcon_*` MCP tools to understand the codebase before making changes.
+
+**Mandatory workflow:**
+1. At the start of every task, call `falcon_architecture` to understand the project structure
+2. Before modifying any file, call `falcon_file_context` with its path to see what depends on it
+3. Before renaming or refactoring a symbol, call `falcon_symbol_lookup` to find all usages
+4. To understand a package's role, call `falcon_package_info` instead of reading files one by one
+5. Use `falcon_search` instead of grep/glob for finding symbols, files, or packages by name
+6. After major refactoring (renamed packages, moved files), call `falcon_refresh` to re-index
+
+These tools are faster and more accurate than grep — they use a pre-computed dependency graph with full symbol resolution.
+
+If the MCP tools are unavailable, read `.falcon/CONTEXT.md` for a static architecture summary as a fallback.
+<!-- END FALCON -->

app/yarn.lock

@@ -7096,6 +7096,7 @@ __metadata:
     expo-contacts: "npm:~14.2.5"
     expo-dev-client: "npm:~5.2.4"
     expo-device: "npm:~7.1.4"
+    expo-file-system: "npm:~18.1.11"
     expo-gradle-ext-vars: "npm:^0.1.1"
     expo-linear-gradient: "npm:~14.1.5"
     expo-linking: "npm:~7.1.7"