upstream sync, simplify math support, removed unused svelte lib packages

Author: chillenious

.compatibility/report.json

@@ -2,13 +2,15 @@
 
 A modern, ESM-first implementation of the PIE (Platform Independent Elements) specification. This is a **new project** (not a refactor) that provides a clean foundation for future PIE development while maintaining backwards compatibility through the legacy pie-elements project.
 
+**Current Status**: Early development (v0.1.0) - 28 React-based elements synced from upstream, core infrastructure in place.
+
 ## Why a New Project?
 
 The PIE team's work on upstream library modernization (React 18, MUI 7, Tiptap editor) now enables full ESM adoption and modern tooling. This new project takes advantage of those improvements while keeping the legacy pie-elements available for existing consumers.
 
 ## Key Improvements Over Legacy pie-elements
 
-1. **Framework-agnostic architecture** - Supports multiple frameworks (React, Svelte, future Vue/Angular) via web components, not just React
+1. **Framework-agnostic architecture** - Architecture designed to support multiple frameworks (React, Svelte, future Vue/Angular) via web components. Currently: React implementations synced from upstream.
 2. **ESM-first build system** - Browser-managed dependencies, better caching, smaller bundles (vs CommonJS + webpack IIFE bundles)
 3. **Unified player approach** - Element-level players for development (interactive + print), item-level players in pie-players for production
 4. **Symmetric package organization** - Peer folders (delivery/author/controller/print) vs asymmetric legacy structure

README.md

