docs: the hive has no approval queue

config-changes.md (was approvals.md) describes config PRs, the meta flake
and helper events; the approval queue, its kinds, the withdraw path, the
job-queue dispatch and ApprovalResolved go. Every other page drops the
approvals table, endpoints, event, tool group, hivectl verbs, dashboard
section and the loose-end/cancel kind, and links to the renamed page.

docs/integrations/forge.md

@@ -67,7 +67,7 @@ Two things live in the `agent-configs` Forgejo organization:
   allowlists are the `operators` team, and the agent can neither push
   `main` directly nor self-merge. An operator's merge in the Forgejo UI
   deploys the merged commit (see
-  [approvals.md § Config changes](../agent-lifecycle/approvals.md#config-changes)).
+  [config-changes.md § Config changes](../agent-lifecycle/config-changes.md#config-changes)).
   hive-c0re never force-pushes: the `push_config` mirror pushes the
   add-only status tags and `main` without force, and treats a refused
   `main` push as expected.
@@ -75,7 +75,7 @@ Two things live in the `agent-configs` Forgejo organization:
   agent's config. (Agents remain read-only collaborators on `core/meta`.)
   hive-c0re also references this repo as the agent's **persistent meta
   flake input** (`agent-<n>.url = git+http://<forge>/agent-configs/<n>.git`;
-  see [approvals.md § Meta flake](../agent-lifecycle/approvals.md)), fetching it as the `core`
+  see [config-changes.md § Meta flake](../agent-lifecycle/config-changes.md#meta-flake)), fetching it as the `core`
   user via a git credential helper that reads the live forge-core token —
   so the config lives on the forge, not a hand-synced local checkout.
 - The dashboard links each container's "config" anchor to this