Skip to content

docs: Apply approved v1.6 release priorities - #749

Merged
mergify[bot] merged 5 commits into
mainfrom
codex/plan-release-focus-20261009
Oct 9, 2026
Merged

mergify[bot] merged 5 commits into
mainfrom
codex/plan-release-focus-20261009

Conversation

@Cuarroc

@Cuarroc Cuarroc commented Oct 8, 2026 •

Copy link
Copy Markdown
Owner

Der PLAN enthält jetzt die geprüften PR-Stände und die korrigierte Reihenfolge für v1.6.0.
Release-Voraussetzungen, reservierte Nahtstellen und verschobene Arbeiten sind klarer getrennt.
Der PR bleibt als Entwurf bei Root zur Abnahme; der offene Quellenabgleich C8 steht unter „Rest“.

Report

Package: srv-plan-749-finish / #749. Tier: C, documentation only.
Owner / authority: Root reassigned this existing PR to one execution owner after the previous Chief left; requirements are unchanged. Parent: approved canonical PLAN upkeep. Only docs/PLAN.md is changed; no other package, ready transition or merge.
Candidate: d48a2286a97d2a9382ef92fa2cafc254fb1df216. Integrated main base: ea6ca7e2499103660bcd82dff61a47026d332002.
Size: final PR +194/-104 = 298 changed lines; this sync commit +96/-117 = 213. Existing AGENTS-SLIM contract prose was rewrapped without dropping requirements to keep the entire PR within 300 lines.
Native goal evidence: get_goal returned null, then create_goal returned active for this bounded job; the milestone readback remained active before final gates/push. Checked worker handover ends this worker goal; Root acceptance and the parent delivery remain separate.

What changed

Status evidence

Direct gh pr view <n> --json state,mergedAt,isDraft reads completed at 2026-10-08T23:42:17.178540+00:00; open PRs were read again through 2026-10-08T23:47:06.486252+00:00. All commands returned exit 0. These are observations at those times, not claims of ongoing process activity or later queue outcomes.

PLAN package PR Observed status / UTC merge time
DR-04/04a #666 MERGED 2026-10-08T16:04:16Z
DR-04/04b #669 MERGED 2026-10-08T16:35:44Z
DR-04B-FU #727 MERGED 2026-10-08T22:06:42Z
DR-04c #671 MERGED 2026-10-08T17:43:49Z
DR-04c #674 MERGED 2026-10-08T19:45:55Z
DR-05 #734 MERGED 2026-10-08T23:30:05Z
DR-06/06a #676 MERGED 2026-10-08T20:56:05Z
DR-06/06b #681 MERGED 2026-10-08T21:42:27Z
DR-07a #731 MERGED 2026-10-08T23:14:56Z
DR-07b #732 MERGED 2026-10-08T23:14:31Z
DR-07c #752 OPEN Ready
DR-07d #753 MERGED 2026-10-08T23:38:16Z
DR-07e1 #751 OPEN Ready
DR-07e2 #755 OPEN Ready
DR-09 #638 MERGED 2026-10-08T14:46:25Z
DR-09-WIN #660 MERGED 2026-10-08T14:21:03Z
DR-10 #665 MERGED 2026-10-08T19:59:10Z
DR-11 / DR-10-WIRE owner #718 OPEN Draft
DR-12 #740 OPEN Draft
DR-13 #759 OPEN Draft
DR-15b #750 OPEN Draft
HOTFIX-RF-PW #741 OPEN Ready
DOC-OPERATORS #683 MERGED 2026-10-08T15:42:28Z
Z2-PLANPARSER #697 MERGED 2026-10-08T17:43:37Z
Z2-DOKSYNC #670 MERGED 2026-10-08T14:34:08Z
Z2-STATUS-UNKNOWN #739 MERGED 2026-10-08T22:50:42Z
Z2-START-MEASURE #742 MERGED 2026-10-08T22:36:59Z
Z2-MRP-COMPLETE #746 MERGED 2026-10-08T22:55:35Z
Z2-RAM-SLOTS #725 OPEN Draft
Z2-HYGIENE-STATUS #726 MERGED 2026-10-08T23:30:10Z
Z2-PR-PROTECTION #738 OPEN Ready
Z2-CIWATCH-SHAPE #745 OPEN Ready
V16-ARCH-D4-05 #631 MERGED 2026-10-08T08:10:01Z
V16-ARCH-D7 #632 MERGED 2026-10-08T15:25:08Z
V16-ARCH-D2 / UPD-CANCEL predecessor #664 MERGED 2026-10-08T16:13:04Z
V16-ARCH-D5a #704 MERGED 2026-10-08T20:27:48Z
V16-ADR-A1 #667 MERGED 2026-10-08T14:34:03Z
V16-ARCH-D5b #728 OPEN Draft
V16-KI30 / ARCH-D7-WIN disposition #737 OPEN Draft
Z4-ARCH-D1-REST #663 MERGED 2026-10-08T20:55:57Z
Z4-W118B-PROBE #675 MERGED 2026-10-08T14:34:14Z
Z4-W118B-PROFILE #678 MERGED 2026-10-08T15:58:08Z
M4-R19-02a #702 MERGED 2026-10-08T20:13:18Z
M4-R19-02b/03a #705 MERGED 2026-10-08T21:42:19Z
M4-R19-02c #717 MERGED 2026-10-08T22:19:06Z
DEV-KNOW (parked) #651 OPEN Draft
PR-ALT #574 CLOSED, unmerged
PR-ALT #613 CLOSED, unmerged
PR-ALT #614 CLOSED, unmerged
PR-ALT #642 CLOSED, unmerged
Inherited reserve predecessor #722 MERGED 2026-10-08T21:28:34Z

