[kevinten10]

Provider data minimization and public commit identity

• Replace Provider exception text with fixed public messages, preserving only legal portable codes. Normalize stored failure codes/messages before later resource and SDK reads.
• Withhold Provider exception details in conformance reports while retaining runner deadline evidence; reject endpoint userinfo credentials and avoid reflecting invalid Provider states.
• Add 49 synthetic Provider data-safety regressions and six commit-identity tests; retain intentional command output and file content.
• Add a value-withholding identity gate and public safety guidance; update SECURITY, protocol, testing, contribution guidance, changelog and documentation index.

Provenance and scope

Independently derived from this repository's public Provider/runtime contracts and data-minimization principles. All probes use Mock Providers, synthetic markers and temporary fixture identities. No private source, real secrets, company configuration or user data was used.

This changes the development source only. Existing release archives/tags are not modified. Legacy identity findings remain explicit follow-up work requiring a separate owner decision; the new range gate does not claim historical erasure.

Verification

• Earlier implementation check passed 202 tests and coverage on 2026-10-13. Argument-separator compatibility then passed its six focused identity tests.
• Current retry at a62fe6558bde8b348efbb2ecb85d07094e66a884: formatting/lint/types passed; 177 tests passed and 25 failed under severe local host contention with test, hook and child-process watchdog timeouts. The retry did not reach coverage/package/audit stages; full local acceptance is not asserted.
• Independent staging content scan: nine soft matches reviewed (dynamic synthetic variable, public pnpm version strings, reserved example/public noreply fixture identities). No blocking credential, company fingerprint, private-document or dangerous-file finding.
• Exact-head source/history scan and new author/committer range gate are verified separately before push. Only new commits after base 6e2744b55ced3bbfb0b7c714081204f22e3145e9 are covered by the identity range check.
• Required isolated Node.js 22/24 CI must pass before merge; merge author email will be explicitly set to the approved public noreply identity and inspected after merge.

Isolated CI acceptance

CI run 38507276724 completed successfully on exact head a62fe6558bde8b348efbb2ecb85d07094e66a884. Both required Node.js 22/24 checks passed. This provides the full acceptance environment; the documented local watchdog failures are not silently counted as passes. Legacy history and original release assets are unchanged.

[kevinten10]

Verified delivery: merged main e1fbe88 has the same tree as the checked candidate. PR and main Node.js 22/24 CI passed all 202 tests in ordinary and coverage runs, build, package and dependency gates. Candidate/main content scans and new author/committer identity checks passed. Independent staging soft matches were reviewed as synthetic/public fixtures. Original release tags and assets remain unchanged; v0.1.1 now warns that its archive does not include this source fix. Legacy identity remediation still requires a separate owner disposition; no history erasure is claimed.