Repository navigation
fix: recognize empty Clean descriptions in room menus (#2935) - #2938
Merged
Merged
Conversation
|
This was referenced Oct 7, 2026
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
1 participant
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.
Clean remains disabled when a room already has an exact empty task description. Existing legacy-description recognition and title/status/unknown-snapshot guards remain intact; whitespace remains cleanable in both room menus.
Closes #2935
Part of #2930, P01 of approved immutable plan v3. Only the three approved frontend files changed; no IPC or persistence changes.
Validation on HEAD 8ec20ee: 143/143 tests across context-menu/store suites; typecheck, frontend-dependencies, architecture arcs/cycles and diff checks passed. PRE/POST arcs and committed record byte-identical. Grinch independently reviewed full diff and evidence: PASS. Local Node26/npm11.19 differs from CI pins; remote exact-head checks remain required before merge. Visual interaction change validated by DOM matrices in both menus; no native GUI capture. No final build requested.
Step9.5: origin/main adf30ec is ancestor of the tested head; no incoming delta. Next phase P02 begins only after this PR merges and ancestry is verified.