Pick the npm package name (real publishing is gated on this)

[ScriptedAlchemy]

Extracted from the closing ledger of #50: the RFC's build-ownership scope is fully delivered, and the only item gating real npm publishing is picking the public package name. This issue captures the naming facts so the decision has one home.

Facts (verified against the public registry, 2026-08-31)

• agent-bundle is taken. npm view agent-bundle → 0.1.2, an unrelated package ("CLI tool and framework for defining, developing, and shipping AI agent skills"). Publishing this repo's framework under its current name is blocked outright.
• create-agent-bundle is unclaimed. npm view create-agent-bundle → E404 (also confirmed during feat: create-agent-bundle scaffolding package (RFC #50 Phase 3) #62's packed-e2e work). Note the caveat: npm create X resolves create-X, so the scaffolder name is only useful paired with whatever the framework name ends up being — if the framework renames, the create-* name must rename with it.
• Nothing is published under @agent-bundle/* (npm view @agent-bundle/rsc-runtime → E404). Whether the scope itself is claimable on npm has not been verified.
• Four workspace packages are affected: agent-bundle, @agent-bundle/rsc-runtime, @agent-bundle/workbench, create-agent-bundle — plus every README/docs/template mention and the scaffolder's framework-pinning logic (feat: create-agent-bundle scaffolding package (RFC #50 Phase 3) #62 deliberately refuses to guess a semver on non-preview builds because the npm agent-bundle name belongs to an unrelated package).
• Interim channel is unaffected: pkg.pr.new previews are the release channel (chore(release): make pkg.pr.new the interim channel and pre-wire npm provenance #40), same-sha peer pairing works (fix(release): rewrite preview peer ranges via --peerDeps so npm installs matched pkg.pr.new pairs cleanly #46), and the scaffolder derives its paired preview URL from its own -preview-<sha> version, so nothing here is urgent for preview consumers.

Decision to make

Pick one:

1. New unscoped name — rename the framework (and create-<name> with it); cleanest npm story, largest doc/template churn.
2. Scoped names (@<scope>/agent-bundle etc.) — keeps the working name; requires verifying/claiming the scope; npm create @<scope>/x works but is less discoverable.
3. Pursue the existing agent-bundle name (npm support / owner contact) — keeps everything as-is if it succeeds, but the name hosts an active unrelated package at 0.1.2, so treat as a long shot with an unbounded timeline.

Whatever the choice, the rename lands as: package.json names + workspace references → scaffolder templates and pinning logic → docs/READMEs → first real publish (provenance is already pre-wired per #40).

[ScriptedAlchemy]

Closing per maintainer direction. This duplicated #78; the eventual public package-name choice does not need a standalone tracking issue.