chore: remove unused patch file

docs/bun.md

@@ -37,10 +37,6 @@ To add a new patch that works in both pnpm + Bun:
 2. Add the patch file under `patches/`
 3. Run `pnpm install` (updates `pnpm-lock.yaml` patch hash)
 
-## Legacy patch files
-
-`patches/@mariozechner__pi-coding-agent@0.32.3.patch` is currently **unused** (not referenced from `package.json#pnpm.patchedDependencies`), so neither pnpm nor Bun will apply it.
-
 ## Bun lifecycle scripts (blocked by default)
 
 Bun may block dependency lifecycle scripts unless explicitly trusted (`bun pm untrusted` / `bun pm trust`).

patches/@mariozechner__pi-coding-agent@0.32.3.patch

@@ -1,17 +0,0 @@
-diff --git a/dist/config.js b/dist/config.js
-index 7caa66d2676933b102431ec8d92c571eb9d6d82c..77103b9d9573e56c26014c8c7c918e1f853afcdc 100644
---- a/dist/config.js
-+++ b/dist/config.js
-@@ -10,8 +10,11 @@ const __dirname = dirname(__filename);
- /**
-  * Detect if we're running as a Bun compiled binary.
-  * Bun binaries have import.meta.url containing "$bunfs", "~BUN", or "%7EBUN" (Bun's virtual filesystem path)
-+ * Some packaging workflows keep import.meta.url as a file:// path, so fall back to execPath next to package.json.
-  */
--export const isBunBinary = import.meta.url.includes("$bunfs") || import.meta.url.includes("~BUN") || import.meta.url.includes("%7EBUN");
-+const bunBinaryByUrl = import.meta.url.includes("$bunfs") || import.meta.url.includes("~BUN") || import.meta.url.includes("%7EBUN");
-+const bunBinaryByExecPath = existsSync(join(dirname(process.execPath), "package.json"));
-+export const isBunBinary = bunBinaryByUrl || bunBinaryByExecPath;
- // =============================================================================
- // Package Asset Paths (shipped with executable)
- // =============================================================================