Skip to content

Add a preview of the V4D viewer v0.6.0 at /v4d-next/ - #13

Merged
MehranMarxian merged 1 commit into
mainfrom
chore/v4d-next-preview
Nov 11, 2026
Merged

MehranMarxian merged 1 commit into
mainfrom
chore/v4d-next-preview

Conversation

@MehranMarxian

Copy link
Copy Markdown
Owner

What changed and why

Adds v4d-next/: a build of the V4D viewer v0.6.0 (Atelier) for a smoke check before it replaces the live page. The live /v4d/ is not touched and stays at v0.1.0.

  • v4d-next/ is built from the private V4D repository, branch claude/v060-atelier (MehranMarxian/V4D#7), with its apps/viewer/scripts/publish.mjs (VITE_BASE=/v4d-next/). Not hand-edited.
  • Its index.html carries noindex, and no page links to it.
  • CLAUDE.md, docs/SITE-OVERVIEW.md: one line each for the new folder. CHANGELOG.md: one line.

Once merged, Pages serves it at https://mehran-ahmadi.com/v4d-next/ within a minute or two.

How it was tested

Served this branch locally (python -m http.server 8899) and ran the V4D repository's scripts/check-published.mjs http://localhost:8899/v4d-next/ in headless Chrome on the real GPU (RTX 4070 Ti):

  • the Viewer opens on Echo, on the walker (6,000,000 points);
  • the Atelier opens a look on the demo subject (the dancer, 1,534,898 points, fetched from /v4d-next/demo/);
  • it reports v0.6.0;
  • no errors and nothing missing, except works/works.json, which is absent by design until a work is published.

/v4d/ still answers as before. Not tested: Safari, Firefox, a phone.

Risks and follow-ups

  • Size: 75 MB added to the repository (two WebAssembly files, 27 MB and 13 MB, and the 34 MB demo block). It stays in the history even after the folder is removed.
  • The demo block is a dancer generated with Kling AI 4.0 and lifted by ReLift: not a capture of a real person, and non-commercial (see v4d-next/demo/README.md). It is fetched only when opened in the Studio.
  • The site's checks do not cover this folder (it is not a live page).
  • After the smoke check, a second PR would replace v4d/ with the same build and remove v4d-next/.

Suggestions

  1. After approving the preview, publish v0.6.0 to /v4d/ and remove /v4d-next/ in one PR.
  2. Update the V4D story page (v4d-virtual-fourth-dimension.html) with one or two of the new images, once you have chosen the looks you keep.
  3. Add a rule to site-checks.yml that fails a PR if a file over 50 MB is added, so a build can never exceed GitHub's limits by accident.

A build of the private V4D repository's branch claude/v060-atelier (its apps/viewer/scripts/publish.mjs, VITE_BASE=/v4d-next/). The page carries noindex and nothing links to it. The live /v4d/ is unchanged.
@MehranMarxian
MehranMarxian merged commit e21d294 into main Nov 11, 2026
1 check failed
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.

1 participant