ELE PAGES RENDERER

Standalone command line application for Linux, Windows and macOS.
The version printed by --version is the version of the bundled Pages renderer.
No separate installation of Ele, Node.js or Bun is needed.

Extract the ZIP. On Linux and macOS the program is named elepages; on Windows
it is elepages.exe. Place it in a directory on PATH, or use its full path.
If the archive utility drops executable permissions, run chmod +x elepages.

  elepages --version
  elepages build "/absolute/path/site/model.site-model" --output "/path/export"

Windows example:
  elepages.exe build "C:\Sites\Example\model.site-model" --output "C:\Exports\Example"

For existing Ele volume paths, supply each mapping explicitly:
  elepages build "/work/site/model.site-model" --mount "@home=/work" --output "/exports/site"

Run --help for flags. --json writes one JSON result to stdout; progress goes to
stderr. Exit status 0 means success, 1 means failure. The output directory must
be new or empty. --replace can replace a previous CLI output; unrelated files
make it fail. Source files are read-only. A failed render leaves previous output
intact. External dependencies must exist locally; no download or upload is done.

The model file selects the site root, public URL and build settings. Relative
model paths use its directory. Relative content references use the containing
file. The @disk volume is internal; @home and other Ele volumes need --mount.
External assets still obey the Pages model's export.allow / export.deny rules.
Directory symlinks are refused during recursive scanning. Point to individual
files or use a mount. Set model.build to plain or notes for a single export.

The output has the same contents as the Pages export, including manifest,
handoff and report files, plus a CLI marker. A publication step must select the
public files according to the site's existing rules. The program never publishes.

Release builds use the exact extension archive with the same version number.
Embedded Skilt runtime files and compiler version are recorded in release.json.
Linux x64 is tested on the release host. Other downloads are cross-compiled;
they still need native operating-system acceptance tests. macOS and Windows
downloads are currently unsigned, and macOS downloads are not notarized.

Source: Parteroma development/DEU_0.1.3/extensions/local.pages/cli/
Runtime: Bun 1.3.9; its license and third-party notices are in BUN-LICENSE.txt.

BUILD FAILURE VISIBILITY (0.3)

The CLI prints BYGNING MISLYKKEDES and exits 1 on a failed build, including
--quiet --json. It also writes OUTPUT.build-status.json beside the output.
State is running, success or failed, with pid, model, output, version,
startedAt, updatedAt and message. Updates use temporary-file rename.
A SIGKILL or memory-limit termination cannot write failed: a separate monitor
must check the recorded PID and progress timestamp. Never interpret an old
success result file alone as permission to publish a new build.

The personal site's local preview server demonstrates a monitor: it warns
when the recorded process disappears or no progress is seen for 90 seconds.
A stall warning means inspection is needed; it is not proof of process death.
The monitor is operator tooling and is not inserted into the public export.
When an explicit --output is supplied, malformed/missing model errors are also
recorded. Command-line parse errors always go to stderr, but may have no output
path to associate with a preview. Source rendering errors preserve old output.
Promotion uses two directory renames with rollback on caught errors; an OS kill
between these renames may leave the intact old output in .elepages-*-previous
beside the destination. Restore it before continuing if the destination is absent.
