Skip to content

docs(plan): refresh version subplans and STAND (PLAN-CLEAN-2) - #1592

Merged
mergify[bot] merged 1 commit into
mainfrom
codex/plan-clean-2
Oct 16, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
codex/plan-clean-2

Conversation

@Cuarroc

@Cuarroc Cuarroc commented Oct 15, 2026

Copy link
Copy Markdown
Owner

Die Unterpläne für v2.0 und v1.6.0 sowie STAND.md sind an den echten Stand angepasst.
Erledigte Pakete, historische Abschnitte, die abgeschlossene Schlüssel-Sicherung und die Release-Pause stehen jetzt korrekt drin.
Es ist reine Dokumentation; die vollständigen Prüfungen sind grün, offen bleibt nur die Übernahme.

Report

Plan-ID: PLAN-CLEAN-2

Operator: PFLEGEN (Root as offline-Chief deputy, Elias order 16.10.: finish PLAN and roadmap).

What changed — 44 validated corrections from the saved plan-audit synthesis (package 2 of 3, plan-clean-2.json), applied by exact old-text anchors:

  • docs/plan/v2.0/plan.md (+48/−31): stale PR states, historical sections marked, duplicate release IDs resolved (round-3 row renamed V2-REL-R3, "Ersetzt durch V2-REL in 10.1a").
  • docs/plan/v2.0/size-evidence.md (+2): note for the renamed duplicate.
  • docs/plan/v1.6.0/plan.md (+6/−4), STAND.md (+4/−2): merged packages, completed key backup (public wording, no private details), release pause.
  • Total 97 diff lines. Base origin/main @ c7a43fbd, head 7df892cb. Independent of PLAN-CLEAN-1 (docs(plan): apply validated PLAN-CLEAN-1 corrections #1591, different files), so based on main, not stacked.

Evidence

  • node --test scripts/lib/plan-model.test.mjs scripts/lib/dev-plan-lint.test.mjs → 23 pass, exit 0 (PC, 16.10. ~01:17).
  • bash scripts/ci/secret-scan.sh → exit 0 (server, before commit).
  • bash scripts/ci/gates.sh lane prepush in own server worktree root-plan-clean-2, CARGO_TARGET_DIR slot2, CARGO_BUILD_JOBS=1 → exit 0 (16.10. 01:27 MESZ, unpiped, exit code written to file).
  • Push verified with git ls-remote: refs/heads/codex/plan-clean-2 = 7df892cb30363ae62156bb911fa11c5a64ca1624.

NICHT ABGEDECKT (from the prepush run)

  • Linux run only: #[cfg(windows)] tests (run_in_pty, npm_shim, ConPTY, DPAPI) and Windows clippy arms are not covered; the Windows half comes from CI/merge queue.
  • Lane prepush is the fast loop: browser smoke, frontend build and workflow gates run in lane linux (CI).
  • External services (updater endpoint, OmniRoute, mirror) are not checked by any gate.
  • Root-relayed facts (key backup done 14.10., release pause) are recorded as "laut Root" without new observation.

Reviews — Tier C (docs only, no runtime effect): canonical gates suffice (AGENTS.md rule 5). No findings to dispose.

Open points — PLAN-CLEAN-3 (historical sections of docs/PLAN.md) follows stacked on PLAN-CLEAN-1; parser fixes are PLAN-AUTO-1b.

🤖 Generated with Claude Code

Apply 44 validated documentation corrections from the completed plan audit.
Record merged packages, historical scope, the completed key backup, and the release pause.

No-Test: documentation-only plan and status corrections; validated by canonical gates

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 15, 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-15T23:44:54.707730Z 7df892c PR opened
ℹ️ 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: 7df892cb30

ℹ️ 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 STAND.md
Comment on lines +30 to +31
Bis v2.0 kein Patch-Release und kein Tag (Entscheid 15.10., laut Root;
Inbox RELEASE-PAUSE in `docs/PLAN.md`); v2.0 braucht ein neues Ja.

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 Add the claimed decisions to the canonical plan

At this head, docs/PLAN.md contains no RELEASE-PAUSE entry, while its current rows at lines 329 and 755 still say the E14 backup is unperformed even though this change declares it complete. This leaves the canonical plan assigning an already-completed task to the user and makes this new STAND reference point to a nonexistent inbox card; update docs/PLAN.md in the same change before publishing these claims.

AGENTS.md reference: AGENTS.md:L121-L121

Useful? React with 👍 / 👎.

Comment thread docs/plan/v2.0/plan.md
| V2-ACC1 | Gesamtabnahme: alle gemergten Bildschirme (10 Bildschirme und ihre Tabs, Schalter an) × 2 Themen (nur Deutsch), Tabulator, Kontrast, Datenquellen-Test, Gate gegen zweite Zustandsdefinition | fe + ci | – | B | M | alle V2-S | terra | Kriterien 1 bis 6, 15 und 16 mit Befehlen im PR |
| V2-RULE1 | AGENTS.md: neue Größenregel (nur nach Freigabe von Frage 4b) und, nur nach Freigabe von Frage 4d, Regel 6 (parallele Pakete unter `store/`) | doc | – | C | S | Fragen 4b, 4d | Koordinator | D |
| V2-REL | Release v2.0: Update-Drill, Signatur, Tag, Veröffentlichung | N | – | – | – | V2-ACC1, E3, E14 (offen in `docs/PLAN.md`) | Nutzer | Kriterium 11 |
| V2-REL-R3 | Release v2.0 (Fassung Runde 3): Update-Drill, Signatur, Tag, Veröffentlichung. **Ersetzt durch V2-REL in 10.1a (15.10., enger Schnitt)** | N | – | – | – | V2-ACC1, E3, E14 (damals offen in `docs/PLAN.md`; E3 erledigt 09.10., E14 erledigt 14.10.) | Nutzer | Kriterium 11 |

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 Exclude the renamed release row from package counts

After this rename, the counter embedded in size-evidence.md treats V2-REL-R3 as one package because it only zeroes V2-REL and V2-N1; since mapping.md still maps an adopted V2-REL, that old ID is then counted a second time as well. Running the documented counter on this head therefore adds two fictitious packages relative to the prior naming, so update the exclusion/mapping logic and any affected totals rather than only adding the explanatory note.

Useful? React with 👍 / 👎.

Comment thread docs/plan/v1.6.0/plan.md
# Plan v1.6.0 (Entwurf, der Nutzer entscheidet)
# Plan v1.6.0 (historisch; v1.6.0 veröffentlicht 09.10.2026)

**Status 15.10.2026: abgeschlossen.** v1.6.0 am 09.10. veröffentlicht (Tag `d2582ceb`), Patches bis v1.6.6. Offene Reste stehen in `docs/PLAN.md` (V16-FU-2, V16-NACHBEOB, V16-03, Z4-R19-*); die Tabellen unten sind der ursprüngliche Entwurf vom 05.10.

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 Point the follow-up banner at the existing V16-FU row

A repository-wide search at this head finds no V16-FU-2 identifier, while the canonical follow-up row is V16-FU at docs/PLAN.md:312. Because the new completion banner tells coordinators that open work can be found under these IDs, this typo sends them to a nonexistent package and can hide the listed release follow-ups; reference V16-FU or add the intended canonical row.

AGENTS.md reference: AGENTS.md:L61-L63

Useful? React with 👍 / 👎.

Comment thread docs/plan/v2.0/plan.md
| DS-25 | Klassik-Ablösung je Ansicht zuordnen | DS-13…DS-23; bestehende KR-Wellen in 10.2 | geplant |
| DS-KONTRAST-FU | Kontrast-Nachläufer aus DS-POLISH (laut Root 15.10.; Herkunft: Unbekannt (zu prüfen); vor Dispatch mit DS-24 abgleichen) | DS-07 | geplant: nicht disponiert (15.10.) |

Parallelauftrag **FABRIK-TAB-1**: Fabrik-Tab im Leitstand; Abhängigkeit im Wellenplan: keine; erledigt: #1568 (merged 2026-10-15T16:19:08Z, `90d1a8c9`), Zeile in der Tabelle oben; Review-Lows in FU-1015 (`docs/PLAN.md`); DS-19 vor Dispatch dagegen abgleichen.

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 Add the referenced FU-1015 follow-up to the plan

At this head, a repository-wide search for FU-1015 finds only this newly added sentence; docs/PLAN.md contains no corresponding row. The text therefore claims that the review lows from FABRIK-TAB-1 are tracked when there is no discoverable owner, status, or acceptance record, so add the promised canonical follow-up or point this reference at the actual existing ticket.

AGENTS.md reference: AGENTS.md:L121-L121

Useful? React with 👍 / 👎.

Comment thread docs/plan/v2.0/plan.md
|---|---|---|---|---|---|---|---|---|
| V2-D1-ON | **Stand 15.10.: #1484 gemergt.** D1 standardmäßig an, ausdrückliches Aus gespeichert; der damalige Rückweg-Vertrag ist durch Classic-out überholt | `src/flags/featureFlags.ts`, Flag-/Shell-/App-Tests | nein | B | M | – | `gh pr view 1484 --json state`: MERGED; Implementierungsbelege im PR | Agent |
| V2-SCOPE-1 | **Stand 15.10.: #1499 offen (Draft), Basis jetzt `main`; Fixrunde läuft laut Root-Auftrag.** Beschlossen: Seitenleiste und Palette zeigen Leitstand und Einstellungen; Ersteinrichtung bleibt über `/start` erreichbar. Die übrigen Bereiche (v2.1 und später) bleiben hinter dem Schalter. Beleg der Lücke: `Shell.tsx:25` filtert nur nach `icon`, `CommandPalette.tsx:14` listet alle `ROUTES`, kein `FeatureGate` unter `src/shell` oder `src/screens`; `/steuerung`, `/start`, `/beweise` sind unter D1 gemountet (`routing.ts`) | `src/shell/Shell.tsx`, `src/shell/routes.ts`, `src/shell/header/CommandPalette.tsx`, `src/flags/featureFlags.ts` (neuer Schalter), Tests | nein | B | M | V2-D1-ON (#1484) | roter Test: bei D1 an und Schalter „weitere Bereiche“ aus fehlen die Einträge und `resolveRoute` landet auf `/leitstand`; `npx vitest run src/shell` Exit 0 | Agent |
| V2-SCOPE-1 | **Stand 15.10.: #1499 gemergt (2026-10-15T15:55:14Z, `d1616352`).** Beschlossen: Seitenleiste und Palette zeigen Leitstand und Einstellungen; Ersteinrichtung bleibt über `/start` erreichbar. Die übrigen Bereiche (v2.1 und später) bleiben hinter dem Schalter. Beleg der Lücke: `Shell.tsx:25` filtert nur nach `icon`, `CommandPalette.tsx:14` listet alle `ROUTES`, kein `FeatureGate` unter `src/shell` oder `src/screens`; `/steuerung`, `/start`, `/beweise` sind unter D1 gemountet (`routing.ts`) | `src/shell/Shell.tsx`, `src/shell/routes.ts`, `src/shell/header/CommandPalette.tsx`, `src/flags/featureFlags.ts` (neuer Schalter), Tests | nein | B | M | V2-D1-ON (#1484) | roter Test: bei D1 an und Schalter „weitere Bereiche“ aus fehlen die Einträge und `resolveRoute` landet auf `/leitstand`; `npx vitest run src/shell` Exit 0 | Agent |

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 resolved V2-SCOPE-1 gap from the criteria

This update marks #1499 as merged, but the same row still describes the pre-merge implementation as current (Shell.tsx filtering only by icon, no feature flag), and criterion 1 at line 759 still labels that exact behavior an “Offene Lücke.” The merged code now uses visibleRoutes() and the weitere_bereiche flag, so the plan simultaneously presents V2-SCOPE-1 as completed and still missing; update the criterion and row description to the post-merge state.

AGENTS.md reference: AGENTS.md:L121-L121

Useful? React with 👍 / 👎.

@Cuarroc Cuarroc added the review-ok Pipeline: review disposition complete, no open high finding label Oct 15, 2026
@Cuarroc

Cuarroc commented Oct 15, 2026

Copy link
Copy Markdown
Owner Author

Root acceptance (Tier C: docs/plan/** + STAND.md only, gates suffice per AGENTS.md rule 5). review-ok bound to head 7df892c; all checks green at 2026-10-16 ~01:57 MESZ. Any later push voids this. The PLAN-CLEAN-2 row status is updated in a later plan sync (self-reference, plan-clean-context duty 8).

@Mergifyio queue

@mergify mergify Bot added the queued label Oct 15, 2026
@mergify mergify Bot mentioned this pull request Oct 15, 2026
30 of 46 tasks
@mergify
mergify Bot merged commit a3b6106 into main Oct 16, 2026
18 checks passed
@mergify

mergify Bot commented Oct 16, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

  • ✅ Entered queue — 2026-10-15 23:53 UTC · Rule: default · triggered by merge protections
  • ✅ Checks passed · on draft merge queue: checking #1592 on main (23d0c91) #1595
  • ✅ Merged — 2026-10-16 00:04 UTC · at a3b6106666b9f2732cdbc4dc0f8d02e1002a13a3 · merge

This pull request spent 10 minutes 23 seconds in the queue, including 9 minutes 40 seconds running CI.

Required conditions to merge
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (linux)
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (windows)
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/red-first
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections

@mergify
mergify Bot deleted the codex/plan-clean-2 branch October 16, 2026 00:04
@mergify mergify Bot removed the queued label Oct 16, 2026
Cuarroc added a commit that referenced this pull request Oct 16, 2026
PLAN-CLEAN-1 -> Erledigt #1591, PLAN-CLEAN-2 -> Erledigt #1592 (both
verified merged via gh), PLAN-CLEAN-3 -> In Pruefung #1596.

No-Test: plan status cells only, checked with npm run plan:check

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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