issues: enrich #46 (deferred) — cross-repo filing intent + gh -R precedent

diff --git a/.forge/issues/df02571d-47b7-4dab-9077-73ecb58da12e/issue.md b/.forge/issues/df02571d-47b7-4dab-9077-73ecb58da12e/issue.mdindex 40615f8..99d40c6 100644--- a/.forge/issues/df02571d-47b7-4dab-9077-73ecb58da12e/issue.md+++ b/.forge/issues/df02571d-47b7-4dab-9077-73ecb58da12e/issue.md@@ -7,7 +7,7 @@ labels:77 assignees: []88 milestone: null99 created: 2026-09-08T10:21:54.787248721Z10-updated: null10+updated: 2026-09-08T21:45:18.210985138Z1111 ---1212 STATUS: DEFERRED by owner 2026-09-08 — do NOT work until the owner1313 says go. Filed because the cost of forgetting exceeds the cost of@@ -39,3 +39,29 @@ CONSTRAINT (bitter lesson): never store derived state as truth; if3939 we "remember", it is a cache — scan is the source of truth.4040 4141 FIX LATER, only after the owner picks a fork.42+43+REFINEMENT after the triggering incident was dissected with the44+owner (2026-09-08):45+The agent reached for repo list with CROSS-REPO INTENT, not46+discovery-for-its-own-sake: it found a bug while working in wr1te47+and wanted to FILE IT ON THE F0RGE TRACKER using f0rge itself —48+issue create against another project's .forge. It gave up on the49+failed verb with no fallback (no whole-computer search), so the50+finding went to chat instead of the ledger. The loop that makes51+this valuable: bug found in project A that belongs to project B52+gets ROUTED into B's tracker the same session, by the agent that53+found it. Today the router is the owner; the forge could be.54+55+gh-literal precedent hardens the shape: gh repo list + gh issue56+create -R <owner/repo> are a PAIR — discovery feeding targeting.57+Our local version: f0rge repo list (scan paths) + --repo <path>58+on issue/pr verbs (target another repo's .forge). Same-owner59+multi-repo is simpler than federation: no trust layer, just60+discovery + targeting + write discipline (file + commit into the61+target repo's tree). Also: when the target is not found, the scan62+must say WHERE it looked (the give-up was a silent dead end — the63+same class as #37 parse hints).64+65+STILL DEFERRED. Owner deciding: scan vs remember; how --repo66+validates target state (uncommitted .forge? concurrent agents? —67+likely just document + refuse on dirty .forge).