Files
LumaWeb/planning
wt a338d3a1dd S00-022: Record newly available external input for independent verification
Changes: Release external waiting state for S00-022 through tasks.py. Input: New primary-source candidate supplied: libomemo.js@3.0.0 https://github.com/conversejs/libomemo.js declares legacy OMEMO and OMEMO2 0.9.1 urn:xmpp:omemo:2, WASM and browser worker-client; Converse 14 source uses this dependency and encryptSCE/decryptSCE. Source links and limitations in state/runs/coordinator-research/omemo2-sources.md. Previous npm E404 queries did not include libomemo.js. Upstream explicitly lacks third-party security audit; GPL-3.0 compatibility, actual target tests, preservation of accepted verified engine/persistence and security review remain mandatory. New candidate is sourcing input only, not permission to replace an accepted engine, waive audit/requirements, or claim acceptance. Fresh task executor must evaluate this candidate under the existing card and escalate any unresolved bounded requirement.
Validation: External input availability checked; tasks.py release-external succeeded. Acceptance and dependent tasks remain unverified pending fresh executor and independent review.

Task: S00-022
Agent: coordinator-input-s00-022
Role: orchestrator
Action: release-external
Status: todo

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

План разработки

  • ROADMAP.md: 22 логически связанных этапа с входным/выходным gate.
  • TASK_MATRIX.md и task_matrix.csv: 275 задач, операторы/reviewers, статусы и prerequisites.
  • tasks/<ID>.md: bounded outcome, scope, inputs, steps, acceptance/checks.
  • tasks.json: полные definitions; читать целиком небольшой модели не нужно.
  • requirements.json: 221 ID исходных документов, 211 применимых к Web, 10 native-only с причиной исключения.
  • TRACEABILITY.md: requirement → tasks, allocation не implementation.
  • ATOMICITY.md: ограничения задач/контекста и порядок split.

Начальное состояние всех задач — todo. Подготовленные в этой основе workflow/docs/tooling не являются выполнением будущих продуктовых tasks. Первая доступная задача — S00-001, выбор framework идёт после Web profile.

Этапные gates проверяют результат данного этапа; окончательный Web acceptance — S21. Тестовые fixtures не заменяют interoperability/provider evidence.