launch-threadlisted

Turn a project's README and its first release into a full launch thread — the one-shot public moment that says *this exists, and here's why it matters.* **You (the agent) write every part** from what the repo actually is; capx never generates content — it only ships each part, guarded by casserole at send. A launch amplifies, so the bar for being *true* is higher here than anywhere. User's extra intent, if any: "$ARGUMENTS" Follow these steps: 1. **Connect and confirm who's launching.** Run `whoami`. If no account is connected, stop and point the user at the **connect** skill — a launch has to go out under the right handle. Show the handle it will post from and confirm it's the one they want to launch on. 2. **Read the repo's reality.** Pull the launch facts from the source, not your imagination: the `README` (the top "what is this / why / how" section), and the first release — `git tag`, `git show` on the tag, release notes or `CHANGELOG`, and `package.json` name + version + description. If "$ARGUMENTS" names a file, tag, or angle, use it. **If there's no release yet**, say so and ask whether to launch off the README alone or wait for the tag. 3. **Extract the load-bearing facts and check them back.** List for the user: the one-line pitch, the concrete problem it solves, the 2–4 things it *actually* does today, any real proof (a benchmark, a test count, a working demo — only if it exists in the repo), the canonical link (repo / docs / landing), th