- Shorten root README Details row
- Document line-oriented config and call-a-script pattern for multi-line
- Drop non-ASCII (em-dash) from launcher script comments and log line
- Rewrite VERIFY.md: lead with 5-step quick path, add Mermaid diagrams,
  drop TIP terminology, promote compose-mounted config as the recommended
  production path, rewrite source provenance around Sigstore attestation
  (not bit-for-bit reproducibility), and re-anchor the smoke transcript
  on compose-hash <-> sha256(app_compose) binding from a real production
  Phala smoke (CVM twl-cfg-smoke-20260511-180207, deleted after capture).

Drop "reproducibly built" claims outside VERIFY.md. The release workflow
publishes a Sigstore build-provenance attestation that binds the image
digest to a specific GitHub workflow run / repo / ref / SHA; that is a
signed chain of custody, not a guarantee of bit-for-bit reproducibility.

Updated README.md trust-model diagram and verifier list, and the
examples/web-app.conf header.

Make INSTALL_CMD and RUN_CMD optional and add a recommended default mode:
when neither is set the launcher runs 'bash tee-launch.sh' from the
pinned commit (under REPO_SUBDIR if set, else repo root). The script's
bytes are covered by source provenance of COMMIT_SHA, so the trust-
bearing config in default mode collapses to REPO_URL + COMMIT_SHA. The
existing RUN_CMD path is preserved as an advanced mode for repos that
cannot host their own entry script; INSTALL_CMD remains optional and
must accompany RUN_CMD.

Aligned changes:

- bin/trusted-workload-launcher: validate INSTALL_CMD requires RUN_CMD,
  drop "INSTALL_CMD must be set" and "RUN_CMD required" gates, add the
  default-mode branch that requires ./tee-launch.sh in target. No exec
  bit required (we invoke 'bash tee-launch.sh'). Refreshed top comment
  and parse_config comment to reflect the new model.
- tests/run-tests.sh: extended fixture repo with c3 (adds
  sub/tee-launch.sh, intentionally non-executable), added
  default_mode_happy, default_mode_missing_script_fails, and
  install_cmd_without_run_cmd_fails.
- README.md, examples/web-app.conf: lead with default mode; advanced
  mode explicitly scoped to "workload repo cannot host its own entry
  script"; clarified that no executable bit is required.
- VERIFY.md: quick path shortened to 4 steps for default mode, with an
  explicit one-line note that advanced mode adds the command audit;
  step 4 covers tee-launch.sh under source provenance and step 5 shows
  the default-mode log lines. Updated the recommended-path Mermaid
  diagram. Smoke transcript annotated that the prior production run
  used advanced mode because Hello-World ships no tee-launch.sh, and
  that the compose-hash binding it demonstrates is identical.
- Root README: Details-table description compressed to a true one-liner
  ("Run a pinned Git commit in a TEE.").

Three precision fixes to avoid overclaiming the simplification:

- Default mode: trust-bearing config is REPO_URL + COMMIT_SHA and
  REPO_SUBDIR when used (it selects which tee-launch.sh runs). Made
  this explicit in the example README intro, the default-mode section,
  the VERIFY.md quick-path summary and Mermaid diagram, and step 4 of
  the deep-path checklist. Clarified that WORK_DIR is local plumbing
  (not trust-bearing) and that CHILD_ENV_FILE / runtime env can affect
  runtime behavior but not the bytes that run, so it should be audited
  as runtime deployment configuration rather than as source.
- Advanced mode: corrected the framing so RUN_CMD / INSTALL_CMD are
  described as "trust-bearing deployment config" rather than "source
  code at the pinned commit" — they live in the launcher config, not
  in the upstream repo at COMMIT_SHA, and so are not covered by its
  source provenance.
- VERIFY.md log example: reordered to match what the launcher actually
  emits (mode line during the config summary, then checking out, then
  HEAD verified, then exec) and described the lines as ones the output
  should include, not a strict transcript.

reference-value comparison

Aggregator runtime now goes through the dstack SDK for KMS keys and TDX
quotes against /var/run/dstack.sock, so the launcher's docs/examples
need to (a) match the entry-script name workloads adopt and (b) make
the dstack agent socket visible inside the workload container. The
verifier-side review also asked for an explicit reference-values vs
attestation-measurements comparison.

Changes:

- bin/trusted-workload-launcher: rename default entry script to
  entrypoint.sh and accept a new optional ENTRYPOINT_SCRIPT key (relative
  path, validated against absolute paths and '..'). Default mode still
  runs `bash <entry>` with no exec-bit requirement. Updated usage/help
  text, top comments, parse_config comment, and the `mode:` / `entry:`
  log lines.
- tests/run-tests.sh: fixture's c3 now adds sub/entrypoint.sh and a
  sub/alt-entry.sh; added entrypoint_script_override and
  entrypoint_script_escape_rejected; updated default-mode marker
  assertions. 21/21 PASS.
- examples/web-app.conf: now describes entrypoint.sh as the convention
  and documents ENTRYPOINT_SCRIPT as an optional override.
- README.md (example): same convention; intro now lists
  `REPO_SUBDIR` / `ENTRYPOINT_SCRIPT` as the two path-selection trust-
  bearing fields. Added a `Mounting the dstack socket` subsection and
  added `/var/run/dstack.sock:/var/run/dstack.sock` to every compose
  snippet (local dev, production option A, and a note for option B).
  Workload-specific endpoint envs (e.g. DSTACK_LLM_ROUTER_DSTACK_ENDPOINT)
  are explicitly directed to CHILD_ENV_FILE, not to launcher config.
- VERIFY.md: added a `Reference values to compare` block under step 2
  with the concrete extraction shell snippet for `mrtd`, `rtmr0..2`,
  `compose-hash`, `os-image-hash`, `app-id`, and the launcher image
  digest inside the attested compose. Updated the quick-path step 1 to
  state explicitly that this comparison is what makes the attestation
  useful. Mentions of `REPO_SUBDIR` now also list `ENTRYPOINT_SCRIPT`.
- README.md (root): unchanged in this commit (still the one-liner from
  b0478b6).

No Rust-specific logic added to the launcher; it remains a build-system-
agnostic bash launcher. Removed nothing about ALLOW_INSECURE /
DSTACK_LLM_ROUTER_DSTACK_QUOTER_URL because neither was ever referenced
here (confirmed via grep).