From 944a92253c749e1c72c96563d3bf43aa30bfa039 Mon Sep 17 00:00:00 2001 From: Rogee Date: Fri, 21 Aug 2026 14:38:22 +0800 Subject: [PATCH] HH-390: document cache event collection Co-authored-by: multica-agent --- AGENTS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index eb69ce1..e6c80ca 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -18,7 +18,7 @@ ## Architecture and data flow - CDP access validates short-lived credentials, protects the WebSocket connection, discovers targets, binds sessions, maintains heartbeats, and reports disconnects. -- The collector enables CDP `Network`/`Fetch` as needed, correlates `requestId`, records HTTP and WebSocket lifecycles, and reads response bodies only on demand. +- The collector enables CDP `Network`/`Fetch` as needed, correlates `requestId`, records HTTP, cache, and WebSocket lifecycles, and reads response bodies only on demand. - The policy layer normalizes events, filters by URL/resource/status, and applies redaction, sampling, size, event, and retention limits. - Start storage and query with JSONL containing session, target, request, timing, URL/method, safe header summaries, body availability/reference, and error fields. Do not persist full bodies by default. - Keep query and redacted export session-isolated and paginated. Re-evaluate Postgres, object storage, and asynchronous streams only after MVP evidence. @@ -30,7 +30,7 @@ CDP observes browser-internal decrypted events. It is not a client/server proxy, ## Priority -- P0: single-instance CDP access; HTTP request/response/failure and WebSocket events; `requestId` correlation; default redaction; body/event limits; JSONL export; session isolation; disconnect observability. +- P0: single-instance CDP access; HTTP request/response/failure, cache, and WebSocket events; `requestId` correlation; default redaction; body/event limits; JSONL export; session isolation; disconnect observability. - P1: multiple targets/sessions, paginated query, metrics/alerts, permission audit, asynchronous event streams, and tiered storage. - P2: Fetch mutation, versioned rules, replay, browser-cluster access, and a minimal console.