Repository navigation
Document and apply tokenwar scan recommendations - #18
Merged
Merged
Conversation
ousamabenyounes
force-pushed
the
docs/update-scan-readme
branch
from
August 31, 2026 18:25
e9be841 to
cb00d68
Compare
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
tokenwar scanusage, supported clients, local log roots, env overrides, and decision labelstokenwar scan --apply, a guarded activation flow for directENABLErecommendationscaveman,claude-mem, andponytail; it does not install new tools, edit RTK hooks, remove pxpipe, or choose third-party code-context toolsTest verification (RED -> GREEN)
RED with the new
--applytests before implementation:GREEN on this branch:
Additional validation: