wt
bac7706480
Changes: Release external waiting state for S00-028 through tasks.py. Input: Coordinator supplies the active compatible argv from runner.local.json: codex -c sandbox_workspace_write.network_access=true exec --approve-for-me --ephemeral -. Explicit --sandbox was removed before the S00-024/S00-022/S00-025 fresh agent launches. --approve-for-me retains workspace-write per installed CLI help; no danger-full-access or bypass option. Actual subsequent run state/runs/auto-storage-ae5930b6fbdf/run.json shows the fresh harness executed tools and reached its own escalate, unlike the original immediate CLI exit 2. Installed CLI bounded help check codex exec --approve-for-me --ephemeral --help exited 0. Outbound network config retains existing proxy and TLS, independently probed via codex -c sandbox_mode='"workspace-write"' -c sandbox_workspace_write.network_access=true sandbox -- python3 /tmp/luma-probe-registry.py, exit 0; state/runs/coordinator-network/output.log. Fresh S00-028 executor/QA must verify supported argv and filesystem scope; no storage task completion or launcher repair acceptance claimed. Validation: External input availability checked; tasks.py release-external succeeded. Acceptance and dependent tasks remain unverified pending fresh executor and independent review. Task: S00-028 Agent: coordinator-input-s00-028 Role: orchestrator Action: release-external Status: todo Task title: Repair conflicting Codex harness sandbox arguments
3.9 KiB
3.9 KiB
S00: Профиль и проверка стека
Зафиксировать Web scope, browser targets и проверенные кандидаты, не устанавливая непроверенный framework по догадке.
Входной gate: нет. Выходной gate: S00-010.
Задачи
- S00-001: Утвердить Web-профиль — orchestrator; done.
- S00-002: Выбрать framework и build runtime — orchestrator; done.
- S00-003: Проверить XMPP WSS/auth библиотеку — protocol; blocked.
- S00-004: Проверить browser OMEMO backend — crypto; blocked.
- S00-005: Выбрать IndexedDB wrapper и migration policy — storage; blocked.
- S00-006: Зафиксировать browser/reference matrix — orchestrator; todo.
- S00-007: Утвердить password и crypto unlock модель — security; todo.
- S00-008: Описать WSS/upload/TURN/push topology — ci-cd; todo.
- S00-009: Согласовать результаты spikes — orchestrator; todo.
- S00-011: Restore verified npm registry access for the stack spike — ci-cd; done.
- S00-012: Fix runner prompt delivery after partial stdin timeout — ci-cd; done.
- S00-013: Bound oversized S21-006 runner context without truncating requirements — ci-cd; done.
- S00-014: Fix repeated runner cleanup after a submitted parent is reaped — ci-cd; done.
- S00-015: Устранить прерывание: Fix runner prompt delivery after partial stdin timeout — ci-cd; done.
- S00-016: Restore reviewer model availability after provider capacity failure — ci-cd; done.
- S00-017: Establish fail-closed SCRAM server-final validation — protocol; done.
- S00-018: Validate bounded standalone XML ingress for the XMPP candidate — protocol; done.
- S00-019: Validate browser-compatible SCRAM-SHA-512 through a public mechanism API — crypto; done.
- S00-020: Restore access to the pinned Linux XMPP experiment toolchain — ci-cd; blocked.
- S00-021: Устранить прерывание: Проверить browser OMEMO backend — crypto; done.
- S00-022: Confirm or source a verified browser/WASM-capable OMEMO2 backend for the Web client endpoint — crypto; blocked.
- S00-023: Устранить прерывание: Выбрать IndexedDB wrapper и migration policy — storage; blocked.
- S00-024: Устранить прерывание: Restore access to the pinned Linux XMPP experiment toolchain — ci-cd; blocked.
- S00-025: Устранить прерывание: Устранить прерывание: Выбрать IndexedDB wrapper и migration policy — storage; blocked.
- S00-026: Provide approved access to the pinned Linux experiment artifacts — ci-cd; todo.
- S00-027: Restore approved npm registry connectivity for the OMEMO2 backend investigation — ci-cd; todo.
- S00-028: Repair conflicting Codex harness sandbox arguments — ci-cd; todo.
- S00-010: Gate: Профиль и проверка стека — qa; todo.
Граница этапа
Выходной gate проверяет evidence/готовые проверки, не реализует функции за остальные задачи. Если отдельная карточка требует слишком большой контекст — split с сохранением requirements coverage.