@systemfsoftware/arethetypeswrong-cli 2.0.0 → 3.0.0

package/CHANGELOG.md

@@ -1,5 +1,74 @@
 # @systemfsoftware/arethetypeswrong-cli
 
+## 3.0.0
+
+### Major Changes
+
+- Collapse projection tags into the ports they projected
+
+  A `*ExecutorDeps` tag whose service type was indexed off other ports recorded which members
+  one operation happened to reach for. Exporting it turned internal composition into a surface
+  commitment: a consumer had to discover and provide an aggregator for each operation, where the
+  port it came from already served. The tags rode the `R` channel of exported signatures, so a
+  consumer met them only at their own call site.
+
+  Each was removed the way its evidence directed — no tag was renamed, and none was replaced:
+
+  - `AttwCliExecutorDeps`, `CheckPackageExecutorDeps` — deleted. Zero consumers, no Live layer;
+    callers already required the real capabilities directly.
+  - `HookDispatcherExecutorDeps` — was a 1:1 alias of `Scope.Scope`. Requiring `Scope` names the
+    same service.
+  - `InjectInstructionsExecutorDeps` — packed `FileSystem`, `Path` and `TomlLoader` with no logic.
+    Consumers require the three ports.
+  - `EffectVitestDeps` → `EffectVitestBindings`. Never a `Context.Tag`: a plain type alias already
+    passed as an ordinary parameter, so only the name misdescribed it. A stale api report that no
+    `api-extractor` regenerates was deleted with it.
+
+  A consumer providing a port instead of an aggregator provides no more than before, since a
+  service `{ a, b }` is assignable to a requirement `{ a }`.
+
+### Minor Changes
+
+- cut over to effect v4 (4.0.0-rc.108): public surface derives from effect types; peers flip effect ^3→^4
+
+### Patch Changes
+
+- Array types are spelled one way. `Array<T>` and `ReadonlyArray<T>` in emitted
+  declarations become `T[]` and `readonly T[]`, which the type checker cannot tell
+  apart: no exported type changes, only how it is written.
+
+- An `.attw.json` in the working directory is read again. Rules listed under `ignoreRules`
+  were being discarded, so a package that had waived a resolution condition still failed on
+  it, and the only way to get a passing run was to repeat every rule on the command line
+
+- Rename five mislabelled `*.workflow.ts` files to `*.kernel.ts`.
+
+  `computeExitCode`, `applyProfile`, `renderAnalysis`, `detectEntrypointResolutions`, and
+  `detectModuleKindDisagreement` each return a bare value — a decision instance, a string, an array, or
+  `undefined` — never an `Either`. None has a failure mode, so none is a workflow, and the suffix was
+  claiming a contract the files never held. The `UninhabitedError` marker in
+  `@systemfsoftware/effect-cell-types` prescribes exactly this repair: "this workflow cannot fail, so it
+  decides nothing; give it an error variant or move it to a `*.kernel.ts`". Wrapping their results in
+  `Either.right` to satisfy the constructor was rejected — that manufactures a success-only decision.
+
+  Neither package takes a dependency on the constructor. Both are listed as `TOOLING` in
+  `scripts/guards/check-lint-coverage.mjs` ("port of arethetypeswrong, tooling"), carry no
+  `oxlint.config.ts`, and the cell rules deliberately do not reach them.
+
+  The public symbols and the `export *` surface of `core/src/index.ts` are unchanged, so no consumer
+  import breaks. The bump is real rather than empty because both packages ship `dist/` built from these
+  sources: the emitted chunk filenames change, and `arethetypeswrong-cli` rebuilds its `bin` target at
+  pack time via `prepack`. Test files and one non-UTF-8 property test were repointed alongside.
+
+- Packing for analysis (attw --pack) no longer runs the target package's pack lifecycle scripts: packing acquires the artifact for analysis instead of rebuilding it, so analyzing a package never mutates its build output.
+
+- New version is published through npm trusted publishing, so it carries a provenance attestation you can verify.
+
+- Build the `bin` target during install. Both CLIs point `bin` at gitignored build output, which pnpm's two bin-link passes skip when it is absent, leaving a fresh clone without the command and never retrying. A `prepare` script now builds the target between the passes; `arethetypeswrong-cli` drops its committed `bin/attw.mjs` launcher in favour of the same pattern.
+
+- Updated dependencies:
+  - @systemfsoftware/arethetypeswrong-core@3.0.0
+
 ## 2.0.0
 
 ### Patch Changes

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "@systemfsoftware/arethetypeswrong-cli",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "description": "A CLI tool for arethetypeswrong.github.io — owned and maintained by systemfsoftware",
   "author": "Ryan Lee <drdgvhbh@gmail.com>",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/systemfsoftware/systemfsoftware.git",
-    "directory": "packages/arethetypeswrong/cli"
+    "directory": "packages/testing/type-testing/arethetypeswrong/cli"
   },
   "files": [
     "dist",
@@ -25,7 +25,7 @@
     "@effect/platform-node": "^4.0.0-rc.108",
     "@effect/platform-node-shared": "^4.0.0-rc.108",
     "effect": "4.0.0-rc.108",
-    "@systemfsoftware/arethetypeswrong-core": "2.0.0"
+    "@systemfsoftware/arethetypeswrong-core": "3.0.0"
   },
   "devDependencies": {
     "@effect/vitest": "4.0.0-rc.108",
@@ -37,13 +37,13 @@
     "tsdown": "^0.22.14",
     "vite-tsconfig-paths": "^6.1.1",
     "vitest": "^4.1.10",
-    "@systemfsoftware/effect-schema-law": "^0.7.0",
-    "@systemfsoftware/effect-schema-vite": "^1.5.2",
+    "@systemfsoftware/effect-gherkin-spec": "^2.0.0",
+    "@systemfsoftware/effect-schema-law": "^0.8.0",
+    "@systemfsoftware/tsconfig": "^1.3.3",
+    "@systemfsoftware/effect-schema-vite": "^1.5.3",
+    "@systemfsoftware/vitest-config": "^0.1.0",
     "@systemfsoftware/oxlint-config": "^0.1.0",
-    "@systemfsoftware/oxlint-plugin-effect-dmmf": "^2.0.0",
-    "@systemfsoftware/effect-gherkin-spec": "^1.0.0",
-    "@systemfsoftware/tsconfig": "^1.3.2",
-    "@systemfsoftware/vitest-config": "^0.1.0"
+    "@systemfsoftware/oxlint-plugin-effect-dmmf": "^3.0.0"
   },
   "engines": {
     "node": ">=24"