[GH-ISSUE #881] [Feature] Observe website execution and trace source attribution #359

New issue

Closed

opened 2026-10-15 18:24:15 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:24:15 +00:00

Owner

Originally created by @N0zoM1z0 on GitHub (Oct 7, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/881

Parent: #774. Follows module/import-map and source-map identity work in #851.

Need

Current page/source inventory and request initiator locations establish retained or loaded sources; they do not establish which code executed during a selected observation window. The user requested runtime attribution as the next website capability.

Scope

A narrow shared application workflow with a replaceable browser execution port. Reuse current CDP endpoint/target identity and allowed-origin validation; keep provider wire protocols out of domain/application.
Precise execution coverage for an explicit target and finite observation window, including actual armed/ended timestamps, source/script identity, UTF-16 ranges, observed counts and unknown/incomplete facets.
Explicit instrumentation/reset effects and lifecycle cleanup. The chosen operation expresses intent; no redundant approval booleans or replay language.
Inspect selected DOM event listener source locations and associate available request initiator locations with exact source identities. Preserve ambiguity and distinguish association from UI causality.
Retain provider-reported hash separately from independently calculated source digest. Loaded is not executed; coverage is not proof of causality.

Acceptance

Real Chrome fixture with independently triggered external action after readiness, executed and unexecuted branches, Unicode offsets, selected listener locations and initiator association. CLI/MCP parity, actual SDK schemas, cancellation/disconnect/navigation/cleanup regressions and no page application evaluation beyond explicitly declared authority. Extend conditional Chrome CI for these concrete claims.

Originally created by @N0zoM1z0 on GitHub (Oct 7, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/881 Parent: #774. Follows module/import-map and source-map identity work in #851. ## Need Current page/source inventory and request initiator locations establish retained or loaded sources; they do not establish which code executed during a selected observation window. The user requested runtime attribution as the next website capability. ## Scope - A narrow shared application workflow with a replaceable browser execution port. Reuse current CDP endpoint/target identity and allowed-origin validation; keep provider wire protocols out of domain/application. - Precise execution coverage for an explicit target and finite observation window, including actual armed/ended timestamps, source/script identity, UTF-16 ranges, observed counts and unknown/incomplete facets. - Explicit instrumentation/reset effects and lifecycle cleanup. The chosen operation expresses intent; no redundant approval booleans or replay language. - Inspect selected DOM event listener source locations and associate available request initiator locations with exact source identities. Preserve ambiguity and distinguish association from UI causality. - Retain provider-reported hash separately from independently calculated source digest. Loaded is not executed; coverage is not proof of causality. ## Acceptance Real Chrome fixture with independently triggered external action after readiness, executed and unexecuted branches, Unicode offsets, selected listener locations and initiator association. CLI/MCP parity, actual SDK schemas, cancellation/disconnect/navigation/cleanup regressions and no page application evaluation beyond explicitly declared authority. Extend conditional Chrome CI for these concrete claims.

bsakaguchi

2026-10-15 18:24:15 +00:00

closed this issue
added the
P1: high

area: mcp

area: domain

enhancement
labels

bsakaguchi added

enhancement

and removed

enhancement

labels

2026-10-31 00:29:05 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

morluto/rea#359

No description provided.

Rows
Columns