Changes: Preserve incomplete work and blocker metadata for S00-020. This checkpoint does not mark implementation accepted. Validation: Session ended with status blocked. Blocker: Previous runner session was interrupted before submit/escalate; processes stopped. User now explicitly requests resuming development. Preserve partial artifacts, verify them in a fresh bounded remediation, and return original to a new executor only after independent review. Task: S00-020 Agent: auto-ci-cd-5a18c8aa1b42 Role: ci-cd Action: claim Status: blocked Task title: Restore access to the pinned Linux XMPP experiment toolchain
59 lines
3.1 KiB
Markdown
59 lines
3.1 KiB
Markdown
# S00-020: Restore access to the pinned Linux XMPP experiment toolchain
|
||
|
||
- Remediation для: S00-003; root: S00-003; depth: 1
|
||
|
||
> 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, S00-024
|
||
- Требования: ACC-004, NET-003, NET-004
|
||
|
||
## Один результат
|
||
|
||
One independently reviewed environment-access probe demonstrates authentic pinned Linux Node/npm and integrity-verified installation of the parent locked dependency graph without changing accepted stack or network security policy.
|
||
|
||
## Разрешённые пути
|
||
|
||
- `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
|
||
|
||
## Шаги
|
||
|
||
1. Read S00-003 blocker evidence and accepted stack pins.
|
||
2. Obtain external approved HTTPS connectivity or authentic locally supplied pinned Linux runtime and locked dependency artifacts.
|
||
3. Verify vendor checksum for runtime, exact node/npm versions, and lock integrity with a script confined to the remediation directory; install a copy of the parent manifest/lock only inside that directory.
|
||
4. Document reproducible approved artifact paths or connectivity and actual results; submit for independent review.
|
||
|
||
## Приёмка
|
||
|
||
1. Node 24.21.0 and npm 11.19.0 execute on this Linux host with authenticated vendor checksum verification recorded.
|
||
2. Copied unchanged parent package-lock installs successfully with package integrity enforced and Stanza 12.22.1 available.
|
||
3. No stack/lock/spec changes, engine or TLS bypass, proxy policy bypass or secrets in evidence.
|
||
|
||
## Focused checks
|
||
|
||
1. Exact runtime version and official checksum comparison.
|
||
2. Isolated npm ci of unchanged parent manifest/lock with lifecycle scripts disabled and TLS verification retained.
|
||
3. Independent review repeats access/runtime/lock checks.
|
||
|
||
## Блокер и завершение запуска
|
||
|
||
Для всех ролей 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 при блокере.
|