Confusion RE: WebLN types

WebLN types is annoying just as a typings library. It needs to be manually installed in every project and manually a file needs to be added that references the imported definition. It should be converted to actual Typescript rather than just definitions. (AI got stuck on this before I added specific info in the skill) - I think we should release a new major version of this library that just has standard typescript code and exports.

The issue does not name files, tests, or an entry point. Start by locating the WebLN types package and reviewing its current installation, reference-file, and export setup; completion would be a major-version TypeScript package that can be installed and imported without those manual steps.

Written by the indexing model from the issue text.