Evidence

Command / check Exit code / result
git rev-parse HEAD at takeover 0; matched 36241d17181ce8cd4e7bc0c02e4ef1803f820043
git fetch origin; git merge --no-commit origin/main 0 each; conflict-free, normal commit hooks
npm run dev:start-check before gate/commit/push runs 0; RAM and cargo checks passed; provider usage was not measured
bash scripts/ci/secret-scan.sh before both commits 0 each; no leaks
git diff --check 0
npm run dev:plan-lint 0; 29 packages
Python readback assertions for changed status/time evidence, preserved DF rows, historical column counts, scope and both size caps 0
git show ea6ca7e:<seam-file> with Python line counting 0; four measurements above
gh release list --limit 5 --json tagName,publishedAt,isDraft,isPrerelease 0; v1.5.0/v1.5.1 confirmed
Normal git commit hooks for merge and documentation sync 0 each
bash scripts/ci/gates.sh lane prepush on 9e76d83 0; 177 s
bash scripts/ci/gates.sh lane prepush on d48a228 0; 176 s; all 22 gates green, HQ/parser tests included, Rust 1892 passed / 7 skipped
git push -u origin codex/plan-release-focus-20261009 after each green step 0 each; normal push hooks passed
git ls-remote origin codex/plan-release-focus-20261009 after each push 0 each; matched 9e76d83, then the full candidate SHA above
gh pr view 749 --json url,state,isDraft,headRefOid,mergeable 0; open Draft, candidate matched, mergeable

No new test is appropriate for this documentation-only change. Sync trailer: No-Test: documentation only (PLAN status sync). Existing tests were not changed.

NICHT ABGEDECKT

  • Linux does not compile/run the #[cfg(windows)] tests or Windows clippy branches; the Windows lane runs in the merge queue. No Windows verdict is claimed here.
  • Prepush does not include browser smoke, frontend build or all linux workflow gates; external service state is not checked. No live PC drill, installation, release, runtime behavior repair or new decision was performed.
  • AgentsRoom lage-jetzt and its worktree mirror were unavailable. Direct Git/GitHub reads were used. Provider limit, actual harness model and worker-log activity were not measured by the start check.
  • Earlier dated history/contract sections are preserved; a source merge is not a claim of installed, usable or fully accepted product behavior. No worker start follows from this PLAN update.

Reviews and disposition

Review: ausstehend (Stufe C).

No external reviewer was started by this worker. Root/orchestrator owns disposition and any review scheduling. Self-check confirmed the bounded status evidence, retained parser rows, release dependency exclusions and both size caps; it does not replace Root acceptance.

Rest

