# Ready-to-run builds and complete sources — 2026-10-05

| Application | Ready-to-run archive | Source + assets archive |
| --- | --- | --- |
| 3JHV terrain tint | [Build](3JHV-terrain-tint-ready-to-run-2026-10-05.tar.gz) | [Source](3JHV-terrain-tint-source-2026-10-05.tar.gz) |
| PCTE Three.js editor | [Build](PCTE-threejs-editor-ready-to-run-2026-10-05.tar.gz) | [Source](PCTE-threejs-editor-source-2026-10-05.tar.gz) |
| 3JPCS | [Build](3JPCS-ready-to-run-2026-10-05.tar.gz) | [Source](3JPCS-source-2026-10-05.tar.gz) |

The requested 3HV-texture-tint and PCTE-rewrite/threejs names correspond to the existing workspace folders 3JHV-terrain-tint and PCTE-rewrite/threejs-editor. These packages use those actual applications. Each is an independent build of its current source. Existing source trees and dist directories are unchanged.

The builds are also extracted under ready-to-run/. Enter the desired application folder and run ./launch.sh on Linux/macOS, launch.cmd on Windows, or python3 serve.py. Python 3.8+ and a current desktop browser with WebGL 2 are required. The launcher chooses a free loopback port, opens the browser and prints the URL. Ctrl+C stops it. Node.js, npm and internet access are not required to run these builds.

To unpack a build elsewhere, extract its tar.gz archive; it creates ready-to-run/<application>/. Run the launcher inside that folder. The site's compiled HTML, JavaScript, workers, configuration and assets are in site/. Publish the contents of site/ for static HTTP hosting, including beneath a subdirectory. Direct file:// use is unsupported.

Each build's README.md gives a small manual check and its PROJECT_README.md retains application controls. Bundled input examples are included for 3JHV and 3JPCS. For the pipeline, create/export terrain in PCTE, import the terrain ZIP into 3JPCS, export a viewer bundle, then import that viewer bundle into 3JHV.

Source archives contain all application source, project-local assets, configurations, package lockfiles, documents, tests and existing fixtures. PCTE also contains its frozen Python reference and sibling planning documents. PCTE and 3JHV include shared browser_validation package manifests at their original relative paths. Extract the source archives into one parent directory; enter each application's original directory and run npm ci followed by npm run build. Installation needs registry access or a populated npm cache. See SOURCE_RELEASE.md inside each application for details. Installed dependency folders, Git metadata, old dist directories and temporary artifacts are excluded.

The owner states that assets are CC0 or public domain and authorizes redistribution. Existing asset/provenance notices are retained as supplied, including legacy GPL asset notices. The application code and third-party dependencies keep their existing licences; licence texts and runtime dependency notices travel with each package.

All three production builds passed, including the editors' TypeScript checks. Focused headless Chromium checks used the packaged Python launchers from a different working directory and covered viewer import/palette changes, PCTE view switching/project save, and 3JPCS terrain import/local catalogue/prefab placement/project save. No console errors, failed requests or external runtime requests occurred. VALIDATION.json records the browser, temporary URLs, actions and warnings. No screenshots were captured. Headless SwiftShader does not verify real-GPU appearance, pointer lock or desktop feel. Windows/macOS launcher execution remains unverified.

Every packaged asset was compared byte-for-byte by SHA-256 against its source. All source copies were checked against the current workspace. Every tar.gz was read back to verify exact contents, member paths and executable permissions. Per-file manifests are included inside the archives; RELEASES.json records archive sizes/hashes and SHA256SUMS.txt is ready for sha256sum -c SHA256SUMS.txt.