AuraGlass 3.3 Release Notes — AuraGlass by AuraOne

#What 3.3 ships

AuraGlass 3.3 is the post-3.2 trust release. The package keeps the dependency-sovereign app chrome from 3.2 and adds focused package subpaths for forms, data, navigation, overlays, workflows, and marketing so product teams can import smaller feature families with clearer ownership.

The registry now exposes 28 recipes. Eight new 3.3 starters cover AI operations, semantic search, vision review, collaboration room state, support triage, release operations, developer docs, and marketing launch pages. AI/server recipes default to provider-unconfigured UI states until the app wires authenticated provider-backed routes.

#Focused package subpaths

Use focused subpaths when a route only needs one product family. The root entrypoint remains convenient for core UI, while the subpaths make package boundaries easier to review in dashboards, form flows, data-heavy routes, overlays, workflow screens, and launch pages.

aura-glass/forms

Form, validation, and settings surfaces for app-owned data handling

aura-glass/data

Data tables, grids, metrics, charts, and analytics-ready display surfaces

aura-glass/navigation

Navigation, sidebars, tabs, breadcrumbs, and app chrome helpers

aura-glass/overlays

Dialogs, drawers, popovers, command surfaces, and overlay composition

aura-glass/workflows

Workflow shells, Kanban, wizard, timeline, and operations layouts

aura-glass/marketing

Launch-page hero, feature, proof, install, and social-proof surfaces

#Hosted runtime contract

The optional hosted runtime is documented as opt-in. Core package use still requires only React, React DOM, the package, and the stylesheet. Backend features require explicit API, WebSocket, Redis, auth, and provider configuration by the consuming app.

3.3 standardizes the local contract around API `3002` and WebSocket `3001`, with fail-closed provider-unconfigured responses. Missing AI/search/vision provider configuration should produce typed, secret-safe errors and disabled provider-backed actions rather than mock success.

API server

http://localhost:3002 for optional provider-backed routes

WebSocket server

ws://localhost:3001 for optional room, presence, cursor, and selection state

Provider missing

Render provider-unconfigured UI and keep manual review paths usable

Collaboration editing

Explicitly unsupported until a real CRDT/OT operation model ships

#Recipe registry

The CLI and registry now expose 28 recipe IDs through `aura-glass/registry` and `npx aura-glass`. Use `list --json` for tooling, `info <recipe>` for metadata, and `add <recipe>` or `add all` to scaffold copyable app surfaces.

bash

npx aura-glass list --json
npx aura-glass info ai-ops-control-room
npx aura-glass add release-command-center
npx aura-glass add marketing-launch-kit
npx aura-glass add all --dry-run --json

#Upgrade checklist

Upgrade apps by installing `aura-glass@3.3.0`, keeping the stylesheet import at the app root, replacing stale recipe counts in local docs, and moving new feature routes to focused package subpaths when that makes bundle review clearer.

Treat backend features as opt-in. Do not claim provider-backed AI, semantic search, vision review, or collaboration editing is production-ready until the consuming app has configured provider keys, auth, Redis, route policy, monitoring, and its own integration tests.

bash

npm install aura-glass@3.3.0
npx aura-glass doctor --json
npx aura-glass list --json