chore: release mc-populated-blank v0.2.1 and publish guidance

Bump @pie-element/mc-populated-blank to 0.2.1 and record the changelog entry, and document workspace-targeted npm publish plus sandbox auth fallback to prevent root-package publish and token confusion.

Made-with: Cursor

Author: chillenious

.claude/instructions.md

@@ -228,6 +228,8 @@ oclif-based CLI for:
 - **Default bump policy**: Always use `patch` by default for releases/versioning.
 - Use `minor` or `major` only when the user explicitly requests it.
 - **Selective publish only**: Publish only selected packages and changeset-propagated dependents, never all unpublished packages.
+- **Workspace-targeted npm publish**: In this monorepo, publish using an explicit workspace target (for example `npm publish --workspace @pie-element/<name> --access public`) so npm does not try to publish the private root package.
+- **Sandbox publish fallback**: If npm publish/auth fails in sandbox while token is valid, retry outside sandbox and use explicit npm auth config via `NPM_CONFIG_USERCONFIG` with `NPM_TOKEN`.
 - **Independent versions (current policy)**: Packages version independently (no workspace-wide lockstep assumption).
 - **Upstream sync versioning**: `upstream:update` must preserve/copy upstream package versions for synced `elements-react` and `lib-react` packages.
 

.cursorrules

@@ -13,5 +13,7 @@
 - Release/versioning default: always use a patch bump by default.
 - For Changesets-driven releases, default to `patch` unless the user explicitly asks for `minor` or `major`.
 - Publish policy: publish only explicitly selected packages (and packages bumped by changeset dependency propagation), never "all unpublished packages".
+- For npm publishing in this monorepo, always target a specific workspace package (for example `npm publish --workspace @pie-element/<name> --access public`) to avoid accidentally publishing the private repo root package.
+- If npm auth/publish fails in sandbox despite a valid token, retry outside sandbox with an explicit npm user config pointing at `NPM_TOKEN` (for example `NPM_CONFIG_USERCONFIG=.npmrc.publish`).
 - Versioning policy (current): packages are versioned independently; do not assume workspace-wide lockstep versions.
 - Upstream sync policy: `upstream:update` should preserve/copy package versions from upstream package.json when syncing `packages/elements-react/*` and `packages/lib-react/*`.

packages/elements-svelte/mc-populated-blank/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @pie-element/mc-populated-blank
 
+## 0.2.1
+
+### Patch Changes
+
+- Prepare a patch release for mc-populated-blank.
+
 ## 0.2.0
 
 ### Minor Changes

packages/elements-svelte/mc-populated-blank/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pie-element/mc-populated-blank",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Multiple-choice option populates an inline blank in a sentence template (Svelte 5 PIE element)",
   "type": "module",
   "main": "./dist/index.js",