docs(prompts): Order A3 master prompt draft (bug-class taxonomy + canary recall for Codex) #20

Merged

pdurlej merged 1 commit from claude/orders/order-a3-prompt-draft into main

2026-05-02 02:46:35 +02:00

claude commented

2026-05-02 02:43:02 +02:00

Collaborator

Summary

Drafted by GLM-5.1 sisyphus (oh-my-opencode framework, ULW-LOOP mode) per .sisyphus/plans/order-a3-prompt.md, following prompts/order-c-codex-askpass.md gold standard. 346 lines covering bug-class taxonomy storage, recall, and convergent-class detection.

Why DRAFT

Pre-Oracle-review draft. Operator pastes prompt to Oracle UI for sanity check before delegation to Codex. Same pattern as Order C prompt PR #11 (Oracle-validated before merge).

Scope (per charter §3 review-by-impact)

Small impact: docs only, single new file (prompts/order-a3-bug-class-taxonomy.md), no behavior change → ensemble review optional. Companion evidence file in .sisyphus/evidence/order-a3-prompt-summary.md.

When Codex implements per this prompt: ~200 LOC code + ~200 LOC tests = medium impact → 3+3 ensemble required at implementation PR.

Key clarification

A3 does NOT add the bug_class field to reviewer schema — that's already documented in charter §3 "Bug-class clustering hints" sub-rule (Oracle Q5 ruling 2026-05-01). A3 operationalizes:

Append-only JSONL storage of emitted bug_class tags
Cross-canary recall (last 10 canaries window)
Per-PR convergent-class detection (≥2 reviewers same class)
Operator alert when class hits ≥3 occurrences in window

Reviewer prompts (_base.py) are NOT touched — schema field already exists.

Linkage

Closes (when implementation lands) open loop reviewer-fix-patch-schema step A3 (deadline 2026-05-22)
Final of 3 split orders (A1 PR #18, A2 PR #19, A3 this PR)
Codex implementation must use linked-worktree pattern per charter §4 v2 (PR #15)

Token-arbitrage

GLM-5.1 wrote 346 lines on flat-fee z.ai subscription. Claude orchestrator reviewed + committed (~5k tokens). Estimated savings: 17-22k orchestrator tokens.

Co-authors

GLM-5.1 (z.ai sisyphus draft via OpenCode CLI — opencode run -m zai-coding-plan/glm-5.1)
Claude Opus 4.7 (1M context, orchestrator review + commit)

## Summary Drafted by **GLM-5.1 sisyphus** (oh-my-opencode framework, ULW-LOOP mode) per `.sisyphus/plans/order-a3-prompt.md`, following `prompts/order-c-codex-askpass.md` gold standard. 346 lines covering bug-class taxonomy storage, recall, and convergent-class detection. ## Why DRAFT **Pre-Oracle-review draft.** Operator pastes prompt to Oracle UI for sanity check before delegation to Codex. Same pattern as Order C prompt PR #11 (Oracle-validated before merge). ## Scope (per charter §3 review-by-impact) **Small impact**: docs only, single new file (`prompts/order-a3-bug-class-taxonomy.md`), no behavior change → ensemble review optional. Companion evidence file in `.sisyphus/evidence/order-a3-prompt-summary.md`. When Codex implements per this prompt: ~200 LOC code + ~200 LOC tests = **medium impact** → 3+3 ensemble required at implementation PR. ## Key clarification A3 does **NOT** add the `bug_class` field to reviewer schema — that's already documented in charter §3 "Bug-class clustering hints" sub-rule (Oracle Q5 ruling 2026-05-01). A3 operationalizes: 1. Append-only JSONL storage of emitted bug_class tags 2. Cross-canary recall (last 10 canaries window) 3. Per-PR convergent-class detection (≥2 reviewers same class) 4. Operator alert when class hits ≥3 occurrences in window Reviewer prompts (`_base.py`) are NOT touched — schema field already exists. ## Linkage - Closes (when implementation lands) open loop `reviewer-fix-patch-schema` step A3 (deadline 2026-05-22) - Final of 3 split orders (A1 PR #18, A2 PR #19, A3 this PR) - Codex implementation must use linked-worktree pattern per charter §4 v2 (PR #15) ## Token-arbitrage GLM-5.1 wrote 346 lines on flat-fee z.ai subscription. Claude orchestrator reviewed + committed (~5k tokens). Estimated savings: 17-22k orchestrator tokens. ## Co-authors - GLM-5.1 (z.ai sisyphus draft via OpenCode CLI — `opencode run -m zai-coding-plan/glm-5.1`) - Claude Opus 4.7 (1M context, orchestrator review + commit)

claude added the

ready-for-operator

label

2026-05-02 02:43:02 +02:00

pdurlej was assigned by claude

2026-05-02 02:43:03 +02:00

claude added 1 commit

2026-05-02 02:43:03 +02:00

docs(prompts): Order A3 master prompt draft (bug-class taxonomy + canary recall for Codex) 7d33217fa8

Drafted by GLM-5.1 sisyphus per .sisyphus/plans/order-a3-prompt.md, following
prompts/order-c-codex-askpass.md gold standard. 346 lines covering:
- Operationalization of charter §3 "Bug-class clustering hints" (Oracle Q5 ruling 2026-05-01)
- tools/taxonomy.py module spec (~80 LOC) — record_class, recall_classes, convergent_classes
- Append-only JSONL storage at state/reviews/_taxonomy.jsonl
- Convergent-class detection in decision comments (≥2 reviewers same bug_class)
- Cross-canary recall hook with operator alert at ≥3 occurrences in last 10 canaries
- 8+ tests (record + recall + convergent + alert threshold + JSONL durability)
- NO reviewer prompt edits (_base.py untouched per plan hard constraint)
- Bootstrap rule for linked worktree (per charter §4 v2 / Order C-followup)

Pre-Oracle-review draft. Operator pastes to Oracle UI before delegation to Codex.

Per charter §3 review-by-impact: small impact (docs only, single new file,
no behavior change) → ensemble review optional.

Closes (when implementation lands) open loop reviewer-fix-patch-schema step A3
(deadline 2026-05-22). Final of 3 split orders (A1 PR#18, A2 PR#19, A3 this).

Co-authored-by: GLM-5.1 (z.ai sisyphus draft via OpenCode CLI)
Co-authored-by: Claude Opus 4.7 (1M context, orchestrator review + commit)

pdurlej merged commit 203701abc4 into main

2026-05-02 02:46:35 +02:00

pdurlej referenced this pull request from a commit

2026-05-02 02:46:36 +02:00

Merge pull request 'docs(prompts): Order A3 master prompt draft (bug-class taxonomy + canary recall for Codex)' (#20) from claude/orders/order-a3-prompt-draft into main