The JWT chain scanner only accepted a header at the start of a segment or
after `-`, so `session_<JWT>` reached the audit and cost logs unredacted.
Treat `_` as a prefix boundary too and cover it in the tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CLASSIFIER_NOTICE matched by prefix, so a pasted notice followed by a
user question was dropped from both summary paths. Anchor it to the
whole message so trailing user text is kept, and add a regression test.
Also pass ECC_SKIP_LLM_SUMMARY=1 in the withTranscript fixture helper so
an inherited ECC_LLM_SUMMARY_INTERVAL=1 cannot trigger claude -p.
Refs #3867
Assisted-by: Claude <noreply@anthropic.com>
Either package can own the top-level python3/python alias when Store Python is installed too, and the alias honours PYTHON_MANAGER_DEFAULT while the Python\bin shortcut always starts the runtime it was generated for. Swapping in the shortcut in either case could run a different interpreter. The Store check is a glob, so it starts no process.
Clear CLV2_NO_PROJECT and PYTHON_MANAGER_DEFAULT from the inherited
environment: with CLV2_NO_PROJECT=1 exported, detect-project.sh returned
before hashing and the project-hash test failed.
Add cases where the alias should be kept: Microsoft Store Python also
provides it, so either package may own it, and PYTHON_MANAGER_DEFAULT is
set, which the alias honours and the Python\bin shortcut does not.
Before 3.12 the parser rejects f"{d["k"]}" outright, so the shared sample
stopped at a parse error and the per-finding assertions failed on 3.11.
Samples that every supported Python parses now carry the per-finding
checks; the newer f-string forms run one per sample and accept either the
specific finding or the parse error.
Also flag unquoted X | Y annotations, which can fail at definition time
before 3.10, and check that a quoted union is not flagged.
In double quotes Bash drops a backslash-newline before it expands
anything, so a tail of `$\<newline>HOME` after the substitution's `)` is
`$HOME` and expands. The expansion check read the tail with the
continuation still in it and saw an escaped newline, so the hook
validated `fix: a$HOME` with no warning. Continuations are now dropped
first, while other escapes stay for the check: `\$\<newline>HOME` is
still the literal `$HOME`.