task: add portable privacy and security rules #33

Goal and acceptance

Add portable privacy and security rules so agents and contributors do not put real private addresses, IPs, hostnames, usernames, personal paths or authentication material into shared code, documentation, logs, evidence or PR text.

Completion criteria:

• The agent entry contract links to explicit privacy/security requirements.
• A focused contributor document covers placeholders, runtime configuration, secret handling, redaction, safe external inputs and pre-publication checks.
• Public source attribution and required DCO identity remain possible; redaction must not fabricate or weaken evidence verdicts.
• The documentation-only PR records checks, limits and revision-scoped independent review.

Scope and constraints

In scope: AGENTS.md, a dedicated privacy/security guide and a contributor-guide link.
Out of scope: a repository-wide historical cleanup, history rewriting, secret-scanning automation, CI changes, runtime changes, merge, release or production activation.

Ownership and authorization

• Actual requester / goal-acceptance owner: the human user in the current Codex chat.
• Accepted scoped delegation: the user requested privacy/security rules prohibiting concrete addresses/IPs and usernames/passwords, then explicitly requested a PR to this repository to refresh those rules.
• Status: accepted for this documentation slice by that direct user instruction; this record does not grant merge or Issue-closure authority.
• Accountable parent / implementer: Codex acting through the authenticated contributor account.

Inputs and deliverables

Follow the current main branch agent contract, contribution guide and issue-led collaboration conventions. Deliver one focused PR with documentation, actual check results and independent review findings.

Completion and closure

The human requester retains goal acceptance and closure. Use a non-closing PR reference; leave this Issue open pending acceptance.