@vib3code/sdk 2.0.3-canary.89c05e0 → 2.0.3-canary.8d2fdcd

package/DOCS/AGENT_HARNESS_ARCHITECTURE.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ Agent Harness Architecture
 
 **Purpose**: Close the feedback loop between AI agents and VIB3+ visualization, enabling agents to design ultra-intricate reactive choreographed visuals that would be impractical via manual UI.

package/DOCS/ANDROID_DEPLOYMENT.md

@@ -0,0 +1,59 @@
+Last reviewed: 2026-02-17
+
+# Building VIB3+ Ultra for Android
+
+This guide explains how to build the "Crystal Labyrinth" demo as an Android APK using the existing Flutter integration.
+
+## Prerequisites
+
+- Flutter SDK installed
+- Android Studio / Android SDK installed
+- Connected Android device or emulator
+
+## Quick Build (GitHub Actions)
+
+The repository includes a workflow `.github/workflows/flutter-apk.yml` that automatically builds an APK on push to `examples/flutter_demo/`.
+
+To trigger a build for the Crystal Labyrinth demo:
+1.  Copy the built web assets to the Flutter assets directory (see Local Build below).
+2.  Push changes.
+3.  Download the artifact from the Actions tab.
+
+## Local Build Instructions
+
+1.  **Build the Web Demo**
+    Run the Vite build to bundle the Crystal Labyrinth demo:
+    ```bash
+    npm install
+    npm run build:web
+    ```
+    This will output optimized files to `dist/`.
+
+2.  **Prepare Flutter Assets**
+    Copy the build output to the Flutter project's asset folder:
+    ```bash
+    mkdir -p examples/flutter_demo/assets/vib3/
+    cp -r dist/* examples/flutter_demo/assets/vib3/
+    ```
+
+3.  **Configure Entry Point**
+    Open `examples/flutter_demo/lib/vib3_controller.dart` and ensure the WebView points to the local index file or the deployed GitHub Pages URL:
+    `https://<your-username>.github.io/vib3codeSDK/examples/dogfood/crystal_labyrinth.html`
+
+4.  **Build APK**
+    Navigate to the Flutter directory and build:
+    ```bash
+    cd examples/flutter_demo
+    flutter build apk --release
+    ```
+
+5.  **Install**
+    ```bash
+    flutter install
+    ```
+
+## VIB3Link Networking on Android
+
+For multi-user features (`VIB3Link`) to work on Android:
+- Ensure the device has internet access.
+- If using local dev server, use `adb reverse tcp:5173 tcp:5173` to forward ports.

package/DOCS/ARCHITECTURE.md

@@ -0,0 +1 @@
+Last reviewed: 2026-02-17

package/DOCS/CI_TESTING.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # CI and testing guide
 
 This guide outlines the baseline CI/test expectations for the project and a recommended set of

package/DOCS/CLI_ONBOARDING.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Agentic CLI onboarding
 
 This guide aligns the current CLI surface (package scripts and telemetry helpers) with an agentic workflow. It is intentionally explicit so automation agents and humans can share the same runbook.

package/DOCS/CONTROL_REFERENCE.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Control & API Reference
 
 This document walks through every control surface in `index.html` and the JavaScript entry points they call so you can quickly map UI inputs to runtime behavior.

package/DOCS/CROSS_SITE_DESIGN_PATTERNS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Cross-Site Design Pattern Synthesis
 
 **Based on actual visual analysis of 4 reference sites via Playwright screenshots**

package/DOCS/ENV_SETUP.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Environment setup (Firebase, gcloud, Flutter, Android, GH CLI)
 
 This doc provides a **copy/paste** bootstrap script to install and configure:

package/DOCS/EPIC_SCROLL_EVENTS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # EPIC SCROLL EVENTS — VIB3+ Landing Page Choreography Plan
 
 **20 scroll-driven events that combine GSAP, GPU visualizers, CSS effects, and masking layers

package/DOCS/EXPANSION_DESIGN.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ Premium Tier — Expansion Design Document
 
 **Purpose**: Technical specification for `@vib3code/premium`, a separate npm package that extends the free `@vib3code/sdk` with fine-grained shader control, axis locking, per-layer geometry, event-triggered state changes, and live CSS/framework integration.

