release: land release/phase1 → main (phase 1 integration, before or with lens#36)

.github/workflows/candidate.yml

@@ -15,6 +15,9 @@ on:
       cut:
         default: false
         type: boolean
+      override:
+        default: ''
+        type: string
 
 permissions:
   contents: read
@@ -43,18 +46,31 @@ jobs:
           GH_TOKEN: ${{ github.token }}
           COMPONENT: ${{ inputs.component }}
           CANDIDATE: ${{ inputs.candidate }}
+          OVERRIDE: ${{ inputs.override }}
+          CUT: ${{ inputs.cut }}
         run: |
           let name = if ($env.CANDIDATE | is-empty) { $"candidate-(date now | format date '%Y%m%d').1" } else { $env.CANDIDATE }
-          python3 release/train.py snapshot --manager . --component $env.COMPONENT --candidate $name --output snapshot
+          let extra = ($env.OVERRIDE | split row -r '\s+' | where {|x| $x != ''} | each {|x| ['--override' $x]} | flatten)
+          let extra = if $env.CUT == 'true' { $extra | append '--cut' } else { $extra }
+          python3 release/train.py snapshot --manager . --component $env.COMPONENT --candidate $name --output snapshot ...$extra
           if $env.LAST_EXIT_CODE != 0 { error make {msg: "source snapshot failed"} }
+          # The Linux executables are built on glibc 2.35 (Ubuntu 22.04) because the genesis
+          # host cyberproxy is Ubuntu 22.04; the gate linux-glibc-floor checks it on the ELF.
+          # macos-14 retires 2026-11-02 (actions/runner-images#13518); its brownout cancelled
+          # rehearsal 41315563611's aarch64-apple-darwin leg, so that leg runs on macos-15.
+          # the stack leg and cyb's android leg run on the build service (build-a on Akash, servers/build-a in apparatus):
+          # warm sccache, warm cargo registry, 16 cores; neither ships a linux-gnu executable, so the glibc floor below
+          # does not bind them. the x86_64 product leg stays on ubuntu-22.04: its executable must link against
+          # glibc 2.35 (linux-glibc-floor), and build-a is Debian 13 (glibc 2.41). arm64 and macOS stay GitHub-hosted.
+          let build = [self-hosted linux x64 build]
           let rows = [
-            {runner: ubuntu-24.04, target: stack}
-            {runner: ubuntu-24.04, target: x86_64-unknown-linux-gnu}
-            {runner: ubuntu-24.04-arm, target: aarch64-unknown-linux-gnu}
-            {runner: macos-14, target: aarch64-apple-darwin}
+            {runner: $build, target: stack, os: linux}
+            {runner: ubuntu-22.04, target: x86_64-unknown-linux-gnu}
+            {runner: ubuntu-22.04-arm, target: aarch64-unknown-linux-gnu}
+            {runner: macos-15, target: aarch64-apple-darwin}
             {runner: macos-15-intel, target: x86_64-apple-darwin}
           ]
-          let rows = if $env.COMPONENT == cyb { $rows | append {runner: ubuntu-24.04, target: aarch64-linux-android} } else { $rows }
+          let rows = if $env.COMPONENT == cyb { $rows | append {runner: $build, target: aarch64-linux-android, os: linux} } else { $rows }
           $"candidate=($name)\n" | save --append $env.GITHUB_OUTPUT
           $"matrix=({include: $rows} | to json --raw)\n" | save --append $env.GITHUB_OUTPUT
       - uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a
@@ -69,7 +85,11 @@ jobs:
       fail-fast: false
       matrix: ${{ fromJSON(needs.snapshot.outputs.matrix) }}
     runs-on: ${{ matrix.runner }}
-    timeout-minutes: 90
+    # The stack leg runs every stack gate serially: rehearsal 40437685274 measured
+    # 4752.7 s over 19 gates plus ~650 s sources/setup, and was cancelled at 90 min
+    # inside simulation-gate (gate timeout 3600 s). 210 min covers that worst case
+    # (~155 min) with headroom, under GitHub's 360-min hosted limit; platform legs keep 90.
+    timeout-minutes: ${{ matrix.target == 'stack' && 210 || 90 }}
     defaults:
       run:
         shell: nu {0}
@@ -79,6 +99,18 @@ jobs:
           repository: cyberia-to/soft3
           ref: ${{ inputs.manager_ref }}
           persist-credentials: false
+      # The hosted toolcache has no Python build for the self-hosted Debian
+      # build-service runner, so setup-python fails there (G18, run
+      # 41344227676 job 124960560558). Those legs use the host python3.
+      - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5.6.0
+        if: ${{ !contains(matrix.runner, 'build') }}
+        with:
+          python-version: '3.12'
+      - name: Host Python (build service)
+        if: ${{ contains(matrix.runner, 'build') }}
+        shell: bash
+        run: |
+          python3 -c 'import sys; print(sys.version); sys.exit(0 if sys.version_info >= (3, 12) else "python3 >= 3.12 required on the build service, found " + sys.version)'
       - uses: hustcer/setup-nu@9215c80adb545a85c419d5085b76eb6d082f49e7
         with:
           version: '0.112.2'
@@ -92,7 +124,7 @@ jobs:
           if $env.LAST_EXIT_CODE != 0 { error make {msg: "Rust installation failed"} }
           rustup default 1.95.0
       - name: Desktop Linux libraries
-        if: inputs.component == 'cyb' && startsWith(matrix.runner, 'ubuntu') && matrix.target != 'stack'
+        if: inputs.component == 'cyb' && (matrix.os == 'linux' || startsWith(matrix.runner, 'ubuntu')) && matrix.target != 'stack'
         run: |
           sudo apt-get update
           if $env.LAST_EXIT_CODE != 0 { error make {msg: "apt update failed"} }
@@ -107,7 +139,8 @@ jobs:
         env:
           TARGET: ${{ matrix.target }}
           RUSTUP_TOOLCHAIN: '1.95.0'
-          CARGO_BUILD_JOBS: '2'
+          # four cores on GitHub-hosted runners, sixteen on the build service shared by up to six runners
+          CARGO_BUILD_JOBS: ${{ contains(matrix.runner, 'build') && '6' || '2' }}
           PYTHONUNBUFFERED: '1'
         run: |
           let args = if $env.TARGET == stack { [--stack] } else { [] }

.github/workflows/notify-simulation.yml

@@ -1,7 +1,13 @@
 # Every soft3 merge runs the chain simulator's gate suite against the merged
 # revision (cyberia-to/simulation .github/workflows/gate.yml listens for
-# `soft3-merged`). gh only; the simulation also runs every six hours, so a
-# missed dispatch is caught there.
+# `soft3-merged`). The kernel the simulator exercises is cybernode's since
+# 2026-10-27 (proposals/cybernode.md); the simulator still reaches it through
+# the soft3 facade crate (simulation/chain/Cargo.toml depends on soft3), so a
+# soft3 merge is still the event that can change what it builds. When the
+# simulator depends on cybernode directly, this dispatch moves to the
+# cybernode repository (`cybernode-merged`) and this workflow goes.
+# gh only; the simulation also runs every six hours, so a missed dispatch is
+# caught there.
 name: Notify simulation
 
 on:

.github/workflows/release-engine.yml

@@ -1,10 +1,8 @@
 name: Release engine
 on:
   pull_request:
-    paths: ['release/**', '.github/workflows/candidate.yml', '.github/workflows/release-*.yml']
   push:
     branches: [main]
-    paths: ['release/**', '.github/workflows/candidate.yml', '.github/workflows/release-*.yml']
 permissions:
   contents: read
 jobs:
@@ -15,3 +13,29 @@ jobs:
         with:
           persist-credentials: false
       - run: python3 -m unittest discover -s release -p 'test_*.py' -v
+  # proposals/cybernode.md C3 (2026-10-27): the node left soft3 for cyberia-to/cybernode; moved means
+  # moved. A returning path is a regression (AGENTS.md), and rung 7 is cybernode on every surface.
+  # Every pull request, not only release/** changes: the paths this job guards are the whole tree.
+  moved-stays-moved:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1
+        with:
+          persist-credentials: false
+      - name: moved
+        run: |
+          status=0
+          for path in crate/src/chain crate/src/genesis crate/src/node deploy/chain; do
+            if [ -e "$path" ]; then
+              echo "::error::$path is back in soft3; it lives in cybernode (proposals/cybernode.md section 3.4)"
+              status=1
+            fi
+          done
+          exit $status
+      - name: stale
+        run: |
+          if git grep -n -i "rung 7 soft3\|rung 7 \`soft3\`\|seventh rung is soft3" -- ':!audit' ':!proposals/cybernode.md' ':!release/director/plan.md' ':!.github/workflows/release-engine.yml'; then
+            echo "::error::rung 7 is cybernode; the lines above still say soft3"
+            exit 1
+          fi
+          echo "no stale rung-7 line"

.github/workflows/release-train.yml

@@ -1,7 +1,7 @@
 name: Release train
 on:
-  schedule:
-    - cron: '0 12 * * 5'
+  schedule:            # daily at 12:00 UTC (the owner, 2026-10-24); was fridays
+    - cron: '0 12 * * *'
   workflow_dispatch:
     inputs:
       candidate:
@@ -12,6 +12,10 @@ on:
         description: 'Create a draft candidate after recording all gates'
         default: true
         type: boolean
+      override:
+        description: 'Rehearsal only (cut=false): space-separated <sibling>=<ref>, ref = branch, pull/N/head or commit'
+        default: ''
+        type: string
 permissions:
   contents: write
 concurrency:
@@ -25,3 +29,4 @@ jobs:
       manager_ref: ${{ github.sha }}
       candidate: ${{ inputs.candidate || '' }}
       cut: ${{ github.event_name == 'schedule' || inputs.cut == true }}
+      override: ${{ inputs.override || '' }}

AGENTS.md

@@ -20,6 +20,7 @@ navigation linked to this foundation when changing architecture.
 |-----|------|--------|
 | `js/` | JavaScript/TypeScript SDK (Bostrom chain, CosmJS-based) | active |
 | `schema/` | canonical wire format definitions | draft |
+| `crate/` | the `soft3` crate: the stack facade over `cybernode` (rung 7, github.com/cyberia-to/cybernode) | active |
 | `cli/` | `soft3` command-line tool (Rust) | scaffold |
 | `mcp/` | MCP server for AI assistant access | scaffold |
 | `py/` | Python SDK | scaffold |
@@ -28,7 +29,7 @@ navigation linked to this foundation when changing architecture.
 
 soft3 SDK depends on: hemera (particle), bbg (state + proofs), lens (verification), cybergraph (signal submission), radio (transport)
 
-do NOT implement stack logic here. call into the stack repos via FFI, WASM, or RPC. the SDK is an adapter, not a reimplementation.
+do NOT implement stack logic here. call into the stack repos via FFI, WASM, or RPC. the SDK is an adapter, not a reimplementation. the node — chain kernel, genesis, node, wallet, network, its specs and deploy units — is `cybernode` since 2026-10-27 (proposals/cybernode.md); a `crate/src/chain` reappearing here is a regression.
 
 ## do not touch zones
 
@@ -52,6 +53,7 @@ tracked paths must be valid on NTFS. never use `<>:"/\|?*`, trailing `.` or spac
 | `lens` | polynomial commitment backends |
 | `radio` | P2P transport |
 | `foculus` | consensus |
+| `cybernode` | the node (rung 7): chain kernel, genesis, wallet, network; the facade's path dependency `../../cybernode/rs` |
 
 ## current blockers (do not implement past these)
 
@@ -72,6 +74,7 @@ Before changing the engine, run:
 Candidate gates are `origin-checkouts`, `phase1-pins`, `release-notes-source`, `package-resolution`,
 `source-inputs-unchanged`, `stack-*`, `conformance-snapshot`, `stack-chain-genesis`,
 `simulation-gate` (the chain simulator's gate suite, cyberia-to/simulation), `soft3-tests`,
-`soft3-release`, and `node-status`. Products add `soft3-dependency` and their
+`soft3-release` (the facade crate), `cybernode-tests`, `cybernode-release` (the node, built from
+the `cybernode` sibling), `stack-pussy-identity`, `node-status` and `linux-glibc-floor`. Products add `soft3-dependency` and their
 application gates. Missing implementations and failed gates remain red evidence.
-Owner-only promotion, tags and bump merges follow `~/cyber/AGENTS.md`.
+Owner-only promotion, tags and bump merges follow `~/cyber/AGENTS.md`. the `node-status` gate boots the cybernode binary that `cybernode-release` builds; `cybernode` is a sibling in `release/phase1.toml`.

README.md

@@ -41,14 +41,15 @@ candidates with source inventories, platform binaries and gate receipts.
 ## install
 
 ```bash
-cargo install soft3          # stack CLI + real node
+cargo install --git https://github.com/cyberia-to/cybernode cybernode   # the node (rung 7); the crates.io name is not published yet
+cargo install soft3          # the stack facade; forwards the node verbs for one release
 cargo install true-cyber     # product face (binary: cyber)
 ```
 
 ## run a node
 
 ```bash
-soft3 node --home ~/.spacepussy-test --bind 127.0.0.1:7780 --moniker dev-1
+cybernode node --home ~/.spacepussy-test --bind 127.0.0.1:7780 --moniker dev-1
 ```
 
 engine: **cybergraph + bbg**. not a status stub.
@@ -59,14 +60,14 @@ curl -sS -X POST http://127.0.0.1:7780/v1/link \
   -H 'content-type: application/json' \
   -d '{"neuron":"01","from":"0a","to":"0b","amount":1}'
 
-soft3 sync                   # public edge on cybernode
+cybernode sync               # public edge on cybernode.ai
 cyber sync                   # same via true-cyber
 ```
 
 public chaosnet: `https://cyb.ai/spacepussy-test` (cyberproxy).
 
 launch manual: [[soft3/docs/launch|launch spacepussy-test]].
 
-cosmos **space-pussy** / **bostrom** on cybernode are bootloader chains — different substrate. see [[bootloader]].
+cosmos **space-pussy** / **bostrom** run on the apparatus hosts (the cybernode.ai instance) as bootloader chains — different substrate. see [[bootloader]].
 
 [[cyber]] · [[cyb]] · [[soft3/status]] · [[install]] · [[soft3/docs/launch|launch]]