[Cuarroc]

Der Abschnitt „v1.5.0-beta“ im CHANGELOG ist jetzt auf dem Stand von heute, sodass R-1 nur noch das Datum eintragen muss. Neu aufgenommen sind Update-Wiederherstellung, Audit, Beweis-Tests, Fehlerkorrekturen, die Umgebungs-Stufe und die Drill-Seite. Die Zahl „Schema 25“ habe ich im Code nachgeprueft und sie stimmt; den Updater-Hinweis konnte ich nicht belegen und habe ihn unveraendert gelassen.

Report

What changed: CHANGELOG.md only (+31/-1): one bullet per theme for W3-02e..j (#411, #425, #446, #457, #462), audit (#408, #423), acceptance-matrix proofs (#412, #443, #440, #456, #453), claim/discovery refusals (#431, #448), FJ-1/FJ-3 (#465, #450), env stage W5-02b3 (#438, #442), drill runbook (#467). Only merged PRs; W3-02i/k not listed. Source line date bumped to 05.10.2026.

Verification:

• "Schema 25" is correct: MIGRATIONS at src-tauri/src/store.rs:872-906, highest entry (25, "trusted development test evidence source") at store.rs:905; target_schema_version() at store.rs:910-915 takes the maximum. No number change needed.
• Updater note: src-tauri/tauri.conf.json:53 holds the pubkey, unchanged since the initial public commit (git log). No doc or tag in the repo ties that key to v1.4.1, so the claim "same key v1.4.1 -> v1.5.0" is unverified and left as is.

Evidence: base origin/main f3e6c7f; bash scripts/ci/gates.sh lane prepush at HEAD d25988a: exit 0 (log outside repo). Diff: 1 file, +31/-1. Trailer: No-Test: documentation only.

NICHT ABGEDECKT: Windows half (#[cfg(windows)] tests, runs in the merge queue); Updater key continuity v1.4.1 -> v1.5.0 (needs the release signing key / published v1.4.1 pubkey); release content claims of the update PRs on a real PC (drills).

Review: pending (coordinator), tier C.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Cuarroc]

Orchestrator evidence for the open point "updater key continuity": the pubkey in src-tauri/tauri.conf.json at tag v1.4.1 of the archive repo (local clone, git show v1.4.1:src-tauri/tauri.conf.json) and at origin/main here hash identically (md5 of the pubkey line fe102042b977545532571ed52e5f5b49 in both). So an installed v1.4.1 verifies v1.5.0 updates with the same public key, provided the release is signed with the matching private key (W3-07, user's PC). Still not covered: a real signed update from v1.4.1 on the PC (updater drill).

[Cuarroc]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-10-05 08:10 UTC · Rule: default · triggered by @Cuarroc with the @mergifyio queue command
• ✅ Checks passed · on draft merge queue: checking #472 on main (f3e6c7f), stacked on #471 #474
• ✅ Merged — 2026-10-05 08:22 UTC · at dae3e0e6ae92dbb9da92d351e560fa072734a41e · merge

This pull request spent 11 minutes 56 seconds in the queue, including 11 minutes 38 seconds running CI.

Required conditions to merge

• check-success = gates (linux)
• check-success = gates (windows)
• check-success = red-first
• label != do-not-merge
  • docs(changelog): sync v1.5.0-beta draft with merged PRs #472