Dev: gmind Accounts NodeLink cannot mount

Found by the Task 7281 acceptance run on dev (app.dev.jaah.ai). The gmind org's "Accounts" NodeLink (EFS fs-0cb491ee4553ae69f, access point fsap-08514ba2314df3092, root /accounts) is Not mounted on every node it is attached to. Node › NodeLinks says on gmind-m8i-1-host: `Failed to resolve "fs-0cb491ee4553ae69f.efs.us-east-1.amazonaws.com" - ... ensure that the VPC has an EFS mount target`. ts2-node6 reports the same. The Storage tab shows Mount target IP "—" and Policy "Outdated — No mount-target condition". So gmind's signed-in accounts (cod1 Codex, gem1 Gemini, agy1 Antigravity, acct2 Claude) are unreachable. Codex, Gemini and Antigravity tasks wait with "no … API/subscription available". Make the gmind Accounts NodeLink mount on dev's out-of-VPC nodes (pool-c-host co-located nodes, gmind-m8i-1-host). Set the mount target IP and the network path per docs/policies/nodelink.md § The out-of-VPC node, and repair the policy, through the console. Out of scope: product code changes unless the console cannot express the fix (then name the gap); other orgs' NodeLinks. Done means: - Node › NodeLinks on ts2-node6 (now a gmind node) shows Accounts "Mounted". - A gmind task bound to codex dispatches onto cod1 with no "no subscription available" wait.

Diagnosed, not fixed: the gmind EFS is in the legacy account and its VPC (10.60/16) collides with dev's, so no mount-target route can work. Fix: Jaah-managed storage. 7469 supersedes this task and was already acting; I handed it the diagnosis. Filed draft 7470.