wt/LumaWeb
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

S00-022: Record blocked task and remediation handoff

Browse Source 
Changes: Preserve incomplete work and blocker metadata for S00-022. This checkpoint does not mark implementation accepted.
Validation: Session ended with status blocked.
Blocker: Pinned libomemo.js@3.0.0 supplies real embedded WASM but is a different unaudited ratchet and excludes consumer SCE; no approved decision reconciles it with S00-022 retained audited engine/persistence requirement.

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

Task title: Confirm or source a verified browser/WASM-capable OMEMO2 backend for the Web client endpoint
This commit is contained in:
wt committed 2026-10-15 17:17:19 +07:00
1 parent 8bfaa06e64
commit 28320ff35a
14 files changed
+386 -31
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

state/handoffs/S00-022.md
+21 -12
View File
@@ -1,17 +1,26 @@
# Handoff S00-022
Agent: auto-crypto-316a193d6c3e; role: crypto. Disposition: blocker escalation; no backend accepted.
Agent: auto-crypto-bcd7f2a71667; role: crypto. Disposition: blocker; no backend accepted.
## Reached result
Registry connectivity works. Pinned libomemo.js@3.0.0 metadata query and validated
HTTPS tarball inspection exit 0; SRI matches, archive 1,061,939 bytes. Browser ESM,
UMD and worker bundles embed real 85,585-byte WASM (magic/hash checked only).
Pinned README excludes consumer SCE and reports no formal third-party audit.
Candidate is a different ratchet, not a verified browser port preserving existing
native libsignal engine/session records. Existing unsupported probe again exits 2.
Full commands/digests/limitations: state/evidence/S00-022-auto-crypto-bcd7f2a71667.md.
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: no approved backend strategy reconciles this concrete alternative
with card's audited engine/persistence preservation and ENC-009/011. No browser
known-answer full OMEMO2/SCE test, audit, migration or wire compatibility passed.
No source/ADR edits made after identifying blocker; ADR 0003 remains proposed.
## 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.
Required external input: architecture/security/product owner records one backend
strategy: retained audited engine's maintained browser port with primary-source
license/support/SCE path, or authorization to evaluate a named alternative with
independent security assessment and explicit license/persistence migration route.
Any changed preservation condition must be reviewed through plan workflow, not
silently waived. No relaxation of ENC-003/009/011. Resolver records only this
bounded decision; it does not implement crypto or mark S00-004/S00-022 complete.
Fresh continuation may correct universal registry-absence/Signal-WASM assertions
in ADR and evaluate approved pinned target. Reporter exits after escalation.