docs(governance): PR template + two-approver human gate for access work [#345]

Founder ruling 2026-09-02: physical server-room access 100% human
required — logged, approved, signed off. Branch protection lands
immediately after this commit. Also excludes .gitea/ from the
doc-pointer scan (framework dir, not docs).

https://projects.knownelement.com/issues/345

AGENTS.md

@@ -26,6 +26,20 @@ House rules layering: `~/.zcode/AGENTS.md` (global) < PFVCluster
   [tests/remote.sh](https://git.knownelement.com/KNEL/PFVCluster/src/branch/main/tests/remote.sh).
 - DNS names only — never IP literals.
 
+## PR process (founder ruling 2026-09-02) — physical access is 100% human-gated
+
+- `main` is BRANCH-PROTECTED: no direct pushes, by anyone. All changes
+  land via PR with the sign-off template (`.gitea/pull_request_template.md`).
+- **Two human approvals required to merge.** Gitea enforces the count.
+  Agents may author and push PR branches and implement review feedback —
+  agents NEVER approve, NEVER merge, NEVER bypass (`--no-verify` is not
+  a bypass for the approval count).
+- Access-control changes (badge roster, unlock policy, door-adjacent
+  code) additionally require the template's checklist and a
+  founder-approved ticket.
+- Full audit chain per change: Redmine ticket → PR description → two
+  named human approvals → merge → deployment note (#356).
+
 ## Scope boundary: Home Assistant
 
 The HA side (webhook receiver, whitelist, automations, alerts) is owned by