An app page's Link header says which JSON manifest is the app's and which is its repository's on the forge #8288

On lab's production, / carries two rel="alternate"; type="application/json" links: </api/v1/here?path=%2F> (the app's own) and <https://forge.open-platform.sh/api/v1/here?path=%2Ftrevato%2Fforge>, which the proxy adds (discoveryLinks in src/apps/proxy.ts). Neither has a title, so an agent cannot tell which one describes what it can do with the app's repository.

Done when:

• [ ] The link the proxy adds carries title="this app's repository on its forge" (one constant, quoted and escaped as REPORT_LINK is)
• [ ] /llms.txt's line about rel="alternate" names that title, so an agent knows which link to follow
• [ ] A test proxies a public app that sends its own rel="alternate" link and proves both survive, with the forge's carrying the title. It fails without the change

Files: src/apps/proxy.ts, test/apps-discovery-links.test.ts Risk: none beyond the header. A private app still gets no links.