chore: promote dev → master (P2 comment cleanup)#98
Merged
Jaureguy760 merged 1 commit intomasterfrom Apr 19, 2026
Merged
Conversation
Delete 58 speculative / commented-out / debug-print / typo-laden comments across 15 files. Categories removed per Google Python Style Guide §3.8.1 (comments explain WHY, not WHAT): - "Should i…" / "Maybe X" / "How should i format" speculation (~30) - Debug print() statements preserved in comments (~6) - Commented-out alternative code paths (~9) - Stale TODO markers where the referenced work is already done (~6) - Informal "gotta" / "kinda" / typo-laden notes (~7) No functional / runtime behavior changes. Ten of the removed comments flagged genuinely unimplemented features; those are preserved in a private audit catalog for issue-tracker migration.
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.
Summary
Promote `dev` to `master`. Single new commit on dev since last master sync:
Master already has `d242c8a` (P1 — internal tooling refs + hardcoded path removal, merged directly earlier this session) that dev does not. This promotion therefore also brings that commit back into dev's lineage via the merge.
Files touched are disjoint — no conflicts expected.
Test plan