docs(prompts): F1.5 + Hardening + F2 dispatch for Codex (operator-autonomous) #257

Merged

pdurlej merged 1 commit from claude/orders/codex-f1.5-hardening-f2-2026-05-13 into main

2026-05-13 08:29:55 +02:00

claude commented

2026-05-13 08:22:20 +02:00

Collaborator

Tier per ADR-0007: Lite — single new prompt file, 396 LoC, no sacred paths, no schema/runtime/code changes. Operator-merge.

Why now

Operator's morning voice memo 2026-05-13 ~08:40 CEST after first ⚛️ (run #621):

"kupuję to 1.5, musimy hardening, nie możemy teraz puścić tego, żeby to się popsuło (...) żebyśmy mogli wejść w F2 (...) Może dzisiaj spróbujmy dobić do F3 i jesteśmy w domu."

Operator goes to work after pasting this prompt; Codex executes autonomously; operator reviews checkpoints + approves next phase upon return.

What ships

Single file: prompts/codex-f1.5-hardening-f2-2026-05-13.md (396 lines)

Contains:

§ 0 Wake-up read list (recovery plan, handover, ADRs, this file)
§ 1 State inherited (run #621 ⚛️, runner active, 63 containers, known issues)
§ 2 Work queue:
- F1.5 — 3 stateless no-op smokes (n8n-main, excalidraw-app, mirotalk-sfu) with strict-v2 fill-as-needed
- Hardening A — runner poller reliability (Forgejo issue + watchdog patch)
- Hardening B — STATUS_NOW.md post-cutover baseline update
- Hardening D — strict-v2 batch fill for 5-7 F2 candidates (one batch PR, not per-service)
- F2 — 5-7 stateless smokes (uptime-kuma / umami / searxng / karakeep / karakeep-chrome / excalidraw-room / homepage), conditional on Codex quota + Pan Herbatka self-check
- F3 PREP only — stateful design issue + strict-v2 fill + backup-before script; NO smoke without operator
§ 3 Token budget + cutoffs (<30% defer F2, <20% handover, <10% hard stop)
§ 4 Operator approval gates: G1-G3 pre-approved (no-op smokes + Lite PRs); G4-G7 hard gates (real-change, F3 smoke, prod restart, sacred path)
§ 5 Stop conditions (3-strikes, prod unhealthy, sacred path, quota/time/strange behavior cliffs)
§ 6 Reporting format (mandatory after each Phase)
§ 7 End-of-session handover format
§ 8 Cousin coordination (Pan Herbatka off, glm passive, DeepSeek silent, Iskra off-limits)
§ 9 References

What this PR does NOT do

Does NOT execute F1.5/F2/F3 — that's Codex's job after operator pastes
Does NOT touch RS2000
Does NOT modify production code, compose, or runtime
Does NOT pre-approve real-change apply or stateful smoke (operator hard gate)
Does NOT auto-trigger Codex dispatch (operator pastes when ready)

Test plan

Operator reviews § 4 (approval gates) — agree with G1-G3 pre-approval scope?
Operator reviews § 5 (stop conditions) — agree with hard gates list?
Operator reviews § 2 F3 PREP scope — agree NO smoke without operator on duty?
Operator merge → prompt lives in repo for Codex
Operator pastes prompt body into Codex app → Codex begins F1.5
Operator returns home → reviews checkpoint comments on #142 → decides next session

Operator's North Star

Family time > heroic cutover. Today's plan: F1.5 + Hardening + F2 if green. F3 = next session (operator on duty, clear head). Codex stops at 22:00 CEST regardless of progress.

🍵 — Pan Herbatka, autonomous dispatch ready, 2026-05-13 ~08:50 CEST

Refs: PR #250 (recovery plan), #251-#256 (cutover stack), #142 (main thread), run #621/757 (dashboard ⚛️)

Tier per ADR-0007: **Lite** — single new prompt file, 396 LoC, no sacred paths, no schema/runtime/code changes. Operator-merge. ## Why now Operator's morning voice memo 2026-05-13 ~08:40 CEST after first ⚛️ (run #621): > *"kupuję to 1.5, musimy hardening, nie możemy teraz puścić tego, żeby to się popsuło (...) żebyśmy mogli wejść w F2 (...) Może dzisiaj spróbujmy dobić do F3 i jesteśmy w domu."* Operator goes to work after pasting this prompt; Codex executes autonomously; operator reviews checkpoints + approves next phase upon return. ## What ships Single file: `prompts/codex-f1.5-hardening-f2-2026-05-13.md` (396 lines) Contains: - § 0 Wake-up read list (recovery plan, handover, ADRs, this file) - § 1 State inherited (run #621 ⚛️, runner active, 63 containers, known issues) - § 2 Work queue: - **F1.5** — 3 stateless no-op smokes (n8n-main, excalidraw-app, mirotalk-sfu) with strict-v2 fill-as-needed - **Hardening A** — runner poller reliability (Forgejo issue + watchdog patch) - **Hardening B** — STATUS_NOW.md post-cutover baseline update - **Hardening D** — strict-v2 batch fill for 5-7 F2 candidates (one batch PR, not per-service) - **F2** — 5-7 stateless smokes (uptime-kuma / umami / searxng / karakeep / karakeep-chrome / excalidraw-room / homepage), conditional on Codex quota + Pan Herbatka self-check - **F3 PREP only** — stateful design issue + strict-v2 fill + backup-before script; NO smoke without operator - § 3 Token budget + cutoffs (<30% defer F2, <20% handover, <10% hard stop) - § 4 Operator approval gates: G1-G3 pre-approved (no-op smokes + Lite PRs); G4-G7 hard gates (real-change, F3 smoke, prod restart, sacred path) - § 5 Stop conditions (3-strikes, prod unhealthy, sacred path, quota/time/strange behavior cliffs) - § 6 Reporting format (mandatory after each Phase) - § 7 End-of-session handover format - § 8 Cousin coordination (Pan Herbatka off, glm passive, DeepSeek silent, Iskra off-limits) - § 9 References ## What this PR does NOT do - Does NOT execute F1.5/F2/F3 — that's Codex's job after operator pastes - Does NOT touch RS2000 - Does NOT modify production code, compose, or runtime - Does NOT pre-approve real-change apply or stateful smoke (operator hard gate) - Does NOT auto-trigger Codex dispatch (operator pastes when ready) ## Test plan - [ ] Operator reviews § 4 (approval gates) — agree with G1-G3 pre-approval scope? - [ ] Operator reviews § 5 (stop conditions) — agree with hard gates list? - [ ] Operator reviews § 2 F3 PREP scope — agree NO smoke without operator on duty? - [ ] Operator merge → prompt lives in repo for Codex - [ ] Operator pastes prompt body into Codex app → Codex begins F1.5 - [ ] Operator returns home → reviews checkpoint comments on #142 → decides next session ## Operator's North Star Family time > heroic cutover. Today's plan: F1.5 + Hardening + F2 if green. F3 = next session (operator on duty, clear head). Codex stops at 22:00 CEST regardless of progress. 🍵 — *Pan Herbatka, autonomous dispatch ready, 2026-05-13 ~08:50 CEST* Refs: PR #250 (recovery plan), #251-#256 (cutover stack), #142 (main thread), run #621/757 (dashboard ⚛️)

claude added 1 commit

2026-05-13 08:22:20 +02:00

docs(prompts): F1.5 + Hardening + F2 dispatch for Codex (operator-autonomous)

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

Details

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

Details

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

Details

05feddcbf0

Operator's morning voice memo 2026-05-13 ~08:40 CEST:
"kupuję 1.5, musimy hardening (...) żebyśmy mogli wejść w F2 (...)
spróbujmy dobić do F3 i jesteśmy w domu."

Pan Herbatka rec interpretation:
- F1.5 (3 stateless no-op smokes: n8n-main / excalidraw-app / mirotalk-sfu)
- Hardening A (runner poller reliability)
- Hardening B (STATUS_NOW.md post-cutover baseline)
- Hardening D (strict-v2 batch fill for F2 candidates)
- F2 (5-7 stateless smokes IF Codex feels OK)
- F3 PREP only — NO smoke without operator on duty + backup-before

Operator pre-approves G1-G3 (no-op smokes + Lite/Trivial PRs).
Hard gates G4-G7 (real-change, F3 smoke, prod restart, sacred path)
require explicit operator approval during operator's session.

Stop conditions hard-coded: 3-strikes, prod unhealthy, sacred path,
quota cliff, time cliff (>22:00 CEST), strange behavior.

Token budget cutoffs: stop at <30% post-F1.5 (defer F2),
<20% mid-Hardening (handover), <10% hard stop.

Reporting format mandatory after each Phase + final handover.

Refs: PR #250 (recovery plan), #251-#256 (cutover stack), #142 (main thread),
run #621/757 (dashboard ⚛️ proven)