@dasasian/firebase-structured-logger 0.9.0 → 1.1.0

package/skills/logs/SKILL.md

@@ -170,6 +170,16 @@ bc.nav(screen: string): void                                   // on navigation
 bc.error(type: string, data?: Record<string, unknown>): void   // on errors
 ```
 
+Import `enableNavigation` from `firebase-structured-logger/client/navigation`:
+```ts
+enableNavigation(options?: { routeFor?: (path: string) => string | undefined; cleanPath?: (path: string) => string; path?: false }): void
+```
+- Call once at startup. Every route change becomes a `nav` breadcrumb, and every entry
+  gets `route` (the pattern, `/orders/:id`), `path` (the real path) and `routeSource`.
+- When an app has called it, do not flag a missing `bc.nav` on route changes — it is
+  automatic. Suggest it for a single-page app that hand-writes `bc.nav` everywhere.
+- A separate import on purpose: apps that do not use it ship none of it.
+
 Import `sendFeedback` from `firebase-structured-logger/client`:
 ```ts
 sendFeedback(text: string, extras?: { labels?: Partial<AppLabels>; attachments?: Record<string, Blob | File | string> }): void

package/skills/query-logs/SKILL.md

@@ -8,6 +8,20 @@ The `firebase_functions_logs` MCP tool reads from:
 - **Production**: Google Cloud Logging (default)
 - **Development**: Local JSONL file when `DEV_LOG_FILE` env var is set in the MCP server
 
+## Missing or odd logs? Check the setup first
+
+Before reading logs to explain why something is missing — no entries at all, stacks that
+stay minified, no attachments — run the setup check. Most of those failures are silent
+misconfigurations, and doctor reads them straight off disk:
+
+```
+npx fsl doctor --json
+```
+
+`findings` lists anything wrong, each with an `id`, `level` and `fix`; `setup` says how
+logging, trace ids and Storage will behave. An empty `findings` means the setup is not
+the problem, and the answer is in the logs.
+
 ## Queryable Labels
 
 All entries written by firebase-structured-logger include these labels:
@@ -16,7 +30,10 @@ All entries written by firebase-structured-logger include these labels:
 |-------|-------------|
 | `appId` | Application identifier (e.g. `acme`, `store`) |
 | `userId` | Firebase Auth UID |
-| `screen` | Current screen name |
+| `screen` | Current screen name (falls back to `route` when the app never set one) |
+| `route` | Route pattern, e.g. `/orders/:id/items` — group by this (apps using `enableNavigation`) |
+| `path` | Real path, e.g. `/orders/1042/items` — one specific page or record; query string never stored |
+| `routeSource` | `router` (the app named the route) or `pattern` (ids replaced by rule) |
 | `releaseId` | Git short hash or explicit release ID |
 | `platform` | `ios`, `android`, `macos`, `windows`, `web` |
 | `browser` | `chrome`, `firefox`, `safari`, `edge` |