@@ -21,7 +21,6 @@
   },
   "devDependencies": {
     "@pie-element/multiple-choice": "workspace:*",
-    "@pie-element/shared-math-rendering-core": "workspace:*",
     "@pie-element/shared-math-rendering-mathjax": "workspace:*",
     "@sveltejs/adapter-auto": "^3.3.1",
     "@sveltejs/kit": "^2.50.1",

apps/element-demo/package.json

@@ -16,7 +16,7 @@ export async function waitForMathRendering(page: Page, timeout = 5000) {
         if (!mathJax) return true; // No MathJax, consider done
 
         // MathJax 3.x check
-        if (mathJax.startup && mathJax.startup.promise) {
+        if (mathJax.startup?.promise) {
           return mathJax.startup.promise.then(() => true).catch(() => true);
         }
 

apps/element-demo/test/e2e/test-helpers.ts

@@ -1,5 +1,5 @@
 {
-  "$schema": "https://biomejs.dev/schemas/2.3.13/schema.json",
+  "$schema": "https://biomejs.dev/schemas/2.3.14/schema.json",
   "vcs": {
     "enabled": true,
     "clientKind": "git",

biome.json

@@ -2,7 +2,13 @@
 
 ## Overview
 
-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. Future plans include native Svelte 5 implementations for smaller bundle sizes and better performance.
+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)
+- Future plans include native Svelte 5 implementations and public npm releases
 
 ## Core Philosophy
 
@@ -43,9 +49,9 @@ This project differs fundamentally from the legacy pie-elements in eight key way
 - **Controllers** are pure TypeScript business logic (completely framework-independent)
 - **UI implementations** can use any framework (React, Svelte, Vue, Angular) as long as they produce web components
 - **Element Player** loads elements via custom element registry, regardless of underlying framework
-- **Coexistence**: React and Svelte elements work side-by-side in the same application
+- **Current State**: All 28 elements use React; architecture supports future multi-framework implementations
 
-This flexibility allows choosing the right framework for each use case (e.g., Svelte for smaller bundles, React for ecosystem compatibility).
+This architectural flexibility will allow choosing the right framework for each use case (e.g., Svelte for smaller bundles, React for ecosystem compatibility).
 
 ### 2. ESM-First Build System
 
@@ -428,16 +434,20 @@ $ git push
 
 **Publishing strategy:**
 
-Not all packages in the monorepo are published to npm:
+**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**:
 
-- **Element packages** (`@pie-element/*`) - Published for external consumption
-- **Library packages** (`@pie-lib/*`) - **NOT published independently**
+Once the project reaches a stable release (v1.0.0+):
+
+- **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 never import `@pie-lib` packages directly
+  - External consumers will never import `@pie-lib` packages directly
   - Simplifies the public API surface
 
-This differs 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 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.
 
 **Trade-offs:**
 
@@ -489,7 +499,7 @@ This project maintains compatibility with the existing PIE ecosystem by syncing
 ### Source Repositories
 
 - **[pie-elements](https://github.com/PieLabs/pie-elements)** → `packages/elements-react/`
-  - 50+ production-tested React element implementations
+  - 28 React element implementations synced from upstream
   - Controllers (business logic)
   - UI components (delivery, authoring, print modes)
 
@@ -499,7 +509,7 @@ This project maintains compatibility with the existing PIE ecosystem by syncing
 
 ### Why Sync?
 
-1. **Leverage existing work** - Reuse 50+ production-tested elements
+1. **Leverage existing work** - Reuse production-tested elements from upstream
 2. **Maintain compatibility** - Ensure consistency with existing PIE consumers
 3. **Modernize existing code** - Transform to ESM, TypeScript, and modern tooling
 4. **Stable baseline** - Synced React elements provide production-ready implementations
@@ -1160,19 +1170,25 @@ Note: `'unsafe-inline'` for styles is required for Svelte scoped styles.
 
 ### NPM Publishing
 
-Packages are published to npm via GitHub Actions:
+**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:
 
 1. Developer creates changeset: `bun run changeset`
 2. PR merged to main
 3. GitHub Action creates "Version Packages" PR
 4. Maintainer merges Version PR
 5. Packages automatically published to npm
 
-See [PUBLISHING.md](./PUBLISHING.md) for details.
+See [PUBLISHING.md](./PUBLISHING.md) for details (when available).
 
 ### Versioning
 
-This project uses **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. See [section 8 above](#8-workspace-wide-versioning) for a detailed explanation of why this approach was chosen and the problems it solves.
+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.
+
+See [section 8 above](#8-workspace-wide-versioning) for a detailed explanation of why this approach was chosen and the problems it solves.
 
 **Semantic Versioning (SemVer)**:
 
@@ -1190,7 +1206,7 @@ All packages follow semantic versioning as a coordinated unit:
 4. All element packages are released together with the same new version
 5. Internal dependencies automatically updated to the new version
 
-**Example release:**
+**Example release (future, when published):**
 
 ```bash
 # Before: All element packages at 1.4.0
@@ -1199,14 +1215,16 @@ $ bun run changeset
 # PR merged
 
 # After: All element packages bumped to 1.5.0
-@pie-element/multiple-choice: 1.5.0     # Published to npm
-@pie-element/drag-in-the-blank: 1.5.0   # Published to npm (even though unchanged)
+@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)
 ```
 
+**Current Reality**: All packages are at `0.1.0` and private (not published).
+
 This ensures all packages are always compatible and tested together. External consumers only interact with `@pie-element/*` packages, which bundle all necessary dependencies.
 
 ### CDN Distribution

bun.lock

@@ -1,11 +1,11 @@
 # Math Rendering in pie-elements-ng
 
-**Last Updated:** 2026-02-01
+**Last Updated:** 2026-02-09
 **Status:** ✅ Production Ready (MathJax v4)
 
 ## Overview
 
-pie-elements-ng uses **MathJax v4** as the default math renderer, providing:
+pie-elements-ng uses **MathJax v4** as the math renderer, providing:
 - ✅ Full accessibility (Speech Rule Engine, WCAG AAA)
 - ✅ Native MathML rendering (100% fidelity)
 - ✅ ESM-compatible (unlike MathJax v3)
@@ -14,37 +14,28 @@ pie-elements-ng uses **MathJax v4** as the default math renderer, providing:
 
 ## Architecture
 
-### Wrapper Pattern
+### Direct Implementation
 
 ```
 @pie-lib/math-rendering (wrapper)
   └─> @pie-element/shared-math-rendering-mathjax (~2.7MB via CDN)
       └─> MathJax v4 library
 ```
 
-The wrapper maintains API compatibility with upstream `@pie-lib/math-rendering` while allowing internal implementation changes.
+The wrapper maintains API compatibility with upstream `@pie-lib/math-rendering`.
 
 ### Key Packages
 
-1. **`@pie-lib/math-rendering`** - Wrapper package (re-exports from adapter)
+1. **`@pie-lib/math-rendering`** - Wrapper package (re-exports from MathJax)
    - Location: `packages/lib-react/math-rendering/`
    - Auto-generated by sync system
    - Maintains upstream API compatibility
 
-2. **`@pie-element/shared-math-rendering-mathjax`** - MathJax v4 adapter
+2. **`@pie-element/shared-math-rendering-mathjax`** - MathJax v4 implementation
    - Location: `packages/shared/math-rendering-mathjax/`
    - Loads MathJax v4 from CDN
    - Full accessibility support
-
-3. **`@pie-element/shared-math-rendering-katex`** - KaTeX adapter (legacy)
-   - Location: `packages/shared/math-rendering-katex/`
-   - Lightweight alternative (~100KB)
-   - Available for special use cases
-
-4. **`@pie-element/shared-math-rendering-core`** - Core types
-   - Location: `packages/shared/math-rendering-core/`
-   - `MathRenderer` interface
-   - Shared utilities
+   - Direct implementation (no abstraction layer)
 
 ## Usage
 
@@ -63,13 +54,12 @@ queueMicrotask(() => {
 
 ### For Player Developers
 
-Use the factory function for dependency injection:
+Use the factory function for custom configuration:
 
 ```typescript
 import { createMathjaxRenderer } from '@pie-element/shared-math-rendering-mathjax';
-import type { MathRenderer } from '@pie-element/shared-math-rendering-core';
 
-const mathRenderer: MathRenderer = createMathjaxRenderer({
+const mathRenderer = createMathjaxRenderer({
   accessibility: true,       // Enable Speech Rule Engine
   useSingleDollar: false,    // Disable $...$ delimiters
   loadFonts: true,           // Load MathJax fonts
@@ -146,22 +136,13 @@ MathJax v4 provides WCAG AAA compliance:
 
 ## Why MathJax v4?
 
-### Previous Approach (2026-01-30)
-
-Initially used KaTeX wrapper due to MathJax v3 CommonJS incompatibility:
-- ✅ Light bundle (~100KB)
-- ✅ Fast rendering
-- ⚠️ Limited accessibility
-- ⚠️ MathML via conversion (fidelity loss)
+MathJax v4 is the only viable option for production because:
 
-### Current Approach (2026-02-01)
-
-Switched to MathJax v4 because:
-1. **ESM-compatible** - MathJax v4 is pure ESM (unlike v3)
-2. **Full accessibility** - Required for WCAG AAA compliance
+1. **ESM-compatible** - Pure ESM (unlike MathJax v3)
+2. **Full accessibility** - Required for WCAG AAA compliance (Speech Rule Engine)
 3. **Native MathML** - 100% rendering fidelity
 4. **Same API** - Backward compatible with upstream
-5. **CDN loading** - Zero bundle impact in production
+5. **CDN loading** - Zero bundle impact (~2.7MB loaded once, cached)
 
 ## Migration from Upstream
 
@@ -233,27 +214,29 @@ MathJax v4 renders MathML natively - no conversion needed. If MathML doesn't ren
 2. **Test with screen reader**: Right-click math → should see context menu
 3. **Check ARIA labels**: Inspect rendered math for `aria-label` attributes
 
-## Alternative: KaTeX Adapter
+## Authoring Tools
 
-For lightweight contexts where full accessibility isn't required:
+### React Elements (Current)
 
-```typescript
-import { createKatexRenderer } from '@pie-element/shared-math-rendering-katex';
+React elements use the upstream **`@pie-lib/editable-html-tip-tap`** package for authoring interfaces. This package includes:
 
-const renderer = createKatexRenderer();
-await renderer(element);
-```
+- **Custom TipTap math extension** with MathQuill integration
+- **Interactive math editing** (not just static rendering)
+- **MathQuill** for authoring/editing (visual WYSIWYG math editor)
+- **MathJax** for final output rendering
+
+This is already synced from upstream and works correctly with React elements.
+
+### Svelte Elements (Future)
+
+When Svelte-based PIE elements are created, the math editing approach will be determined at that time. Options include:
+- Porting the custom TipTap math extension to Svelte
+- Using the React component via interop
+- Creating a Svelte-native math editing solution
 
-**Use when:**
-- Preview/authoring interfaces (internal tools)
-- Bundle size is critical
-- Content is LaTeX-only (no MathML)
-- Basic accessibility is sufficient
+### Demo Applications
 
-**Limitations:**
-- MathML via conversion (may lose fidelity)
-- No Speech Rule Engine
-- Limited screen reader support
+The demo app's RichTextEditor is primarily for displaying/editing JSON source code and doesn't require math support. Math rendering in the demo happens via the element player using MathJax.
 
 ## Development
 
@@ -310,6 +293,7 @@ bun cli upstream:sync
 
 - **2026-01-30**: Initial KaTeX wrapper (ESM compatibility)
 - **2026-02-01**: Switched to MathJax v4 (full accessibility)
+- **2026-02-09**: Simplified to MathJax-only (removed abstraction layer)
 
 ---
 

docs/ARCHITECTURE.md

@@ -74,7 +74,9 @@ Where `itemConfig` includes:
 
 ## Print Element Architecture
 
-Each element package includes a print export:
+**Current Coverage**: Print support is available for 10 out of 28 elements. Print components are being added incrementally as elements are developed.
+
+Each element package can include a print export:
 
 ```
 packages/elements-react/multiple-choice/

docs/MATH-RENDERING.md

@@ -7,7 +7,6 @@
     "packages/shared/*",
     "packages/elements-react/*",
     "packages/elements-react/*/demo",
-    "packages/lib-svelte/*",
     "packages/lib-react/*",
     "packages/element-player",
     "packages/core",
@@ -66,7 +65,6 @@
     "@types/dompurify": "^3.2.0",
     "@types/glob": "^9.0.0",
     "@types/js-yaml": "^4.0.9",
-    "@types/katex": "^0.16.7",
     "@types/lodash": "^4.17.21",
     "@types/node": "^25.0.3",
     "@types/prop-types": "^15.7.15",