-
Notifications
You must be signed in to change notification settings - Fork 12
feat: dead role sub-categories (Phase 4.1) #504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
1f44ed3
docs: align roadmap and backlog with architecture audit findings
carlos-alm 17a9db0
docs: remove dual-engine architectural note from Phase 6
carlos-alm 926b566
docs: add ADR-001 for dual-engine architecture decision
carlos-alm 8c0b3b0
fix: backfill typeMap via WASM when native binary lacks type-map support
carlos-alm 639d06c
docs: address review feedback on backlog/roadmap consistency (#503)
carlos-alm d888968
fix: use async fs.promises.readFile in typeMap backfill loop (#503)
carlos-alm 8f40966
fix: reconcile Phase 5.9 Kill List with Phase 6.6 metric scope (#503)
carlos-alm dd747f1
Merge remote-tracking branch 'origin/main' into docs/roadmap-audit-al…
carlos-alm 7802ab3
docs: fix missing strikethrough on completed/promoted backlog items
carlos-alm 3d841d5
docs: remove dead link to unpublished architecture audit file
carlos-alm 7945a05
Merge remote-tracking branch 'origin/main' into docs/roadmap-audit-al…
carlos-alm 9e23ea3
feat: sub-classify dead role into dead-leaf, dead-entry, dead-ffi, de…
carlos-alm 168cdce
docs: document dead-ffi vs dead-entry priority ordering
carlos-alm dec7b27
refactor: extract DEAD_ROLE_PREFIX constant to eliminate duplicated p…
carlos-alm ac87b8f
docs: fix stale JSDoc in roles.test.js (dead -> dead-unresolved)
carlos-alm 057b6ec
fix: use parameterized LIKE binding for DEAD_ROLE_PREFIX queries
carlos-alm 55bb468
fix: use DEAD_ROLE_PREFIX constant in module-map.js
carlos-alm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dead-ffipriority blindsdead-entryfor FFI files in entry-point pathsBecause the file-extension check (→
dead-ffi) runs before the path-pattern check (→dead-entry), a function in, say,src/cli/commands/analyze.rswill always be labelleddead-ffi— even though it lives in a CLI command directory. The existing priority tests coverdead-leaf > dead-ffianddead-leaf > dead-entry, but there is no test for thedead-ffivsdead-entrycase. This is presumably intentional (the FFI boundary is considered more fundamental than the path hint), but a comment noting the deliberate ordering would prevent future readers from accidentally swapping the two blocks.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 20881fa. Added a comment above the
dead-fficheck explaining the deliberate priority: FFI boundary is a more fundamental classification than path-based entry-point hints (e.g. a .so/.dll in a routes/ directory is still FFI, not an entry point).