Files
reverse-engineering-anything/docs/specs/agent-environments/rich-captures/plan.md
T
f93a0335a8 feat(analysis-view): project rich captures from Evidence files and template path pairs (#5293)
Project large local Evidence captures through the authenticated file-source boundary and add guarded opt-in sibling-pair path inference. Preserve request cancellation, resource ownership and file-relative validation diagnostics.

Validated relevant source and compiled CLI/MCP/environment boundaries, static/build/docs/catalog gates, and a real isolated Gitea 28.2.0 capture through CLI, default stdio MCP and HTTP replay. Current-head automated review passed; unrelated long-running platform jobs may still be pending.

Co-authored-by: Edgar Arakelyan <edgar.arakelyan@scale.com>
Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
Co-authored-by: gensokyo-dev <gensokyo-dev@users.noreply.github.com>
2026-10-20 10:33:52 +08:00

19 lines
1000 B
Markdown

# Plan
1. Add the `evidence-file` source to `analysisViewSourceSchema`
(`src/domain/analysisView/analysisView.ts`).
2. Add `inspectAnalysisViewWithFiles` / `inspectAnalysisViewValidatedWithFiles`
to `AnalysisViewService`: read with `readJsonFile`, authenticate with
`parseEvidence`, then project through the retained path with a lookup that
returns the file's Evidence. The synchronous path refuses an unread file
source.
3. Route the CLI command (with `source.path` resolved against the working
directory) and the MCP tool through the file-aware entry point.
4. Add `sibling-pair-variance` to `TEMPLATE_RULES`, with its merge pass before
`sibling-variance`, its parameter names and its segment-limit limitation.
5. Document both in the tool contract, `docs/cli.md` and
`docs/web-network-captures.md`.
6. Tests: service (file equals inline; a capture refused inline is accepted
from a file; refusals), CLI and MCP boundaries, and the pair rule's merges
and non-merges.