build(deps-dev): bump the major-updates group across 1 directory with 12 updates

[dependabot]

Bumps the major-updates group with 12 updates in the / directory:

Package	From	To
@systemfsoftware/all	1.1.3	2.1.2
@systemfsoftware/tsconfig	1.3.3	2.0.1
@types/node	24.13.3	26.6.2
@oh-my-pi/pi-coding-agent	17.4.2	18.3.1
@systemfsoftware/effect-cell-types	6.0.1	10.2.0
@systemfsoftware/effect-gherkin-spec	4.0.1	5.0.0
@systemfsoftware/effect-memfs	1.3.4	4.1.0
@systemfsoftware/effect-schema-law	2.0.2	3.0.0
@systemfsoftware/stryker-js-cli	6.0.0	9.0.0
@systemfsoftware/stryker-js-typescript-checker	5.0.0	7.1.0
@systemfsoftware/stryker-js-vitest-runner	4.0.0	7.2.0
@systemfsoftware/stryker-test-contribution	2.0.0	4.0.0

Updates @systemfsoftware/all from 1.1.3 to 2.1.2

Release notes

Sourced from @​systemfsoftware/all's releases.

@​systemfsoftware/oxlint-config-recommended@​v2.0.1

2.0.1

Patch Changes

• Both presets stop enabling strict-effect-provide (strictEffectProvide in the language service), so the rule keeps the Effect language service's own default, which is off, and an Effect.provide with a Layer passes without an opt-out. You can delete any overrides entry or @effect-diagnostics directive you added to turn the rule off. To keep the check, set effecttsgo/strict-effect-provide to error in your lint configuration, or strictEffectProvide to error in your tsconfig's diagnosticSeverity.

@​systemfsoftware/tsconfig@​v2.0.1

2.0.1

Patch Changes

• Both presets stop enabling strict-effect-provide (strictEffectProvide in the language service), so the rule keeps the Effect language service's own default, which is off, and an Effect.provide with a Layer passes without an opt-out. You can delete any overrides entry or @effect-diagnostics directive you added to turn the rule off. To keep the check, set effecttsgo/strict-effect-provide to error in your lint configuration, or strictEffectProvide to error in your tsconfig's diagnosticSeverity.

@​systemfsoftware/oxlint-plugin-cell-architecture@​v2.0.0

2.0.0

Major Changes

• no-io-boundary-tests is removed rather than renamed. It selected on the filename (/\.(?:acl|store|adapter|handler)\.[cm]?tsx?$/), so it could not fire on its own subject — an author writing a module that calls the filesystem does not name it .acl.ts — and two of the four suffixes it advertised matched no file in this tree. The verdict it was aimed at is already owned, decided from the module's own called non-type imports, by oxlint-plugin-test-discipline's no-io-module-in-source-test; a second rule deriving the same verdict from the same imports would report every violation twice. Consumer configs naming no-io-boundary-tests must drop the entry.

  The remaining none entries record touches that release nothing: no exported name changes.

@​systemfsoftware/tsconfig@​v2.0.0

2.0.0

Major Changes

• The effect preset now reports strictBooleanExpressions, missingPipeableSignature, missedPipeableOpportunity, strictEffectProvide, processEnv, nodeBuiltinImport and anyUnknownInErrorContext as errors instead of leaving them off. A new effect/entrypoint preset carries the same policy without strictEffectProvide and nodeBuiltinImport, for tests, runnable examples and code whose job is to provide layers. Extend @systemfsoftware/tsconfig/effect/entrypoint from those projects, and fix or restructure the newly reported sites in the rest.

@​systemfsoftware/effect-schema-discovery@​v2.0.0

2.0.0

Major Changes

