@alwaysmeticulous/debug-workspace 2.286.0 → 2.287.0

package/dist/templates/CLAUDE.md

@@ -243,12 +243,38 @@ replay), and drop into phase 4 only as needed.
 9. **Logs index** -- grep `debug-data/logs-index/<role>-<replayId>.txt` by source
    (`source=application`), type (`type=warn`), keyword, or virtual time (`vt=1234`).
 
+### 3b. Check network match quality (when diffs involve partial matches)
+
+When the replay shows "Low accuracy: Network issues", or `network-log/` shows pollyReplay
+entries with a `repair=` suffix (indicating session repair was needed to serve a response)
+in the root cause time span (events preceding the first visual difference), this is a
+high-priority check:
+
+1. Grep `timeline.ndjson` for `pollyReplay` events near the first divergence point. Each
+   event's `data` contains both:
+   - `data.pollyRequest.request.url` -- the **actual request** made during replay.
+   - `data.matchedRequest.request.url` -- the **original recorded request** whose saved
+     response was served (null if no match was found).
+2. Compare these URLs for each pollyReplay event. If they differ significantly (different
+   endpoint, different query parameters, different resource), the response served almost
+   certainly doesn't match what the application expected. This is a common root cause for
+   diffs and should be flagged.
+
+For example, if the actual request was `GET /api/v1/items` but Meticulous served a saved
+response originally recorded for `GET /api/v1/orders?page=1&search=...`, the
+response schema is likely wrong for the requesting code, causing downstream UI differences.
+
+When you identify such a mismatch, report it as the likely root cause and note that the diff
+can be disregarded -- it stems from a network matching issue, not a real code regression.
+
 ### 4. Deeper dives (as needed)
 
 10. **Screenshot timeline context** -- `debug-data/screenshot-timeline-context/` for the 30
     events before and 10 after each screenshot.
 11. **Network activity** -- grep `debug-data/network-log/` for endpoints, status codes,
-    domains.
+    domains. For any pollyReplay entries with a `repair=` suffix, cross-reference with
+    `timeline.ndjson` to compare the actual request URL against the matched recorded request
+    URL (see phase 3b above).
 12. **Virtual time progression** -- `diff` on `debug-data/vt-progression/` files to find
     where head and base diverge.
 13. **Replay parameters** -- `debug-data/params-diffs/` for computed diffs, or

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alwaysmeticulous/debug-workspace",
-  "version": "2.286.0",
+  "version": "2.287.0",
   "description": "Shared debug workspace pipeline for investigating Meticulous diffs and replays",
   "license": "ISC",
   "main": "dist/index.js",
@@ -14,7 +14,7 @@
     "prettier": "^3.5.3",
     "@alwaysmeticulous/client": "2.286.0",
     "@alwaysmeticulous/common": "2.283.1",
-    "@alwaysmeticulous/downloading-helpers": "2.286.0"
+    "@alwaysmeticulous/downloading-helpers": "2.287.0"
   },
   "devDependencies": {
     "vitest": "^4.1.4"