Files
LumaWeb/state/evidence/S00-026-auto-ci-cd-4255c34da227.md
T
wt 2af4f143d8 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
2026-10-15 16:57:59 +07:00

4.8 KiB

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 : 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.