kylon-cli 0.1.0-next.13 → 0.1.0-next.130

package/README.md

@@ -334,7 +334,7 @@ The release artifact is a single-file ESM bundle produced by
 |---|---|---|---|
 | `pnpm --filter kylon-cli bundle` | `dist/kylon-bundle.mjs` | _(none)_ | debugging the bundled shape while keeping readable names — not shipped |
 | `pnpm --filter kylon-cli bundle:minify` | `dist/kylon-bundle.mjs` | `--minify` | reproducing the pre-obfuscation size and behavior for a bisect |
-| `pnpm --filter kylon-cli bundle:release` | `dist/kylon-bundle.mjs` | `--minify --obfuscate` | what ships on npm (and the frozen fallback bundle) |
+| `pnpm --filter kylon-cli bundle:release` | `dist/kylon-bundle.mjs` | `--minify --obfuscate` | what ships on npm |
 
 The `bundle:release` path runs esbuild with `--minify`, then passes the
 output through `javascript-obfuscator`. It's also what the `prepack` hook
@@ -470,12 +470,3 @@ npm deprecate kylon-cli@<bad> "Broken release — use <last-good>."
 Operators on `@latest` pick up the re-pointed version the next time they
 `npm install -g kylon-cli@latest`; in-flight daemons keep their current CLI
 until they restart. Do not `npm unpublish`.
-
-### Fallback bundle (deprecated)
-
-A single-file bundle is still served at `/docs/cli/kylon.mjs` (redirecting to
-the public CDN) as a grace-period fallback for pre-npm install commands. It is
-**frozen**: `release-cli.yml` — which built and uploaded it on every CLI push —
-has been removed, so no new bundles are produced. The endpoint will be retired
-once `docs.kylon.io` and any in-the-wild `curl` install commands have moved to
-npm.