Skip to content

docs: renumber duplicate KI-31, record W3-02j fix status - #476

Merged
mergify[bot] merged 1 commit into
mainfrom
claude/ki31-renumber
Oct 5, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
claude/ki31-renumber

Conversation

@Cuarroc

@Cuarroc Cuarroc commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Zwei Einträge in KNOWN_ISSUES.md trugen die Nummer KI-31; der Eintrag zum main-red-guard-Fehlalarm heißt jetzt KI-32. Der Update-Eintrag (KI-31) ist für den Journal-Pfad als behoben durch PR #462 markiert. Offen bleibt ein echter Lauf „Update installieren und neu starten“ auf dem Windows-PC.

Report

What changed (KNOWN_ISSUES.md only, 2 lines, no code):

  • Resolved-table entry "main-red-guard red although both lanes were green" (run 37156370787): KI-31 -> KI-32 (next free number; git grep -nE "KI-3[2-9]" found none before).
  • Update entry KI-31: severity and fixed-by column updated: fixed by W3-02j / PR fix(update): accept post-update handshake on identity, record digests #462 (trust-on-first-run handshake) for updates installed through the journal path. Still open: a real install-and-restart run on the PC, and updates not installed through the journal path (workaround stays for those).

git grep -n "KI-31" hits (before): KNOWN_ISSUES.md:48 = update entry, kept as KI-31; KNOWN_ISSUES.md:57 = main-red-guard entry, renumbered KI-32. No other hit in the tree (docs, PLAN, STAND, .pa). Immutable references outside the tree: commit message/PR #258 use "KI-31" for main-red-guard; PR #463 uses it for the update entry.

Discrepancy with the task premise: git log -S shows the main-red-guard KI-31 is the older one (ab49ea4, PR #258, 2026-10-04); the update entry came later (8e54129, PR #463, 2026-10-05). I followed the explicit instruction (keep KI-31 for the update entry, an open, actively referenced item); the historic PR #258 text therefore points at the old number. Swapping is a two-line change if the coordinator prefers.

Evidence: base origin/main dae3e0e (predecessor PR #472 merged; #462 merged). bash scripts/ci/gates.sh lane prepush at final HEAD 9d69d7a: exit 0 (log: /tmp/ki31-prepush.log on the server). Diff: 2 lines changed. Trailer: No-Test: documentation only.

NICHT ABGEDECKT: #[cfg(windows)] tests / Windows clippy arms (Windows lane runs in the merge queue); a real update install-and-restart on the PC; no gate checks the KI numbering itself.

Review: pending (coordinator), Tier C.

🤖 Generated with Claude Code

No-Test: documentation only

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@Cuarroc
Cuarroc marked this pull request as ready for review October 5, 2026 08:41
@chatgpt-codex-connector

Copy link
Copy Markdown

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

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

Cuarroc commented Oct 5, 2026

Copy link
Copy Markdown
Owner Author

@Mergifyio queue

@mergify mergify Bot added the queued label Oct 5, 2026
@mergify mergify Bot mentioned this pull request Oct 5, 2026
12 tasks done
@mergify
mergify Bot merged commit 566d2bb into main Oct 5, 2026
15 checks passed
@mergify
mergify Bot deleted the claude/ki31-renumber branch October 5, 2026 08:58
@mergify

mergify Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 14 minutes 13 seconds in the queue, including 13 minutes 56 seconds running CI.

Required conditions to merge

@mergify mergify Bot removed the queued label Oct 5, 2026
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