howone 0.1.50 → 0.1.51

package/templates/vite/.howone/skills/web-shader-extractor/references/qa-failure-policy.md

@@ -1,100 +0,0 @@
-# QA and Failure Policy
-
-Validation happens twice:
-
-1. Source -> Baseline: does the local baseline match the target evidence?
-2. Baseline -> Editable: did projectization avoid regression?
-
-## Fixed Conditions
-
-Keep these identical across comparisons:
-
-- viewport
-- DPR
-- browser/backend
-- fixed time or selected frame
-- pointer, scroll, resize, route state
-- random seed when controllable
-- background, alpha, and DOM composite
-- crop and time point
-
-## Validation Levels
-
-1. Build: dependencies and assets resolve
-2. GPU: shaders/pipelines compile and link
-3. Structural: pass, FBO, program, resource, and state match Manifest
-4. Visual: color, composition, alpha, edges
-5. Temporal: multi-frame rhythm, phase, randomness
-6. Interaction: pointer, scroll, resize, route
-7. Regression: editable project vs baseline
-
-## Minimum Source -> Baseline Protocol
-
-Minimum verification requires more than one static screenshot:
-
-1. Compare at the initial frame or a fixed time.
-2. Compare at a later frame.
-3. Compare after one relevant interaction if the target is interactive.
-4. For scroll-coupled effects, compare at top, middle, and target section.
-5. For route-coupled effects, compare at the route transition or persistent renderer state.
-6. Always record viewport, DPR, browser/backend, crop, time, pointer, scroll, and route state.
-
-Every comparison must save or reference:
-
-- source image or frame evidence
-- baseline image or frame evidence
-- diff image, numeric comparison, or written visual difference record
-
-If the environment cannot produce image diffs, write a structured visual difference record and keep that limitation in `known-gaps.md`. A single matching first frame is not enough for `BASELINE_VERIFIED`.
-
-## Truth Audit
-
-Run this audit before marking the final state:
-
-- Every implementation-critical fact in `replay-manifest.json` has direct evidence or a `PARTIAL` / `GUESS` label.
-- Leaf facts and wiring facts were checked separately. A verified shader or config value does not prove the active render graph, timing, coordinate space, or input route.
-- Any parameter changed to improve appearance is recorded as `GUESS` unless source/runtime/frame evidence proves it.
-- Any mismatch is routed to the upstream unknown that explains it. Do not cover mismatches with tuning.
-- Known gaps state the blocking unknown and the evidence needed to resolve it.
-
-The QA report is the gate artifact for `BASELINE_VERIFY` and `PROJECT_VERIFY`. Do not mark either gate passed while any required row is `pending`, any P0/P1/P2 issue is open, or the final status is absent.
-
-## Severity
-
-- `P0`: cannot run, cannot render, or route impossible
-- `P1`: wrong target, render graph, composition, or main interaction
-- `P2`: visible timing, color, alpha, responsive, or input drift
-- `P3`: polish or performance issue that does not block delivery
-
-Automatically loop only P0/P1/P2.
-
-## Failure Routing
-
-| Symptom | Category | Return |
-|---|---|---|
-| wrong canvas or missing shared surface | target | `SURFACE_ATTRIBUTION` |
-| missing shader/resource/input | evidence | `SOURCE_TRACE` |
-| wrong FBO, time, coordinates, color model | replay model | `CAPTURE_MINIMUM_TRUTH` |
-| dependency, path, or code error | implementation | `RAW_REPLAY` |
-| browser, GPU, CORS, or context issue | environment | `BASELINE_RUN` |
-| evidence complete but implementation visually wrong | fidelity implementation | `RAW_REPLAY` |
-
-Do not route all mismatches into parameter tuning.
-
-## Failure Signatures
-
-Use these signatures to classify mismatches before editing values.
-
-| Symptom | Likely Root Cause |
-|---|---|
-| overall too bright or color-shifted | color space, tone mapping, premultiplied alpha |
-| animation slowly drifts | seconds vs frames, delta, time origin |
-| vertical flip | UVs, render target orientation, SDF/image coordinate system |
-| black blocks or missing layers | FBO, clear, blend, depth, missing resources |
-| noise differs | RNG, precision, filtering, noise implementation |
-| edge softness differs | DPR, AA, derivatives, SDF smoothing |
-| scroll position drifts | DOM-canvas binding or scroll normalization |
-| route flicker | renderer lifecycle, resource cache, route persistence |
-| pointer response offset | canvas CSS transform, DPR, page scroll, coordinate normalization |
-
-Confirm the category with evidence before changing implementation constants.

