Skip to content

Data Liberation: add portable website capture - #4697

Closed
chubes4 wants to merge 1 commit into
trunkfrom
feat/data-liberation-portable-capture
Closed

Data Liberation: add portable website capture#4697
chubes4 wants to merge 1 commit into
trunkfrom
feat/data-liberation-portable-capture

Conversation

@chubes4

@chubes4 chubes4 commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Related issues

Proposed changes

  • Add bounded portable website artifact capture and export.
  • Preserve responsive HTML, resources, interactions, layout geometry, provenance, and media references.
  • Add bounded Wix route discovery, including same-page anchor and subpath handling.
  • Expose capture through the DLA CLI, MCP server, and committed runtime bundles.
  • Improve shared screenshot, extraction, and media handling used by existing DLA workflows.
  • Keep responsive mobile CSS when desktop and mobile bodies match but their styles differ.

This PR is deliberately limited to packages/data-liberation-agent/**. Studio-owned create --from orchestration remains in #3952.

Attribution

The focused commit preserves contributions from Aagam Shah, Ellen Bauer, and Claude Fable 5 through co-author trailers.

Verification

  • npm -w data-liberation run build
  • Deterministic bundle rebuild with a clean packages/data-liberation-agent/dist tree
  • src/lib/capture-export.test.ts: 28 passed
  • Full DLA suite exercised locally: 3,016 tests passed in the serial run; four late timeout/state-contamination cases all passed individually in fresh processes
  • Every failed file from the initial concurrent run passed serially or in isolation

How AI was used

OpenAI GPT-5.6 Sol via OpenCode was used to project the package-only diff from #3952 onto current trunk, inspect scope and attribution, run verification, diagnose local browser-test timeout contamination, and prepare this PR.

Extract the shared Data Liberation runtime from #3952 so portable capture, responsive evidence, resource and interaction capture, Wix discovery, and media handling can land independently of Studio CLI orchestration.

Co-authored-by: Aagam Shah <aagam.shah@automattic.com>

Co-authored-by: Ellen Bauer <ellen.bauer@automattic.com>

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
@wpmobilebot

Copy link
Copy Markdown
Collaborator

📊 Performance Test Results

Comparing 96043fb vs trunk

app-size

Metric trunk 96043fb Diff Change
App Size (Mac) 1422.06 MB 1422.12 MB +0.06 MB ⚪ 0.0%

site-editor

Metric trunk 96043fb Diff Change
load 1173 ms 1192 ms +19 ms ⚪ 0.0%

site-startup

Metric trunk 96043fb Diff Change
siteCreation 7548 ms 7532 ms 16 ms ⚪ 0.0%
siteStartup 2892 ms 3375 ms +483 ms 🔴 16.7%

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

@chubes4 chubes4 closed this Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants