S00-026: Verify pinned Linux runtime and isolated locked dependency access

Changes: Add a bounded reproducible HTTPS/checksum/runtime probe under environment-access, vendor checksums, unchanged parent manifest/lock copies, strict npm settings, result and reproduction notes. Record evidence and QA handoff; submit S00-026 without completing parent tasks.
Validation: Run verify.py twice successfully: vendor Linux archive SHA256 matched, Node 24.21.0/npm 11.19.0 executed, fresh-cache npm ci installed eight integrity-locked packages with scripts disabled, parent bytes stayed unchanged and Stanza import passed. tasks.py validate, git diff --check and scoped file whitespace checks passed. No browser/WSS, detached signature or provenance audit performed.

Task: S00-026
Agent: auto-ci-cd-4255c34da227
Role: ci-cd
Action: claim
Status: review

Task title: Provide approved access to the pinned Linux experiment artifacts

state/commit_messages/auto-ci-cd-4255c34da227.txt

@@ -0,0 +1,4 @@
+Verify pinned Linux runtime and isolated locked dependency access
+
+Changes: Add a bounded reproducible HTTPS/checksum/runtime probe under environment-access, vendor checksums, unchanged parent manifest/lock copies, strict npm settings, result and reproduction notes. Record evidence and QA handoff; submit S00-026 without completing parent tasks.
+Validation: Run verify.py twice successfully: vendor Linux archive SHA256 matched, Node 24.21.0/npm 11.19.0 executed, fresh-cache npm ci installed eight integrity-locked packages with scripts disabled, parent bytes stayed unchanged and Stanza import passed. tasks.py validate, git diff --check and scoped file whitespace checks passed. No browser/WSS, detached signature or provenance audit performed.

state/evidence/S00-026-auto-ci-cd-4255c34da227.md

