wt
c35046a675
Changes: Preserve incomplete work and blocker metadata for S00-015. This checkpoint does not mark implementation accepted. Validation: Session ended with status blocked. Blocker: S00-012 fresh reviewer exited before review because its execution provider returned HTTP 503 and Selected model is at capacity. Provider availability or operator-authorized local harness model configuration is external to S00-015 source scope. Task: S00-015 Agent: auto-ci-cd-5475930af078 Role: ci-cd Action: claim Status: blocked Task title: Устранить прерывание: Fix runner prompt delivery after partial stdin timeout
60 lines
3.0 KiB
Markdown
60 lines
3.0 KiB
Markdown
# S00-016: Restore reviewer model availability after provider capacity failure
|
||
|
||
- Remediation для: S00-015; root: S00-002; depth: 3
|
||
|
||
> Generated from planning/tasks.json; status is in state/tasks.json.
|
||
|
||
- Этап: S00
|
||
- Оператор: ci-cd
|
||
- Reviewer: qa
|
||
- Зависимости: S00-001, S00-011, S00-013, S00-014
|
||
- Требования: инженерная подготовка
|
||
|
||
## Один результат
|
||
|
||
A verified available tool-capable fresh reviewer execution path after explicit external provider/configuration readiness, without bypassing S00-012 independent review.
|
||
|
||
## Разрешённые пути
|
||
|
||
- `scripts/runner.py`
|
||
- `tests/tooling/test_automation.py`
|
||
|
||
Не изменять другие 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/orchestrator.md
|
||
- docs/decisions/README.md
|
||
- state/blockers/S00-012.md
|
||
- state/blockers/S00-015.md
|
||
- state/blockers/S00-016.md
|
||
|
||
## Шаги
|
||
|
||
1. Obtain coordinator confirmation that the configured reviewer model is available or an available replacement is explicitly authorized and locally configured; do not put credentials in evidence.
|
||
2. After external release, verify the readiness condition using the coordinator-authorized harness in a fresh process; do not retry indefinitely.
|
||
3. Record actual readiness evidence and submit remediation for independent review; leave S00-012 acceptance to its subsequent fresh reviewer.
|
||
|
||
## Приёмка
|
||
|
||
1. Provider/configuration readiness is explicitly supplied by the coordinator.
|
||
2. A fresh tool-capable reviewer execution path succeeds without the recorded startup capacity/503 failure.
|
||
3. S00-012 is not accepted or bypassed by the remediation.
|
||
|
||
## Focused checks
|
||
|
||
1. Inspect failed reviewer run evidence for the exact external failure.
|
||
2. Record actual authorized fresh harness startup result after external readiness; do not claim unavailable checks passed.
|
||
|
||
## Блокер и завершение запуска
|
||
|
||
Для всех ролей 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 при блокере.
|