docs: name the actor instead of the vague 'we'/'our'

Per mara's ruling on hyperhive#4041 (Microsoft.We): keep the rule enabled,
same treatment as the 'backend' rewrites. Traced all 21 genuine hits (4
gateway.md 'Let's Encrypt' hits are a substring-match false positive, left
alone) to their actual referent: some name a specific component already
established nearby in the same doc (forge_notify, hive-github-notify's
poller, hive-forge, hive-agent/the harness, colors.css, the dashboard),
others were pure filler that adds nothing once dropped.

docs/process/conventions.md

@@ -279,7 +279,7 @@ straight to `new Date(s)` for display.
 
 Every HTTP API in this repo answers failures with **RFC 9457
 `application/problem+json`** (`{ type, title, status, detail }`), with the
-human-readable cause in `detail`. An endpoint of ours returning a bare string
+human-readable cause in `detail`. An endpoint returning a bare string
 or a bespoke error shape is a **bug to file against the daemon that
 returned it**, not something for the caller to work around.
 

docs/process/gotchas.md

@@ -1,6 +1,6 @@
 # Gotchas
 
-NixOS + nspawn quirks and lessons we hit the hard way. If something
+NixOS + nspawn quirks and hard-won lessons. If something
 here looks unmotivated in the code, there's probably a story underneath.
 Grouped by area — jump to the section that matches what you're
 touching.
@@ -30,7 +30,7 @@ Not `boot.isContainer = true`. Renamed in nixos-25.11+.
 
 …in the `.conf`. The start script's `if HOST_ADDRESS set →
 --network-veth` branch then forces a private netns — silently fatal
-for our web UIs (the bind is invisible from the host). Every agent
+for the web UIs (the bind is invisible from the host). Every agent
 container runs isolated: `hive-priv`'s `write_nspawn_flags` writes
 `PRIVATE_NETWORK=1` plus a veth pair onto the host bridge, `HOST_ADDRESS`
 set to the bridge gateway IP (so `nixos-container`'s in-container init
@@ -204,7 +204,7 @@ the `TIME_WAIT` case from a clean previous exit; retry covers the
 genuine "previous process is still alive during a systemd restart
 overlap" case. REUSEADDR does **not** allow two simultaneous
 `LISTEN` sockets on the same port (that would be `SO_REUSEPORT`,
-which we don't use) — it preserves exclusivity.
+not used here) — it preserves exclusivity.
 
 ## Approvals
 
@@ -417,8 +417,8 @@ connects to the compositor at `127.0.0.1:<vnc_port>`.
   bind-address flag (unlike the `rdp-backend`'s `--address`), so the
   listener binds `0.0.0.0`. The harness relay only connects via
   `127.0.0.1`; the host firewall blocks the per-agent VNC port range
-  from external access. A future weston.ini `[vnc] address=` will
-  let us restrict the bind directly once upstream supports it.
+  from external access. A future weston.ini `[vnc] address=` would
+  restrict the bind directly, once upstream supports it.
 - **PAM service name**: literal `weston-remote-access` — that's the
   string libweston passes to `pam_start()` in `libweston/auth.c`.
   Using `weston` falls back to the system default PAM stack and