docs: scope organization security claims to repository policy

[lukisch]

Summary

• Replace organization-wide network, telemetry, privilege, and process-management assurances with repository-scoped descriptions.
• Use neutral security-policy badges and correct Zombie-Killer-Tray wording, while separating the targeted 2026-10-03 readback from the wider activity snapshot.
• Preserve the organization response timeline, contacts, supported-version rows, repository counts, and partner index.

Validation

• python -m pytest -q -p no:cacheprovider: 12 passed
• git diff --check: passed

[github-actions]

Thanks for your first pull request! A maintainer will review it soon.
Please make sure you've read our Contributing Guide.

[lukisch]

Independently reviewed the full diff at dd73abe against fc3be3a. Repository-specific wording replaces blanket behavior assurances; canonical security-policy links are preserved. English/German parity, wider snapshot dates/counts, and organization response commitments/contact data remain intact. Existing local parity checks passed (12); the hosted welcome check passed and is not a documentation-test run. No source-runtime behavior or protection settings change.