feat: initial implementation

.github/workflows/ci.yml

@@ -0,0 +1,27 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  ci:
+    strategy:
+      matrix:
+        node-version: [22, 24, 26]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: voidzero-dev/setup-vp@v1
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: true
+          run-install: false
+
+      - run: vp install --frozen-lockfile
+      - run: vp run check

.gitignore

@@ -0,0 +1,5 @@
+node_modules
+.pnpm-store
+dist
+*.log
+.DS_Store

AGENTS.md

@@ -0,0 +1,88 @@
+# @b2m9/anyall — agent guide
+
+`@b2m9/anyall` evaluates a deliberately closed, serializable filter language:
+OR across `any` groups and AND across the predicates in each group's `all`.
+Read the public contract in `README.md` and the API JSDoc in `src/` before
+changing behavior. This file records the constraints behind that contract.
+
+## Toolchain
+
+ESM-only, Node ≥22, zero runtime dependencies. Use Vite+ (`vp`) through the
+pnpm-managed workspace: `vp check` (format/lint/types), `vp test run`, and
+`vp pack` (build). Run `vp run check` before handing off; it also validates the
+published package and types.
+Import test APIs from `vite-plus/test` so the suite uses Vite+'s bundled,
+version-locked runner.
+
+## Working method
+
+- Work in one observable slice at a time: write the smallest failing test,
+  confirm it fails for the intended reason, then implement only enough to pass.
+- Keep tests table-driven where the contract is a semantics matrix. Use
+  property tests for laws such as round trips, purity, and reference identity.
+- Treat `code` and `path` in issues as stable API. Message wording and issue
+  position are not.
+
+## Constraints to preserve
+
+- **The language stays closed.** Six operators plus the orthogonal `not` flag;
+  custom behavior belongs in declared field normalizers, never in expressions.
+  This is a security boundary, not a style preference.
+- **DNF stays fixed-depth.** Do not add recursive groups or left-to-right
+  reduction; the two-level shape is the protection against grouping ambiguity.
+- **Fields are declared capabilities.** Expressions select registry names; the
+  package does not parse paths or inspect record structure itself. Definition
+  objects reject string keys beyond `get` and `normalize`; ignored keys would
+  hide typos.
+- **No-filter is explicit.** `null` matches everything. Empty expressions and
+  empty groups are invalid rather than acquiring vacuous truth values.
+- **Validation has one source of truth.** `parse`, `compile`, and row conversion
+  must not drift into subtly different definitions of a valid predicate.
+- **Well-formed foreign versions stop validation.** A reader cannot make useful
+  claims about a positive-integer grammar version it does not understand;
+  malformed versions are V1 shape issues, not `unsupported-version`.
+- **Segment before discarding rows.** An invalid row may be removed in
+  interactive mode, but it must never alter the groups around it. A leading
+  join is ignored because it cannot separate two groups.
+- **Stored data stays data.** Parsing rebuilds fresh canonical plain objects;
+  evaluation-time normalization never rewrites saved needles. Token arrays
+  keep their order and duplicates; deduplication exists only in a compiled
+  `one-of` set.
+- **Explicit `undefined` means absence.** Required properties still fail as
+  missing; successful canonical output omits optional undefined properties.
+- **Empty has one meaning.** A value is empty exactly when resolution yields no
+  matchable texts. Every operator and its negation derive boundary behavior
+  from that definition rather than special-casing cells.
+- **Preserve reference no-ops.** `filter` returns its input array when every
+  record survives, and returns a fresh array only when something is excluded.
+- **Remain pure, deterministic, and synchronous.** No clock, locale or `Intl`,
+  global state, or input mutation. Accessor and normalizer failures propagate
+  so programmer bugs are not disguised as empty fields; a non-string normalizer
+  result is malformed configuration, never a matchable value.
+
+## Design principles
+
+The library's value is partly the vocabulary it refuses to grow. Hold these
+boundaries when recurring feature requests appear:
+
+- **Regex operators:** no. They create a ReDoS surface as soon as expressions
+  are untrusted data.
+- **User-defined operators:** no. Data that carries or names code stops being
+  portable, storable, and trustable. Custom behavior is a registry normalizer,
+  versioned with the application.
+- **Nesting:** no. JSON Logic already serves recursive expression trees. Fixed
+  DNF plus per-predicate `not` keeps grouping explicit, at worst with some
+  predicate duplication.
+- **Path strings:** accessors already provide compiler checks without adding a
+  grammar, prototype-safety policy, or getter semantics. If data-driven
+  registries eventually need convenience, a helper that returns an accessor is
+  the v1-compatible direction.
+
+Prefer removing code to adding it. Every option, operator, and public export
+must earn its maintenance cost. Anything that changes the expression grammar
+increments the wire version independently of package semver.
+
+## Comments
+
+Comments explain why an ordering, guard, or no-op is load-bearing. Do not
+paraphrase self-evident code. Prefer terse, complete sentences in present tense.

CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Bob Massarczyk
+
+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.