• identityOf now takes a FoundSchema and returns a SchemaIdentity (<file>#<name>); call identityOf({ filePath, name }) where you passed the two strings. quote returns a QuotedText.

@​systemfsoftware/hex-schema@​v1.8.12

1.8.12

Patch Changes

• Update peer and runtime dependency on effect and companion packages to 4.0.0-rc.117.

@​systemfsoftware/oxlint-plugin-effect-platform@​v1.4.1

1.4.1

Patch Changes

• The recommended config's no-unported-time-source ports name effect-schema-law, trace-spec, and vitest at their new packages// paths.

... (truncated)

Commits

• c238a74 chore(release): version packages (#447)
• 692a988 build(global): stop printing successful build chatter (#441)
• a9efa4e chore(release): version packages (#435)
• 1b0e525 refactor(global): align @​effect/tsgo on the catalog and adopt its rule fixes ...
• 3a27bde feat(global): scope cell and tsgo rules to src and tests (#434)
• d6cbdef build(repo): resolve workspace source through the @​systemfsoftware/source con...
• b2ae7d0 chore(release): version packages (#416)
• 825851d refactor(effect-cell-types): honest source resolution, coverage gate, vocabul...
• 68b133e chore(release): version packages (#408)
• f5b6189 chore(release): version packages (#388)
• Additional commits viewable in compare view

Updates @systemfsoftware/tsconfig from 1.3.3 to 2.0.1

Release notes

Sourced from @​systemfsoftware/tsconfig's releases.

@​systemfsoftware/tsconfig@​v2.0.1

2.0.1

Patch Changes

• Both presets stop enabling strict-effect-provide (strictEffectProvide in the language service), so the rule keeps the Effect language service's own default, which is off, and an Effect.provide with a Layer passes without an opt-out. You can delete any overrides entry or @effect-diagnostics directive you added to turn the rule off. To keep the check, set effecttsgo/strict-effect-provide to error in your lint configuration, or strictEffectProvide to error in your tsconfig's diagnosticSeverity.

@​systemfsoftware/tsconfig@​v2.0.0

2.0.0

Major Changes

• The effect preset now reports strictBooleanExpressions, missingPipeableSignature, missedPipeableOpportunity, strictEffectProvide, processEnv, nodeBuiltinImport and anyUnknownInErrorContext as errors instead of leaving them off. A new effect/entrypoint preset carries the same policy without strictEffectProvide and nodeBuiltinImport, for tests, runnable examples and code whose job is to provide layers. Extend @systemfsoftware/tsconfig/effect/entrypoint from those projects, and fix or restructure the newly reported sites in the rest.

Commits

• 7de99e2 chore(release): version packages (#490)
• b5cc3b3 fix(global): stop the Effect presets enabling strict-effect-provide (#489)
• 05de29e chore(release): version packages (#483)
• 2506fc9 feat(global): scope Effect policy by role and typecheck every file (#479)
• c238a74 chore(release): version packages (#447)
• a9efa4e chore(release): version packages (#435)
• f5b6189 chore(release): version packages (#388)
• 5351688 chore(deps): move attw to 4.1.0 and retire its named catalog (#396)
• See full diff in compare view

Updates @types/node from 24.13.3 to 26.6.2

Commits

• See full diff in compare view

Updates @oh-my-pi/pi-coding-agent from 17.4.2 to 18.3.1

Release notes

Sourced from @​oh-my-pi/pi-coding-agent's releases.

v18.3.1

@​oh-my-pi/pi-agent-core

Added

• Added live steering support for Codex WebSocket transports, allowing users to provide input while a response is in progress.
• Added passive tool-call context support, allowing hooks and tools to supply additional context for subsequent model processing.
• Improved context-window handling by automatically adjusting output-token limits and supporting models that truncate output at the context-window limit.

Changed

• Improved prompt token counting for requests with anchored prefixes by using provider-reported usage and limiting local estimation to new message content.

@​oh-my-pi/pi-ai

Added

• Added live steering support for GPT-6 models, allowing queued user messages to be delivered during an active streaming response.
• Added the anthropicSlowMode stream option for first-party Claude OAuth requests, enabling slow-mode rate-limit handling, per-account rate-limit reporting, and server-paced retries during capacity limits.
• Added support for capturing and redeeming Anthropic fallback credit tokens, including prompt-cache repricing for classifier refusals.
• Added Vercel AI Gateway app attribution by sending http-referer: https://omp.sh/ and x-title: omp by default; user-provided header values take precedence.

Fixed

• Fixed account selection for OpenCode Go and SuperGrok (xai-oauth) so accounts without available funds or included quota are skipped in favor of eligible accounts.
• Improved visibility into automatically disabled authentication credentials by logging a warning and including the affected account details in credential-disabled events.

@​oh-my-pi/browser-relay

Fixed

• Fixed browser relay support when multiple browser instances, such as Chrome and Edge, are connected simultaneously, ensuring tabs and relay requests remain associated with the correct browser while preserving single-browser compatibility for extensions without an instance identifier.

@​oh-my-pi/pi-catalog

Added

• Added compatibility flags for models that stop output at the context-window limit and models that support steering, including defaults for Claude 4.5+ and GPT-6+ models.

Fixed

• Fixed forced-tool requests for Claude Opus 5.5 so tool selection falls back gracefully when necessary.
• Added the provider-advertised xhigh reasoning level for Yolo-Auto Qwen3.8 models.
• Fixed Devin Fusion pairing requests failing with no API providers are available by routing them through the lead model with the lead's limits and pricing; pairings without an available lead are no longer listed (#13000 by @​DarkPhilosophy).

@​oh-my-pi/pi-coding-agent

Added

• Added native filesystem support for local:// and omp:// URLs across file-search, content-search, AST, shell, and related tools, including support for virtual working directories.

... (truncated)

Changelog

Sourced from @​oh-my-pi/pi-coding-agent's changelog.

[18.3.1] - 2026-09-25

Added

• Added a filter to the Esc Esc rewind selector: press f and type to show only items containing every word, then Enter to rewind (#13295 by @​H4vC)
• Added native filesystem support for local:// and omp:// URLs across file-search, content-search, AST, shell, and related tools, including support for virtual working directories.
• Added a native cp builtin for filesystem copy operations.
• Added IDA Pro integration for opening executables and IDA databases, browsing pseudocode, assembly, imports, exports, strings, and cross-references, and performing database-aware actions such as renaming, commenting, type editing, function creation, saving, and persistent Python execution.
• Added shared, project-scoped IDA database access with broker-managed host processes, configurable concurrency and idle cleanup via ida.maxOpen and ida.idleCloseSec, automatic autosaving, and universal Mach-O architecture selection with :@<arch> syntax and host-architecture detection. IDA features can be configured with ida.enabled, ida.python, and ida.installDir.
• Added the /slow [on|off|status] command for opting into lower-priority service tiers on OpenAI, Google, and Anthropic subscription sessions, including automatic continuation when Anthropic session limits are reached.
• Added the providers.openaiLiveSteering setting to control whether input can be delivered while a response is in progress.
• Added session-wide approval for configuration changes through an Always for this session option in cfg:// prompts, with clear timeout handling for unanswered prompts.
• Added the cfg:// protocol and a configuration registry for reading, modifying, unsetting, and reactively managing layered agent settings with approval and precedence feedback.
• Added paged reading for large files, with metadata that allows clients to recover and continue displaying results.
• Added per-agent compaction thresholds for task and evaluation subagents, configurable as percentages or fixed token limits without changing the main session threshold.
• Added trusted additional context for extension and hook tool results, including ctx.addAdditionalContext(), allowing instructions to reach the model without altering displayed tool results.
• Added dictation support to /btw follow-up input.
• Added support for multiple simultaneous browser instances, including concurrent Chrome and Edge connections.
• Added detailed benchmark phases for measuring single-user throughput, parallel scaling, and prefill performance, with automatic prefill sizing based on model context limits.
• Added opt-in CUDA support to the Nix package for tiny-model inference through ONNX Runtime.
• Added reliable RPC prompt lifecycle reporting with prompt_result, structured provider errors, session-settled state, prompt identifiers, event filtering, and --no-ui support for non-interactive hosts.
• Added RPC session management through open_session, plus corresponding TypeScript and Python client APIs including openSession, setEventFilter, onPromptResult, onSessionSettled, and waitForSettled.
• Added attachment:// and conflict:// resource URL handlers.
• Added a per-server MCP instructions: false option to keep a server's guidance out of the system prompt while retaining its tools.
• Added stale tool-result eviction for advisors: before each review, an advisor replaces its own read/grep/glob output from reviews older than the latest one with a short placeholder, so it stops re-sending that output on every request. The deltas it reviews, the notes it wrote, and other tool results such as recall are never touched. Turn it off with advisor.evictStaleResults (#13238 by @​alnaggar-dev)

Changed

• Improved recovery from output-length and context-window limits so truncated but actionable turns can be retained and retries are handled more accurately.
• Shortened the default system prompt by approximately 150 tokens while preserving its guidance.
• Improved Anthropic fallback handling so credit tokens and signed thinking context are preserved across same-provider fallbacks.
• Improved filesystem safety and path consistency across virtual URL protocols, including symlink and containment validation and correct Windows long-path reporting.
• Improved IDA database resource management with project sharing, bounded concurrency, idle cleanup, autosave, and clearer database status in listings.
• Improved runtime configuration behavior with type-safe layered settings, live updates, and safe sequential saves.
• Improved authentication and credential management to support live broker and credential-store changes.

Fixed

• Fixed concurrent project access by enforcing file locking across processes.
• Fixed Windows file reads with line selectors such as :1-40.
• Fixed omp update and startup update checks to honor configured npm registries, including scoped registries and authentication tokens.
• Fixed invalid auto-QA grievance reports blocking the rest of the upload queue; rejected reports are now surfaced with the server error while other reports continue.
• Fixed advisor reviews making unnecessary follow-up requests, losing context after pruning, using the wrong thinking effort, or sending excessively large edit diffs.
• Fixed /login crashes in source-link and development installs after extension loading.
• Fixed retry fallback loops that could continue indefinitely when the fallback resolved to the same effective request.
• Fixed setup wizard detection for Gemini web search when Antigravity OAuth is active.
• Fixed headless print mode failing to complete an advisor review when a configured fallback reviewer was available.
• Fixed embedded shell startup when the inherited working directory had been deleted.
• Fixed Codex usage displays showing stale subscription plans and corrected usage views that combined separate quota limits.
• Fixed explicit model and provider selections bypassing disabledProviders; disabled providers are now refused and skipped during fallback.

... (truncated)

Commits

• 6204b75 fix(launch): fenced detached daemon callbacks after broker shutdown
• 63e009b test(coding-agent): keyed memory backend session to its model provider
• dc72c11 test(coding-agent): dropped assertions on the removed bash skill hint
• 03de996 chore: bump version to 18.3.1
• 872b76f chore: rewrite changelog
• b40e47a feat: improved builtin failure handling and length-stop recovery
• 210ea7f feat: added Claude 4.5+ context window truncation awareness and improved outp...
• 7dc2ef9 feat: unified filesystem access for native tools and internal URLs
• 2a8e432 feat(tui/prompt): added transient chrome handling to composer runtime children
• b6e254f feat(coding-agent/ida): migrated IDA databases to broker-managed host daemons
• Additional commits viewable in compare view

Updates @systemfsoftware/effect-cell-types from 6.0.1 to 10.2.0

Commits

• See full diff in compare view

Updates @systemfsoftware/effect-gherkin-spec from 4.0.1 to 5.0.0

Release notes

Sourced from @​systemfsoftware/effect-gherkin-spec's releases.

@​systemfsoftware/effect-gherkin-spec@​v5.0.0

5.0.0

Minor Changes

• Then, And and But bodies take (state, expect) and return exactly one check (or an Effect of one); expect is no longer imported from @effect/vitest. Only Given and When open a new observed state, so a Then followed by an And or But on the same state is refused: merge the facts into one Then over a record. Then.soft, Then.poll and When.poll, with their And/But forms, are removed, as are checkSoftFailures, owned and recordAssertion. A background pipeline may carry the check service.

Patch Changes

• Updated dependencies:
  • @​systemfsoftware/vitest@​0.1.0

Commits

• See full diff in compare view

Updates @systemfsoftware/effect-memfs from 1.3.4 to 4.1.0

Release notes

Sourced from @​systemfsoftware/effect-memfs's releases.

@​systemfsoftware/effect-memfs@​v4.1.0

4.1.0

Minor Changes

• The layer from MemoryFileSystem.make(...).layer now also provides a MemoryFileSystem.Watcher service, so a test can tell exactly when a watch is live instead of yielding and hoping. watcher.start(path, options) completes only once the watch is registered and returns its event stream; stopping the scope closes the watch. watcher.awaitOpen(path) waits until a watch on path is open, which covers code under test that watches through the plain FileSystem.watch. watcher.openWatches lists the paths that still have an open watch, so a test can check that nothing was left watching. makeDirectory on a path that already holds a file now fails with AlreadyExists, even with recursive: true, as Node's filesystem does; it used to succeed.

Patch Changes

• Path-level writes, moves and deletes on the in-memory filesystem now apply before the calling effect continues, and folder watchers hear the change in that same step instead of on a later host microtask. Reads and open-file handles behave as before.

Commits

• cb7c8ea fix(trace-spec): stop the nested vitest run that recursed into the whole suit...
• ecd30db feat(vitest): take expect from the test callback and yield every check (#517)
• 1c78b69 fix(global): empty dist before each tsdown build
• 213232c chore(release): version packages (#516)
• aa19537 refactor(global)!: import the lawful runner under its own name (#520)
• de5414e docs(global): tighten architectural commitments and leaf governance (#518)
• 13fab8d feat(global): test Effect concurrency under replayable schedules (#510)
• 6682e31 chore(release): version packages (#509)
• 659321d feat(vitest): make the lawful test patterns the default with a fork of @​effec...
• 3916c76 feat(global): build blueprints and handles on typed cell kinds (#506)
• Additional commits viewable in compare view

Updates @systemfsoftware/effect-schema-law from 2.0.2 to 3.0.0

Release notes

Sourced from @​systemfsoftware/effect-schema-law's releases.

@​systemfsoftware/effect-schema-law@​v3.0.0

3.0.0

Patch Changes

• Updated dependencies:
  • @​systemfsoftware/vitest@​0.1.0

Commits

• See full diff in compare view

Updates @systemfsoftware/stryker-js-cli from 6.0.0 to 9.0.0

Release notes

Sourced from @​systemfsoftware/stryker-js-cli's releases.

@​systemfsoftware/stryker-js@​v9.0.0

9.0.0

Major Changes

• The incremental file now carries incrementalVersion (the Stryker package version). Stryker writes it on every incremental run and discards an incremental file it cannot parse or whose incrementalVersion differs from the running version, falling back to a full mutation testing run instead of failing. IncrementalReportSchema requires incrementalVersion, and decodeIncrementalReport and IncrementalReportError are no longer exported.

@​systemfsoftware/stryker-js-instrumenter@​v9.0.0

9.0.0

Major Changes

• Mutant ids, mutator names and file names are now branded schemas, and the string helpers are replaced by codecs.

  • Build ids and names with MutantId, MutatorName and CanonicalFileName. Empty values are refused.
  • Replace errorToString with ErrorText.fromCause and causeText with CauseText.fromCause. Both return an Option.
  • Replace normalizeFileName with a CanonicalFileName decode, and isMutant with Schema.is(Mutant).
  • Read the values formerly in INSTRUMENTER_CONSTANTS from the InstrumenterContext statics.

• Each package's main entry point now groups its exports into namespaces named after a capability, such as Plugin, TestRunner and Report.

  • Import the namespace and qualify each name, for example Plugin.TestRunnerRpcs after importing Plugin from the plugin interface.
  • Import instrumenter schemas such as Location and MutantStatus from the instrumenter's Mutant namespace, and plugin-interface names from the plugin interface, instead of through another package's entry point.
  • The engine's /config, /events and /promises entry points are unchanged.

• HTML templates and Svelte components are no longer instrumented by this package on their own: each format now comes from its framework plugin, the Angular plugin for .html, .htm, and .vue and the Svelte plugin for .svelte, both published alongside this release. Install the plugin whose format your project uses and add it to plugins. A file whose extension no loaded format claims is reported in the run's skipped files instead of being instrumented, and svelte is no longer an optional peer dependency of this package; the angular-html-parser dependency moves to the Angular plugin.

  The Angular signal ignore rule is unaffected and continues to ship in @systemfsoftware/stryker-ignorer-angular.

• The format registry can now be extended with a framework plugin's contribution: frameworkEntryOf adapts a Framework into a registry entry whose parse, transform, print, and disable-type-checks hooks delegate to the plugin over its embedded document, and the AST union gains the embedded-document variant those entries parse to.

  A registry entry you build yourself must now declare the owner module of its format, the ownerVersion incremental state keys on, and a transform hook; an entry without them no longer type-checks.

Patch Changes

• Every mutant now reports its position as 1-based coordinates — the base the

... (truncated)

Commits

• See full diff in compare view

Updates @systemfsoftware/stryker-js-typescript-checker from 5.0.0 to 7.1.0

Release notes

Sourced from @​systemfsoftware/stryker-js-typescript-checker's releases.

@​systemfsoftware/stryker-js-typescript-checker@​v7.1.0

7.1.0

Patch Changes

• The checker no longer looks dead while it type-checks. A check that runs longer than the host's connection patience window used to leave the checker unable to answer the host, dropping its connection mid-run; long checks are now answered and the connection survives them.

• The typescript checker no longer discards include, exclude, files, extends, and any other unrecognized top-level key from the tsconfig it rewrites. Projects that list files outside the default include patterns, import their own package manifest, or extend a shared preset now type-check during mutation runs the same way they do under tsc; only the compiler options the checker intentionally overrides still differ, and single-project mode alone drops references. Referenced projects are covered too: every tsconfig a build-mode project references is rewritten with those same overrides, so a library that opts into noUnusedLocals (or any option the checker overrides) is checked under the checker's settings instead of its own.

@​systemfsoftware/stryker-js-typescript-checker@​v7.0.5

7.0.5

Patch Changes

• Exported declarations that previously took unknown now take a defaulted type parameter: calls that omit the type argument are unchanged, and calls that were previously rejected for passing an unconstrained value are accepted. No runtime behaviour changes.

@​systemfsoftware/stryker-js-typescript-checker@​v7.0.4

7.0.4

Patch Changes

• Effect moves to 4.0.0-rc.116 (with @effect/platform-node, @effect/platform-node-shared, @effect/vitest and @effect/opentelemetry on the same release), the @systemfsoftware/* toolchain pins move to their current releases, and vitest 5 with oxc-parser 0.150 come along. Both worker bundles (stryker-js-typescript-checker, stryker-js-vitest-runner) now inline their whole runtime rather than resolving effect, @effect/* and the sibling packages from the host's tree, so a worker runs on its own copy of the effect that built it; the project's typescript and vitest remain the only imports beside Node builtins. The filter-level arbitrary.candidate generators that the thresholds schemas carried are gone: v4 no longer reads them, so thresholds still reject a low above high and the property tests generate the pair from the schema again. Log calls inside Effect.catch* handlers moved to Effect.tapError/Effect.tapCause at the same level and message. @systemfsoftware/stryker-ignorer-interface re-exports the 0.150 AST, where FormalParameterRest.decorators is now Array<Decorator>.

@​systemfsoftware/stryker-js-typescript-checker@​v7.0.3

7.0.3

Patch Changes

• A checker that fails now fails mutation testing with that checker's cause, instead of crashing with an empty error. The TypeScript checker type-checks each mutant, so compile errors appear in the report. Verdict counts are non-negative integers; Metrics is a class you can build from mutant statuses; a threshold low may not exceed high.

@​systemfsoftware/stryker-js-typescript-checker@​v7.0.2

7.0.2

Patch Changes

• The checker request carries a plain data record, not the instrumenter's Mutant class. CheckerRequest.mutants and CheckerService.check/group now speak CheckerMutantWire - id, fileName, mutatorName, replacement, and location. A mutant that cannot be described to a checker is skipped instead of reaching it.

  With OTEL_ENABLED=true the CLI now exports its OpenTelemetry metrics to OTEL_EXPORTER_OTLP_ENDPOINT, and OTEL_METRIC_EXPORT_INTERVAL sets the export interval in milliseconds. Checker timings, mutant counts, and worker crashes now reach a metrics backend.

  ConfigEnv and resolveExtends are no longer exported. Import ConfigEnv from the config entry point of the package, and read merged options with loadConfigCell or readConfig from the package root - either performs the extends walk, validation and merge in order.

• Updated dependencies:

  • @​systemfsoftware/stryker-js-plugin-interface@​7.0.0

@​systemfsoftware/stryker-js-typescript-checker@​v7.0.1

7.0.1

Patch Changes

• Updated dependencies:

... (truncated)

Commits

• 789240d fix(repo): settle dropped worker requests, kill nested-describe mutants, keep...
• 3ff3c16 chore(release): version packages (#93)
• 4938e0f refactor(repo): move every package to the compound-pack bar (#94)
• ad14ca4 feat(repo): extract Angular and Svelte into framework plugins over an open fo...
• 5ed86e2 feat(repo): add opt-in mutators that plant Effect concurrency faults (#86)
• 4d62105 chore(release): version packages (#81)
• deeda90 build(deps): update workspace toolchain and packages to latest (#79)
• fcfd36a test(repo): retire the effect-skew fixture in favour of the real worker seam ...
• a16eeb9 build(deps): replace @​systemfsoftware/all with recommended oxlint preset and ...
• 0c2477d build(deps): catalog all workspace deps, patch instrumenter, and protect main...
• Additional commits viewable in compare view

Updates @systemfsoftware/stryker-js-vitest-runner from 4.0.0 to 7.2.0

Release notes

Sourced from @​systemfsoftware/stryker-js-vitest-runner's releases.

@​systemfsoftware/stryker-js-vitest-runner@​v7.2.0

7.2.0

Patch Changes

• Mutant runs now execute the tests that cover the mutant and report the verdict those tests earn. With the default related option, every mutant run filtered out all test files, so mutants came back as errors (No test files found) instead of killed or survived. Mutants covered only by tests inside describe blocks — any depth, including describe.each — now run exactly those covering tests and are reported Killed when any of them fails; mutants covered only by top-level tests keep their existing selection and verdicts.

@​systemfsoftware/stryker-js-vitest-runner@​v7.1.1

7.1.1

Patch Changes

• Exported declarations that previously took unknown now take a defaulted type parameter: calls that omit the type argument are unchanged, and calls that were previously rejected for passing an unconstrained value are accepted. No runtime behaviour changes.

@​systemfsoftware/stryker-js-vitest-runner@​v7.1.0

7.1.0

Minor Changes

• A finite mutant is killed or survived from its tests. Timeout is reserved for one named nonterminating trap, detected by a hit bound rather than a wall-clock budget. A wall-clock timeout fails the run instead of being stored as a detected mutant.

Patch Changes

• Mutants that execute far past their dry-run hit count now fail at the hit limit instead of waiting out the test timeout. Coverage from the dry run is recorded again, so the limit is armed.

@​systemfsoftware/stryker-js-vitest-runner@​v7.0.1

7.0.1

Patch Changes

• Effect moves to 4.0.0-rc.116 (with @effect/platform-node, @effect/platform-node-shared, @effect/vitest and @effect/opentelemetry on the same release), the @systemfsoftware/* toolchain pins move to their current releases, and vitest 5 with oxc-parser 0.150 come along. Both worker bundles (stryker-js-typescript-checker, stryker-js-vitest-runner) now inline their whole runtime rather than resolving effect, @effect/* and the sibling packages from the host's tree, so a worker runs on its own copy of the effect that built it; the project's typescript and vitest remain the only imports beside Node builtins. The filter-level arbitrary.candidate generators that the thresholds schemas carried are gone: v4 no longer reads them, so thresholds still reject a low above high and the property tests generate the pair from the schema again. Log calls inside Effect.catch* handlers moved to Effect.tapError/Effect.tapCause at the same level and message. @systemfsoftware/stryker-ignorer-interface re-exports the 0.150 AST, where FormalParameterRest.decorators is now Array<Decorator>.

@​systemfsoftware/stryker-js-vitest-runner@​v7.0.0

7.0.0

Major Changes

• The runner now requires vitest 4.1 or later, and the peer dependency says so: vitest >=4.1.0.

  Upgrade vitest to 4.1 or later before upgrading this package. Projects that must stay below 4.1 should stay on the previous release.

  The published bundle now also inlines oxc-parser and @eslint-community/regexpp so they ship inside the runner's install. Consumers that previously resolved those packages as transitive dependencies from another tool should now take them from the runner's published bundle.

@​systemfsoftware/stryker-js-vitest-runner@​v6.0.0

6.0.0

... (truncated)

Commits

• 789240d fix(repo): settle dropped worker requests, kill nested-describe mutants, keep...
• d11f626 fix: close vm runner parity with real vitest (#97)
• 5c16035 build(deps): remove effect overrides and rationalize effect peer dependencies...
• 3ff3c16 chore(release): version packages (#93)
• 4938e0f refactor(repo): move every package to the compound-pack bar (#94)
• ad14ca4 feat(repo): extract Angular and Svelte into framework plugins over an open fo...
• 5ed86e2 feat(repo): add opt-in mutators that plant Effect concurrency faults (#86)
• 4d62105 chore(release): version packages (#81)
• deeda90 build(deps): update workspace toolchain and packages to latest (#79)
• fcfd36a test(repo): retire the effect-skew fixture in favour of the real worker seam ...
• Additional commits viewable in compare view

Updates @systemfsoftware/stryker-test-contribution from 2.0.0 to 4.0.0

Release notes

Sourced from @​systemfsoftware/stryker-test-contribution's releases.

@​systemfsoftware/stryker-test-contribution@​v4.0.0

4.0.0

Minor Changes

• Projects using @systemfsoftware/stryker-js as a CLI tool no longer receive warnings or automatic installs for effect. The peer dependency is now optional, required only when importing programmatic APIs from the package.

  @systemfsoftware/stryker-js-vitest-runner and @systemfsoftware/stryker-test-contribution no longer declare a peer dependency on effect.

@​systemfsoftware/stryker-test-contribution@​v3.0.3

3.0.3

Patch Changes

• Effect moves to 4.0.0-rc.116 (with @effect/platform-node, @effect/platform-node-shared, @effect/vitest and @effect/opentelemetry on the same release), the @systemfsoftware/* toolchain pins move to their current releases, and vitest 5 with oxc-parser 0.150 come along. Both worker bundles (stryker-js-typescript-checker, stryker-js-vitest-runner) now inline their whole runtime rather than resolving effect, @effect/* and the sibling packages from the host's tree, so a worker runs on its own copy of the effect that built it; the project's typescript and vitest remain the only imports beside Node builtins. The filter-level arbitrary.candidate generators that the thresholds schemas carried are gone: v4 no longer reads them, so thresholds still reject a low above high and the property tests generate the pair from the schema again. Log calls inside Effect.catch* handlers moved to Effect.tapError/Effect.tapCause at the same level and message. @systemfsoftware/stryker-ignorer-interface re-exports the 0.150 AST, where FormalParameterRest.decorators is now Array<Decorator>.

@​systemfsoftware/stryker-test-contribution@​v3.0.2

3.0.2

Patch Changes

• Updated dependencies:
  • @​systemfsoftware/stryker-js-plugin-interface@​7.0.0

@​systemfsoftware/stryker-test-contribution@​v3.0.1

3.0.1

Patch Changes

• Updated dependencies:
  • @​systemfsoftware/stryker-js-plugin-interface@​6.0.0

@​systemfsoftware/stryker-test-contribution@​v3.0.0

3.0.0

Major Changes

• The plugin system now runs each configured TestRunner/Checker/Reporter plugin in its own spawned process over an @​effect/rpc wire: plugins load from the project's config-declared specifiers (no glob discovery), boundary failures are typed errors, and plugin spans link into the host trace. Breaking: the in-process plugin Layer contract is removed.

Patch Changes

• Maintenance release. Every published entry point, export, option, and behaviour is exactly as it was.

• the types condition now points at the emitted dist/index.d.ts, the effect peer range widens to ^4.0.0-rc.112, and repository metadata now points at stryker-js-effect

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

---

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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.