check-issue-refs: catch full forge issue URLs too, drop internal links from docs entirely

docs/agent-lifecycle/agent-hierarchy.md

@@ -4,8 +4,7 @@ Every agent has a place in an operator-editable parent/child tree, used
 to scope which agents can manage which others. This doc covers how
 hive-c0re stores and edits the tree today, the rules that are meant to run on top
 of it once enforcement is finished, and where the manager still gets
-special-cased in the meantime. Tracking issue:
-`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/361`.
+special-cased in the meantime, as a tracked cleanup.
 
 ## Where the tree lives
 
@@ -235,10 +234,7 @@ uid 0 and have the setuid bit set."
 
 ## Cross-references
 
-- Milestone: "Agent privileges and sub-agents"
-  (`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/361`)
-- Dashboard render: "show agent topology in container list"
-  (`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/363`)
-- Audit table source: milestone comment
-  (`$HIVE_FORGE_URL/hyperhive/hyperhive/issues/361#issuecomment-3335`)
+- Milestone: "Agent privileges and sub-agents" (tracked internally)
+- Dashboard render: "show agent topology in container list" (tracked internally)
+- Audit table source: milestone comment (tracked internally)
 - Operator/agent trust boundary (orthogonal axis): [`boundary.md`](../trust-boundary/boundary.md)