Update to Fullstory

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -17,44 +17,44 @@
 
 ## MCP Tools
 
-The tools follow this pattern:
-
-```
-fullstory:session_open  →  (fullstory:session_screenshot | fullstory:session_get_a11y_tree | fullstory:session_diff)*  →  fullstory:session_close
-```
-
-1. **`fullstory:session_open`**: Pass `session_id`. Returns event summaries and a `client_id`. The `session_id` accepts a bare id (`<device-id>:<session-id>`), a full session URL, or a short link.
-2. **`fullstory:session_screenshot`**: Rendered screenshot at a timestamp. Pass `client_id`, `page_id`, `timestamp` (ms from session start); optional `full_page` for the whole scrollable page. Sequential calls with increasing timestamps are faster.
-3. **`fullstory:session_get_a11y_tree`**: Page structure (accessibility tree / DOM) at a timestamp. Pass `client_id`, `page_id`, `timestamp`.
-4. **`fullstory:session_diff`**: Highlights changes between two timestamps within a page. Pass `client_id`, `page_id`, `from_ts`, `to_ts`.
-5. **`fullstory:session_close`**: Always call when done to free resources. Pass `client_id`.
-
-`session_view` is deprecated and removed — it was split into `session_screenshot` (the rendered image) and `session_get_a11y_tree` (page structure). Use those two instead.
+| Goal | Tool |
+|------|------|
+| Open a session | `fullstory:review-open` |
+| See what happened in a time window | `fullstory:review-zoom` |
+| See the screen at a moment | `fullstory:review-snapshot` |
+| See what changed on screen | `fullstory:review-snapshot` at two timestamps, compare the trees |
+| Close | `fullstory:review-close` |
 
 ## Workflow
 
 ### 1. Open the Session
 ```
-fullstory:session_open(session_id="https://app.fullstory.com/ui/<org-id>/session/<device-id>:<session-id>")
+fullstory:review-open(session_url="https://app.fullstory.com/ui/<org-id>/session/<device-id>:<session-id>")
 ```
-Returns: event summaries (navigation, clicks, errors, custom events) and `client_id`. You can also pass a bare `<device-id>:<session-id>` id or a short link as `session_id`.
+Returns: a map of the session, an event slice, and a `client_id`.
+
+Pass the whole URL as `session_url`. Here `session_id` means only the session part and must come with `device_id`. Other ways to open: `trace_id`, `trace_url`, `email_address`, `user_uid`.
 
 ### 2. Identify Key Moments
-Scan event summaries for:
+Scan the returned events for:
 - **Page navigations** — entry points into different views
 - **Click events** — user interactions with buttons, links, forms
 - **Error events** — console errors, network failures, renderer errors
 - **Rage clicks / mouse thrash** — signs of UX friction
 - **Custom events** — application-specific telemetry
 
-Note the `page_id` and `timestamp` for each moment you want to inspect.
+To read more of one stretch, narrow by time:
+```
+fullstory:review-zoom(client_id="<id>", t0_ms=<start_ms>, t1_ms=<end_ms>)
+```
 
 ### 3. Visual Inspection
-At each key moment, capture the screenshot — and the accessibility tree when you need the structure or text content:
+At each key moment, use `fullstory:review-snapshot` to see what the user saw. It finds the page from the timestamp, so you never pass a page id:
 ```
-fullstory:session_screenshot(client_id="<id>", page_id="<page>", timestamp=<ms>)
-fullstory:session_get_a11y_tree(client_id="<id>", page_id="<page>", timestamp=<ms>)
+fullstory:review-snapshot(client_id="<id>", timestamp=<ms>)
 ```
+It returns a screenshot and the component tree. Use the tree when you need element structure (roles, labels, hierarchy).
+
 Check for:
 - Layout correctness (elements positioned properly)
 - Content rendering (text, images, icons present)
@@ -62,11 +62,12 @@
 - Empty/loading states handled
 
 ### 4. Compare States
-For before/after analysis:
+For before/after analysis, take a snapshot at each timestamp and compare the two trees:
 ```
-fullstory:session_diff(client_id="<id>", page_id="<page>", from_ts=<before_ms>, to_ts=<after_ms>)
+fullstory:review-snapshot(client_id="<id>", timestamp=<before_ms>)
+fullstory:review-snapshot(client_id="<id>", timestamp=<after_ms>)
 ```
-Returns a screenshot with changed regions highlighted plus a text summary of component changes.
+Whole trees are large. To keep the comparison cheap, focus on one element with `component_id` from an earlier snapshot, or ask for the interactive elements only with `lens="interactive"`.
 
 ### 5. Report Findings
 Summarize what was observed:
@@ -78,26 +79,27 @@
 ### 6. Cleanup
 Always close the session:
 ```
-fullstory:session_close(client_id="<id>")
+fullstory:review-close(client_id="<id>")
 ```
 
 ## Example
 
 When a user reports "the checkout button didn't work" and provides a session URL:
 
-1. Call `fullstory:session_open` with the session URL as `session_id`
-2. Find the checkout-related events in the summaries (note the `page_id` and `timestamp`)
-3. Use `fullstory:session_screenshot` — and `fullstory:session_get_a11y_tree` if you need the DOM — to see the UI state just before the button click
-4. Use `fullstory:session_diff` to compare before/after the click attempt to see what changed (or didn't)
+1. Call `fullstory:review-open` with `session_url`
+2. Find the checkout-related events (note the timestamps)
+3. Use `fullstory:review-snapshot` to see the UI state just before the button click
+4. Take a second snapshot just after the click and compare the trees to see what changed (or didn't)
 5. Report findings: what the user saw, any errors, why the action may have failed
-6. Call `fullstory:session_close` to clean up
+6. Call `fullstory:review-close` to clean up
 
 ## Common Mistakes
 
 | Mistake | Fix |
 |---------|-----|
-| Forgetting to close session | Always call `fullstory:session_close` — even on errors |
-| Using `session_view` | Removed — use `fullstory:session_screenshot` + `fullstory:session_get_a11y_tree` |
+| Forgetting to close session | Always call `fullstory:review-close` — even on errors |
 | Random timestamp access | Use sequential increasing timestamps for faster access |
-| Skipping the diff tool | `fullstory:session_diff` highlights changes automatically — faster than comparing two screenshots manually |
-| Not checking for error events | Scan event summaries for errors before visual inspection |
+| Passing the session URL as `session_id` to `fullstory:review-open` | Use `session_url` for a URL. `session_id` is only the session part and needs `device_id` |
+| Taking whole-page snapshots to compare states | Focus with `component_id` or `lens="interactive"` |
+| Not checking for error events | Scan the events for errors before visual inspection |
+