@systemfsoftware/effect-daemon-spec 0.7.2 → 2.0.0

package/CHANGELOG.md

@@ -0,0 +1,189 @@
+# @systemfsoftware/effect-daemon-spec
+
+## 2.0.0
+
+### Major Changes
+
+- Pass capabilities as arguments instead of requiring them through a projection tag, in these two packages
+
+  Wlaschin's second approach — dependency parameterization — is preferred over the
+  Reader, and it removes the requirement from the signature entirely rather than
+  relocating it. Each operation in `effect-daemon-spec` and `stryker-js-cli` that
+  previously reached into the context for a projection now receives what it uses,
+  and the composition root is the single place that acquires the port.
+
+  The remaining `*ExecutorDeps` projections live in `omp/**/src/internal/`, fenced
+  behind each package's own `exports` map, so they are unreachable from any consumer;
+  the exported-wiring gate scans `src/` outside `src/internal/`, so internal composition
+  stays internal and is not a migration target here.
+
+  - `effect-daemon-spec` — `withLeaderLock` takes `lock: LeaderLock['Type']`, and the
+    supervisor body takes `reporter: DaemonReporter['Type']`. Every `yield* LeaderLock`
+    and `yield* DaemonReporter` now lands in `mod.ts`; the exported `worker` and
+    `supervisor` shapes are unchanged, and `withLeaderLock` loses `LeaderLock` from `R`.
+  - `stryker-js-cli` — `StrykerCliExecutorDeps` and its service interface are gone.
+    `runStrykerCli` and the handler take `detectMode` and `createRunEventStream`, typed
+    as indexed accesses off the two port services, and both lose the requirement from
+    `R`. `main.ts` acquires both ports and passes the members down.
+
+  For these two packages, a caller that provided the projection layer now provides
+  nothing, because the operation no longer requires anything.
+
+- Carry the lock decision as a `LockBinding` so a required lock can never silently vanish.
+
+  The three lock-taking operations — the internal `worker`, `supervisor`, and the
+  `withLockByMode` operation behind them — now take a single discriminated
+  argument, `LockBinding`, in place of a `(LockConfig, LeaderLock['Type'] | null)`
+  pair. `unlocked` is the one case for a body that takes no lock; `locked` carries
+  the keyed spec and the adapter that honours it.
+
+  A spec declaring `mode: 'required'` paired with a null or missing adapter
+  previously fell through to the body unwrapped — a silent downgrade from "must
+  hold the leader lock" to "no lock at all". That combination is no longer
+  representable: `unlocked` only exists for a `{ mode: 'none' }` spec, and `locked`
+  demands both a keyed spec (via `KeyedLockConfig`) and an adapter (via
+  `LeaderLock['Type']`). The composition root — `worker` and `supervisor` in
+  `mod.ts` — is now the one place that builds the binding, and its public shapes
+  are unchanged.
+
+### Minor Changes
+
+- cut over to effect v4 (4.0.0-rc.108): public surface derives from effect types; peers flip effect ^3→^4
+
+- Produce every workflow through `Workflow.make`.
+
+  `decideRestart`, `interpretHookResult`, and `admitSurvivorsRun` are now built by the constructor rather
+  than annotated with `Workflow<Command, Decision, Error>`. Each decision is behaviourally identical —
+  `make` is the identity at runtime — but the channels are now inferred from the decider instead of
+  asserted by hand, so a total decision resolves to `UninhabitedError` and becomes uncallable rather than
+  compiling as a workflow that cannot fail.
+
+  `effect-daemon-spec` takes a minor bump because the change is consumer-visible beyond its own source:
+  `@systemfsoftware/effect-cell-types` moves from `devDependencies` to `dependencies`, so installing this
+  package now installs it. That reclassification is required, not incidental — `make` is a runtime call,
+  and `scripts/guards/check-runtime-deps.mjs` fails a runtime import declared only as a dev dependency.
+  `omp-claude-compat` gains the same dependency; `stryker-js-cli` already declared it.
+
+  `RestartDecisionWorkflow` survives as a type-only export: one in-repo consumer, its own property test,
+  references it through `ReturnType<…>`.
+
+### 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.
+
+- New version is published through npm trusted publishing, so it carries a provenance attestation you can verify.
+
+- Express each executor's sandwich as a `Cell` description.
+
+  Every call site that previously sequenced the phases by hand now builds one description and hands it to the interpreter, so the order these executors run in is carried by the phase types instead of by the order the statements happen to appear in. Behaviour is preserved and no public surface moves: the change is confined to `src/internal/*.executor.ts`, and each package's golden API report is unchanged.
+
+  One site needed a real fix rather than a translation. `supervisor-body.executor.ts` wrote before it could classify — it recorded a restart, then read the resulting rate — which is a read that depends on an earlier decision. Its read now gathers the restart record and the resulting rate as one product, which keeps that site a single layer, with the intensity tracker passed as the read's command rather than captured from the surrounding scope.
+
+- The base mutation preset selects at the make boundary.
+
+  The preset carries both ignorers (`effect-schema-declarations`, `workflow-make-boundary`) and
+  `disableBail: true`, so killer recording is structural for every inheriting config. The sandwich
+  packages (daemon-spec, stryker-js-cli, omp-claude-compat) widen `mutate` to all non-test source
+  at explicit 100/100/100 thresholds — the ignorer is the selector, so membership is forced by the
+  brand rather than chosen by a path list. Library packages' mutate arrays are byte-identical.
+
+- `restart-decision.workflow.ts` has its pure decision in a new internal `restart-decision.kernel.ts` with a colocated property test. Both files are internal, so the package's public surface is unchanged and the restart behaviour is identical.
+
+- Updated dependencies:
+  - @systemfsoftware/effect-cell-types@3.0.0
+
+## 1.0.0
+
+### Major Changes
+
+- Pass capabilities as arguments instead of requiring them through a projection tag, in these two packages
+
+  Wlaschin's second approach — dependency parameterization — is preferred over the
+  Reader, and it removes the requirement from the signature entirely rather than
+  relocating it. Each operation in `effect-daemon-spec` and `stryker-js-cli` that
+  previously reached into the context for a projection now receives what it uses,
+  and the composition root is the single place that acquires the port.
+
+  The remaining `*ExecutorDeps` projections live in `omp/**/src/internal/`, fenced
+  behind each package's own `exports` map, so they are unreachable from any consumer;
+  the exported-wiring gate scans `src/` outside `src/internal/`, so internal composition
+  stays internal and is not a migration target here.
+
+  - `effect-daemon-spec` — `withLeaderLock` takes `lock: LeaderLock['Type']`, and the
+    supervisor body takes `reporter: DaemonReporter['Type']`. Every `yield* LeaderLock`
+    and `yield* DaemonReporter` now lands in `mod.ts`; the exported `worker` and
+    `supervisor` shapes are unchanged, and `withLeaderLock` loses `LeaderLock` from `R`.
+  - `stryker-js-cli` — `StrykerCliExecutorDeps` and its service interface are gone.
+    `runStrykerCli` and the handler take `detectMode` and `createRunEventStream`, typed
+    as indexed accesses off the two port services, and both lose the requirement from
+    `R`. `main.ts` acquires both ports and passes the members down.
+
+  For these two packages, a caller that provided the projection layer now provides
+  nothing, because the operation no longer requires anything.
+
+- Carry the lock decision as a `LockBinding` so a required lock can never silently vanish.
+
+  The three lock-taking operations — the internal `worker`, `supervisor`, and the
+  `withLockByMode` operation behind them — now take a single discriminated
+  argument, `LockBinding`, in place of a `(LockConfig, LeaderLock['Type'] | null)`
+  pair. `unlocked` is the one case for a body that takes no lock; `locked` carries
+  the keyed spec and the adapter that honours it.
+
+  A spec declaring `mode: 'required'` paired with a null or missing adapter
+  previously fell through to the body unwrapped — a silent downgrade from "must
+  hold the leader lock" to "no lock at all". That combination is no longer
+  representable: `unlocked` only exists for a `{ mode: 'none' }` spec, and `locked`
+  demands both a keyed spec (via `KeyedLockConfig`) and an adapter (via
+  `LeaderLock['Type']`). The composition root — `worker` and `supervisor` in
+  `mod.ts` — is now the one place that builds the binding, and its public shapes
+  are unchanged.
+
+### Minor Changes
+
+- cut over to effect v4 (4.0.0-rc.108): public surface derives from effect types; peers flip effect ^3→^4
+
+- Produce every workflow through `Workflow.make`.
+
+  `decideRestart`, `interpretHookResult`, and `admitSurvivorsRun` are now built by the constructor rather
+  than annotated with `Workflow<Command, Decision, Error>`. Each decision is behaviourally identical —
+  `make` is the identity at runtime — but the channels are now inferred from the decider instead of
+  asserted by hand, so a total decision resolves to `UninhabitedError` and becomes uncallable rather than
+  compiling as a workflow that cannot fail.
+
+  `effect-daemon-spec` takes a minor bump because the change is consumer-visible beyond its own source:
+  `@systemfsoftware/effect-cell-types` moves from `devDependencies` to `dependencies`, so installing this
+  package now installs it. That reclassification is required, not incidental — `make` is a runtime call,
+  and `scripts/guards/check-runtime-deps.mjs` fails a runtime import declared only as a dev dependency.
+  `omp-claude-compat` gains the same dependency; `stryker-js-cli` already declared it.
+
+  `RestartDecisionWorkflow` survives as a type-only export: one in-repo consumer, its own property test,
+  references it through `ReturnType<…>`.
+
+### 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.
+
+- New version is published through npm trusted publishing, so it carries a provenance attestation you can verify.
+
+- Express each executor's sandwich as a `Cell` description.
+
+  Every call site that previously sequenced the phases by hand now builds one description and hands it to the interpreter, so the order these executors run in is carried by the phase types instead of by the order the statements happen to appear in. Behaviour is preserved and no public surface moves: the change is confined to `src/internal/*.executor.ts`, and each package's golden API report is unchanged.
+
+  One site needed a real fix rather than a translation. `supervisor-body.executor.ts` wrote before it could classify — it recorded a restart, then read the resulting rate — which is a read that depends on an earlier decision. Its read now gathers the restart record and the resulting rate as one product, which keeps that site a single layer, with the intensity tracker passed as the read's command rather than captured from the surrounding scope.
+
+- The base mutation preset selects at the make boundary.
+
+  The preset carries both ignorers (`effect-schema-declarations`, `workflow-make-boundary`) and
+  `disableBail: true`, so killer recording is structural for every inheriting config. The sandwich
+  packages (daemon-spec, stryker-js-cli, omp-claude-compat) widen `mutate` to all non-test source
+  at explicit 100/100/100 thresholds — the ignorer is the selector, so membership is forced by the
+  brand rather than chosen by a path list. Library packages' mutate arrays are byte-identical.
+
+- `restart-decision.workflow.ts` has its pure decision in a new internal `restart-decision.kernel.ts` with a colocated property test. Both files are internal, so the package's public surface is unchanged and the restart behaviour is identical.
+
+- Updated dependencies:
+  - @systemfsoftware/effect-cell-types@2.0.0

package/LICENSE

@@ -1,21 +1,203 @@
-MIT License
-
-Copyright (c) 2026 Ryan Lee
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Copyright (c) 2026 Ryan Lee (systemfsoftware)
+
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Ryan Lee (systemfsoftware)
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.