docs: propose public repository standard and redisctl adoption record

[joshrotenberg]

Current checkpoint — accepted targets, October 6

Addresses #1181. Current pushed head: 60c739d0fb3c61f418175de52916957fd2ecb0fe.
Refreshed with main 2f139f15caa7dd93400a283e578c6b5641323586, the human-merged #1176 pilot. PR diff against main remains exactly four documentation/navigation files; no runtime, manifest, lockfile or workflow changes are proposed.

Josh accepted:

1. Required meaningful CI, independent agent review and Josh Rotenberg's merge decision.
2. GitHub private vulnerability reporting with a named human triage owner.

The documents now distinguish accepted targets from unadopted settings. The named security triage person, permanent standard owner/home, repository responsibility assignments and exact authorized settings adoption remain unresolved. Existing required GitHub human approval is unchanged; no bypass, invented owner, response promise or compliance claim.

Delivered

• Versioned candidate PUB-01–PUB-12 checklist with observable evidence, separate product profiles and adoption-record format.
• Historical redisctl source/settings assessment at 1453352a88017612fda48f2e54b286100a64bd88, clearly distinguished from later accepted-policy and migration updates.
• Exact intended/ruleset-required/advisory checks, explicit gaps, supported/advertised-versus-demonstrated distribution and pending adoption details.
• Migration record now verifies feat(mcp): add opt-in redis-mcp read-only database pilot #1176 merged at 19:08:45 UTC as 2f139f1: immutable public pin 8eff8240679d38157ee08b9d5e5eaeb656ce7550; opt-in/read-only, legacy default. Setup docs: audit and improve rustdoc documentation quality #128, lifecycle refactor: fix additional naming inconsistencies and typos in Cloud API #125, family/Cluster parity and registry/release packaging remain separate.

Leaves #628, #1088, #1087 and #1085 open. Their broader implementation is not absorbed. Unicode #1180 and release #1178 remain separate; no later CI-gate packet started.

Fresh validation at 60c739d

• Strict MkDocs: pass, 1.51s using the existing disposable repository-requirements venv.
• Focused Markdown lint of both candidate/adoption pages: pass with existing CI exclusions MD013/MD033/MD041.
• Formatting, diff checks and all-target/all-feature Clippy with warnings denied: pass before push (18.38s Clippy).
• Existing proc-macro-error2 future-compatibility warning remains; not a Clippy failure.
• Independent read-only editorial agent review of the entire four-file PR is complete at exact head 60c739d0fb3c61f418175de52916957fd2ecb0fe: no actionable findings. Reviewer corroborated historical source, current read-only settings, migration state and accepted-target/adoption separation; no edits/settings mutations or broad test reruns. This is independent agent evidence, not GitHub human approval.
• Final-head validation is complete: 15 successful checks, 7 expected skips, no failed/pending checks at 60c739d0fb3c61f418175de52916957fd2ecb0fe. CI completed successfully October 6 at 12:33:19 PDT: Quick Checks, all three unit jobs, hosted integration, Linux full all-feature workspace tests, Linux/macOS/Windows builds and CI Status. Documentation passed strict MkDocs, both strict rustdoc builds, advisory lint/link jobs and aggregate. Dist plan passed; skipped artifact/publication jobs and main-only coverage/deployment are not release evidence. Cargo-deny/audit are path-filtered and not triggered by this four-file docs-only PR; no checks/settings were changed or bypassed.
• Prior head ea987de had passing CI/docs/dist plan; those runs are historical, not validation of this new head. The unchanged landing page has 12 pre-existing MD060 lint diagnostics, previously verified against baseline; no additional rules are disabled or unrelated table cleanup added. Fresh link-path verification at this head passed: 15 relative paths and 14 distinct immutable source paths, none missing.

Visibility and boundaries

Dedicated empty kickoff 46d8a2c, push and this visible draft preceded edits. Existing scoped draft continues; no duplicate issue or PR.
Documentation only. The whole standard remains a candidate: two accepted targets are not organization-policy adoption. No settings/security/ruleset, credentials, merge, release, publication, default cutover or downstream-repository mutation.
This PR remains draft for policy/adoption discussion even when editorial review and documentation validation finish.

Timing and next

Initial preparation October 6 11:04–11:13 PDT; original estimate 45–75 minutes preparation +20–30 review, with CI separate. Accepted-policy follow-up started 12:16 PDT; pushed at 12:18 PDT. Review and new-head CI overlap; active/test/wait components are not separately instrumented. Idle interval between runs is not engineering time.
Independent editorial review and fresh local documentation validation are complete at the pushed head. No changes were requested. Hosted final-head validation is now reconciled too. The bounded documentation and independent editorial-review assignment is complete. Remaining next action is discuss named-owner/home/exact-settings adoption details without implementing or merging them; PR stays draft as assigned.

Final validation checkpoint reconciled October 6 at 13:06 PDT. No code changed, passing suites were not redundantly rerun, and the interval since the previous checkpoint is not reported as active preparation/review time.