pdurlej/platform

Fork 0

DRAFT: docs(prompts): stage F2 post-260 soak ramp #287

Closed

codex wants to merge 1 commit from codex/f2/post-260-soak-dispatch into main

codex commented

2026-05-15 18:53:19 +02:00

Collaborator

Canary status: missing — fire canary 3+3 manually before merge

DRAFT — do not merge until #260 08:00 soak evidence is green.

Canary Context Pack

Product story

Tomorrow morning should not be another planning session. If #260 soak is clean, the operator should have a ready dispatch for the remaining immediate F2 stateless no-op smokes.

What changed

Adds prompts/codex-f2-post-260-soak-ramp-2026-05-16.md, a tightened F2 dispatch that starts with #260 soak evidence, then runs the remaining stateless candidates one at a time.

Why it changed

The old F2 prompt assumed #260 was still an observation lane. After the deploy-runner scope fix, the next F2 ramp should treat watchdog restarts as a stop signal, not expected diagnostic noise.

Files touched

prompts/codex-f2-post-260-soak-ramp-2026-05-16.md

Relevant context

#260 deploy-runner scope fix and post-fix runs #957/#958.
ADR-0018 root-cause-first framing.
Previous prompts/codex-f2-ramp-continuation-2026-05-14.md.

Runtime evidence

No runtime mutation in this PR. The prompt references already collected post-fix evidence: #957 and #958 picked up without watchdog restart.

Known constraints

Merge only after #260 soak is clean at 08:00.
F2 smokes are workflow_dispatch no-op smokes only.
Meerkat and F3 are explicitly out of this dispatch.

Explicit out-of-scope

No Meerkat canonical compose import.
No F3/stateful smoke.
No production restart.

Requested decision

Keep as a draft until the #260 soak is green, then merge/use as the morning F2 execution packet.

Merge blockers

Any #260 watchdog restart after the DB repair.
Any evidence that recent auto-apply jobs again sit with task_id=0 for minutes.
Operator decides to defer F2 after soak.

Spec sources read

prompts/codex-f2-ramp-continuation-2026-05-14.md — prior F2 dispatch.
decisions/0018-agentic-first-fix-root-causes.md — no recurring false-fire framing.
docs/ci/runner-contract.md — deploy runner contract after #286.

Test plan

git diff --check -- prompts/codex-f2-post-260-soak-ramp-2026-05-16.md

Canary status: missing — fire canary 3+3 manually before merge DRAFT — do not merge until #260 08:00 soak evidence is green. ## Canary Context Pack ### Product story Tomorrow morning should not be another planning session. If #260 soak is clean, the operator should have a ready dispatch for the remaining immediate F2 stateless no-op smokes. ### What changed Adds `prompts/codex-f2-post-260-soak-ramp-2026-05-16.md`, a tightened F2 dispatch that starts with #260 soak evidence, then runs the remaining stateless candidates one at a time. ### Why it changed The old F2 prompt assumed #260 was still an observation lane. After the deploy-runner scope fix, the next F2 ramp should treat watchdog restarts as a stop signal, not expected diagnostic noise. ### Files touched - `prompts/codex-f2-post-260-soak-ramp-2026-05-16.md` ### Relevant context - #260 deploy-runner scope fix and post-fix runs #957/#958. - ADR-0018 root-cause-first framing. - Previous `prompts/codex-f2-ramp-continuation-2026-05-14.md`. ### Runtime evidence No runtime mutation in this PR. The prompt references already collected post-fix evidence: #957 and #958 picked up without watchdog restart. ### Known constraints - Merge only after #260 soak is clean at 08:00. - F2 smokes are workflow_dispatch no-op smokes only. - Meerkat and F3 are explicitly out of this dispatch. ### Explicit out-of-scope - No Meerkat canonical compose import. - No F3/stateful smoke. - No production restart. ### Requested decision Keep as a draft until the #260 soak is green, then merge/use as the morning F2 execution packet. ### Merge blockers - Any #260 watchdog restart after the DB repair. - Any evidence that recent auto-apply jobs again sit with `task_id=0` for minutes. - Operator decides to defer F2 after soak. ## Spec sources read - `prompts/codex-f2-ramp-continuation-2026-05-14.md` — prior F2 dispatch. - `decisions/0018-agentic-first-fix-root-causes.md` — no recurring false-fire framing. - `docs/ci/runner-contract.md` — deploy runner contract after #286. ## Test plan ```bash git diff --check -- prompts/codex-f2-post-260-soak-ramp-2026-05-16.md ```

codex added the

tier/full

cutover-gate

risk/process

labels

2026-05-15 18:53:19 +02:00

codex added 1 commit

2026-05-15 18:53:19 +02:00

docs(prompts): stage F2 post-260 soak ramp

canary-required / collect-diff (pull_request) Successful in 4s

Details

base-is-main / guard (pull_request) Successful in 2s

Details

canary-required / canary (pull_request) Successful in 12s

Details

edad4f1ea3

codex referenced this pull request

2026-05-15 18:59:37 +02:00

[coordination-lane] Cutover Flight Phase 2: v2 catalog to gate #142

codex referenced this pull request

2026-05-15 19:05:35 +02:00

[coordination-lane] Cutover Flight Phase 2: v2 catalog to gate #142

codex commented

2026-05-24 07:59:59 +02:00

Author

Collaborator

Fork D triage — closing superseded

Role: executor
Decision: close, no rewrite.

This PR is a historical F2 post-#260 dispatch for 2026-05-16. The F2/F3/cutoff work it prepared has already been completed and the active planning surface is now the milestone roadmap / current status, not this dated prompt. Keeping this open would invite a future agent to replay an obsolete migration instruction.

No production mutation performed. Closing as superseded.

## Fork D triage — closing superseded **Role:** executor **Decision:** close, no rewrite. This PR is a historical F2 post-#260 dispatch for 2026-05-16. The F2/F3/cutoff work it prepared has already been completed and the active planning surface is now the milestone roadmap / current status, not this dated prompt. Keeping this open would invite a future agent to replay an obsolete migration instruction. No production mutation performed. Closing as superseded.

codex closed this pull request

2026-05-24 07:59:59 +02:00