feat(tools): add bounded URL evidence and contact redaction components

[seonghobae]

Current authority — 2026-09-11

• protected base: develop@042b0c70531b229af3acbd0421a2f23098d848b3
• generated predecessor: 4aaad40c0f482d775bb0b069c808e6c0d9f6d195
• ordinary retirement commit / exact head: 0275f130731856c1e88b46f7cee28c7778b345f1
• lifecycle: provenance-only / zero effective delta / valid intent fully owned by feat(tools): add auditable URL and contact hygiene #1418 and feat(tools): add bounded content checksum generator #1361 / safe to close as succeeded
• fresh compare: ahead 4 / behind 0 / 0 effective files.

This generated branch crossed two existing canonical product owners and therefore must not become a third implementation authority.

URL/contact hygiene succession

Canonical #1418 (feat/tools: add auditable URL and contact hygiene, exact a4a4da69ff9df89bac9d0a00e7473f35685be567) already owns the URL/contact bounded context, registry/API wiring, stable machine-readable errors, ADR/doctoring/operations evidence, and stronger fail-closed behavior.

The generated URL module here was materially weaker than #1418: it silently stopped after max_matches rather than failing closed on excessive matches, truncated overlong candidates instead of rejecting the raw candidate, used a smaller character-count input boundary rather than the owner's explicit UTF-8 byte budget, and did not carry the canonical hostname/IDNA/IP validation and registry contract. Its valid source-span/dedup/userinfo intent is already represented more completely by #1418.

The generated contact redactor also duplicated #1418 while weakening entity semantics: repeated occurrences of the same contact value received new sequential placeholders ([EMAIL_1], [EMAIL_2]) rather than the canonical class-scoped stable placeholder mapping, and it lacked the canonical stable tool-error/API/doctoring surface. Its supported-class warning and source/replacement-span intent are already represented by #1418.

Checksum succession

Canonical #1361 (feat/tools: add bounded content checksum generator, exact 165cfa91402e716401cd099d87404cde59d58003) owns the checksum surface. It enforces the 1 MiB UTF-8 ceiling, stable error codes, invalid-Unicode handling, modern allowlist, explicit authenticity warning, registry/API/auth/docs contracts, deterministic vectors, and chunked-equivalence evidence.

The generated backend/services/content_checksum.py had no one-MiB bound, exposed only raw ValueError/TypeError failures, and duplicated the same three approved algorithms without the canonical product boundary. Its valid checksum/chunked-equivalence intent is therefore fully succeeded by #1361.

Repair

Ordinary child 0275f130... preserves the generated branch history as first-parent provenance but points back to the exact protected develop tree. No force push, destructive rebase, source copy, owner merge, or gate weakening was used. Fresh compare against protected develop returns zero effective files.

#1247 remains open and is not claimed complete. Continue only through #1418 for URL/contact hygiene and #1361 for content checksum; registry ownership is not #1646, which is itself a zero-delta provenance lane over #1505.

Close this PR only as a fully succeeded duplicate/provenance lane; do not merge it independently.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Added the next isolated #1247 component in commit : \ supports only SHA-256, SHA3-256, and BLAKE2b-256, with explicit UTF-8 text handling, chunked/one-shot equivalence, and fail-closed rejection of MD5/SHA-1/unknown algorithms. Added . Combined focused verification: 21 passed under ; Ruff and \ clean. Registry/API integration and remaining #1247 acceptance criteria stay out of scope.

[seonghobae]

Correction to the preceding handoff note: commit 97455ad adds backend/services/content_checksum.py with SHA-256, SHA3-256, and BLAKE2b-256 only, explicit UTF-8 text handling, chunked/one-shot equivalence, and fail-closed rejection of MD5/SHA-1/unknown algorithms. Tests are in backend/tests/test_content_checksum.py. Combined focused verification: 21 passed under -W error::DeprecationWarning; Ruff and git diff --check clean. Registry/API integration and remaining #1247 acceptance criteria stay out of scope.

[seonghobae]

Commit 4aaad40 adds span-contract regressions for Unicode prefixes, source/replacement round trips, deterministic placeholders, and malformed overlapping phone/email-like candidates. Focused URL/redaction/checksum verification now passes 23 tests under -W error::DeprecationWarning; Ruff and git diff --check are clean. The redactor production contract was unchanged.