@viji-dev/core 0.5.4 → 0.5.6

package/dist/index.d.ts

@@ -218,6 +218,14 @@ export declare class AudioSystem {
     private lastPhaseLogTime;
     private onsetLogBuffer;
     private debugMode;
+    /**
+     * One-way lifecycle flag flipped at the top of `resetAudioState()`.
+     * Gates re-entry into `ensureAudioContext()` and the public stream-mutation
+     * entry points so an in-flight async caller (e.g. a worker RPC firing
+     * mid-teardown) cannot resurrect a fresh `AudioContext` after destroy
+     * has already nulled the field. AudioSystem is single-use after reset.
+     */
+    private destroyed;
     private diagnosticLogger;
     private onsetDetection;
     private essentiaOnsetDetection;
@@ -419,8 +427,13 @@ export declare class AudioSystem {
     /**
      * Reset all audio state (called when destroying).
      * Disconnects all channels, closes AudioContext, resets all modules.
+     *
+     * Returns a Promise that resolves once `AudioContext.close()` has fully
+     * transitioned the context to `closed`. Callers tearing the system down
+     * (e.g. `VijiCore.destroy()`) MUST await this; otherwise Blink keeps the
+     * context alive in `Pending activities` and leaks ~4 MB per cycle.
      */
-    resetAudioState(): void;
+    resetAudioState(): Promise<void>;
     /**
      * Add an additional audio stream (lightweight analysis, no beat detection).
      * @param streamIndex Global stream index (from VijiCore: AUDIO_ADDITIONAL_BASE + n or AUDIO_DEVICE_BASE + n)
@@ -442,9 +455,12 @@ export declare class AudioSystem {
     getChannelCount(): number;
     /**
      * Record a tap for the specified instrument onset.
-     * `options.skipRecognition` retains visual envelope + session timing but
-     * bypasses the recognition pipeline — used by host-side relay of forwarded
-     * tap messages where another core is doing the authoritative recognition.
+     * `options.skipRecognition` opts the tap out of the recognition pipeline
+     * only (no IOI accumulation, no `tryRecognizePattern`, no `applyPattern`).
+     * Mode still flips `'auto' → 'tapping'` so the visual envelope and
+     * audio-event filter run; only the pattern-detection pipeline is bypassed.
+     * Used by host-side relay of forwarded tap messages where another core
+     * owns the authoritative recognition.
      */
     tapOnset(instrument: InstrumentType, options?: {
         skipRecognition?: boolean;
@@ -2251,7 +2267,7 @@ declare type TrackingState = 'TRACKING' | 'LOCKED' | 'BREAKDOWN' | 'LOST';
 /** Returned by `on*` listener registration calls; invoke to unsubscribe. */
 export declare type Unsubscribe = () => void;
 
-export declare const VERSION = "0.5.4";
+export declare const VERSION = "0.5.6";
 
 /**
  * Real-time video API: drawable frame, dimensions, and the source-side
@@ -3023,13 +3039,17 @@ export declare class VijiCore {
              * First tap switches the instrument from auto to tapping mode.
              * If a repeating pattern is recognized, it continues after tapping stops.
              *
-             * `options.skipRecognition: true` keeps the visual envelope and session
-             * timing but bypasses pattern recognition entirely (no IOI accumulation,
-             * no mode transition, no `applyPattern`, no `handlePatternTap`). Use
-             * this when relaying tap messages from another instance that owns the
-             * authoritative recognition (e.g. host receiving forwarded controller
-             * taps over WebRTC). The receiving core's mode is then driven only by
-             * `importSessionState` from the authoritative sender.
+             * `options.skipRecognition: true` opts the tap out of the **recognition
+             * pipeline only** — no `tapIOIs` accumulation, no `tryRecognizePattern`,
+             * no `applyPattern`, no `handlePatternTap`. Mode still flips
+             * `'auto' → 'tapping'` on the first tap of a session (and back to
+             * `'auto'` on the 5s timeout). The mode flip is load-bearing for
+             * `processFrame`'s drain of `pendingTapEvents`, the audio-event filter
+             * that prevents music+tap doubling, and `onModeChange` consumers. Use
+             * `skipRecognition` when relaying tap messages from another instance
+             * that owns the authoritative recognition (e.g. host receiving
+             * controller taps over WebRTC); the receiving core's pattern is then
+             * driven only by `importSessionState` from the authoritative sender.
              *
              * The `MIN_TAP_INTERVAL_MS` debounce still applies regardless of the
              * `skipRecognition` flag.

package/dist/index.js

@@ -1,4 +1,4 @@
-import { A, V, a, b } from "./index-_PbbZgmh.js";
+import { A, V, a, b } from "./index-Yg6_UX8C.js";
 export {
   A as AudioSystem,
   V as VERSION,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@viji-dev/core",
-  "version": "0.5.4",
+  "version": "0.5.6",
   "description": "Universal execution engine for Viji Creative scenes",
   "type": "module",
   "main": "./dist/index.js",