wt
a53f0f1a14
Changes: Preserve incomplete work and blocker metadata for S00-028. This checkpoint does not mark implementation accepted. Validation: Session ended with status blocked. Blocker: S00-028 cannot independently validate project filesystem sandbox: installed Codex sandbox exits before command execution because the app-server socket directory must be user-owned with mode 0700. Host socket repair is outside launcher arguments scope. Automatic blocker limit reached; explicit external resolution required. Task: S00-028 Agent: auto-ci-cd-211cf3a2bd08 Role: ci-cd Action: claim Status: blocked Task title: Repair conflicting Codex harness sandbox arguments
62 lines
2.7 KiB
Markdown
62 lines
2.7 KiB
Markdown
# S00-028: Repair conflicting Codex harness sandbox arguments
|
||
|
||
- Remediation для: S00-025; root: S00-005; depth: 3
|
||
|
||
> Generated from planning/tasks.json; status is in state/tasks.json.
|
||
|
||
- Этап: S00
|
||
- Оператор: ci-cd
|
||
- Reviewer: qa
|
||
- Зависимости: S00-002, S00-030
|
||
- Требования: инженерная подготовка
|
||
|
||
## Один результат
|
||
|
||
A reviewed compatible runner argv starts a fresh harness with project write sandbox without the mutually exclusive argument error.
|
||
|
||
## Разрешённые пути
|
||
|
||
- `runner.local.json`
|
||
- `runner.example.json`
|
||
- `docs/AUTOMATION.md`
|
||
|
||
Не изменять другие 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/storage.md
|
||
- docs/decisions/README.md
|
||
- state/blockers/S00-023.md
|
||
- state/blockers/S00-025.md
|
||
- state/blockers/S00-028.md
|
||
|
||
## Шаги
|
||
|
||
1. Inspect the recorded CLI usage error and configured argv without logging secrets
|
||
2. Obtain coordinator input for the active runner configuration and preserve project-only sandbox
|
||
3. Correct only conflicting launcher arguments and document the supported invocation
|
||
4. Validate argument compatibility with a bounded non-product smoke check and submit for independent review
|
||
|
||
## Приёмка
|
||
|
||
1. The conflicting approval/sandbox combination is removed from the active launcher
|
||
2. Project write sandbox remains enforced
|
||
3. No original storage task is marked complete or executed during launcher repair
|
||
|
||
## Focused checks
|
||
|
||
1. Inspect codex exec help and the selected argument combination
|
||
2. Run a bounded launcher smoke check without resuming a conversation or selecting product work
|
||
|
||
## Блокер и завершение запуска
|
||
|
||
Для всех ролей 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 при блокере.
|