package/templates/vite/.howone/skills/web-shader-extractor/references/recon-kernel.md

@@ -1,206 +0,0 @@
-# Recon Kernel
-
-The Recon Kernel is the core workflow. It prevents scope drift into website cloning or unrelated bundle analysis.
-
-## Kernel Loop
-
-```text
-LIST        list candidate surfaces and rank them
-ATTRIBUTE   prove which surfaces contribute to the requested target visual
-LOCK        bind target surface group to context, owner, and source clues
-TRACE       choose the lowest-cost authoritative evidence route
-REPLAY      capture required facts and build a local baseline
-```
-
-## State Flow
-
-```text
-INTAKE
--> CAPABILITY_SNAPSHOT
--> QUICK_SCOUT
--> SURFACE_ATTRIBUTION
--> TARGET_LOCK_GATE
--> SCOPE_CHECK
--> TRACE_ROUTE_SELECT
--> SOURCE_TRACE
--> CAPTURE_MINIMUM_TRUTH
--> REPLAY_READY_GATE
--> RAW_REPLAY
--> BASELINE_RUN
--> BASELINE_VERIFY
--> BASELINE_VERIFIED
--> PROJECTIZE
--> PROJECT_VERIFY
--> OPTIONAL_LITE
--> PACKAGE
-```
-
-Use these branches:
-
-```text
-TARGET_LOCK_GATE
-  - failed/provisional -> REFINE_SCOUT loop
-  - attributed -> owner/backend/source probe, then return to TARGET_LOCK_GATE
-  - locked -> SCOPE_CHECK
-
-REPLAY_READY_GATE
-  - blocking unknowns remain -> SOURCE_TRACE / CAPTURE_MINIMUM_TRUTH loop
-  - ready -> RAW_REPLAY
-
-BASELINE_VERIFY
-  - target error -> SURFACE_ATTRIBUTION
-  - evidence gap -> SOURCE_TRACE
-  - replay model error -> CAPTURE_MINIMUM_TRUTH / RAW_REPLAY
-  - implementation error -> RAW_REPLAY
-  - environment error -> BASELINE_RUN
-  - passed -> BASELINE_VERIFIED
-```
-
-Use `REFINE_SCOUT` when target lock fails or remains provisional. Use the failure routes in `references/qa-failure-policy.md` when verification fails.
-
-## Initial Protocol
-
-Perform these actions first and persist artifacts under the output directory:
-
-1. Record canonical URL, route, viewport, DPR, browser/backend, and a source screenshot.
-2. Enumerate visible canvases in the main page and iframes. Record OffscreenCanvas, Worker, WebGPU, video, and DOM mask/clip/sticky clues.
-3. Sample two or three frames per plausible surface; estimate visual coverage, temporal activity, z-order, and interaction response.
-4. For top candidates, run short reversible ablation tests: hide, opacity/freeze, transform, or output replacement. Record which target pixels or behaviors disappear.
-5. Probe minimal pointer, scroll, and resize interactions to identify coupling.
-6. Identify the target surface group context, owner thread/frame/worker, and creation source. If needed, reload once with a preload probe.
-7. Accept platform, framework, runtime, and source evidence only when it is bound to the target surface group.
-8. Select exactly one next evidence path and write `scout-card.json`.
-9. Before `TARGET_LOCKED`, do not download or deobfuscate full bundles. Use source maps, public structured definitions, or narrow bundle slices only when they resolve the next unknown.
-
-## Gate Semantics
-
-`TARGET_ATTRIBUTED` means visual causality is proven for a surface group.
-Context, owner, framework, or source may still be incomplete.
-Only owner/backend/source probes tied to `nextProbe` are allowed.
-
-`TARGET_LOCKED` means the target is a surface group.
-Visual attribution exists.
-Context and owner are known or reliably located.
-Source/framework evidence is target-bound.
-Effect boundary is known.
-One trace route is selected.
-Alternatives are recorded.
-
-`REPLAY_READY` means no blocking unknowns remain, or every remaining blocker has an explicit fallback and fidelity tier.
-Time/input rules, output color/alpha/composite, critical resources, and replay route are sufficient for the first local baseline.
-
-`BASELINE_VERIFIED` means the baseline starts independently.
-Main composition/layers are correct.
-Animation and key interactions are checked.
-Render graph/output composite has no P0/P1/P2 issue.
-Known gaps are documented instead of masked by manual tuning.
-
-## Gate Artifact Contract
-
-Gate artifacts are transition guards.
-A gate is not passed until the required artifact exists, uses the bundled template shape, has no placeholders in gate-critical fields, and points to persisted evidence or a documented external blocker.
-
-| Gate | Required artifact | Minimum pass condition |
-|---|---|---|
-| `TARGET_LOCK_GATE` | `scout-card.json` | `lockStatus=locked`; `targetSet` non-empty; attribution evidence referenced; context and owner known; alternatives recorded; primary trace route selected. |
-| `REPLAY_READY_GATE` | `replay-manifest.json` | replay route and fidelity tier set; target surfaces and runtime owner/backend recorded; facts labeled; no blocking unknowns without fallback and downgrade. |
-| `BASELINE_VERIFY` | `qa-report.md` plus `replay-manifest.json` | Source -> Baseline checks have evidence; P0/P1/P2 issues closed or routed back; fact audit complete; final status set. |
-| `PROJECT_VERIFY` | `qa-report.md` | Baseline -> Editable regression checks have evidence; P0/P1/P2 regressions closed; projectization did not change replay route or fidelity tier silently. |
-
-Evidence checklist entries must be structured objects, not prose strings:
-
-```json
-{
-  "status": "unknown",
-  "allowedStatus": ["passed", "blocked", "unknown"],
-  "evidenceId": "ev-001",
-  "path": "evidence/scout/ablation-surface-1.json",
-  "truth": "GUESS",
-  "allowedTruth": ["SOURCE", "PARTIAL", "GUESS"],
-  "notes": ""
-}
-```
-
-If a required artifact is missing or incomplete, keep the current state.
-Set `run-state.json.nextAction` to create or repair that artifact.
-Do not replace artifact fields with prose in the final answer.
-
-`run-state.json.gateStatus` copies the artifact status. It is not a separate evidence source. Update it only after the corresponding gate artifact passes.
-
-## Working Rule
-
-At every step, write down the unknown being reduced. A valid next action has this shape:
-
-```text
-state: SURFACE_ATTRIBUTION
-unknown: whether canvas#hero or iframe[0] owns the target distortion
-action: hide/freeze both candidates for one frame window and compare target crop
-expected evidence: ablation impact by surface
-```
-
-If the action has no target unknown, reject it.
-
-## Evidence Chain
-
-Prefer evidence in this order when it is target-bound:
-
-1. Public structured definition or source for the target embed/effect.
-2. Runtime object directly owning the target canvas/context.
-3. Source map or readable module that creates the target surface.
-4. GPU/frame capture tied to the target context.
-5. Narrow bundle slice selected by stack, call stack, or target IDs.
-6. Inference from minified code or visual behavior.
-
-Do not promote global framework hints to conclusions. They become conclusions only after `references/target-lock.md` criteria pass.
-
-## Artifact Discipline
-
-Keep large facts out of the conversation:
-
-- screenshots and crops under `evidence/screenshots/`
-- DOM and style snapshots under `evidence/dom/`
-- network index under `evidence/network/`
-- frame captures under `evidence/gpu/`
-- runtime probes under `evidence/runtime/`
-- source slices under `evidence/source/`
-
-Reference them from `scout-card.json`, `replay-manifest.json`, and `qa-report.md`.
-
-## Autonomy And State
-
-Default to autonomous execution. Ask only for product scope changes or external access/permission blockers.
-
-```text
-Observe
--> Compare against current Gate / Manifest
--> Classify failure or unknown
--> Choose the lowest-cost action that reduces an unknown
--> Execute
--> Persist evidence and state
--> Measure progress
-```
-
-"Try again" is not a valid action unless something changes.
-
-A retry must change at least one:
-
-- tool
-- injection timing
-- browser or GPU backend
-- target surface
-- interaction state
-- viewport
-- evidence source
-- bundle slice
-- root-cause hypothesis
-
-Default budgets:
-
-- same strategy: 2 attempts
-- capture strategy categories: 3
-- P0/P1/P2 repair rounds: 6
-- plateau: 2 consecutive rounds with no reduction in blocking unknowns and no QA improvement
-
-Persist `.web-shader-extractor/run-state.json`.
-Include state, gate status, strategy, attempts, target set, unknowns, evidence index, artifacts, budgets, plateau, next action, replay tier, and QA.
-Use `templates/run-state.json` as the starting schema.

