Private-content scan: catch encoded home paths; redact 11 committed locations and re-pin their hashes - #697

…re, URLs included, aligned with #697's publication rule (Opus read P1, P2s)

GPT-6.1 Sol round sweep-superseded-g:
- the local rule and the generic rules run over URL tokens again;
- redacted-key collisions fail closed;
- the docs state that until #697 lands, the publication check detects no dash-encoded path.
486 tests OK (8 skips), including a run with #697's candidate pattern added.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

… claims, publication-safe refusals (round h)

- convert.py: every Users branch (bare -Users-, Windows drive and /mnt forms) matches in any case, as #697's rule
  does at 0d2a38b; -home- and the example exemption stay case-sensitive. Fixtures cover case variants in bare text,
  after projects/ and claude-<uid>/, in URLs, assignments, JSON keys and values (c5 P1).
- README and docstrings name #697 at 0d2a38b and state exactly which roots and contexts both rules cover (P2).
- Dots-only names are redacted; the example boundary matches #697's; the local rule consumes dotted and underscore
  name continuations; residues are checked before any artifact or summary is written (exit 3, nothing written);
  collision errors print index locators, never key text (P3a-e).
- A regression test runs the redactor's output through the actual encoded-home rule in scripts/validate.py; it
  fails until #697 is on the base (no skip), and passed 113,400 constructed cases with #697's validate.py overlaid.
GPT-6.1 Sol round sweep-superseded-h through the packaged SDK worker; the coordinator commits.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…f the exact emitted bytes

- convert.py: the private-name rule now ends on a name-start lookahead. It removes
  punctuation, Unicode and control-character tails in bare, anchored and URL contexts. The
  example controls, root-case rules and prose controls still pass through. Local name
  continuations consume Unicode word characters, dots and dashes.
- Before the output directory is created, artifacts and the summary are serialized with
  write_json's own serialization. The decoded documents and the exact emitted text are
  scanned, and the inspected UTF-8 bytes are what gets written. Serialized residue exits 3
  and publishes nothing.
- README and docstrings: the delimiter coverage is unrestricted (distinct from #697's
  terminator rule), projects/ and claude-<uid>/ use the same generic rule, and the scan is
  described as covering both decoded and serialized output.
- Tests: non-name tails in every context, serialized profile tails with a Unicode summary,
  refusal on serialized residue, and the CLI wiring of the selected checkout's
  PRIVATE_CONTENT.

Built by GPT-6.1 Sol through the packaged SDK worker (round sweep-superseded-i); committed by
the coordinator.

Co-Authored-By: Claude Opus 5.5 <[email protected]>