@underpostnet/cyberia 3.3.0 → 3.3.73

package/deploy/lib/host.sh

@@ -0,0 +1,185 @@
+# Host preparation for deploy/<deploy-id>/*.sh. Sourced, never executed directly.
+# Requires lib/github-actions-logging.sh for deploy_step.
+
+# The host configuration store, if this node has one.
+#
+# Every step below drives the CLI through `sudo`, so the store the CLI writes is root's, not the
+# store of whoever sourced this file. Both are looked at, the sourcing account first, so a script
+# run as root and a script run as an operator with sudo read the same node configuration.
+#
+# Usage: host_config_path
+host_config_path() {
+    local root path
+
+    root="$(npm root -g 2>/dev/null)" || root=''
+    path="$root/underpost/.env"
+    if [ -n "$root" ] && [ -f "$path" ]; then
+        printf '%s' "$path"
+        return 0
+    fi
+
+    # Only when the sourcing account has no store of its own: `sudo -n` is non-interactive, so a
+    # host without passwordless sudo declines instead of prompting.
+    root="$(sudo -n -- /bin/bash -lc 'npm root -g' 2>/dev/null)" || root=''
+    path="$root/underpost/.env"
+    [ -n "$root" ] && [ -f "$path" ] && printf '%s' "$path"
+
+    return 0
+}
+
+# One key of this node's resolved host configuration, read straight out of the store the host
+# domain owns (`underpost host get|set`). Pure shell for the same reason `deploy_id_from_repo`
+# is: it resolves the manifest that makes that CLI runnable, so it cannot ask the CLI.
+#
+# Usage: host_config <key>
+host_config() {
+    local key="$1" path value
+
+    path="$(host_config_path)"
+    [ -n "$path" ] || return 0
+
+    value="$(sed -n "s/^[[:space:]]*${key}[[:space:]]*=[[:space:]]*//p" "$path" | tail -n 1)"
+    value="${value%"${value##*[![:space:]]}"}"
+    value="${value%\"}"
+    value="${value#\"}"
+    value="${value%\'}"
+    value="${value#\'}"
+    printf '%s' "$value"
+}
+
+# The repository pair a node prepares itself from: the environment, then the node's own host
+# configuration, where `underpost wireguard --sync` records the pair it moved the node onto.
+# Named nowhere else — left empty, the pull resolves the pairing itself.
+ENGINE_SRC_REPO="${ENGINE_SRC_REPO:-$(host_config ENGINE_SRC_REPO)}"
+ENGINE_SRC_PRIVATE_REPO="${ENGINE_SRC_PRIVATE_REPO:-$(host_config ENGINE_SRC_PRIVATE_REPO)}"
+
+# The deploy id a source repository belongs to: `engine-cyberia` and `engine-test-cyberia` are
+# both `dd-cyberia`. Pure shell on purpose — it resolves the manifest that makes the CLI
+# runnable, so it cannot be resolved by running the CLI. Prints nothing for a repository that
+# names no deploy (the monorepo itself), which callers read as "leave the checkout's own".
+#
+# Usage: deploy_id_from_repo [owner/repo]
+deploy_id_from_repo() {
+    local name="${1:-$ENGINE_SRC_REPO}"
+    name="${name##*/}"
+    name="${name#engine-test-}"
+    name="${name#engine-}"
+    name="${name%-private}"
+
+    [ -n "$name" ] && [ "$name" != "engine" ] && printf 'dd-%s' "$name"
+}
+
+# Installs the node's dependencies from the deploy's own package manifest and links the checkout's
+# CLI globally. Every later bare `underpost` command must execute this checkout, never a package
+# left behind by an older image or host preparation.
+#
+# A deploy id owns its dependency set the same way it owns the rest of its configuration, and
+# `engine-private/conf/<deploy-id>/package.json` is where that set lives. The checkout's own
+# manifest is not it: a product tree declares only what it publishes, so installing against it
+# prunes packages the CLI imports — and the CLI is what pulls and repairs the checkout, so the
+# node loses the ability to fix itself. A deploy with no manifest of its own installs the
+# checkout's, which is the previous behaviour.
+#
+# Usage: install_deploy_dependencies <engine-root> [deploy-id]
+install_deploy_dependencies() {
+    local engine_root="${1:-/home/dd/engine}"
+    local deploy_id="$2"
+    local manifest="engine-private/conf/$deploy_id/package.json"
+
+    if [ -n "$deploy_id" ] && [ -f "$engine_root/$manifest" ]; then
+        deploy_step "Install dependencies ($deploy_id)" \
+        sudo -n -- /bin/bash -lc "cd $engine_root && cp -a ./$manifest ./package.json && npm install"
+    else
+        deploy_step "Install dependencies" \
+        sudo -n -- /bin/bash -lc "cd $engine_root && npm install"
+    fi
+
+    deploy_step "Link underpost CLI" \
+    sudo -n -- /bin/bash -lc \
+    "cd $engine_root && npm link --force && test \"\$(readlink -f \"\$(command -v underpost)\")\" = \"\$(readlink -f ./bin/index.js)\""
+}
+
+# Brings a node to the state every deploy assumes: the engine source at HEAD, its dependencies
+# installed, its CLI globally linked, and the host configuration loaded into the underpost root
+# env store. `host load` is the one entry point for that store — see `underpost host`.
+#
+# Dependencies are installed before the pull, not only after: the pull runs through this
+# checkout's own CLI, so a tree whose node_modules no longer match its manifest cannot repair
+# itself — the entrypoint fails to import long before it can replace the source. They are
+# installed again after it, because the pull resets the checkout to its remote and takes
+# `package.json` with it.
+prepare_host() {
+    local engine_root="${1:-/home/dd/engine}"
+    local src_repo="${2:-$ENGINE_SRC_REPO}"
+    local src_private_repo="${3:-$ENGINE_SRC_PRIVATE_REPO}"
+    local deploy_id="${4:-$(deploy_id_from_repo "$src_repo")}"
+    
+    install_deploy_dependencies "$engine_root" "$deploy_id"
+    
+    deploy_step "Pull repository" \
+    sudo -n -- /bin/bash -lc \
+    "cd $engine_root && node bin run pull $src_repo${src_private_repo:+ --repo-engine-private $src_private_repo}"
+    
+    install_deploy_dependencies "$engine_root" "$deploy_id"
+    
+    deploy_step "Load host config" \
+    sudo -n -- /bin/bash -lc "cd $engine_root && node bin host load"
+}
+
+# Whether a tracked path carries uncommitted changes, as `1` or empty.
+#
+# An asset repository is committed only when it actually changed, so this stays outside
+# `deploy_step`: its stdout is the value the caller branches on, and a step's logging would
+# swallow it. The engine root is a parameter rather than an inherited global so a script that
+# drives more than one checkout cannot read the wrong one.
+#
+# Usage: has_changes <path> [engine-root]
+has_changes() {
+    local path="$1"
+    local engine_root="${2:-${ENGINE_ROOT:-/home/dd/engine}}"
+    
+    sudo -n -- /bin/bash -lc \
+    "cd $engine_root && node bin cmt $path --has-changes" | tr -d '\n'
+}
+
+# The in-pod bootstrap, emitted as a `--cmd` payload (comma-separated: `underpost deploy`
+# splits on commas, one shell command per element).
+#
+# A pod starts from an image whose global `underpost` is only as new as the last image build,
+# and the engine shells out to that bare command on every production path
+# (`options.dev ? 'node bin' : 'underpost'`). Replacing the image's engine with this deploy's
+# own source and repointing the global bin at it is what makes the pod run the CLI that
+# deployed it rather than the one its image was published with.
+#
+# Pair it with `--skip-pull-repo-base` on the `underpost start` that follows: this *is* the pull
+# `start --build` performs, so leaving it on clones and installs the same tree twice.
+#
+# In-pod bootstrap, emitted as a `--cmd` payload (comma-separated). Three stages, in order:
+# the deploy's own source replaces the image's engine and the global bin is repointed at it;
+# that CLI then stamps `container-status`, which is why the stamp cannot come first — an image
+# predating the state domain answers `unknown command 'state'`. The caller appends the start.
+#
+# The global npm prefix is handed to the container user before either npm call: the manifest's
+# `install` hook installs global tooling and `npm link` publishes the CLI there, and both write
+# a tree the image left owned by root.
+#
+# Usage: pod_bootstrap_cmd <deploy-id> [env] [owner/repo]
+pod_bootstrap_cmd() {
+    local deploy_id="$1"
+    local env="${2:-production}"
+    local repo="${3:-underpostnet/engine-test-${deploy_id#dd-}}"
+    local name="${repo##*/}"
+    
+    printf '%s' "cd /home/dd, \
+underpost clone ${repo}, \
+mkdir -p /home/dd/engine, \
+cp -a /home/dd/${name}/. /home/dd/engine/, \
+rm -rf /home/dd/${name}, \
+cd /home/dd/engine, \
+sudo mkdir -p \$(npm prefix -g)/lib/node_modules \$(npm prefix -g)/bin, \
+sudo chown -R \$(id -u):\$(id -g) \$(npm prefix -g)/lib/node_modules \$(npm prefix -g)/bin, \
+npm install, \
+npm link --force, \
+test \"\$(readlink -f \"\$(command -v underpost)\")\" = \"\$(readlink -f ./bin/index.js)\", \
+    underpost state set container-status ${deploy_id}-${env}-build-deployment"
+}

package/deploy/lib/state.sh

@@ -0,0 +1,62 @@
+# Runtime telemetry streaming. Sourced, never executed directly.
+#
+# The one source of streamed state for every context. Nothing here is conditional on GitHub
+# Actions: annotations are just the rendering the state domain picks when it detects a workflow.
+
+STATE_ENV="${STATE_ENV:-production}"
+STATE_NAMESPACE="${STATE_NAMESPACE:-default}"
+STATE_STREAM="${STATE_STREAM:-1}"
+# Seconds between frames. The live table is the default; 0 observes once and exits, which is
+# what a non-interactive caller wants.
+STATE_WATCH="${STATE_WATCH:-2}"
+
+# Streams one observation of a deployment's live execution state, health and metrics.
+#
+# Not wrapped in deploy_step: run_quiet prints only pattern-matched lines and discards its debug
+# log on success, so the payload never reached the terminal. The target defaults to the caller's
+# directory name.
+#
+# Usage: stream_state <engine-root> [deploy-id] [instance-id]
+stream_state() {
+    local engine_root="${1:-/home/dd/engine}"
+    local deploy_id="${2:-$(basename "$(cd "$(dirname "${BASH_SOURCE[1]}")" && pwd)")}"
+    local instance_id="${3:-}"
+    local args="deploy-id=${deploy_id}"
+    local target="$deploy_id"
+
+    [ "$STATE_STREAM" = "0" ] && return 0
+
+    if [ -n "$instance_id" ]; then
+        args="${args},instance-id=${instance_id}"
+        target="${deploy_id}/${instance_id}"
+    fi
+
+    deploy_start "Runtime state ${target}"
+
+    if [ "$STATE_WATCH" != "0" ]; then
+        # In-place redraw, the same shape run_quiet uses for the deploy table: the cursor is
+        # parked above the block and each frame overwrites it. Runs until interrupted.
+        local refresh=0 frame lines=0
+        printf '\033[?25l'
+        trap 'printf "\033[?25h\n"; return 0' INT
+        while true; do
+            refresh=$((refresh + 1))
+            frame=$(sudo -n -- /bin/bash -lc \
+                "cd ${engine_root} && node bin state status \
+                  --env ${STATE_ENV} \
+                  --namespace ${STATE_NAMESPACE} \
+                  --args ${args},refresh=${refresh}" 2>/dev/null)
+            [ "$lines" -gt 0 ] && printf '\033[%dA' "$lines"
+            printf '%s\n' "$frame" | while IFS= read -r line; do printf '%s\033[K\n' "$line"; done
+            lines=$(printf '%s\n' "$frame" | wc -l)
+            sleep "$STATE_WATCH"
+        done
+    fi
+
+    # RUN_QUIET_CI survives the SSH hop; unset in an ordinary shell, where this prints JSON.
+    sudo -n -- /bin/bash -lc \
+        "cd ${engine_root} && RUN_QUIET_CI=${RUN_QUIET_CI:-} node bin state publish \
+          --env ${STATE_ENV} \
+          --namespace ${STATE_NAMESPACE} \
+          --args ${args}"
+}

package/deploy/pwa-microservices-template/deploy.sh

@@ -2,7 +2,7 @@
 set -euo pipefail
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/../lib/logging.sh"
+source "$SCRIPT_DIR/../lib/github-actions-logging.sh"
 
 # Runs in the workflow's rockylinux:9 container against the checked-out
 # workspace instead of over SSH, so the repository root is this script's
@@ -10,62 +10,35 @@ source "$SCRIPT_DIR/../lib/logging.sh"
 REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
 
 main() {
-    echo "Starting github pages deploy"
+    deploy_start "Starting github pages deploy"
 
     cd "$REPO_ROOT"
 
-    run_quiet \
-        "Install required packages" \
-        "Target pod:" \
-        14 \
+    deploy_step "Install required packages" \
         dnf install -y sudo tar gzip bzip2 git
 
-    run_quiet \
-        "Install curl" \
-        "Target pod:" \
-        14 \
+    deploy_step "Install curl" \
         dnf install -y curl --allowerasing
 
-    run_quiet \
-        "Add Node.js repository" \
-        "Target pod:" \
-        14 \
+    deploy_step "Add Node.js repository" \
         bash -c "curl -fsSL https://rpm.nodesource.com/setup_24.x | bash -"
 
-    run_quiet \
-        "Install Node.js" \
-        "Target pod:" \
-        14 \
+    deploy_step "Install Node.js" \
         dnf install nodejs -y
 
-    run_quiet \
-        "Install dependencies" \
-        "Target pod:" \
-        14 \
+    deploy_step "Install dependencies" \
         npm install
 
-    run_quiet \
-        "Build dd-github-pages configuration" \
-        "Target pod:" \
-        14 \
+    deploy_step "Build dd-github-pages configuration" \
         node bin new --default-conf --conf-workflow-id dd-github-pages
 
-    run_quiet \
-        "Create dd-github-pages deployment" \
-        "Target pod:" \
-        14 \
+    deploy_step "Create dd-github-pages deployment" \
         node bin new --deploy-id dd-github-pages
 
-    run_quiet \
-        "Load dd-github-pages production environment" \
-        "Target pod:" \
-        14 \
-        node bin env dd-github-pages production
+    deploy_step "Load dd-github-pages production environment" \
+        node bin app load --env production --args deploy-id=dd-github-pages
 
-    run_quiet \
-        "Build dd-github-pages client" \
-        "Target pod:" \
-        14 \
+    deploy_step "Build dd-github-pages client" \
         env NODE_ENV=production node bin client dd-github-pages '' underpostnet.github.io /pwa-microservices-template-ghpkg
 }
 

package/deploy/release/deploy.sh

@@ -2,59 +2,29 @@
 set -euo pipefail
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/../lib/logging.sh"
+source "$SCRIPT_DIR/../lib/github-actions-logging.sh"
+source "$SCRIPT_DIR/../lib/host.sh"
 
 ENGINE_ROOT=/home/dd/engine
 
 main() {
-    echo "Starting remote release deploy"
+    deploy_start "Starting remote release deploy"
 
-    run_quiet \
-        "Pull repository" \
-        "Target pod:" \
-        14 \
-        sudo -n -- /bin/bash -lc \
-        "cd $ENGINE_ROOT && node bin run pull"
-
-    run_quiet \
-        "Install dependencies" \
-        "Target pod:" \
-        14 \
-        sudo -n -- /bin/bash -lc \
-        "cd $ENGINE_ROOT && npm install"
-
-    run_quiet \
-        "Sync secrets" \
-        "Target pod:" \
-        14 \
-        sudo -n -- /bin/bash -lc \
-        "cd $ENGINE_ROOT && node bin run secret"
+    prepare_host "$ENGINE_ROOT"
 
-    run_quiet \
-        "Install underpost CLI" \
-        "Target pod:" \
-        14 \
+    deploy_step "Install underpost CLI" \
         sudo -n -- /bin/bash -lc \
         "cd $ENGINE_ROOT && npm install -g underpost"
 
-    run_quiet \
-        "Resync secrets" \
-        "Target pod:" \
-        14 \
+    deploy_step "Resync secrets" \
         sudo -n -- /bin/bash -lc \
-        "cd $ENGINE_ROOT && node bin run secret"
+        "cd $ENGINE_ROOT && node bin host load"
 
-    run_quiet \
-        "Configure git" \
-        "Target pod:" \
-        14 \
+    deploy_step "Configure git" \
         sudo -n -- /bin/bash -lc \
         "cd $ENGINE_ROOT && node bin run --dev git-conf"
 
-    run_quiet \
-        "Build and publish docker images" \
-        "Target pod:" \
-        14 \
+    deploy_step "Build and publish docker images" \
         sudo -n -- /bin/bash -lc \
         "cd $ENGINE_ROOT && node bin run docker-image"
 }

package/deployment.yaml

@@ -20,11 +20,17 @@ spec:
     spec:
       containers:
         - name: dd-cyberia-development-blue
-          image: underpost/underpost-engine:v3.3.0
+          image: underpost/underpost-engine:v3.3.73
           imagePullPolicy: IfNotPresent
           envFrom:
             - secretRef:
                 name: underpost-config
+            # The deployment's own environment, with its .env.<env>.oci overlay already
+            # applied by 'app apply'. Optional so a deployment predating that Secret still
+            # starts; the in-pod 'app load' resolves the same overlay as a second path.
+            - secretRef:
+                name: dd-cyberia-development-env
+                optional: true
           env:
             - name: UNDERPOST_INTERNAL_PORT
               value: "4004"
@@ -33,7 +39,6 @@ spec:
             - /bin/sh
             - -c
             - >
-              underpost secret underpost --create-from-env &&
               underpost start --build --run dd-cyberia development
           readinessProbe:
             {

package/docker-compose.yml

@@ -135,7 +135,7 @@ services:
   # server starts but rejects connections until seeded). Serves REST/WS on 4005
   # and the engine gRPC data service on 50051.
   engine-cyberia-runtime:
-    image: ${ENGINE_CYBERIA_IMAGE:-underpost/engine-cyberia-dev}:${ENGINE_CYBERIA_TAG:-v3.3.0}
+    image: ${ENGINE_CYBERIA_IMAGE:-underpost/engine-cyberia-dev}:${ENGINE_CYBERIA_TAG:-v3.3.73}
     container_name: dd-cyberia-engine
     command:
       - /bin/sh
@@ -190,7 +190,7 @@ services:
   # gateway on host port 8081, so one port can route every instance path.
 
   cyberia-server-runtime:
-    image: ${CYBERIA_SERVER_IMAGE:-underpost/cyberia-server-dev}:${CYBERIA_SERVER_TAG:-v3.3.0}
+    image: ${CYBERIA_SERVER_IMAGE:-underpost/cyberia-server-dev}:${CYBERIA_SERVER_TAG:-v3.3.73}
     container_name: dd-cyberia-server
     environment:
       INSTANCE_CODE: amethyst-strata-expansion
@@ -226,7 +226,7 @@ services:
     restart: unless-stopped
 
   cyberia-server-forest:
-    image: ${CYBERIA_SERVER_IMAGE:-underpost/cyberia-server-dev}:${CYBERIA_SERVER_TAG:-v3.3.0}
+    image: ${CYBERIA_SERVER_IMAGE:-underpost/cyberia-server-dev}:${CYBERIA_SERVER_TAG:-v3.3.73}
     container_name: dd-cyberia-server-forest
     environment:
       INSTANCE_CODE: FOREST
@@ -262,7 +262,7 @@ services:
     restart: unless-stopped
 
   cyberia-server-test:
-    image: ${CYBERIA_SERVER_IMAGE:-underpost/cyberia-server-dev}:${CYBERIA_SERVER_TAG:-v3.3.0}
+    image: ${CYBERIA_SERVER_IMAGE:-underpost/cyberia-server-dev}:${CYBERIA_SERVER_TAG:-v3.3.73}
     container_name: dd-cyberia-server-test
     environment:
       INSTANCE_CODE: TEST
@@ -309,7 +309,7 @@ services:
   #   cyberia-server-test   -> cyberia-client-test
 
   cyberia-client-runtime:
-    image: ${CYBERIA_CLIENT_IMAGE:-underpost/cyberia-client-dev}:${CYBERIA_CLIENT_TAG:-v3.3.0}
+    image: ${CYBERIA_CLIENT_IMAGE:-underpost/cyberia-client-dev}:${CYBERIA_CLIENT_TAG:-v3.3.73}
     container_name: dd-cyberia-client
     environment:
       CYBERIA_PORT: '8081'
@@ -334,7 +334,7 @@ services:
     restart: unless-stopped
 
   cyberia-client-forest:
-    image: ${CYBERIA_CLIENT_IMAGE:-underpost/cyberia-client-dev}:${CYBERIA_CLIENT_TAG:-v3.3.0}
+    image: ${CYBERIA_CLIENT_IMAGE:-underpost/cyberia-client-dev}:${CYBERIA_CLIENT_TAG:-v3.3.73}
     container_name: dd-cyberia-client-forest
     environment:
       CYBERIA_PORT: '8081'
@@ -359,7 +359,7 @@ services:
     restart: unless-stopped
 
   cyberia-client-test:
-    image: ${CYBERIA_CLIENT_IMAGE:-underpost/cyberia-client-dev}:${CYBERIA_CLIENT_TAG:-v3.3.0}
+    image: ${CYBERIA_CLIENT_IMAGE:-underpost/cyberia-client-dev}:${CYBERIA_CLIENT_TAG:-v3.3.73}
     container_name: dd-cyberia-client-test
     environment:
       CYBERIA_PORT: '8081'

package/examples/static-page/README.md

@@ -54,23 +54,23 @@ When `--output-path` is provided, the server serves the directory containing the
 
 See [`static-config-example.json`](./static-config-example.json) for a complete working example.
 
-| Field | Type | Description |
-|-------|------|-------------|
-| `page` | `string` | Path to the SSR component to render |
-| `outputPath` | `string` | Output HTML file path |
-| `buildPath` | `string` | Base path for static documents or assets (default: `"/"`) |
-| `env` | `string` | `"production"` or `"development"` |
-| `minify` | `boolean` | Minify HTML output |
-| `lang` | `string` | HTML `lang` attribute |
-| `dir` | `string` | HTML `dir` attribute (`ltr`/`rtl`) |
-| `metadata` | `object` | SEO metadata (title, description, keywords, author, themeColor, canonicalURL, thumbnail, locale, siteName) |
-| `scripts` | `object` | `{ head: [...], body: [...] }` — inline or external scripts |
-| `styles` | `array` | Inline (`content`) or external (`href`) stylesheets |
-| `icons` | `object` | `favicon`, `appleTouchIcon`, `manifest` paths |
-| `headComponents` | `array` | SSR component paths injected into `<head>` |
-| `bodyComponents` | `array` | SSR component paths injected into `<body>` |
-| `microdata` | `array` | JSON-LD structured data objects |
-| `customPayload` | `object` | Arbitrary data injected into the render payload |
+| Field            | Type      | Description                                                                                                |
+| ---------------- | --------- | ---------------------------------------------------------------------------------------------------------- |
+| `page`           | `string`  | Path to the SSR component to render                                                                        |
+| `outputPath`     | `string`  | Output HTML file path                                                                                      |
+| `buildPath`      | `string`  | Base path for static documents or assets (default: `"/"`)                                                  |
+| `env`            | `string`  | `"production"` or `"development"`                                                                          |
+| `minify`         | `boolean` | Minify HTML output                                                                                         |
+| `lang`           | `string`  | HTML `lang` attribute                                                                                      |
+| `dir`            | `string`  | HTML `dir` attribute (`ltr`/`rtl`)                                                                         |
+| `metadata`       | `object`  | SEO metadata (title, description, keywords, author, themeColor, canonicalURL, thumbnail, locale, siteName) |
+| `scripts`        | `object`  | `{ head: [...], body: [...] }` — inline or external scripts                                                |
+| `styles`         | `array`   | Inline (`content`) or external (`href`) stylesheets                                                        |
+| `icons`          | `object`  | `favicon`, `appleTouchIcon`, `manifest` paths                                                              |
+| `headComponents` | `array`   | SSR component paths injected into `<head>`                                                                 |
+| `bodyComponents` | `array`   | SSR component paths injected into `<body>`                                                                 |
+| `microdata`      | `array`   | JSON-LD structured data objects                                                                            |
+| `customPayload`  | `object`  | Arbitrary data injected into the render payload                                                            |
 
 ## CLI Flags
 
@@ -138,10 +138,10 @@ underpost static --page <path>                  # SSR component path
 
 The page content is defined in an SSR component file. See [`ssr-components/CustomPage.js`](./ssr-components/CustomPage.js) for an example.
 
-A component exports an `SrrComponent` function that returns an HTML template literal:
+A component exports an `SSRComponent` function that returns an HTML template literal:
 
 ```js
-SrrComponent = () => html`
+SSRComponent = () => html`
   <div>
     <h1>Hello World</h1>
     <p>Your page content here.</p>

package/examples/static-page/ssr-components/CustomPage.js

@@ -5,10 +5,10 @@
 
 /**
  * SSR Component Example for rendering a custom landing page
- * @function SrrComponent
+ * @function SSRComponent
  * @returns {string} HTML string for the page body
  */
-SrrComponent = () => html`
+SSRComponent = () => html`
   <!-- Main Container -->
   <div class="custom-page">
     <!-- Hero Section -->

package/hardhat/hardhat.config.js

@@ -3,7 +3,7 @@
 // Supports deployment to Hyperledger Besu (IBFT2/QBFT) private networks
 // running on kubeadm-managed Kubernetes clusters (manifests/besu/).
 //
-// Compatible with: Hardhat 3.x + Ethers v6 + hardhat-toolbox-mocha-ethers
+// Compatible with: Hardhat 3.x + viem + hardhat-toolbox-viem
 
 import { defineConfig } from 'hardhat/config';
 import hardhatToolboxViem from '@nomicfoundation/hardhat-toolbox-viem';
@@ -126,11 +126,6 @@ const config = defineConfig({
     outputFile: process.env.GAS_REPORT_FILE || undefined,
     noColors: !!process.env.GAS_REPORT_FILE,
   },
-
-  // ── Mocha (test runner) ─────────────────────────────────────────────────────
-  mocha: {
-    timeout: 60000,
-  },
 });
 
 export default config;