package/templates/vite/.howone/skills/web-shader-extractor/references/replay-policy.md

@@ -1,145 +0,0 @@
-# Replay Policy
-
-Replay policy covers the `REPLAY_READY` gate, first local baseline, and stack choice.
-The goal is to match recorded source behavior with the fewest new assumptions.
-
-## Replay Ready Contract
-
-Record before entering `RAW_REPLAY`:
-
-- replay route: `SOURCE_REPLAY`, `PIPELINE_REPLAY`, or `BEHAVIOR_REBUILD`
-- fidelity tier and known limits
-- blocking, important, deferred, and external unknowns
-- fallback for any unresolved blocking unknown
-- truth labels for implementation-critical leaf and wiring facts
-
-Do not mark `REPLAY_READY` because the capture appears plausible.
-`SOURCE` leaf facts do not imply `SOURCE` wiring.
-If pass order, input coupling, time units, or output composite are still inferred, label those facts `PARTIAL` or `GUESS`.
-Keep inferred gate facts blocking or record an explicit fidelity downgrade.
-
-Proceed to `RAW_REPLAY` only when `blockingUnknowns` is empty, or every blocker has an explicit fallback with a recorded fidelity downgrade.
-Move important unknowns into QA focus.
-
-Do not enter `RAW_REPLAY` until `replay-manifest.json.gateDecision.replayReady` is true.
-Its required evidence checklist must contain structured evidence items.
-If the baseline depends on a fallback, record the fallback and downgrade in the manifest before implementation starts.
-
-If a local baseline uses fitted values to run, those facts are not source replay.
-Keep the values labeled `GUESS`.
-Place them in `known-gaps.md`.
-Route QA toward the missing source/runtime evidence.
-
-## Replay Routes
-
-Choose and record one replay route in `replay-manifest.json`:
-
-- `SOURCE_REPLAY`: public structured definitions, original source, source maps, readable framework modules, platform exports, or configs. Prefer this when available.
-- `PIPELINE_REPLAY`: shader/WGSL, runtime objects, GPU frame capture, draw/pass/resource/state, input, and timing trace. Use when source is incomplete but runtime facts are sufficient.
-- `BEHAVIOR_REBUILD`: partial source plus observed behavior. This is the last fallback and must be labeled approximate.
-
-Do not describe a behavior rebuild as source extraction. Projectization does not change the baseline fidelity tier.
-
-## Stack Selection
-
-Use native WebGL/WebGL2 when the target is:
-
-- fullscreen shader
-- small number of passes
-- no complex scene graph
-- no PBR/material lifecycle
-- no GPGPU lifecycle tied to a framework
-- conversion facts are complete
-
-Use the source stack when:
-
-- the framework/platform version is known or closely bounded
-- source, source map, platform definition, or runtime objects are complete
-- behavior depends on material systems, node graphs, post-processing, scene graph, resource lifecycle, or renderer quirks
-- retaining the source stack reaches an evidence-matched baseline with fewer assumptions
-
-Project-lite is a post-verification optimization. It is not a substitute for the verified baseline.
-
-## Raw Replay Priorities
-
-Raw replay creates the first local baseline with the least rewriting:
-
-1. Preserve recorded source behavior and data shape.
-2. Keep original constants, shader code, pass order, timing, resources, and color model.
-3. Make it run locally with a minimal launch path.
-4. Document known gaps rather than masking them with tuning.
-
-Use the source stack when it adds fewer assumptions. Use native WebGL/WebGL2 only when conversion does not add uncertainty.
-
-## Baseline Directory
-
-Output artifacts should be layered:
-
-```text
-output/
-|-- capture-baseline/
-|-- editable-project/
-|-- project-lite/
-|-- scout-card.json
-|-- replay-manifest.json
-|-- qa-report.md
-|-- extraction-report.md
-|-- known-gaps.md
-`-- .web-shader-extractor/run-state.json
-```
-
-```text
-output/capture-baseline/
-|-- index.html
-|-- src/
-|-- assets/
-|-- README-run.md
-`-- evidence-links.md
-```
-
-## No Compensation Tuning
-
-Do not change brightness, speed, offsets, noise scale, fresnel multipliers, SDF epsilons, or color values without evidence.
-If the result differs, classify the root cause: color, timing, coordinates, FBO graph, resource, state, input, or environment.
-
-Once baseline verification starts, do not overwrite it for projectization.
-Fix baseline in place only for baseline errors.
-Create `editable-project/` separately for refactors.
-
-Use the bundled templates as starting schemas, not free-form notes:
-`templates/scout-card.json`, `templates/replay-manifest.json`, `templates/run-state.json`, `templates/qa-report.md`, `templates/known-gaps.md`, and `templates/extraction-report.md`.
-Fill every placeholder with target-bound evidence or record the gap.
-
-## Projectization
-
-Projectization starts only after `BASELINE_VERIFIED`.
-
-Default output:
-
-```text
-output/editable-project/
-|-- package.json or importmap-based index.html
-|-- src/
-|-- assets/
-|-- README.md
-`-- qa/
-```
-
-Projectization may modularize source, add parameter interfaces, improve naming, or introduce a build pipeline.
-It must not silently change the replay route or fidelity tier.
-
-Run Baseline -> Editable validation after projectization:
-
-- same viewport, DPR, browser/backend
-- same fixed time/frame
-- same pointer/scroll/resize state
-- same crop and background/composite
-
-Any P0/P1/P2 regression returns to `PROJECTIZE`, not to target scouting unless the regression reveals the baseline was wrong.
-
-Create `project-lite/` only when simplification is supported by evidence and independently verified.
-If it fails, remove or mark it experimental.
-Do not downgrade the verified editable project.
-
-Do not create `editable-project/` as the primary deliverable until `qa-report.md` records Source -> Baseline as passed or passed with documented gaps.
-Do not mark `DONE_PROJECTIZED` until Baseline -> Editable regression is recorded in `qa-report.md`.

package/templates/vite/.howone/skills/web-shader-extractor/references/shaders-com.md

@@ -1,212 +0,0 @@
-# shaders.com / TSL Adapter
-
-Use this adapter only after the target surface group has been attributed to a shaders.com renderer or a shaders.com public definition.
-Treat versions, keys, mappings, and backend choice as runtime facts to verify on the current target.
-
-Stability: volatile. Treat endpoint names, variable names, keys, component IDs, short-code mappings, and backend choices as hints until verified on the current target.
-
-shaders.com is a shader design tool. Observed builds use Nuxt.js, Three.js TSL, and Supabase. Verify the exact Three.js version and WebGPU/WebGL backend from target runtime or current bundle evidence.
-
-## Adapter Interface
-
-- `detect(context)`: target canvas has shaders.com renderer evidence, target route/API returns the matching preset/collection definition, or runtime owner binds the renderer to target.
-- `preferredEvidence(context)`: public collection/preset definition, current runtime config, and target-bound Three.js/TSL module route.
-- `capture(context)`: component tree, decoded definition, TSL node source, assets/SDFs, renderer backend, time/input rules, color/output model.
-- `replay(context)`: `SOURCE_REPLAY` when definition and TSL source are sufficient; `PIPELINE_REPLAY` when runtime/capture facts are sufficient but source is incomplete.
-- `validationHints(context)`: SDF Y flip, linear color pipeline, TSL timer rules, Glass parameter fidelity, WebGPU vs WebGL backend.
-- `fallback(context)`: target-bound source-map or module slice, frame capture, then behavior rebuild with explicit downgrade.
-
-## Recognition Signals
-
-- URL pattern: `shaders.com/collection/{slug}/{presetId}` or `shaders.com/preset/{id}`
-- Canvas hints such as `data-renderer="shaders"` plus `data-engine`; verify the version dynamically
-- Nuxt.js paths such as `_nuxt/`
-- Clerk authentication on the site
-- Supabase storage URLs such as `data.shaders.com/storage/v1/`
-
-## Architecture Differences
-
-Compared with Unicorn Studio:
-
-- It commonly uses Three.js TSL node graphs rather than raw GLSL source.
-- It has multiple component types, each potentially backed by a TSL `fragmentNode`; verify the current count and names from the current bundle.
-- Definition data may be XOR + base64 encoded.
-- Components can be nested; for example a Glass component may contain child effects.
-
-## Data Acquisition
-
-### API Endpoints
-
-```bash
-# Collection variant with encoded definition; public when accessible without auth.
-curl -s "https://shaders.com/api/collections/{slug}/{variantId}"
-
-# Preview API with encoded definition and possible watermark injection.
-curl -s "https://shaders.com/api/preview/preset/{presetId}"
-
-# Nuxt payload, usually metadata only rather than shader definition.
-curl -s "https://shaders.com/collection/{slug}/{id}/_payload.json"
-```
-
-### Definition Decoding
-
-Definitions may use XOR + base64 encoding with route-specific keys.
-
-1. Website API (`/api/collections/`):
-   - Extract the obfuscation key from the current Nuxt runtime config. Do not reuse fixed keys from old samples.
-   - Component/property names may use short codes such as `C52` for `Plasma` or `p06` for `angle`.
-   - Decode with `JSON.parse(XOR(base64decode(encoded), keyBytes))`.
-   - Restore readable names with the current code-to-name mapping table.
-
-2. Preview API (`/api/preview/`):
-   - Verify the key and response shape from the current public frontend code.
-   - It may use readable property names directly.
-   - It may inject a watermark `ImageTexture` component.
-
-### Code Mapping Table
-
-Extract component and property short-code mappings from the current JS bundle. Do not assume component counts, sorting, or numeric IDs are stable across releases.
-
-## Known Failure Cases
-
-### Y-Axis Flip
-
-Observed shaders.com samples show a Y flip for SDF textures and UVs.
-
-SDF binaries (`.bin`) often use image coordinates where Y=0 is at the top, while WebGL texture coordinates use Y=0 at the bottom. Loading them directly can flip shapes vertically.
-
-```glsl
-// Wrong: direct sampling.
-float sdf = texture(tSDF, shapeUV).r;
-
-// Correct for known flipped SDFs: flip Y.
-vec2 sdfUV = vec2(shapeUV.x, 1.0 - shapeUV.y);
-float sdf = texture(tSDF, sdfUV).r;
-
-// The Y component of the gradient may also need sign inversion.
-float dSdy = -(texture(tSDF, sdfUV - vec2(0, eps)).r - sdf) / eps;
-```
-
-Component definitions may also use DOM coordinates where Y=0 is at the top. For Glass-style shaders, verify whether `center.y` must be flipped as `center.y = 1.0 - center.y`.
-
-### SDF Binary Format
-
-Known samples use:
-
-- 512 x 512 Float32 single-channel data
-- 1,048,576 bytes: `512 * 512 * 4`
-- signed distance values, negative inside and positive outside
-- raw values without `* 2.0 - 1.0` remapping
-- `OES_texture_float_linear` for linear filtering when needed
-
-WebGL2 loading pattern:
-
-```js
-gl.texImage2D(gl.TEXTURE_2D, 0, gl.R32F, 512, 512, 0, gl.RED, gl.FLOAT, data);
-```
-
-## Component Table
-
-| Category | Components | Complexity |
-|---|---|---|
-| Texture | Plasma, Godrays, SimplexNoise, LinearGradient, RadialGradient | medium |
-| Shape | Glass, Blob, Circle, Ring, Star, RoundedRect, Polygon | high |
-| Distortion | WaveDistortion, ChromaticAberration, Liquify, Twirl, Bulge | low to medium |
-| Stylization | FilmGrain, Halftone, Ascii, Dither, Glow, Bloom | low to medium |
-| Post-processing | Blur, ProgressiveBlur, BrightnessContrast, HueShift | low |
-
-## Render Pipeline
-
-Typical target-bound evidence may reveal:
-
-```text
-Three.js TSL renderer; verify version dynamically
-|- prefers WebGPU, falls back to WebGL
-|- orthographic camera plus one fullscreen quad
-|- component tree composited bottom to top
-|- components with children capture child content through RTT
-|- blend mode implemented with custom blend functions
-`- Glass path: SDF evaluation -> gradient normal -> refraction -> chromatic aberration -> blur -> tint -> highlight -> Fresnel -> composite
-```
-
-## Replay Strategy
-
-1. TSL cannot be copied as raw GLSL; translate it or replay it through the source stack.
-2. Extract the target-bound TSL `fragmentNode` from the current JS bundle when source replay requires it.
-3. Convert the component tree into a multi-pass FBO graph.
-4. Validate SDF Y orientation against the target.
-5. Glass components have many parameters; keep source multipliers exact.
-
-## Color Space
-
-Known shaders.com / Three.js TSL samples commonly use a linear workflow, but the current target must still be verified from renderer, runtime, or source evidence.
-
-- Hex colors such as `#2c2c42` are commonly sRGB values.
-- TSL `color()` commonly converts sRGB to linear.
-- Whether intermediate FBOs store linear values must be verified from the target render graph.
-- The final output encoding stage must be verified from target renderer configuration.
-
-Example for a common path:
-
-```glsl
-// Common path: sRGB hex -> linear at definition time.
-vec3 colorA = pow(vec3(0.173, 0.173, 0.259), vec3(2.2));  // #2c2c42
-
-// Intermediate passes and final output encoding must follow target evidence.
-fragColor = vec4(pow(color.rgb, vec3(1.0 / 2.2)), color.a);
-```
-
-Error case: applying a fixed gamma correction in intermediate or final passes without verifying the target renderer's color configuration.
-
-## Parameter Fidelity
-
-Do not tune parameters manually. Match the formulas and multipliers from the TSL translation:
-
-```text
-Original TSL multiplier       GLSL must use
-aberration * 0.06             not 0.12
-fresnelSoftness * 0.06        not 0.12
-fresnel = 0.17                not 0.4
-SDF gradient eps = 0.01       not 0.005
-```
-
-If the visual result does not match, inspect:
-
-1. color space, especially sRGB/linear confusion
-2. noise implementation differences such as Perlin vs `mx_noise_float`
-3. time base
-4. FBO/component-tree order
-
-Do not change multipliers to mask a mismatch. That may fit one preset while breaking other parameter combinations.
-
-## TSL Time Convention
-
-`timerLocal(speed)` increments by `speed` units per second. Replay as `uTime = seconds * speed`, then apply any component-specific multiplier inside the shader.
-
-| Component | speed parameter | shader multiplier | effective rate per second |
-|---|---:|---:|---:|
-| Plasma | 2 | 0.125 | 0.25 |
-| Godrays | 0.7 | 0.2 | 0.14 |
-| WaveDistortion | 0.8 | 0.5 | 0.4 |
-| FilmGrain | none | none | static |
-
-## TSL To GLSL Identifier Mapping
-
-These mappings are examples from one observed bundle and may change. Extract them dynamically from the current build.
-
-| Local name | TSL function | GLSL |
-|---|---|---|
-| `C` / `z` | `vec4()` | `vec4` |
-| `x` / `D` | `vec2()` | `vec2` |
-| `q` / `N` | `vec3()` | `vec3` |
-| `P` / `J` | `resolution` | `u_resolution` |
-| `A` / `$` | `uv` | `vUv` |
-| `se` / `Oe` | `sin()` | `sin` |
-| `W` / `I` | `cos()` | `cos` |
-| `ne` | `mix()` | `mix` |
-| `D` | `smoothstep()` | `smoothstep` |
-| `fe` | `clamp()` | `clamp` |
-| `ar` | `mx_noise_float()` | `perlinNoise3D()` candidate |
-| `dr` / `Gt` | `timerLocal()` | `u_time * speed` |
-| `Me` / `wt` | `rtt()` | FBO pass |
-| `Ce` | `renderOutput()` | `fragColor` |