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: Stanza 12.22.1 browser HMAC sha-512 fails RFC 4231 Test Case 1: wrong 64-byte block selection. SCRAM-SHA-512 derives that hyphenated algorithm; private algorithm mutation/vendor patches are unsupported. Parent cannot attest browser strongest-mechanism compatibility from Node-only success.

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

Task title: Проверить XMPP WSS/auth библиотеку
This commit is contained in:
wt committed 2026-10-15 02:38:42 +07:00
1 parent 74e1fd87d9
commit e69372c6db
13 files changed
+339 -27

No files matched your search

+26 -8
View File
@@ -1,14 +1,32 @@
# S00-003 blocked handoff
Executor: auto-protocol-902594b44429, protocol, 2026-10-15.
Original outcome remains library selection with WSS/auth/parser/extension spike.
Executor: auto-protocol-dcdf92cd067e, protocol, 2026-10-15.
Outcome remains library selection with WSS/auth/parser/extension spike.
Prior S00-017 SASL validation remediation is independently accepted. Read its ADR/plugin/44-test evidence; this session did not rerun those tests or change that experiment. Stanza is still an unselected candidate and the parent exploratory manifest/lock remain incomplete.
Accepted prerequisites: S00-001 scope, S00-002 stack, S00-017 fail-closed SASL
and S00-018 bounded parser ingress. Their ADRs/evidence were read; their suites
were not rerun or changed. Parent Stanza candidate remains unselected, parent
exploratory manifest/lock incomplete, selection ADR absent.
New bounded probe: experiments/0002-xmpp-library/parser-probe/reproduce.mjs. With the accepted Node 24.21.0 runtime, its actual parser/Client registry accepts a 1 MiB body and 256 nested children and retains/reassembles unfinished XML across 18 writes into a 64 KiB body without error. StreamParserOptions exposes no resource-limit configuration. The shipped WebSocket transport forwards successive messages to that persistent parser without enforcing standalone XML or limits. Evidence and exact command: state/evidence/S00-003-auto-protocol-902594b44429.md. This is a local diagnostic, not WSS/server/browser execution or an exhaustion benchmark.
Blocker newly reproduced in pinned Stanza 12.22.1 browser crypto:
createHmac('sha-512', RFC 4231 section 4.2 key/data) returns a different digest
than the fixed primary-spec vector and Node native crypto. sha512 alias and
sha-256/sha-1 controls match. Browser Hmac tests only alg === 'sha512' for its
128-byte block size, while SCRAM-SHA-512 derives 'sha-512'; that SCRAM field
is private in declarations. Direct browser module execution in Node is a
backend diagnostic, not actual browser/WSS execution. Exact reproduction and
digests: state/evidence/S00-003-auto-protocol-dcdf92cd067e.md.
Blocker: cannot attest the required bounded parser ingress using the candidate's stock input path. Needs one separately reviewed experiment enforcing finite input resource limits and complete standalone text XML per WebSocket message, using vetted parsing and a supported integration path. Do not patch ignored vendor source or rely on post-import events after allocations. Keep policy local to the experiment; no shared contract/product-limit decision is authorized here.
Source edits stopped; none were made. Do not patch ignored vendor code/private
fields, implement primitives, change wire name, claim successful SHA-512 from
Node-only crypto or silently downgrade to avoid the defect. One fresh crypto
resolver must produce an isolated browser-compatible SCRAM-SHA-512 integration
using vetted existing crypto and supported public mechanism extension APIs,
with known vectors, full proof/server-final and negative tests. Independent
security review must accept that outcome before coordinator resumes original.
Source edits stopped after diagnosis. No selection ADR, actual WSS handshake, browser build/runtime, complete mechanism policy, module extension roundtrip or independent interoperability is completed. No make check/clean install claimed for this run; source/accepted dependencies/specs were not altered beyond the bounded probe.
Next input: fresh resolver agent performs only the issue's parser ingress experiment and independent reviewer validates it. Only after reviewed done and coordinator commit may a new original executor resume remaining S00-003 acceptance. Current reporter must exit after escalation, cannot implement resolver, unblock, claim again or launch another agent.
No WSS handshake, browser build/runtime, complete mechanism policy, extension
roundtrip, selection or independent interoperability has been completed in this
session. No clean install/make check claimed. No shared/spec/accepted dependency
changes. Reporter exits immediately after escalate and cannot implement resolver,
unblock/reclaim or launch another process.