diff --git a/docs/forge.md b/docs/forge.md
index 0aa0f90c..bf109010 100644
--- a/docs/forge.md
+++ b/docs/forge.md
@@ -53,7 +53,10 @@ Two things live in the `agent-configs` Forgejo organization:
 
 - A config repo per agent (`agent-configs/<name>`). The
   agent is a **write collaborator on its own** repo — it can push
-  config-change branches and (once config-PR support lands) open config PRs — but
+  config-change branches and open config PRs (Forgejo `pull_request`
+  webhook at `/webhook/config-pr` queues a `MergeConfigPr` approval;
+  `hive-c0re/src/forge/config_pr_poll.rs` re-scans every 5 minutes as a
+  fault-tolerance backstop) — but
   `main` is branch-protected core-only: only hive-c0re's verify-and-ff-push
   merge handler lands on `main`, an operator-team approval is required, and
   the agent can neither push `main` directly nor self-merge. `main` is
@@ -289,7 +292,7 @@ subject's `created_at`. Anything later is labeled `activity on <kind>`
 activity was without an extra reviews fetch. Missing/unparseable
 timestamps default to `new` (preserve prior behavior rather than mask a
 genuine new item). Timestamps are parsed by a small dependency-free
-RFC 3339 → epoch-seconds helper (`parse_rfc3339_secs`).
+RFC 3339 helper (`parse_rfc3339`).
 
 Number is extracted from `subject.html_url`'s last path segment
 (strips `#anchor` first); repo slug from `repository.full_name`.