shader-retire

Archiving shader files involves relocating .json, .glsl, .hlsl, and iChannel texture files to a legacy/shaders_retired/ directory. This cleanly removes shaders from active development while preserving them in long-term storage.

Managing the shader lifecycle for retired assets involves relocating unused shader files to a designated legacy archive. This keeps the project organized by separating active development files from preserved shaders.

Automated regeneration executes build scripts like tools/shader_bundle.ps1 and tests/test.ps1 after archiving shaders. This updates shader bundles and resource files to accurately reflect the relocated assets and validate the changes.

Shader archiving handles texture files automatically by using the shader's JSON metadata. It identifies and relocates associated iChannel texture files alongside the main shader code to the legacy directory.

You need PowerShell scripts to update shader bundles post-archival. Executing tools/shader_bundle.ps1 and tests/test.ps1 is required to regenerate build artifacts and validate the project after moving shader files.

Move shaders to long-term storage when they are no longer actively developed but need to be preserved. This maintains project organization without permanently losing the shader code and associated assets.