docs: remove production approval step from deploy docs

[onutc]

Summary

• remove the stale release-manager approval wording from ClawHub deploy docs
• clarify that the Production environment now only holds deploy secrets

Verification

• GitHub Production environment no longer has required reviewers
• git diff --check

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clawhub	Ready	Preview, Comment	Apr 3, 2026 7:26am

[greptile-apps]

Greptile Summary

This is a documentation-only PR that removes stale wording about a openclaw-release-managers approval gate from the production deploy documentation. All three changed files (AGENTS.md, CLAUDE.md, docs/deploy.md) now consistently reflect that the GitHub Production environment is used solely to hold deploy secrets (no human-approval requirement).

• AGENTS.md: Removed two lines referencing the openclaw-release-managers team approval gate and the associated warning to non-members. Updated the environment description to clarify it holds secrets only.
• CLAUDE.md: Updated the single line describing the Production environment to remove the approval-wait language.
• docs/deploy.md: Same documentation correction applied to the deploy notes section.

The changes are consistent with the project's CLAUDE.md rules (which already reflect the approval-free wording), and no code is modified.

Confidence Score: 5/5

This PR is safe to merge — it is a documentation-only change with no code modifications.

All three files receive straightforward wording updates that remove a stale approval-gate reference. The updated language is consistent with the project rules already captured in CLAUDE.md. No logic, configuration, or runtime behaviour is affected.

No files require special attention.

_{Reviews (1): Last reviewed commit: "docs: remove production approval step fr..." | Re-trigger Greptile}