Redact instructions for making PRs, it was a dumb idea

AGENTS.md

@@ -43,21 +43,6 @@ Guidance for coding agents working in this repo.
 - For live game validation, follow `docs/SMOKETEST.md` and tear down Beat Saber
   processes afterward.
 
-## Pull Requests
-
-- When the user asks for a PR against an upstream plugin, compose and submit a
-  polite pull request using the user's existing `gh` session.
-- Keep upstream PRs small, focused, and easy for the maintainer to verify. Favor
-  narrow compatibility fixes, clear commit messages, and minimal formatting or
-  project-file churn.
-- Work from the upstream checkout under `~/src/<owner>/<repo>` when available.
-  If the upstream remote is not writable, create or reuse the user's fork with
-  `gh repo fork`, push a topic branch there, and open the PR against upstream.
-- Include concise verification notes in the PR body, especially the exact build
-  or smoke-test command and any generated artifact name. Mention local-only
-  build configuration separately if it was needed, and do not commit machine
-  paths or helper state unless the user explicitly asks for it.
-
 ## Launch Notes
 
 - BSManager may inherit Beat Saber launch arguments configured in Steam.