upstream update and making libs publishable

Author: chillenious

.changeset/config.json

@@ -7,5 +7,5 @@
   "access": "public",
   "baseBranch": "master",
   "updateInternalDependencies": "patch",
-  "ignore": ["esm-player-test", "@pie-element/math-inline", "@pie-element/math-templated"]
+  "ignore": ["esm-player-test"]
 }

.compatibility/report.json

@@ -106,6 +106,8 @@ Use release labels to tag a coordinated release wave across packages while keepi
 
 ### Manual Publish Recovery (GitHub Actions)
 
+`@pie-element/*` and `@pie-lib/*` packages are configured as publishable and are released through this workflow.
+
 If a publish fails after the version PR was already merged, rerun the Release workflow manually:
 
 1. Actions → **Release** → **Run workflow**

README.md

@@ -5,9 +5,10 @@
 This is a modern implementation of the PIE (Platform Independent Elements) specification, built with TypeScript, ESM, and contemporary tooling. The project currently syncs React-based elements from the upstream [pie-elements](https://github.com/PieLabs/pie-elements) repository while providing modern ESM packaging, Vite builds, and improved developer experience.
 
 **Current Status**: Early development (v0.1.0)
+
 - 28 React elements synced from upstream
 - Core infrastructure and build tooling established
-- Elements are private packages (not yet published to npm)
+- Element and lib packages are publish-enabled (versioned/released via Changesets + GitHub Actions)
 - Future plans include native Svelte 5 implementations and public npm releases
 
 ## Core Philosophy
@@ -434,20 +435,14 @@ $ git push
 
 **Publishing strategy:**
 
-**Current Status**: All packages are currently marked as `"private": true` and are not published to npm. This is an early development phase decision.
-
-**Future Publishing Plan**:
+**Current Status**: `@pie-element/*` and `@pie-lib/*` packages are configured to be publishable and are managed by the Changesets release workflow.
 
-Once the project reaches a stable release (v1.0.0+):
+**Release behavior**:
 
-- **Element packages** (`@pie-element/*`) - Will be published for external consumption
-- **Library packages** (`@pie-lib/*`) - Will **NOT** be published independently
-  - These are internal implementation details of the elements
-  - Bundled into element packages during build
-  - External consumers will never import `@pie-lib` packages directly
-  - Simplifies the public API surface
+- **Element packages** (`@pie-element/*`) are versioned and published by CI.
+- **Library packages** (`@pie-lib/*`) are also versioned/publishable so internal dependency graphs stay coherent during coordinated releases.
 
-This will differ from the legacy approach where `@pie-lib` packages were independently published and consumed. In pie-elements-ng, `@pie-lib` packages exist purely for internal code organization within the monorepo.
+This differs from earlier phases where most synced packages were intentionally private.
 
 **Trade-offs:**
 
@@ -581,7 +576,7 @@ The architecture consists of three main layers:
 **Key organizational decisions**:
 
 - **@pie-lib integration**: The `@pie-lib/*` packages (formerly a separate repository) are now in `packages/lib-react/` for better version management and coordination
-- **Versioning**: Independent versioning using Changesets. Most synced packages are marked private; core packages like `@pie-element/core` are publishable
+- **Versioning**: Changesets-managed coordinated versioning and publishing for `@pie-element/*` and `@pie-lib/*` packages
 - **Workspaces**: Bun workspaces with `"workspace:*"` references ensure consistency across the monorepo
 
 ### Element Package Anatomy
@@ -1170,12 +1165,10 @@ Note: `'unsafe-inline'` for styles is required for Svelte scoped styles.
 
 ### NPM Publishing
 
-**Current Status**: Packages are not yet published to npm (all marked as `"private": true`).
-
-**Future Publishing Strategy**: Once ready for public release, packages will be published via GitHub Actions:
+**Current Strategy**: Publishing is CI-driven via GitHub Actions and Changesets:
 
 1. Developer creates changeset: `bun run changeset`
-2. PR merged to main
+2. PR merged to `master`
 3. GitHub Action creates "Version Packages" PR
 4. Maintainer merges Version PR
 5. Packages automatically published to npm
@@ -1190,7 +1183,7 @@ See [PUBLISHING.md](./PUBLISHING.md) for details (when available).
 
 This project is designed to use **workspace-wide versioning** where all packages share the same version number. This is a deliberate architectural decision that differs from the upstream pie-elements/pie-lib projects.
 
-**Current Status**: All packages are at version `0.1.0` and marked as `"private": true` (not published). Workspace-wide versioning will be enforced when packages are published publicly.
+**Current Status**: `@pie-element/*` and `@pie-lib/*` packages are publish-enabled and released through the Changesets CI flow.
 
 See [section 8 above](#8-workspace-wide-versioning) for a detailed explanation of why this approach was chosen and the problems it solves.
 
@@ -1222,12 +1215,12 @@ $ bun run changeset
 @pie-element/multiple-choice: 1.5.0     # Will be published to npm
 @pie-element/drag-in-the-blank: 1.5.0   # Will be published to npm (even though unchanged)
 
-# Internal packages are versioned but NOT published:
-@pie-lib/render-ui: 1.5.0               # Internal only (bundled into elements)
-@pie-lib/math-rendering: 1.5.0          # Internal only (bundled into elements)
+# Lib packages are versioned in the same coordinated release:
+@pie-lib/render-ui: 1.5.0
+@pie-lib/math-rendering: 1.5.0
 ```
 
-**Current Reality**: All packages are at `0.1.0` and private (not published).
+**Current Reality**: Package releases are coordinated through the CI release workflow.
 
 This ensures all packages are always compatible and tested together. External consumers only interact with `@pie-element/*` packages, which bundle all necessary dependencies.