package/DOCS/EXPANSION_DESIGN_ULTRA.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ Ultra — The Emergent Media Engine
 
 **Purpose**: This document defines the **Ultra Tier** expansion for VIB3+. While the Premium Tier (`EXPANSION_DESIGN.md`) focuses on professional visualization tools, the Ultra Tier transforms the SDK into a **full-stack emergent media engine** capable of powering 4D video games, generative cartoons, and multi-user hallucinations.

package/DOCS/EXPORT_FORMATS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Export formats
 
 This reference documents the target export formats supported by the agentic pipelines and how they are validated.

package/DOCS/GPU_DISPOSAL_GUIDE.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # GPU disposal patterns
 
 This guide documents safe GPU resource disposal patterns to prevent memory leaks across rendering backends.

package/DOCS/HANDOFF_LANDING_PAGE.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ Landing Page & Marketing Handoff Prompt
 
 **Copy this entire document as the initial prompt when starting a new session focused on the landing page, marketing site, and forward-facing aspects.**

package/DOCS/HANDOFF_SDK_DEVELOPMENT.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ SDK — Comprehensive Agent Handoff
 
 **Copy this entire document as the initial prompt when starting a new session focused on SDK development.**

package/DOCS/LICENSING_TIERS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Licensing tiers (draft)
 
 This document outlines the proposed licensing tiers for the VIB3+ SDK and agentic tooling. It is intended as a working draft for Phase 5.

package/DOCS/MASTER_PLAN_2026-01-31.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ CORE — Master Plan & Full Audit
 
 **Date**: January 31, 2026

package/DOCS/MULTIVIZ_CHOREOGRAPHY_PATTERNS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ Multi-Visualizer Choreography Patterns
 
 **Generated: 2026-02-09**
