Files
LumaWeb/planning/tasks/S00-026.md
T
wt 6f0b4029c4 S00-024: Record blocked task and remediation handoff
Changes: Preserve incomplete work and blocker metadata for S00-024. This checkpoint does not mark implementation accepted.
Validation: Session ended with status blocked.
Blocker: S00-024 cannot establish readiness for S00-020: official checksum retrieval fails with configured proxy DNS error and host Node/npm differ from accepted pins; no partial environment-access artifacts exist.

Task: S00-024
Agent: auto-ci-cd-988167c541cf
Role: ci-cd
Action: claim
Status: blocked

Task title: Устранить прерывание: Restore access to the pinned Linux XMPP experiment toolchain
2026-10-15 16:35:52 +07:00

61 lines
3.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# S00-026: Provide approved access to the pinned Linux experiment artifacts
- Remediation для: S00-024; root: S00-003; depth: 3
> Generated from planning/tasks.json; status is in state/tasks.json.
- Этап: S00
- Оператор: ci-cd
- Reviewer: qa
- Зависимости: S00-001, S00-002, S00-017, S00-018, S00-019
- Требования: инженерная подготовка
## Один результат
One independently verified approved access path supplies authentic pinned Linux Node/npm and integrity-verifiable parent locked dependencies for S00-020.
## Разрешённые пути
- `experiments/0002-xmpp-library/environment-access/**`
Не изменять другие modules, shared contracts или spec snapshots без изменения плана. Stem без расширения разрешает принятые stack-specific extensions и focused test рядом.
## Прочитать
- docs/WEB_PROFILE.md
- docs/ARCHITECTURE.md
- docs/CONTRACTS.md
- docs/TESTING.md
- roles/protocol.md
- docs/decisions/README.md
- state/blockers/S00-020.md
- state/blockers/S00-024.md
- state/blockers/S00-026.md
## Шаги
1. Obtain environment-owner confirmation of restored approved HTTPS access or local authentic runtime/checksum/dependency artifact paths, without credentials in reports.
2. Verify Linux Node 24.21.0 vendor checksum material and executing Node 24.21.0/npm 11.19.0.
3. Install unchanged copies of parent manifest and lock only inside environment-access using npm ci with scripts disabled and TLS/integrity verification retained.
4. Record reproducible paths, checks and limits for independent review; leave original tasks unfinished.
## Приёмка
1. Approved access or authentic local artifacts are available and documented without policy bypass.
2. Exact pinned Linux runtime executes and vendor checksum verification succeeds.
3. Unchanged copied parent lock installs with integrity enforced and Stanza 12.22.1 available; no stack/spec/lock change.
## Focused checks
1. Repeat original official HTTPS retrieval or independently verify approved supplied artifact provenance/checksum.
2. Check exact node/npm versions and isolated locked npm ci with scripts disabled.
3. Verify source changes stay within environment-access and no TLS/proxy/engine bypass occurs.
## Блокер и завершение запуска
Для всех ролей scope — только эта задача. При блокере создать issue JSON по state/ISSUE_TEMPLATE.json, вызвать escalate с текущим ID/role/agent, проверить status=blocked и resolution_task, затем немедленно завершить запуск. Не решать blocker и не выбирать следующую задачу самому. Новый агент назначается runner. Правки metadata через CLI — единственное исключение scope.
## Передача
Сохранить evidence/handoff; submit → review и завершить запуск. Reviewer также выполняет только эту задачу, включая обязательное escalate при блокере.