S00-003: Record blocked task and remediation handoff

Changes: Preserve incomplete work and blocker metadata for S00-003. This checkpoint does not mark implementation accepted.
Validation: Session ended with status blocked.
Blocker: S00-003 cannot reproduce accepted Node 24.21.0/npm 11.19.0 or install locked Stanza: host tools are 24.1.0/11.3.0, parent node_modules is absent, and normal official HTTPS retrieval fails with unresolved configured proxy.

Task: S00-003
Agent: auto-protocol-59f4d359b339
Role: protocol
Action: claim
Status: blocked

Task title: Проверить XMPP WSS/auth библиотеку

state/evidence/S00-003-auto-protocol-59f4d359b339.md

@@ -0,0 +1,40 @@
+# S00-003 environment blocker evidence
+
+Agent: auto-protocol-59f4d359b339 (protocol), 2026-10-15.
+Input: assigned S00-003, startup/workflow/role documents, required TESTING and
+ADR registry, task card/context, previous handoff, accepted scope/stack/SASL/
+parser/SHA512 ADRs and direct dependency evidence/reviews. Exact ACC-004,
+NET-003 and NET-004 read from specs/tz_clear.md. Dependency suites were not rerun.
+Output remains one library-selection/WSS/auth/parser/extensions spike. Acceptance
+requires an actual test WSS handshake and no fabricated channel binding.
+
+## Actual commands/results
+
+- python3 scripts/tasks.py resume --agent auto-protocol-59f4d359b339: exit 0;
+  S00-003 assigned in_progress. No repeat claim.
+- python3 scripts/tasks.py show S00-003: exit 0; scope/dependencies confirmed.
+- node --version: exit 0, v24.1.0.
+- npm --version: exit 0, 11.3.0.
+- command -v chromium chromium-browser google-chrome firefox openssl:
+  found /usr/bin/chromium, /usr/bin/firefox, /usr/bin/openssl. Browser presence
+  is not a successful execution or handshake.
+- ls experiments/0002-xmpp-library/node_modules/stanza: exit 2, path absent.
+  (Combined diagnostic shell ended 0 because the subsequent issue-template
+  read succeeded; this ls failure is not reported as passed.)
+- curl --fail --silent --show-error --connect-timeout 10 --max-time 20
+  https://nodejs.org/dist/v24.21.0/SHASUMS256.txt
+  -o /tmp/luma-S00-003-SHASUMS256.txt: exit 5,
+  `curl: (5) Could not resolve proxy: proxy.micran.ru`.
+- git status --short: exit 0; only coordinator state/tasks.json claim initially.
+
+Accepted ADR 0001 and parent manifest/lock require Node 24.21.0/npm 11.19.0.
+The prior evidence used a macOS ARM64 runtime under /private/tmp; this Linux
+session has different tools and no installed parent Stanza. Normal configured
+HTTPS runtime retrieval fails before reaching the vendor. No network bypass,
+TLS/engine override, alternate versions or source workaround attempted.
+
+No source changes, npm install, build, test suite, browser execution, WSS
+handshake, extension roundtrip, library selection or make check was performed.
+No success or product readiness claimed. Existing accepted remediations remain
+unchanged. One external environment remediation is requested; reporter stops
+immediately after escalate and cannot implement it or continue another task.