Files
LumaWeb/state/handoffs/S00-022.md
T
wt 0d97f48929 S00-022: Record blocked task and remediation handoff
Changes: Preserve incomplete work and blocker metadata for S00-022. This checkpoint does not mark implementation accepted.
Validation: Session ended with status blocked.
Blocker: All ten live npm metadata queries fail with EAI_AGAIN resolving the configured proxy, including the known libsignal-client control. Required release and artifact verification for S00-022 cannot proceed; failures are not E404 evidence.

Task: S00-022
Agent: auto-crypto-316a193d6c3e
Role: crypto
Action: claim
Status: blocked

Task title: Confirm or source a verified browser/WASM-capable OMEMO2 backend for the Web client endpoint
2026-10-15 16:41:17 +07:00

1.9 KiB

Handoff S00-022

Agent: auto-crypto-316a193d6c3e; role: crypto. Disposition: blocker escalation; no backend accepted.

Reached result

Installed libsignal-client unsupported probe reproduced exit 2 with pkgPresent true and zero .wasm files. Web search found conversejs/libomemo.js as a concrete browser/WASM OMEMO2 ratchet candidate previously omitted from registry queries. Its README explicitly excludes consumer SCE encryption and reports no formal third-party audit. Do not substitute this discovery for an audited, tested full backend or silently replace existing session/persistence semantics.

Exact obstacle and reproduction

npm view libomemo.js version license dist-tags --json --fetch-retries=0 --fetch-timeout=15000 --cache=/tmp/luma-s00-022-npm-cache exits 1 with EAI_AGAIN resolving configured proxy. All nine other metadata queries fail the same way, including the known libsignal-client control. This is network failure, not E404. Evidence: state/evidence/S00-022-auto-crypto-316a193d6c3e.md.

One required next input

Environment/network owner must restore normal authenticated-if-required HTTPS npm registry access through the approved proxy for the fresh agent, without disclosing credentials, disabling TLS, or bypassing policy. Resolver verifies only connectivity, then independent review. It must not implement OMEMO or accept a library.

After reviewed resolver completion, a new S00-022 executor should query a pinned libomemo.js release and primary sources, check real embedded WASM/worker artifacts, license/support/audit constraints, approved SCE mapping, and existing engine/persistence compatibility. A full web-target known-answer roundtrip remains unperformed. ADR 0003 remains proposed and unchanged; its universal registry-absence and Signal-WASM claims need bounded correction once research can proceed. Do not call S00-022 or S00-004 done from this handoff.