Correct four prose sites that had gone false against the code - #146
Merged
Conversation
…them Found while updating the issue tracker after #145 merged. No behaviour changes. - namir-platform `thread_priority`: claimed the `min + 10` change was "not yet recorded in D-13.2". Changelog 0.36 recorded it. The decision's original text is deliberately left as written -- a decision is superseded by an appended note here, never silently rewritten -- so the comment now says to read the two together. - namir-clap `gui.rs`: claimed `set_size` had "no upstream ticket to track". It was filed as prokopyl/clack#101. Still no released version to move to. - §22 R-18: said "not mitigated today" while M14 had already taken the first of the three mitigations the row itself lists. Appended rather than edited, since "not mitigated" was true of M9b and the row is M9b's statement. The note also records what the change does *not* retire -- the ~161 ms parse still exists, only deferred -- and that deferring it created issue #96 in turn. - fr-ui-110-brand-mark.md: attributed its headless-window failure to GLX. The cause is sRGB (240 healthy GLXFBConfigs under Xvfb, sRGB flag clear on all). The observation is kept and the explanation corrected beneath it. Roadmap §21 Phase 6's "take the index off the instantiation path" bullet gains a dated done-note rather than being struck. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FHVuZbYNsdWUfemA2tLP5N
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
2 participants
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.
Found while updating the issue tracker after #145 merged. No behaviour changes.
namir-platform/src/thread_priority.rsmin + 10is "not yet recorded in D-13.2"namir-clap/src/gui.rsset_sizehas "no upstream ticket to track"docs/manual-tests/fr-ui-110-brand-mark.mdGLXFBConfigs under Xvfb, sRGB flag clear on every one (#143)Roadmap §21 Phase 6's "take the index off the instantiation path" bullet gains a dated done-note.
R-18, the Phase 6 bullet and D-13.2 are appended to, not rewritten. "Not mitigated" was true of M9b and that row is M9b's statement; D-13.2's original text still reads "at that policy's maximum priority". A decision is superseded by a note here, never silently edited.
R-18's note records what the change does not retire: the ~161 ms parse still exists, only off the instantiation path and guarded by
LIBRARY_INDEX_BUDGET— and deferring it is what created #96.Changelog row 0.37.
Verified:
fmt,clippy -p namir-platform -p namir-clap --all-targets -D warnings, all twelvextaskgates,cargo test -p namir-platform -p namir-clap -p xtask— including xtask's 314 tests, which parse the real FRS, roadmap and manual-test documents.🤖 Generated with Claude Code
https://claude.ai/code/session_01FHVuZbYNsdWUfemA2tLP5N
Generated by Claude Code