C8 remains unchanged under the brief's explicit source condition: docs/plan/v2.0/plan.md:3 says “Dieser Entwurf ändert nichts an docs/PLAN.md und nichts an v1.6.0” and conditions validity on G0; it does not itself state the requested single-release decision. Line 5 separately does say one v2.0 release with no v1.7–v1.9 intermediate releases. Root should reconcile that source reference before the requested roadmap relabeling. No user decision was inferred or altered.

Handover

Implemented, locally tested and pushed; PR remains Draft. Root acceptance, ready transition and merge remain outstanding. This handover completes the bounded worker delivery, not the parent release goal. No other files, dependencies or licenses were introduced.

Root-Abnahme (09.10.2026, head d48a228)

Check Result
Tier C (docs/PLAN.md only) — gates suffice, no external review required
Size +194/-104 = 298 ≤ 300
Evidence worker: gates.sh lane prepush exit 0 (2×), dev:plan-lint exit 0, secret-scan.sh exit 0, git diff --check exit 0
Scope brief srv-plan-sync-0910 A/B/C; C8 documented under "Rest"
Follow-up User decisions E1–E3 (09.10., after this brief: round 3 for #741/#737/#725, store exclusive to #737, V16-F3 fail-closed, release environment needs the user's approval) go into the next PLAN commit (ticket PLAN-SYNC), not into this PR — this PR is at the 300-line limit.

NICHT ABGEDECKT addendum: Windows lane comes from the merge queue.

Park cleanup work after v1.6 and bind the AGENTS slim contract after DR-12. Preserve completed evidence and record the tester dry-run decision.

No-Test: PLAN decisions and documentation contracts only

Co-Authored-By: Codex GPT-6.1-Sol <noreply@openai.com>
@mergify

mergify Bot commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

@Cuarroc Dieser PR hat einen Konflikt mit main und kann nicht in die Merge-Queue. Bitte main hineinmergen (kein Rebase, kein Force-Push) und den Konflikt loesen; das Label conflict verschwindet danach von selbst.

@mergify mergify Bot added the conflict label Oct 8, 2026
Cuarroc and others added 3 commits October 9, 2026 01:20
Resolve the real main conflict while preserving DR-07 port contracts. Record Root-approved DR-16 cuts and five bounded independent reserve contracts.

No-Test: documentation only

Co-Authored-By: Codex <codex@openai.com>
Name each regression test and preserve the fixed Z2 table schema.

No-Test: documentation only

Co-Authored-By: Codex <codex@openai.com>
No-Test: documentation only (PLAN status sync)
@mergify mergify Bot removed the conflict label Oct 8, 2026
No-Test: documentation only (PLAN status sync)
@Cuarroc
Cuarroc marked this pull request as ready for review October 9, 2026 00:01
@Cuarroc Cuarroc added the review-ok Pipeline: review disposition complete, no open high finding label Oct 9, 2026
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 9, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-09T00:10:25.056330Z d48a228 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d48a2286a9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/PLAN.md
| V16-KI30 | KI-30 Windows-Flake: Restursache nach V16-01 | Performance- und Benchmark-Spezialist | st exklusiv für #737 bis zum Tag v1.6.0 | Server | A | In Prüfung: Draft #737 | neuer Beleg (Queue-Lauf-ID) vor Fix; danach 10 Queue-Läufe ohne KI-30 | – |
| V16-03 | Tester-Kit: Installation, Rückmeldeformular, Grenzen | Implementierer · Codex | Inbox E16; kein Pflichtkonto | PC / erster externer Tester | C | Geplant: Konto entfällt laut Elias 08.10.; kein Release-Vorgänger | Trockenlauf in Windows Sandbox ODER beim ersten externen Tester; Sandbox-Aktivierung nicht freigegeben | – |
| V16-CHANGELOG | CHANGELOG v1.6.0 und Release-Notiz | Stabschef | DR-17 und die release-blockierenden Pakete aus V16-RELEASE (ohne diesen CHANGELOG selbst) | egal | C | Geplant | Eintrag `v1.6.0` über `v1.5.1` | – |
| V16-RELEASE | Tag v1.6.0 (Beta-Regel x.y.0) | Elias | Z1 (bis DR-17), V16-KI30, V16-ARCH-D5b, V16-UPD-CANCEL, V16-CHANGELOG sowie Nutzerentscheidung V16-F3 (V16-06 ja/nein) | PC | – | Geplant | Elias’ Entscheidung, danach Release-Pipeline grün | – |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the signing-key backup release gate

If the listed dependencies finish while E14 remains open, this authoritative release row allows v1.6.0 to appear ready even though docs/plan/v1.6.0/plan.md:219 explicitly names E14 as a prerequisite and the active inbox still warns that losing the only key copy would break update trust. Add Z4-E14/E14 to the release dependencies so the release cannot advance before the offline backup is confirmed.

AGENTS.md reference: AGENTS.md:L44-L49

Useful? React with 👍 / 👎.

Comment thread docs/PLAN.md
| DR-06a | P1-Server mit D2/H2; externen physischen State-Pfad und Root-ID fail-closed prüfen | bestehender qfytpd | DR-04c | eigener Worktree; Gates Server | A | Erledigt #676 (merged 2026-10-08T20:56:05Z) | kompilierendes Rot, eigene prepush/zwei Fremdreviews; `/api/state.rootAgentId` nur bei tatsächlichem Frontend-Leser, sonst D2-Meta-Tag erhalten | c044dc2b |
| DR-06b | P1-CLI verhaltensgleich nach Server übernehmen | bestehender Root-Serverjob, Claude Sonnet laut Root; qfytpd nur Fixrunde | DR-06a | Server | A | Erledigt #681 (merged 2026-10-08T21:42:27Z) | kompilierendes Rot, originale CLI-Verträge erhalten, eigene prepush/zwei Fremdreviews mit Disposition und Root-Abnahme | e4ad8296 |
| DR-07 | Tests: API, Patches, Fortschritt, freie Antwort, Fragen-Import; ergänzende P1-Ports getrennt | bestehende Denkraum-Lane qfytpd; Root dispatcht/nimmt ab | DR-06b/#681 gemergt `85ab286` | Server | C, Root kann B verlangen | Erledigt #731 (merged 2026-10-08T23:14:56Z) (07a); Erledigt #732 (merged 2026-10-08T23:14:31Z) (07b); 07c/d/e1/e2 separat | Testsuite grün im Gate; P1-Digest/Test-Mapping und D2-Delta; eigene volle prepush; keine Scratch-/Gesamt-Abnahme ableiten | 55ea21ce |
| DR-07c | P1-Sender-Tests portieren; HTTP-Verhalten gegen aktuellen Repo-Server belegen | bestehende Denkraum-Lane qfytpd nach Root-Zuweisung | #681 gemergt; Basis `85ab286`; unabhängig von 07d/e1/e2 | Server | C bei reinem Testport; Root kann B verlangen | In Prüfung: Ready #752 | nur sender.test.mjs; gemeldete 214 ALL/12 Tests; ≤ 300 tatsächlich; P1/D2-Mapping, Node/Suite/prepush grün, Root-Abnahme | 55ea21ce |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Make hygiene recognize the canonical review-status prefix

When npm run dev:hygiene reads this row, it drops it before extracting PR #752 because scripts/dev/hygiene.mjs:85 accepts Ready/Draft only at the start of the status cell, while this and the other newly synchronized open rows start with In Prüfung:. A direct inProgressPackages() read returns none of #752/#751/#755/#718/#740/#759/#750/#725/#738/#745/#728/#737, so a missing or closed candidate will not be reported; update hygiene to accept the canonical prefix (or retain a recognized leading marker) before relying on these statuses.

AGENTS.md reference: AGENTS.md:L53-L58

Useful? React with 👍 / 👎.

Comment thread docs/PLAN.md
Hypothesen stammen aus begrenztem Source-Nachlesen; Graphzugang war nicht angeboten.
| ID | Ziel | Owner | Hängt ab von | Ort | Stufe | Status | Abnahme | Ticket |
|---|---|---|---|---|---|---|---|---|
| Z2-STATUS-CI | main-Gates nicht durch jüngeren grünen CodeQL-Lauf verdecken; gemischte Workflow-Fixture; exklusiv scripts/dev/status-report.mjs + scripts/lib/dev-status-report.test.mjs | Root/Stabschef benennt einen vorhandenen Owner | main a8f0032; unabhängig | Codex Cloud Node 20 möglich; Server Node 24 | B | Startvertrag zur Root-Abnahme; kein Dispatch | benanntes Rot: ältere rote CI + jüngeres grünes CodeQL bleibt sichtbarer CI-Blocker; bestehende Zeit-/Zeilenlimitfälle erhalten | 77c993f3 |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a declared status for the reserve packages

All five new reserve rows use Startvertrag zur Root-Abnahme as their status, but the table contract at docs/PLAN.md:33-39 and goalStatus() in scripts/lib/hq-parse.mjs:299-316 accept only the eight declared status values. Consequently parseGoals() classifies every reserve package as invalid, so HQ cannot present whether the work is planned, ready, or blocked; prefix these cells with the intended declared value, such as Geplant:.

Useful? React with 👍 / 👎.

Comment thread docs/PLAN.md
| DOC-OPERATORS | Operatoren-Katalog und Briefvertrag in AGENTS.md und beiden projecta-workflow-Skills verankern | bestehender Root-Serverjob; kein zweiter Anweisungseditor | konkrete Disposition zu #642 erhalten | Server | C | Draft #683 `d47274a` geliefert; Root-Abnahme/Merge offen | nur Abschnitt vor Detailed operating reference und Skill-Dateiende; ≤ 300 ALL, eigene prepush, Regeln/Freigaben unverändert | 77c993f3 |
| Z2-AGENTS-SLIM | AGENTS.md auf etwa ≤ 8 KB reduzieren: Kernregeln, Befehle und Merge-Kurzregel erhalten, Referenzdetails per eindeutigem Pfad auslagern | ein von Stabschef Ausführung benannter Doku-Owner; Chief pflegt nur PLAN | DOC-OPERATORS/#683 integriert; #642-Anweisungs-/Archivdelta ausdrücklich disponiert; keine Dateikollision | Server | C | Vorgeschlagen, blockiert; kein Ready-Kandidat vor Vorgängern und genauem Schnitt | AGENTS.md plus vorhandene docs/setup/ oder WORKFLOW-Referenzziele; globale CLAUDE/MEMORY und Standard-Skills ausgenommen; Regel-für-Regel-Mapping, Linkcheck, dev:agent-check und eigene prepush Exit 0; ≤ 300 ALL, sonst vor Start serielle Schnitte; Byteziel ist kein Token-/Wirksamkeitsbeleg | 77c993f3 |
| DOC-OPERATORS | Operatoren-Katalog und Briefvertrag in AGENTS.md und beiden projecta-workflow-Skills verankern | bestehender Root-Serverjob; kein zweiter Anweisungseditor | konkrete Disposition zu #642 erhalten | Server | C | Erledigt #683 (merged 2026-10-08T15:42:28Z) | nur Abschnitt vor Detailed operating reference und Skill-Dateiende; ≤ 300 ALL, eigene prepush, Regeln/Freigaben unverändert | 77c993f3 |
| Z2-AGENTS-SLIM | AGENTS.md auf etwa ≤ 8 KB reduzieren: Kernregeln, Befehle und Merge-Kurzregel erhalten, Referenzdetails per eindeutigem Pfad auslagern | ein von Stabschef Ausführung benannter Doku-Owner; Chief pflegt nur PLAN | DR-12 gemergt/abgenommen; DOC-OPERATORS integriert; #642 geschlossen (Elias 08.10.); frischer Dateischnitt/Owner | Server | C | Bereit nach DR-12; Owner/Guard und Root-Zuweisung vor Ausführung | AGENTS.md plus eindeutige docs/development/AGENTS_REFERENCE.md; bestehende Referenzen nur lesen; globale CLAUDE/MEMORY und Standard-Skills ausgenommen; Regel-für-Regel-Mapping, Linkcheck, dev:agent-check und eigene prepush Exit 0; ≤ 300 ALL, sonst vor Start serielle Schnitte; Byteziel ist kein Token-/Wirksamkeitsbeleg | 77c993f3 |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep AGENTS-SLIM blocked until DR-12 is complete

At this candidate DR-12 is still Draft #740, yet this status begins with Bereit; the status contract defines Bereit as having all predecessors fulfilled, and HQ parses the suffix nach DR-12 away while counting the package as ready. This can advertise the instruction-file rewrite for dispatch before its explicit DR-12 merge/acceptance gate, so leave it Geplant or Blockiert until that prerequisite is actually complete.

Useful? React with 👍 / 👎.

Comment thread docs/PLAN.md
| V16-RELEASE | Tag v1.6.0 (Beta-Regel x.y.0) | Elias | Z1, Z3 | PC | – | Geplant | Elias’ Entscheidung, danach Release-Pipeline grün | – |
| V16-KI30 | KI-30 Windows-Flake: Restursache nach V16-01 | Performance- und Benchmark-Spezialist | st exklusiv für #737 bis zum Tag v1.6.0 | Server | A | In Prüfung: Draft #737 | neuer Beleg (Queue-Lauf-ID) vor Fix; danach 10 Queue-Läufe ohne KI-30 | – |
| V16-03 | Tester-Kit: Installation, Rückmeldeformular, Grenzen | Implementierer · Codex | Inbox E16; kein Pflichtkonto | PC / erster externer Tester | C | Geplant: Konto entfällt laut Elias 08.10.; kein Release-Vorgänger | Trockenlauf in Windows Sandbox ODER beim ersten externen Tester; Sandbox-Aktivierung nicht freigegeben | – |
| V16-CHANGELOG | CHANGELOG v1.6.0 und Release-Notiz | Stabschef | DR-17 und die release-blockierenden Pakete aus V16-RELEASE (ohne diesen CHANGELOG selbst) | egal | C | Geplant | Eintrag `v1.6.0` über `v1.5.1` | – |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove the release cycle from the changelog dependency

parseGoals() treats every known package ID mentioned in Hängt ab von as a dependency, so this wording makes V16-CHANGELOG depend on V16-RELEASE; line 271 simultaneously makes V16-RELEASE depend on V16-CHANGELOG. The generated goal graph therefore contains a direct cycle at the end of the release path. Spell out the actual blocking packages here without mentioning V16-RELEASE, or move that explanatory reference outside the dependency cell.

Useful? React with 👍 / 👎.

Comment thread docs/PLAN.md
Comment on lines +209 to +210
ist aus, keine Käufe. OpenRouter: nur vorhandenes Guthaben, keine Nachkäufe;
vor Nutzung muss Auto-Top-up aus sein und Elias den Schlüssel selbst im Vault

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Remove the OpenRouter routing authorization

If a coordinator follows this new routing paragraph, it may place review traffic on OpenRouter and ask Elias to provision an API key, but the repository's current reviewer policy explicitly permits subscriptions only and forbids both OpenRouter and API keys. Existing credit and disabled auto-top-up do not make that route allowed, so remove this authorization unless the governing rule is changed by the user first.

AGENTS.md reference: AGENTS.md:L126-L126

Useful? React with 👍 / 👎.

Comment thread docs/PLAN.md
Comment on lines +99 to +101
| DR-16a | Umschalt-Helfer + Drill-Tests; nur tools/denkraum/switch.mjs + switch.test.mjs, kein Restore | Root benennt einen vorhandenen Serverowner | DR-07 einschließlich 07c/d/e1/e2 (#752/#753/#751/#755), DR-14, DR-15 einschließlich 15b/#750 und UI-Verdrahtung #718 gemergt | Server | A, zwei Fremdanbieter | Geplant; kein Start aus PLAN-Pflege | ≤ 300 ALL; benannte DR16:-Tests rot→grün, node --test --test-name-pattern='^DR16:', npm run test:denkraum, eigene volle prepush, zwei Fremdvendor-Reviews am SHA/Disposition, Root-Abnahme | b0e90b72 |
| DR-16b | Live-Drill auf dem PC: Schreibpause, Sicherung, Umschalten, metadatensicherer Rückweg | Stabschef Ausführung, ein Owner | DR-16a gemergt sowie alle dessen Vorgänger; Root-Livefreigabe für exakten SHA und Zeitfenster | PC | A plus unabhängiges Nachlesen | Blockiert bis G0; keine Livefreigabe durch Dokumentannahme | Gates G0–G7 im gebundenen Vertragsentwurf Ticket b0e90b72; G5 beide UI-Skripte HTTP 200; protokollierter Drill und unabhängige Prüfung; P1/aktuelles Ledger nach Writes erhalten, Root-Abnahme | b0e90b72 |
| DR-17 | Öffentliche README, Anleitung in 5 Schritten, CHANGELOG-Abschnitt Denkraum | Technischer Autor | Entwurf ab DR-14; Trockenlauf nach DR-16a-Merge und Root-Annahme des DR-16b-Protokolls | Server | C | Geplant | Trockenlauf der 5 Schritte im PR-Text; beide UI-Skripte HTTP 200; eigene prepush; No-Test: documentation only | 55ea21ce |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Encode the split DR-16 prerequisites as exact package IDs

parseGoals() only recognizes complete known IDs with an identifier boundary, so the abbreviations 07c/d/e1/e2 and the compounds DR-16a-Merge/DR-16b-Protokolls are not dependencies. The generated graph currently gives DR-16a only DR-07/DR-14/DR-15 and gives DR-17 only DR-14, allowing the supplemental ports or the live DR-16b drill to disappear from the critical path. List each full package ID separately and write DR-16a gemergt / DR-16b-Protokoll with a real boundary.

Useful? React with 👍 / 👎.

Comment thread docs/PLAN.md
| ARCH-D7-WIN | P1/Z1: tatsächlichen nativen Receipt-Fehler getrennt diagnostizieren und kontrolliert rot belegen; verlässliche Queue-Integration für #632 | bestehender DR-15a-Owner; Chief disponiert, Root nimmt ab | CI 37746602240 / Windowsjob 113209450490; Store-Lane frei, schwere Läufe nach DR-09-WIN | vorhandener Windows-Ort | A | Entfallen: aufgegangen in V16-KI30 #737 / Z4-ARCH-11 | ≤ 300 ALL; Host-/SQLite-/Writer-Zeitpunkte kausal unterscheiden, deterministischer kompilierender Rotnachweis; tatsächliche Windows-Prüfung und eigene prepush am Fix-Head; zwei Fremdvendor-Reviews und Root vor Ready; keine pauschalen Zeitfenster-/Retry-Erhöhungen | c4d05a97, 782d9e58 |
| DR-10 | App-Teil Ideen + Werkbank auf Stand B1 | Root-Job `srv-dr-10-opus`; kein zweiter UI-Owner | DR-09/#638 gemergt; Verdrahtung in DR-11/#718 | Server | B | Erledigt #665 (merged 2026-10-08T19:59:10Z) | Ideen-Ablauf wie B1, Harness grün; eigene prepush, Fremdreview/Disposition und Root-Abnahme; Verdrahtung in DR-11/#718 | 08342807, 5945accc |
| DR-10-WIRE | UI-Verdrahtung von ideas.js und app.js in DR-11/#718 enthalten | DR-11-Owner; kein separater Start | DR-11/#718 | eigener Worktree | B | Entfallen (Root 09.10.): Verdrahtung bleibt in #718 (DR-11) | rote Verdrahtungsregression, beide Skripte HTTP 200; inspiziertes Laufzeitbild, eigene prepush/Fremdreview/Root-Abnahme; ≤ 300 ALL | 4e0b5b37 |
| HOTFIX-RF-PW | #741 red-first Playwright identity | Nutzer entscheidet nach zwei Review-Runden | –; Voraussetzung für DR-11 | Server | B | In Prüfung: Ready #741; Nutzerentscheidung nach zwei Review-Runden ausstehend | Entscheidung und gebundene Gate-/Reviewbelege vor DR-11-Integration | – |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reverse the HOTFIX-RF-PW dependency edge

Putting Voraussetzung für DR-11 in this package's Hängt ab von cell makes the parser record HOTFIX-RF-PW as depending on DR-11, while the DR-11 row correctly depends on HOTFIX-RF-PW. The active UI path therefore contains a two-node dependency cycle before either open PR can complete; leave this dependency cell empty and keep HOTFIX-RF-PW only as DR-11's predecessor.

Useful? React with 👍 / 👎.

@mergify
mergify Bot merged commit b302f2d into main Oct 9, 2026
17 checks passed
@mergify

mergify Bot commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 25 minutes 21 seconds in the queue, including 13 minutes 17 seconds running CI.

Required conditions to merge

@mergify
mergify Bot deleted the codex/plan-release-focus-20261009 branch October 9, 2026 00:33
@mergify mergify Bot removed the queued label Oct 9, 2026
mergify Bot added a commit that referenced this pull request Oct 9, 2026
docs: record E1-E3 decisions and synchronize PLAN after #749
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-ok Pipeline: review disposition complete, no open high finding

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant