chore: depend on the workspace @effect-app/cli

[omegent-app]

Summary

Point the root devDependency @effect-app/cli at the workspace package (workspace:*) instead of the published 2.1.0-beta.35 tarball.

That package now runs from TypeScript source. Node 24 strips types by default, the workspace bin loads packages/cli/src/index.ts, and the package exports point at src/*.ts, so pnpm effa works before any build. The root build script no longer compiles the CLI before the other packages. tsconfig.all.json still includes the CLI, so pnpm build emits dist for publish and rewrites declaration imports to .js.

The published manifest keeps bin, exports, and typesVersions on dist JavaScript. Node will not run TypeScript files whose real path is inside node_modules, so the npm package stays compiled. The repo requires Node >=24, which matches CI.

Test plan

• With packages/cli/dist removed, node packages/cli/bin.js --help and the effa shim print help
• import '@effect-app/cli/argv-patch' loads the source export through the workspace link
• tsgo --build in packages/cli emits dist/index.js with a shebang and .js relative imports
• Publish staging points bin, exports, and typesVersions at dist, and node packages/cli/dist/index.js --version runs
• pnpm --dir packages/cli test:run passes

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[pkg-pr-new]

Open in StackBlitz

@effect-app/cli

npm i https://pkg.pr.new/@effect-app/cli@913

effect-app

npm i https://pkg.pr.new/effect-app@913

@effect-app/eslint-codegen-model

npm i https://pkg.pr.new/@effect-app/eslint-codegen-model@913

@effect-app/eslint-shared-config

npm i https://pkg.pr.new/@effect-app/eslint-shared-config@913

@effect-app/infra

npm i https://pkg.pr.new/@effect-app/infra@913

@effect-app/vue

npm i https://pkg.pr.new/@effect-app/vue@913

@effect-app/vue-components

npm i https://pkg.pr.new/@effect-app/vue-components@913

commit: b2a6d64