docs(process): clarify attribution, verification scope and completion audit

AGENTS.md

@@ -75,7 +75,10 @@ code, test results, commits, a passing review or a repository status.
 Use only the project's CLI for process reads and
 writes. If it lacks a needed read or transition, report the gap through the
 project's named channel. Never read credentials or private configuration,
-call its transport directly, or write process state by hand. Ordinary product
+call its transport directly, or write process state by hand. Do not change
+process records just to discover how a command works; use its documentation
+or help output. A `USER:` attribution carries only the human's verbatim answer;
+never compose, paraphrase or predict one. Ordinary product
 documents remain in their project repository and use its documented
 documentation workflow.
 

skills/rdd-completion-review/SKILL.md

@@ -8,7 +8,9 @@ description: Review implemented Epic work and present its exact approved proposa
 Read `PROCESS.md`, the Epic's approved plan and exact proposed content, the
 still-published requirements, ownership, implementation, traces and evidence.
 
-1. Inspect each approved requirement and its actual evidence. Run the owning
+1. Run `rdd-audit` on the Epic's requirements, traces and evidence and include
+   its findings in the completion presentation. Inspect each approved
+   requirement and its actual evidence. Run the owning
    checks with registration before execution and finalized evidence afterward;
    record outcomes and limits before obtaining the implementation review.
    Explicitly authorized deletion

skills/rdd-verify/SKILL.md

@@ -35,7 +35,9 @@ revision and the work remains within approved scope.
    owned requirements read-only, surface the change as a human decision and
    record new work separately for its own plan and human implementation
    approval. Continue unaffected implementation and verification within the
-   active approved scope.
+   active approved scope. Verification may add assertions within the approved
+   criteria. A change to product behavior is implementation work: route it
+   back to `rdd-build`.
 
 Finish evidence collection before independent implementation review. A rerun
 that changes reviewed evidence requires renewing that review.