First-contact fixes from running v26.08.21.1 against project 2:
One-line CSS rules followed by a blank line hashed to sha1("") under the declarations-only fingerprint, so 68 unrelated one-liners read as one body-identical copy at the top of the derive readout. The selector line's tail after { is now part of the hash (issue #2877).
The proposer scanned only unjudged rows for uses edges, so already-classified consumers never got one; judged rows are now scanned once per body (no proposal made on them).
0084 migration docstring reworded (a line starting "function that …" parsed as a definition).
First-contact fixes from running v26.08.21.1 against project 2:
- One-line CSS rules followed by a blank line hashed to sha1("") under the declarations-only fingerprint, so 68 unrelated one-liners read as one body-identical copy at the top of the derive readout. The selector line's tail after `{` is now part of the hash (issue #2877).
- The proposer scanned only unjudged rows for `uses` edges, so already-classified consumers never got one; judged rows are now scanned once per body (no proposal made on them).
- 0084 migration docstring reworded (a line starting "function that …" parsed as a definition).
CI green on dev (run 4184).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
First deploy of v26.08.21.1 showed two gaps:
- Every one-line CSS rule followed by a blank line hashed to sha1("") — the
declarations live on the selector line, which the #2872 "declarations only"
fingerprint dropped — so 68 unrelated one-liners across 17 files read as
one body-identical copy at the top of the derive readout. The selector
line's tail after "{" is now part of the hash; an all-blank remainder falls
back to the whole block.
- The proposer only examined unjudged rows, so consumers that were already
classified (auth.create_invitation → hash_token) never got a uses edge: 3
edges for hash_token after the first refresh. Judged rows are now scanned
for references (once per body), no proposal is made on them.
- 0084 migration docstring reworded: "function that …" at a line start parsed
as a definition (extractor false positive).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
First-contact fixes from running v26.08.21.1 against project 2:
{is now part of the hash (issue #2877).usesedges, so already-classified consumers never got one; judged rows are now scanned once per body (no proposal made on them).CI green on dev (run 4184).
🤖 Generated with Claude Code
First deploy of v26.08.21.1 showed two gaps: - Every one-line CSS rule followed by a blank line hashed to sha1("") — the declarations live on the selector line, which the #2872 "declarations only" fingerprint dropped — so 68 unrelated one-liners across 17 files read as one body-identical copy at the top of the derive readout. The selector line's tail after "{" is now part of the hash; an all-blank remainder falls back to the whole block. - The proposer only examined unjudged rows, so consumers that were already classified (auth.create_invitation → hash_token) never got a uses edge: 3 edges for hash_token after the first refresh. Judged rows are now scanned for references (once per body), no proposal is made on them. - 0084 migration docstring reworded: "function that …" at a line start parsed as a definition (extractor false positive). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>