docs: correct RELEASING bootstrap for @tskm/core rename

The manual bootstrap section described an approach that does not work:
NPM_CONFIG_PROVENANCE=false cannot disable provenance because
publishConfig.provenance:true overrides the env var. Replace it with the
verified procedure — temporarily remove the provenance line, publish with
NPM_CONFIG_OTP, then restore the guardrail — and fix the runtime package
name (tskm -> @tskm/core), the publish order, and the provenance
expectation (the manual bootstrap versions, including @tskm/compiler@0.0.2,
all have no provenance; the first CI OIDC release carries it).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: ushironoko

docs/RELEASING.md

@@ -1,6 +1,6 @@
 # Releasing
 
-How `tskm`, `@tskm/compiler`, and `@tskm/vite` are published, and the one-time setup
+How `@tskm/core`, `@tskm/compiler`, and `@tskm/vite` are published, and the one-time setup
 required before the automated pipeline can run.
 
 Publishing is **CI-only** and **tokenless**: GitHub Actions publishes via npm OIDC
@@ -23,30 +23,55 @@ Do these once, in order, before the first automated release.
 
 ### 2. Own the `@tskm` scope
 - Create / confirm ownership of the `@tskm` scope (org or user scope) on npmjs.com.
-  `@tskm/compiler` and `@tskm/vite` cannot be published otherwise.
+  `@tskm/core`, `@tskm/compiler`, and `@tskm/vite` cannot be published otherwise.
 
 ### 3. Bootstrap publish (first version only)
 The npm Trusted Publisher UI requires a package to already exist before you can attach a
-trusted publisher to it. So publish `0.0.1` of each package **once**, manually, from your
-machine. This first version has **no provenance** (provenance needs the CI OIDC context)
-— that is expected and unavoidable.
+trusted publisher to it. So publish each package **once**, manually, from your machine.
+These bootstrap versions have **no provenance** (provenance needs the CI OIDC context) —
+that is expected and unavoidable.
+
+`publishConfig.provenance: true` stays in every `package.json` as a **fail-closed
+guardrail**: a non-CI publish refuses to run. It is **not** overridable by an environment
+variable — `NPM_CONFIG_PROVENANCE=false` does **not** turn provenance off, because
+`publishConfig` wins over env. So the bootstrap temporarily *removes* the line instead of
+trying to override it, then restores it.
 
 ```sh
 npm login                  # issues a short-lived (~2h) session, prompts for your passkey
 bun install --frozen-lockfile --ignore-scripts
 bun run build
-# Reuses scripts/publish.ts: ordered (compiler → tskm → vite), rewrites @tskm/vite's
-# workspace:* dependency, and is idempotent. NPM_CONFIG_PROVENANCE=false is REQUIRED —
-# publishConfig.provenance is true, which would otherwise fail outside CI.
-NPM_CONFIG_PROVENANCE=false bun run release
+
+# Temporarily drop the guardrail (env vars can't override publishConfig): delete the
+# `"provenance": true` line from each packages/*/package.json. Do NOT commit this.
+
+# scripts/publish.ts publishes in dependency order (@tskm/compiler → @tskm/core →
+# @tskm/vite), rewrites @tskm/vite's workspace:* dependency to a concrete range, and is
+# idempotent (versions already on the registry are skipped). NPM_CONFIG_OTP is required
+# because the account is 2FA "auth-and-writes"; the env propagates to all three
+# `npm publish` calls. The TOTP window is ~30s — if a later publish fails with EOTP, just
+# re-run with a fresh code and the already-published packages are skipped.
+NPM_CONFIG_OTP=<6-digit> bun run release
+
+# Restore the guardrail (leaves main untouched):
+git checkout -- packages/*/package.json
 ```
 
+> Right after a publish, `npm view <pkg>` may return E404 for up to a few minutes
+> (registry propagation lag) even though the publish succeeded — do not mistake it for a
+> failure. The authoritative idempotent check is `bun run release` itself, which reports
+> already-published versions as `skip (already on registry)`.
+
+> An earlier `@tskm/compiler@0.0.1` was published before the runtime was renamed to
+> `@tskm/core` (it targets the never-published unscoped `tskm`); it is **deprecated**. The
+> current compiler bootstrap is `@tskm/compiler@0.0.2`.
+
 ### 4. Install the pkg.pr.new GitHub App (for preview releases)
 - Install <https://github.com/apps/pkg-pr-new> and scope it to **only** `ushironoko/tskm`.
   Without it, `preview.yml` cannot publish preview packages.
 
 ### 5. Configure the Trusted Publisher on npmjs.com (per package)
-For **each** of `tskm`, `@tskm/compiler`, `@tskm/vite`:
+For **each** of `@tskm/core`, `@tskm/compiler`, `@tskm/vite`:
 - Package → Settings → **Trusted Publisher** → GitHub Actions
 - Organization/owner: `ushironoko`
 - Repository: `tskm`
@@ -63,7 +88,8 @@ For **each** of `tskm`, `@tskm/compiler`, `@tskm/vite`:
 ### 7. After the first successful OIDC release
 - For each package, enable **"Require two-factor authentication and disallow tokens"**
   (trusted publishing keeps working under this setting).
-- Revoke any granular token used for the bootstrap publish.
+- The bootstrap publishes with a one-time OTP, not a long-lived token, so there is nothing
+  to revoke — just confirm no granular/classic token was created for it.
 
 ---
 
@@ -83,13 +109,15 @@ For **each** of `tskm`, `@tskm/compiler`, `@tskm/vite`:
    - the `version` job's gate detects an unpublished version (`should_publish=true`);
    - the `publish` job starts and **waits for `release` Environment approval**;
    - once approved, it builds, runs `publint` / `attw` / the clean-room install smoke
-     test, then publishes `compiler → tskm → vite` over OIDC with provenance.
+     test, then publishes `@tskm/compiler → @tskm/core → @tskm/vite` over OIDC with provenance.
 
 4. **Verify** the green provenance badge on npmjs.com and:
    ```sh
    npm audit signatures
    ```
-   Expected provenance: **`0.0.1` = none** (bootstrap), **`0.0.2`+ = present**.
+   Expected provenance: the manually bootstrapped versions — `@tskm/core@0.0.1`,
+   `@tskm/compiler@0.0.2`, `@tskm/vite@0.0.1` — all have **none**. The first CI OIDC
+   release of each package (its next version) is the first to carry **provenance**.
 
 ## Preview releases