Repository navigation
docs: renumber duplicate KI-31, record W3-02j fix status - #476
Merged
Merged
Conversation
No-Test: documentation only Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Cuarroc
marked this pull request as ready for review
October 5, 2026 08:41
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Owner
Author
|
@Mergifyio queue |
12 tasks done
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
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Zwei Einträge in
KNOWN_ISSUES.mdtrugen die Nummer KI-31; der Eintrag zummain-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.mdonly, 2 lines, no code):git grep -nE "KI-3[2-9]"found none before).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 -Sshows 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 prepushat final HEAD9d69d7a: 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