Public procfs documentation triggers the host-path privacy gate during issue sync #193

pm-review's scheduled sync uses pm-github 2026.10.23, resolved from reusable workflow d772360c1a099b968908f86026c1cb53c1a499f8. After repairing duplicate importer identities in that repository, its complete gated preview passes: 4 fetched/planned, 4 matched by provenance, 0 new, 0 skipped.

An isolated tracker copy using the published pm-github 2026.10.23 and PM host 2026.10.25 then refuses this apply before writes:

pm github import unbraind/pm-review --state all --atomic --gate --with-comments

The proposed issue #56 import produces three absolute-host-path findings, all from public Linux documentation:

Source: pm-review issue #56. Its stat example is the generic Linux procfs interface, with no account, host, concrete PID or local topology. This is distinct from the earlier duplicate-identity refusal documented in pm-review #57, and from closed issue #160's URL-path findings.

The host-path rule includes proc among sensitive roots. Its delimiter policy ends the match before <, so the generic example becomes a /proc/ finding. Redacted diagnostics correctly identify the match through its hash; the classification still blocks ordinary technical documentation.

A repository-only workaround using the supported allowlist, with exactly the two reviewed hashes above, permits the isolated apply: 0 imported, 4 updated; privacy PASS, 0 findings, 9 scanned files, 6 allowlisted occurrences. An identical repeat recovers the same transaction with 0 imported/updated, 4 recovered items and identical bytes for 62 item documents and 63 history streams. Strict health passes without warnings. No importer code was changed, no gate disabled, and no imported tracker data was published.

Expected: distinguish generic public procfs documentation from host-identifying paths, or explicitly document the conservative policy and offer a scoped way to review these references. Preserve refusal of personal paths, concrete process/account details and credentials. Regression coverage should include the bare procfs root, trailing slash, a generic PID placeholder, real sensitive-path patterns and mixed safe/unsafe content; a safe reference must never suppress another finding.

The repository-only workaround is reviewable in pm-review PR #60. Its immutable PM acceptance receipt records the isolated apply, repeat byte comparison, privacy/health results, and four direct shipped-scanner probes: generic root and prefix pass, concrete PID metadata and mixed safe/unsafe text still fail.