@@ -11,7 +13,7 @@
 1. [Depth Illusion Engine](#1-depth-illusion-engine)
 2. [Multi-Visualizer Coordination Modes](#2-multi-visualizer-coordination-modes)
 3. [Section-by-Section Choreography Upgrades](#3-section-by-section-choreography-upgrades)
-4. [Accent & Texture Effects Library](#4-accent--texture-effects-library)
+4. [Accent & Texture Effects Library](#4-accent-texture-effects-library)
 5. [Mathematical Intertwining Functions](#5-mathematical-intertwining-functions)
 6. [Implementation Priority Map](#6-implementation-priority-map)
 

package/DOCS/OBS_SETUP_GUIDE.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ OBS Setup Guide
 
 Use VIB3+ as a live visualization overlay in OBS Studio.

package/DOCS/OPTIMIZATION_PLAN_MATH.md

@@ -1,3 +1,4 @@
+Last reviewed: 2026-02-17
 # Optimization Plan: Core Math Library
 
 ## 1. Add `target` Parameters for Allocation-Free Operations

package/DOCS/PRODUCT_STRATEGY.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Product Strategy
 
 ## Purpose

package/DOCS/PROJECT_SETUP.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Project setup (GCP + Firebase)
 
 This document provides a professional, repeatable setup flow for creating and configuring a new

package/DOCS/README.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Documentation Index
 
 ## Strategy & Planning
@@ -54,7 +56,7 @@ Use these canonical documents first:
 | Architecture | [`DOCS/SYSTEM_INVENTORY.md`](./SYSTEM_INVENTORY.md) | ✅ System boundaries, modules, and capabilities | SDK Architecture | 2026-02-12 |
 | Product Strategy | [`DOCS/LICENSING_TIERS.md`](./LICENSING_TIERS.md) | ✅ Packaging, positioning, and commercial model | Product | 2026-02-12 |
 | Master Plan | [`DOCS/MASTER_PLAN_2026-01-31.md`](./MASTER_PLAN_2026-01-31.md) | ✅ Program-level priorities and sequencing | Program Management | 2026-02-12 |
-| Dev Track | [`DOCS/DEV_TRACK_SESSION_2026-02-06.md`](./DEV_TRACK_SESSION_2026-02-06.md) | ✅ Current implementation log and execution status | Engineering | 2026-02-12 |
+| Dev Track | [`DOCS/DEV_TRACK_SESSION_2026-02-06.md`](./dev-tracks/DEV_TRACK_SESSION_2026-02-06.md) | ✅ Current implementation log and execution status | Engineering | 2026-02-12 |
 
 ## Reading Paths by Persona
 
@@ -70,7 +72,7 @@ Use these canonical documents first:
 2. [`DOCS/REPO_MANIFEST.md`](./REPO_MANIFEST.md)
 3. [`DOCS/SYSTEM_INVENTORY.md`](./SYSTEM_INVENTORY.md)
 4. [`DOCS/MASTER_PLAN_2026-01-31.md`](./MASTER_PLAN_2026-01-31.md)
-5. Latest dev track session (currently [`DOCS/DEV_TRACK_SESSION_2026-02-06.md`](./DEV_TRACK_SESSION_2026-02-06.md))
+5. Latest dev track session (currently [`DOCS/DEV_TRACK_SESSION_2026-02-06.md`](./dev-tracks/DEV_TRACK_SESSION_2026-02-06.md))
 
 ### Product lead
 1. [`DOCS/LICENSING_TIERS.md`](./LICENSING_TIERS.md)
@@ -91,7 +93,7 @@ Use these canonical documents first:
 | Category | Scope | Primary files |
 |---|---|---|
 | Architecture | Runtime model, systems, lifecycles, controls | [`SYSTEM_INVENTORY.md`](./SYSTEM_INVENTORY.md) **(SOT)**, [`RENDERER_LIFECYCLE.md`](./RENDERER_LIFECYCLE.md), [`CONTROL_REFERENCE.md`](./CONTROL_REFERENCE.md), [`GPU_DISPOSAL_GUIDE.md`](./GPU_DISPOSAL_GUIDE.md) |
-| Planning | Strategy, roadmap, execution direction | [`MASTER_PLAN_2026-01-31.md`](./MASTER_PLAN_2026-01-31.md) **(SOT)**, [`DEV_TRACK_SESSION_2026-02-06.md`](./DEV_TRACK_SESSION_2026-02-06.md) **(SOT for active sprint log)**, [`DEV_TRACK_SESSION_2026-01-31.md`](./DEV_TRACK_SESSION_2026-01-31.md), [`LICENSING_TIERS.md`](./LICENSING_TIERS.md) **(SOT for product packaging)** |
+| Planning | Strategy, roadmap, execution direction | [`MASTER_PLAN_2026-01-31.md`](./MASTER_PLAN_2026-01-31.md) **(SOT)**, [`DEV_TRACK_SESSION_2026-02-06.md`](./dev-tracks/DEV_TRACK_SESSION_2026-02-06.md) **(SOT for active sprint log)**, [`DEV_TRACK_SESSION_2026-01-31.md`](./dev-tracks/DEV_TRACK_SESSION_2026-01-31.md), [`LICENSING_TIERS.md`](./LICENSING_TIERS.md) **(SOT for product packaging)** |
 | Operations | Setup, CI, runbooks, observability | [`PROJECT_SETUP.md`](./PROJECT_SETUP.md) **(SOT for project bootstrap)**, [`ENV_SETUP.md`](./ENV_SETUP.md), [`CI_TESTING.md`](./CI_TESTING.md), [`OBS_SETUP_GUIDE.md`](./OBS_SETUP_GUIDE.md), [`TELEMETRY_EXPORTS.md`](./TELEMETRY_EXPORTS.md) |
 | Analysis | Benchmarks, visual analysis, design studies | [`WEBGPU_STATUS.md`](./WEBGPU_STATUS.md), [`XR_BENCHMARKS.md`](./XR_BENCHMARKS.md), [`CROSS_SITE_DESIGN_PATTERNS.md`](./CROSS_SITE_DESIGN_PATTERNS.md), `VISUAL_ANALYSIS_*.md`, [`REFERENCE_SCROLL_ANALYSIS.md`](./REFERENCE_SCROLL_ANALYSIS.md) |
 | Archive | Historical plans and audits retained for traceability | [`archive/`](./archive/) including [`archive/SYSTEM_AUDIT_2026-01-30.md`](./archive/SYSTEM_AUDIT_2026-01-30.md), [`archive/STRATEGIC_BLUEPRINT_2026-01-07.md`](./archive/STRATEGIC_BLUEPRINT_2026-01-07.md), [`archive/SESSION_LOG_2026-01-07.md`](./archive/SESSION_LOG_2026-01-07.md) |

package/DOCS/REFERENCE_SCROLL_ANALYSIS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Reference Site Scroll Effect Analysis
 
 **Updated: 2026-02-10**

package/DOCS/RENDERER_LIFECYCLE.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Renderer lifecycle guide
 
 This document describes the renderer lifecycle architecture used by the core visualization systems

package/DOCS/REPO_MANIFEST.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Repository Manifest
 
 This document enumerates the repository's directory structure and provides a high-level purpose for

package/DOCS/ROADMAP.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Strategic Roadmap
 
 This roadmap maps product strategy goals from [`DOCS/PRODUCT_STRATEGY.md`](./PRODUCT_STRATEGY.md) to technical epics and the primary module ownership areas.

package/DOCS/SCROLL_TIMELINE_v3.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ Landing Page — Complete Scroll Timeline v3
 
 ## GPU-First Redesign: Real Visualizers Everywhere

package/DOCS/SITE_REFACTOR_PLAN.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ Landing Page Refactor Plan
 
 **Date:** 2026-02-13

package/DOCS/STATUS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ SDK Status
 
 This file is the single source of truth for high-level release status.

package/DOCS/SYSTEM_INVENTORY.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # VIB3+ SDK System Inventory
 
 **Document Version:** See `DOCS/STATUS.md`

package/DOCS/TELEMETRY_EXPORTS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Telemetry export manifests
 
 The telemetry export pipeline standardizes manifest payloads for downstream automation, QA, and observability. Each manifest is designed to be cache-friendly with deterministic hashes so CI can diff outputs without ambiguity.

package/DOCS/VISUAL_ANALYSIS_CLICKERSS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Visual Analysis: clickerss.com
 
 **Captured: 2026-02-10 via Playwright with wheel-based scrolling**

package/DOCS/VISUAL_ANALYSIS_FACETAD.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Visual Analysis: facetad.com
 
 **Captured: 2026-02-10 via Playwright with wheel-based scrolling**

package/DOCS/VISUAL_ANALYSIS_SIMONE.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Visual Analysis: weare-simone.webflow.io
 
 **Captured: 2026-02-10 via Playwright with wheel-based scrolling**

package/DOCS/VISUAL_ANALYSIS_TABLESIDE.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # Visual Analysis: tableside.com.au
 
 **Captured: 2026-02-10 via Playwright with wheel-based scrolling**

package/DOCS/WEBGPU_STATUS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # WebGPU Backend Status
 
 **Last updated**: 2026-02-15

package/DOCS/XR_BENCHMARKS.md

@@ -1,3 +1,5 @@
+Last reviewed: 2026-02-17
+
 # XR integration benchmarks (draft)
 
 This document captures baseline metrics, targets, and tooling for XR integration work.

package/DOCS/archive/BLUEPRINT_EXECUTION_PLAN_2026-01-07.md

@@ -1,34 +1 @@
-# Blueprint execution plan (2026-01-07)
-
-This execution plan operationalizes the strategic blueprint and defines what each session should deliver. Each session should update `DOCS/archive/SESSION_LOG_2026-01-07.md` with timestamped progress and keep the checklist current.
-
-## Session cadence
-- **Start of session**: review this plan and the strategic blueprint.
-- **During session**: implement the next unchecked items, keep scope tight.
-- **End of session**: update the session log with timestamped outcomes and any blockers.
-
-## Execution checklist
-### Phase 1 — Mathematical foundation
-- [x] Add rotor/matrix utilities for the six rotation planes.
-- [x] Implement stereographic + perspective projection helpers.
-- [x] Add rotation drift/stability tests.
-
-### Phase 2 — Rendering core consolidation
-- [x] Define renderer contracts and resource manager interfaces.
-- [ ] Unify visualization systems behind a shared scene graph.
-- [x] Document GPU disposal patterns and lifecycle hooks.
-
-### Phase 3 — Agentic integration
-- [x] Define MCP tools for create/apply/render workflows.
-- [x] Emit structured telemetry spans and error schemas.
-- [x] Implement CLI JSON output and non-interactive modes.
-
-### Phase 4 — Cross-platform execution
-- [x] Define WASM build target and shared math core strategy.
-- [x] Add Flutter bindings with a batched render command buffer.
-- [x] Prototype WebGPU backend behind feature flags.
-
-### Phase 5 — Production hardening
-- [x] Draft licensing tiers and activation workflow.
-- [x] Add export formats with golden snapshot tests.
-- [x] Document XR integration benchmarks and performance targets.
+Last reviewed: 2026-02-17

package/DOCS/archive/DEV_TRACK_ANALYSIS.md

@@ -1,80 +1 @@
-# Dev track analysis and next steps
-
-> **Archived document:** This file is retained for historical reference in `DOCS/archive/` and is not part of the active docs set.
-
-
-This document summarizes the current development track status, highlights gaps, and proposes the
-next execution steps. It should be updated after each multi-system delivery.
-
-**Last Updated:** 2026-01-30 (v2.0.0)
-
-## Current status snapshot
-- **Math foundation:** rotation utilities, projection clamping, and stability tests are in place.
-- **Renderer lifecycle:** unified contract and lifecycle manager are defined with adapters for the
-  core systems; resource tracking is centralized in the WebGL backend.
-- **Agentic tooling:** MCP/CLI response envelopes are standardized with schema validation.
-- **Docs/ops:** environment setup, CI testing, repo manifest, and project provisioning guides are
-  documented.
-- **WebGPU scaffold:** experimental backend initializes device/context and supports clear-pass render frames.
-- **WebGPU status/testing:** documented current WebGPU state and validation requirements.
-- **v2.0.0 Core Fixes (Phase A):** Quantum color restored, Faceted saturation + audio wired, clickIntensity bug fixed, shader sync tool added.
-- **v2.0.0 SpatialInputSystem:** Universal spatial input with 8 source types, 6 profiles, integrated into VIB3Engine. Decouples "card tilting" from device orientation.
-- **v2.0.0 Creative Tooling (Phase B):** Color presets (22), transitions (14 easings), post-processing (14 effects), parameter timeline (BPM sync).
-- **v2.0.0 Platform Integrations (Phase C):** React, Vue, Svelte component wrappers; Figma plugin; Three.js ShaderMaterial; TouchDesigner GLSL export; OBS mode.
-- **v2.0.0 Advanced Features (Phase D):** WebXR renderer, WebGPU compute shaders, MIDI controller, AI preset generator, OffscreenCanvas worker.
-
-## Completed phases
-| Phase | Status | Deliverables |
-|-------|--------|-------------|
-| Phase 1: Foundation | ✅ Complete | Math, geometry, parameters |
-| Phase 2: Rendering | ✅ Mostly Complete | Contracts, adapters, backends |
-| Phase 3: Agentic | ✅ Complete | MCP, CLI, Telemetry |
-| Phase 4: WebGPU | 🔄 In Progress | Scaffold exists |
-| Phase 5: Hardening | ✅ Complete | 694 tests, XSS prevention |
-| Phase A: Parity & Polish | ✅ Complete | Color/audio/saturation fixes |
-| Phase B: Creative Tooling | ✅ Complete | 4 modules, 3,837 lines |
-| Phase C: Platform Integrations | ✅ Complete | 7 modules, 4,693 lines |
-| Phase D: Advanced | ✅ Complete | 5 modules, 4,262 lines |
-| SpatialInputSystem | ✅ Complete | 1,783 lines, 8 sources, 6 profiles |
-
-## Key gaps to close
-1. **v2.0.0 module test coverage:**
-   - Creative, integrations, and advanced modules need unit/integration tests.
-   - SpatialInputSystem profiles need validation tests.
-2. **WebGPU prototype (Phase 4):**
-   - Confirm feature-flag gating and parity with WebGL backend entry points.
-   - Establish a minimal shader/material pipeline that mirrors the WebGL contract.
-3. **Platform integration validation:**
-   - Test React/Vue/Svelte components with actual framework projects.
-   - Validate Figma plugin with Figma Developer Console.
-   - Test TouchDesigner GLSL export in actual TD environment.
-4. **Cross-platform command buffers:**
-   - Document and validate the render command buffer format for Flutter/WASM integration.
-   - Ensure command buffer batching and lifecycle hooks align with `RendererContract`.
-5. **Telemetry export hardening:**
-   - Add validation for telemetry manifests and scene packs in CI.
-   - Produce golden snapshot tests for core geometries.
-
-## Recommended next steps
-1. **Test coverage for v2.0.0 modules:**
-   - Write Vitest unit tests for SpatialInputSystem (profile loading, input feeding, sensitivity).
-   - Write tests for creative tooling (preset application, transition interpolation, timeline playback).
-   - Add E2E tests for OBS mode and framework components.
-2. **NPM publish preparation:**
-   - Verify all package.json exports resolve correctly.
-   - Test tree-shaking with the creative/integrations/advanced imports.
-   - Run `npm pack --dry-run` to verify published file list.
-3. **WebGPU spike (Phase 4):**
-   - Build a feature-flagged WebGPU backend scaffold in `src/render/backends/`.
-   - Add a minimal triangle pipeline with uniform updates and buffer management.
-4. **Renderer diagnostics:**
-   - Expand `RenderResourceRegistry` stats to include peak usage and per-frame deltas.
-5. **Project automation:**
-   - Provide a scripted `make setup` (or `pnpm setup`) that runs env + project setup steps.
-
-## Risks and mitigation
-- **GPU resource churn:** ensure registry-based disposal is called during renderer swaps.
-- **Numerical drift:** keep normalization utilities and baseline tests running in CI.
-- **Cross-platform divergence:** ensure WebGL and WebGPU share material definitions.
-- **v2.0.0 module breadth:** 18 new files need test coverage before production use.
-- **Framework integration drift:** framework APIs evolve; pin versions in test fixtures.
+Last reviewed: 2026-02-17

package/DOCS/archive/DEV_TRACK_PLAN_2026-01-07.md

@@ -1,42 +1 @@
-# Dev track plan (2026-01-07)
-
-This plan captures the staged work needed to deliver a production-ready agentic telemetry pipeline and export workflow. It is written as a living track plan so future sessions can append progress and maintain consistent architecture decisions.
-
-## North-star goals
-1. Agent-friendly CLI onboarding and help output.
-2. Deterministic telemetry manifest exports with previews and asset hashing.
-3. Clear documentation for automation, QA, and CI workflows.
-
-## Architecture anchors
-- **Telemetry pipeline**: `tools/telemetry/manifestPipeline.js` is the single source of truth for manifest normalization and hashing.
-- **Preview generation**: `js/core/telemetry-director.js` generates previews (renderer-backed or placeholders) and passes them into manifests.
-- **Docs hub**: `DOCS/` is the canonical location for workflow documentation (onboarding, telemetry, control references).
-
-## Planned track (phased)
-### Phase 1 — Onboarding + documentation hardening
-- Publish an agentic CLI onboarding guide with tool requirements, commands, and telemetry workflow steps.
-- Update README references so new onboarding docs are discoverable.
-- Extend telemetry docs with explicit CLI integration guidance and export flow notes.
-- Add a lightweight knowledge-check template that validates geometry/control comprehension without blocking execution.
-
-### Phase 2 — Agentic workflow hooks
-- Add CLI wrappers for telemetry export flows (pack selection, preview generation, manifest hashing).
-- Emit summaries designed for CI cache validation and diffing.
-- Provide optional validation hooks for manifest/preview consistency.
-
-### Phase 3 — Quality and verification
-- Add lint/test targets for telemetry outputs if applicable.
-- Document CI steps for telemetry export validation.
-- Add golden snapshot routines for preview images when the pipeline stabilizes.
-
-## Risks and mitigations
-- **Risk**: Hash drift due to unstable object serialization.  
-  **Mitigation**: Keep stable hashing in `manifestPipeline.js` and avoid non-deterministic fields.
-- **Risk**: Preview generation inconsistency across runtimes.  
-  **Mitigation**: Maintain browser-safe fallback encoding and ensure renderer contracts are documented.
-
-## Deliverables checklist
-- [ ] CLI onboarding doc is complete and linked in README.
-- [ ] Telemetry docs include export integration steps.
-- [ ] Agentic CLI support documented or implemented.
-- [ ] CI guidance includes telemetry hashes and preview artifacts.
+Last reviewed: 2026-02-17