Update Effect Vendored Assets
When to Use
Refresh Effect vendored assets with pinned sources, retained notices, deterministic generation and verified consumer impact.
Workflow
Find the asset's owner, generator, immutable source and all shipped consumers. Check licenses, embedded notices and source-map attribution. Change the generator or exact import source, then repeat the generation to establish stability. Audit the full diff for code, URLs, runtime fetches, encoding, size and dependency effects. Run focused consumer checks, compare relevant bundle bytes and apply repository changeset rules if consumers are affected.
Example
Refresh a pinned browser asset and prove regenerated bytes are stable and its notice still appears in the distributed package.
Limitations
Requires the relevant Effect workspace and its versioned tools. Use local project policy and authorized fixtures. Results cover only the checked packages and environments.
Bundled resources
Use the bundled local references for the applicable branch of the workflow: browser assets. Run commands against the target Effect workspace.
Source
Adapted from the pinned skill tree. See the MIT license.
This snapshot of Effect v4 is vendored by Local Studio.