@@ -0,0 +1,78 @@
+# S00-026 executor evidence
+
+Agent: auto-ci-cd-4255c34da227 (ci-cd), 2026-10-15.
+Outcome: normal configured official HTTPS access works; isolated pinned Linux
+runtime and unchanged parent locked graph verified, awaiting independent QA.
+
+Read master/startup/common/ci-cd, architecture/contracts/profile/workflow/
+automation/Git instructions, assigned resume/show/packet and card; required
+TESTING/protocol/decisions README and blockers S00-020/024/026; previous S00-024
+handoff/evidence, direct dependency executor evidence, accepted scope/stack/
+SASL/parser/SHA512 ADRs. No prior S00-026 handoff existed. Guessed
+0001-web-stack.md was absent (cat exit 1); actual 0001-stack.md was located/read.
+No required artifact is missing. No exact product requirement is assigned here.
+
+Input: parent package.json/package-lock.json, Node 24.21.0/npm 11.19.0 pins,
+existing configured HTTPS path. Output: only environment-access/** with one
+reproducible verification script, copied manifest/lock, strict npm settings,
+vendor checksums, result and README. Workflow metadata is the allowed exception.
+
+## Commands and actual results
+
+- python3 scripts/tasks.py resume --agent auto-ci-cd-4255c34da227: exit 0;
+  assigned S00-026 in_progress; no duplicate claim.
+- python3 scripts/tasks.py show S00-026 and packet S00-026 --agent
+  auto-ci-cd-4255c34da227: exit 0 each; scope/dependencies confirmed.
+- Initial git status --short: exit 0; only coordinator state/tasks.json claim.
+- node --version and npm --version: exit 0 each, v24.1.0 / 11.3.0 (host tools,
+  not used to install dependencies). uname -sm: Linux x86_64.
+- Python existence probe: exit 0; allowed environment-access, parent installed
+  Stanza, and previous macOS runtime path absent.
+- curl --fail --silent --show-error --connect-timeout 10 --max-time 20
+  https://nodejs.org/dist/v24.21.0/SHASUMS256.txt
+  -o /tmp/luma-S00-026-SHASUMS256.txt: exit 0. Previous proxy DNS failure did
+  not reproduce. No proxy/TLS configuration changed or alternate route selected.
+- python3 experiments/0002-xmpp-library/environment-access/verify.py: exit 0
+  initially, then exit 0 again after preserving checksums and adding .npmrc.
+  Both runs downloaded official archive/checksums using curl with HTTPS-only
+  protocol, default certificate verification, bounded timeouts. Both archive
+  SHA256 values match vendor Linux x64 entry:
+  fd8e59d5a511510f6a298afb548f18c7d2b1be404d8b4a27d94fbe49f56cb2d6.
+  Extraction used Python tarfile data safety filter. Exact downloaded tools
+  returned v24.21.0/11.19.0. Python host is 3.14.7.
+- Inside each probe, npm ci --ignore-scripts --no-audit --no-fund
+  --strict-ssl=true --engine-strict=true --registry=https://registry.npmjs.org/
+  --fetch-retries=0 --fetch-timeout=15000 --cache <fresh temporary cache>:
+  exit 0; eight packages installed on both runs. Final run took 908ms.
+  All eight lock entries have HTTPS/SHA512 integrity, installed versions match
+  lock; actual Stanza createClient ESM import passed. Manifest/lock remain byte
+  equal to parent after install. Node/npm notice suggests upgrade; no upgrade run.
+- python3 scripts/tasks.py validate: exit 0; 293 tasks, 22 stages,
+  221 requirements, 211 allocated Web requirements, revision 78.
+- git diff --check and git status --short --untracked-files=all: exit 0 each;
+  no tracked whitespace errors, only scoped seven source/material files and
+  coordinator task state before this evidence. Inline Python checked all seven
+  scoped files including untracked files for final newline/trailing whitespace:
+  exit 0. No app/tooling suite was needed/run for this isolated access outcome.
+
+Final runtime: /tmp/luma-S00-026-gyx_1csp/node-v24.21.0-linux-x64/bin.
+Final cache: /tmp/luma-S00-026-gyx_1csp/npm-cache.
+Parent package SHA256: e0ffb0c94e198e26f8e44e9b22ff4e121760d9f1197ed7bd5a90e1b4bb112766.
+Parent lock SHA256: 9c85ad62721eb2deacb298f29fa2bae211a29c964707d52c2dfbf8614b7dbb05.
+
+## Limits / review input
+
+Access authorization is the assigned probe and enabled session network over the
+existing configured path. No separate environment-owner statement about network
+restoration was supplied; no administrative cause is inferred. Real official
+HTTPS retrieval and fresh-cache locked installation prove present availability.
+Same-origin vendor HTTPS checksums, no detached-signature verification or
+package provenance/advisory clearance. No credentials, real conversations,
+TLS/proxy/engine bypass, dependency additions, lock/stack/spec/shared-contract
+change, system install, browser/WSS/interoperability or readiness claim. No Git
+mutations or other task/agent launch. Temporary runtime/cache can expire.
+
+QA should independently rerun verify.py, compare source parent copies, inspect
+scope/security flags/results and limits. This executor submits S00-026 only;
+S00-020, S00-024 and S00-003 remain unfinished. Coordinator commits transition
+before a fresh reviewer. No done status is set by this executor.

state/handoffs/S00-026.md

@@ -0,0 +1,21 @@
+# S00-026 review handoff
+
+Executor auto-ci-cd-4255c34da227 verified normal configured HTTPS access and
+isolated Linux x64 Node 24.21.0/npm 11.19.0 twice. Official archive checksum
+matched; unchanged copied parent lock installed eight packages with npm ci,
+strict TLS/engines and scripts disabled. Stanza 12.22.1 actual import passed.
+
+QA next: run python3 experiments/0002-xmpp-library/environment-access/verify.py
+from project root on Linux x86_64/Python with tarfile data filter, inspect the
+seven scoped files and state/evidence/S00-026-auto-ci-cd-4255c34da227.md.
+Compare copied manifest/lock to parent; verify fresh official checksum retrieval,
+exact versions, installed graph and no policy bypass. result.json records final
+runtime/cache paths under /tmp/luma-S00-026-gyx_1csp; they may expire, so repeat
+probe for independent evidence. node_modules is isolated and ignored.
+
+No separate owner statement about network restoration was supplied; actual
+approved configured HTTPS path works in this authorized network-enabled session.
+No network/system configuration changed, detached signatures/provenance audit,
+WSS/browser/product readiness verified, or original tasks completed. Separate
+review is required; executor stops on submit. Coordinator alone commits and
+launches the next fresh process.

state/tasks.json

@@ -1,6 +1,6 @@
 {
   "schema_version": 1,
-  "revision": 77,
+  "revision": 79,
   "tasks": {
     "S00-001": {
       "status": "done",
@@ -1365,10 +1365,14 @@
       "handoff": "state/handoffs/S00-025.md"
     },
     "S00-026": {
-      "status": "todo",
-      "owner": null,
+      "status": "review",
+      "owner": "auto-ci-cd-4255c34da227",
       "external_wait": false,
-      "reason": "Approved external artifact preparation completed through configured HTTPS proxy with TLS verification, without changing system tools or project sources. Authentic local supply: /tmp/luma-approved-toolchain/SHASUMS256.txt, node-v24.21.0-linux-x64.tar.xz, npm-11.19.0.tgz; provenance and SHA256/SRI in /tmp/luma-approved-toolchain/verification.json. Exact Node v24.21.0/npm 11.19.0 execute. Unchanged copied parent lock installed with npm ci --ignore-scripts --engine-strict and Stanza 12.22.1, exit 0; /tmp/luma-approved-toolchain/dependency-verification.json and npm-ci.log. Cache /tmp/luma-approved-toolchain/npm-cache permits fresh offline npm ci without proxy access. Fresh executor must independently verify supplied archives/checksums and repeat installation inside its environment-access scope; no task acceptance claimed."
+      "reason": null,
+      "started_at": "2026-10-15T09:54:28+00:00",
+      "updated_at": "2026-10-15T09:57:53+00:00",
+      "evidence": "state/evidence/S00-026-auto-ci-cd-4255c34da227.md",
+      "handoff": "state/handoffs/S00-026.md"
     },
     "S00-027": {
       "status": "todo",
@@ -2341,6 +2345,29 @@
       "task": "S00-028",
       "agent": "coordinator-input-s00-028",
       "reason": "Coordinator supplies the active compatible argv from runner.local.json: codex -c sandbox_workspace_write.network_access=true exec --approve-for-me --ephemeral -. Explicit --sandbox was removed before the S00-024/S00-022/S00-025 fresh agent launches. --approve-for-me retains workspace-write per installed CLI help; no danger-full-access or bypass option. Actual subsequent run state/runs/auto-storage-ae5930b6fbdf/run.json shows the fresh harness executed tools and reached its own escalate, unlike the original immediate CLI exit 2. Installed CLI bounded help check codex exec --approve-for-me --ephemeral --help exited 0. Outbound network config retains existing proxy and TLS, independently probed via codex -c sandbox_mode='\"workspace-write\"' -c sandbox_workspace_write.network_access=true sandbox -- python3 /tmp/luma-probe-registry.py, exit 0; state/runs/coordinator-network/output.log. Fresh S00-028 executor/QA must verify supported argv and filesystem scope; no storage task completion or launcher repair acceptance claimed."
+    },
+    {
+      "revision": 78,
+      "at": "2026-10-15T09:54:28+00:00",
+      "action": "claim",
+      "task": "S00-026",
+      "agent": "auto-ci-cd-4255c34da227",
+      "role": "ci-cd",
+      "from": "todo",
+      "to": "in_progress",
+      "reason": null
+    },
+    {
+      "revision": 79,
+      "at": "2026-10-15T09:57:53+00:00",
+      "action": "submit",
+      "task": "S00-026",
+      "agent": "auto-ci-cd-4255c34da227",
+      "role": null,
+      "from": "in_progress",
+      "to": "review",
+      "reason": null,
+      "evidence": "state/evidence/S00-026-auto-ci-cd-4255c34da227.md"
     }
   ],
   "retired_agents": [