S00-024: Verify restored pinned Linux XMPP environment access

Changes: Add the S00-024 continuation checkpoint, refresh verified runtime/cache paths, and replace the blocked handoff with QA and S00-020 restart instructions.
Validation: Existing verify.py passed official HTTPS/checksum retrieval, Node 24.21.0/npm 11.19.0, fresh-cache locked npm ci and Stanza import. Independent archive/input/version/config assertions, tasks.py validate and diff/scope/whitespace checks passed. Browser/WSS and product readiness remain unverified.

Task: S00-024
Agent: auto-ci-cd-49907d48a6d1
Role: ci-cd
Action: claim
Status: review

Task title: Устранить прерывание: Restore access to the pinned Linux XMPP experiment toolchain

state/evidence/S00-024-auto-ci-cd-49907d48a6d1.md

@@ -0,0 +1,71 @@
+# S00-024 executor evidence
+
+Agent: auto-ci-cd-49907d48a6d1 (ci-cd), 2026-10-15.
+Result: interrupted environment restoration verified ready for independent QA.
+
+Input: master/AGENTS/README/common/ci-cd and required architecture/profile/
+contracts/workflow/automation/Git/TESTING/protocol/decisions README; assigned
+resume/show/card/packet, previous handoff, blockers S00-020/024; direct dependency
+executor evidence and accepted scope/stack/SASL/parser/SHA512 ADRs; S00-026
+executor and independent QA evidence/handoff; existing environment-access source.
+No exact product requirement is assigned to this remediation. No required input
+is missing. Initial git status showed only coordinator state/tasks.json claim.
+
+One output: current reproducible environment-access checkpoint and precise
+handoff, using the existing reviewed S00-026 implementation. Source diff only
+adds a continuation section to scoped README and refreshes result.json runtime/
+cache paths; no repair to probe code or partial source was needed. Prior handoff
+is superseded by the successful fresh run. No parent source/lock, accepted stack,
+shared interface, specs, network/system configuration or dependency changed.
+
+## Actual commands / results
+
+- python3 scripts/tasks.py resume --agent auto-ci-cd-49907d48a6d1: exit 0,
+  assigned S00-024 in_progress, no repeat claim.
+- python3 scripts/tasks.py show S00-024 and packet S00-024 --agent
+  auto-ci-cd-49907d48a6d1: exit 0 each; scope and done prerequisites confirmed.
+- python3 experiments/0002-xmpp-library/environment-access/verify.py: exit 0.
+  Fresh official HTTPS SHASUMS256.txt and Linux x64 archive retrieval succeeded;
+  previous proxy DNS error did not reproduce through the configured route.
+  Archive SHA256 matched vendor fd8e59d5a511510f6a298afb548f18c7d2b1be404d8b4a27d94fbe49f56cb2d6
+  before tarfile data-filter extraction. Executing tools returned Node v24.21.0
+  and npm 11.19.0. Fresh-cache npm ci installed eight packages in 1s using
+  --ignore-scripts --strict-ssl=true --engine-strict=true, HTTPS registry,
+  no audit/fund, bounded timeout and no retries. Lock integrity retained.
+  Actual Stanza createClient ESM import passed.
+- Inline independent Python assertions: exit 0. Rehashed downloaded archive,
+  compared persisted/fresh vendor checksum bytes, copied/parent manifest and
+  lock bytes/hashes, all eight installed versions versus HTTPS/SHA512 lock
+  entries and actual Stanza 12.22.1. Pinned npm config get strict-ssl,
+  engine-strict and ignore-scripts each returned true; inherited
+  NODE_TLS_REJECT_UNAUTHORIZED is not 0.
+- python3 scripts/tasks.py validate: exit 0; 293 tasks, 22 stages,
+  221 requirements, 211 allocated Web requirements, revision 81.
+- git diff --check, git diff --stat, git status --short --untracked-files=all:
+  exit 0 each; only two scoped files and workflow metadata changed.
+  Final newline/trailing whitespace and all changed-path scope assertions:
+  exit 0 (including this evidence and commit message).
+
+Runtime: /tmp/luma-S00-026-ywchja86/node-v24.21.0-linux-x64/bin.
+Cache: /tmp/luma-S00-026-ywchja86/npm-cache.
+Parent manifest SHA256: e0ffb0c94e198e26f8e44e9b22ff4e121760d9f1197ed7bd5a90e1b4bb112766.
+Parent lock SHA256: 9c85ad62721eb2deacb298f29fa2bae211a29c964707d52c2dfbf8614b7dbb05.
+
+## Acceptance / limitations
+
+The interruption has a preserved, runnable, reviewed prerequisite implementation
+and a fresh successful verification. S00-026 QA documents coordinator-approved
+configured HTTPS access. This executor did not bypass network/TLS/engine policy,
+select an alternate route, alter host tools, add secrets/real conversations or
+run Git mutations/other tasks/agents. Existing host tools are not used for npm ci.
+No product build, browser/WSS/client-server interoperability, detached signature,
+package provenance/advisory or release readiness check was run or claimed.
+Same-origin vendor HTTPS checksum is the bounded authenticity evidence.
+No tooling suite was needed for the unchanged probe implementation; validate and
+focused actual environment checks cover this card. Temporary paths can expire.
+
+QA must independently rerun the documented probe and inspect input hashes,
+checksum, strict settings and scoped diff. Approval only accepts S00-024 and
+allows a fresh S00-020 executor to continue through coordinator workflow;
+S00-020/S00-003 acceptance is not supplied here. Executor submits and exits;
+coordinator commits before the next fresh process.