refactor(scripts): migrate scripts to effect and effect-platform

[Rel1cx]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• Test
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• I have added a convincing reason for adding this feature, if necessary

Other information

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
eslint-react	Ready	Preview	Comment	Aug 22, 2025 6:46pm

[Copilot]

Pull Request Overview

This PR migrates the scripts directory from standard Node.js APIs to the Effect ecosystem, specifically using effect, @effect/platform, and @effect/platform-node libraries for better error handling, composability, and functional programming patterns.

• Replaces synchronous file system operations with Effect-based asynchronous equivalents
• Updates import statements to use more specific module imports from Effect platform packages
• Modernizes the codebase to leverage Effect's composition and error handling capabilities

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
scripts/verify-lockfile.ts	Simplifies imports and replaces custom layer composition with NodeContext.layer
scripts/update-website.ts	Complete rewrite from imperative Node.js fs operations to Effect-based functional approach with proper error handling
scripts/update-version.ts	Updates to use NodeContext.layer instead of NodeFileSystem.layer
scripts/update-readme.ts	Converts simple file copy operation to Effect-based implementation with directory creation

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}