ci: validate initial PR readiness declarations (#3302)

AGENTS.md

@@ -94,7 +94,7 @@ required to open an issue.
 Follow [human ownership and readiness](CONTRIBUTING.md#pull-request-ownership-and-readiness)
 when preparing a PR. AI-assisted contributions are welcome; a human must review
 and own the final diff, check the validation evidence and its limitations, and
-explicitly declare the current revision ready for maintainer review.
+explicitly declare the PR ready for initial maintainer review.
 
 Keep the PR body concise and current, with the concrete problem, observable
 outcome, approach, and evidence. Report only checks that actually ran as executed;
@@ -103,11 +103,11 @@ Address actionable automated review findings and explain disagreements.
 
 Leave the template's **Author readiness** declarations unchecked for the human
 owner to complete. Never attest to human review on their behalf. Keep the PR in
-draft until the human declares the current diff ready. After further changes,
-clear the ready-for-review checkbox and refresh affected evidence so the human
-can review and renew the declaration. CI and automated review results support
-review; they do not establish human readiness, maintainer scope approval, or
-merge permission.
+draft until the human declares the PR initially ready. Later pushes do not
+invalidate that declaration or require another human sign-off. Keep the PR body
+and affected validation current as work changes. The readiness check validates
+the filled declaration; CI and automated review results do not establish that
+human review occurred, maintainer scope approval, or merge permission.
 
 <!-- BEGIN:turborepo-agent-rules -->