Route studio create --from URLs through Data Liberation - #3952
Conversation
|
CI follow-up pushed in
AI assistance: openai/gpt-5.6-sol via OpenCode diagnosed the CI lane overlap, drafted the one-line test-selection change, and ran verification. Chris Huber remains responsible for the change. |
1,145-route scale validationThe latest branch head (
This proves the Studio orchestration and dependent SSI batching path can handle the target scale. It does not mark the generated site as fidelity-complete: Richlynn still has 13,055 Dependency PRs:
Validation on the pushed Studio head: AI assistance: openai/gpt-5.6-sol via OpenCode was used for scale-run diagnosis, implementation support, verification, and drafting this evidence update. Chris Huber remains responsible for the submitted changes. |
|
The You can do so via: That being said, switching out liberate's tooling to a different set of direct calls would make sense if the |
|
@borkweb I have not compared the outputs side by side, but I was hoping the approaches could coexist initially. This PR intentionally avoids disrupting existing behavior. Longer term, I think Data Liberation could own the browser-dependent stages: client-side rendering, runtime behavior, and the visual feedback loop, and use the Studio CLI to materialize the site. The shared contract would be a clean HTML-based website artifact, regardless of the original source. I think that refactoring can be explored separately from this PR. Redirecting |
f837702 to
1cf64f6
Compare
|
Synced the DLA iPhone mobile capture identity repair into the existing draft, resolving the generated-bundle-only rebase conflict by rebuilding from the rebased vendor source. Verification: vendor targeted test and full vendor suite passed (87 files, 907 tests); Studio CLI build, lint, and typecheck passed. Full Studio test has 14 environment failures after the fresh dependency setup because the bundled SQLite integration was initially absent; postinstall then completed the runtime asset setup. AI assistance: OpenAI gpt-5.6-terra via OpenCode performed source-level vendoring, regeneration, rebase, and verification. |
Sync the vendored Data Liberation Agent from Automattic/data-liberation-agent@9f03774.
…260911 # Conflicts: # packages/data-liberation-agent/dist/mcp-server.bundle.mjs # packages/data-liberation-agent/scripts/block-fixer/package-lock.json
Proposed Changes
studio create --from <url>routes through Data Liberation and materializes its portable artifact through Static Site Importer. The vendored engine is synchronized with Automattic/data-liberation-agenttrunkat02d8d6403060a859a9846a5c41086cf00b03a8f9, including the URL-scheme allowlist merged in Automattic/data-liberation-agent#198.The branch also keeps tagged real CLI E2E tests out of the parallel unit-test suite, matching the documented Vitest contract. Those tests continue to run serially in the dedicated CLI E2E job, avoiding collisions on their shared test port.
This PR remains draft while the refreshed CI run completes. The synchronized vendor is not by itself a claim of complete site parity or publication to Studio trunk.
Contributor Attribution
Aagam Shah (@aagam-shah) authored the transform-URL safety fix and regression in #4784 (
2b9000c9a9687b551fc9dd95fc7caaad72a0bec7) and the comma-safe srcset fix and regression in #4785 (cdd4723ad00ad275d4abc4e9358ac0e7b4763320). Their original commits and Claude co-author trailers are preserved in this branch history. The fixes were also ported into Automattic/data-liberation-agent#170 and Automattic/data-liberation-agent#171. The upstream port descriptions explicitly credit Aagam; the port commits themselves did not preserve his authorship, which was an attribution mistake.Verification
02d8d640for all changed files.!e2efilter: 388 files and 3,572 tests passed.core/html, and zero invalid blocks.buttonin the source versussummaryin core Navigation) at identical geometry.AI Assistance
GPT-5.6 Sol via OpenCode synchronized and verified the vendored package, diagnosed and corrected the CI suite boundary, exercised the packaged import and WordPress editor/runtime workflows, and prepared this description. Earlier work on the branch also used GPT-5.6 Terra and GPT-6 Astra via OpenCode for vendor synchronization, verification, and contributor-attribution review. Aagam Shah authored the two original fixes credited above; the porting and vendoring work does not replace that credit.