@jsprismarine/predicates 0.0.0 → 0.16.0-unstable-20261029134110

package/CHANGELOG.md

@@ -0,0 +1,71 @@
+# @jsprismarine/predicates
+
+## 0.16.0-unstable-20261029134110
+
+### Patch Changes
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`1e9ada2`](https://github.com/JSPrismarine/JSPrismarine/commit/1e9ada27d7fd15b209521870328a5257440ee4a7) Thanks [@filiphsps](https://github.com/filiphsps)! - Make the loot tables reach the player.
+  
+  A generated container's loot is rolled the first time it is opened. A structure writes a chest
+  with a `LootTable` tag, a `LootTableSeed` and nothing in it, which is what the game writes too,
+  and nothing rolled them: every chest in a village, a shipwreck, a mineshaft, a stronghold, a
+  desert pyramid or a buried treasure opened empty. The fill is Java's `LootTable.fill` step for
+  step over one `java.util.Random` seeded with the stored seed, so the table is rolled, the free
+  slots are shuffled, the stacks of more than one are split over them, and each one is dealt off
+  the back of the shuffled list. Two players in two copies of one world see the same chest. The tag
+  goes with the write, so the second open shows the first open's chest rather than a second roll.
+  
+  `LootRegistry` answers three of its content seams out of the pack stack it already holds: the
+  smelting recipes `furnace_smelt` smelts through, the item tag expansion a tagged ingredient needs,
+  and the reference resolver a `set_contents` entry list parses against. It takes two more from the
+  host, because neither is in a pack: the enchantment view the 25 tables carrying `enchant_randomly`
+  or `enchant_with_levels` draw from, built per roll over the table's own stream so a world seed
+  replays the draw, and the per-item stack limits a rolled count is clamped to. The server passes
+  both. `exploration_map` stays unanswered, because it needs a structure search this server has not
+  got.
+  
+  `furnace_smelt` reads `use_input_count` with Java's own default of true. Reading it as false cut
+  every smelted drop to one, so a cow that died burning gave one cooked beef where Java gives the
+  one to three its `set_count` rolled.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`d42e7c3`](https://github.com/JSPrismarine/JSPrismarine/commit/d42e7c33d23361c5b159078ae6635a230ff70701) Thanks [@filiphsps](https://github.com/filiphsps)! - Fix four item modifier defects and match the `food` member of a player sub-predicate. Each one was
+  checked against the unobfuscated Java 26.3 server jar.
+  
+  - `set_lore`, `set_written_book_pages` and `set_writable_book_pages` read the list operation mode
+    from their own members. `ListOperation.codec` is a `MapCodec` that dispatches on a flat `mode`
+    key, so these three modifiers carry `mode`, `offset` and `size` beside `lore` or `pages`. The
+    parser was handing `listOperation` the value of `mode`, which then looked for a second `mode`
+    inside it and fell back to `replace_all`. Every `append`, `insert` and `replace_section` use
+    silently replaced the whole list instead.
+  - `insert` and `replace_section` leave the list unchanged when the offset is past its end, and
+    `replace_section` without a `size` takes out as many entries as it puts in. The size previously
+    defaulted to zero, which turned that form into an insert.
+  - `set_fireworks` reads its explosions from `explosions.values`. The `explosions` member is a
+    `ListOperation.StandAlone`, so the list and the mode live inside it. The modifier read
+    `explosions` as the list itself, which yielded nothing and cleared the component. An absent
+    `explosions` member now leaves the existing explosions alone instead of clearing them.
+  - `furnace_smelt` multiplies the input count by the count the recipe yields and clamps the result
+    to the stack size, which is what `SmeltItemFunction.run` computes. The count the recipe yields
+    was dropped, so a recipe that produces more than one item smelted too few.
+  - The `food` member of `minecraft:type_specific/player` matches Java's `FoodPredicate`: an int
+    bound on the food level and a float bound on the saturation. Both read the new `food` member of
+    `EntityView`, and a view that does not report hunger makes the predicate fail with a diagnostic.
+    The vanilla `lunge` enchantment uses this member, and the parser used to warn and refuse it.
+  
+  `advancements`, `recipes`, `stats` and `input` on the player sub-predicate still warn. They need
+  per-player progression and client input state, which no host seam in this package exposes, and no
+  vanilla file uses them.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`33c3920`](https://github.com/JSPrismarine/JSPrismarine/commit/33c39204cf625a581b63f3f133bfc68f7adb6510) Thanks [@filiphsps](https://github.com/filiphsps)! - Add `@jsprismarine/predicates`, the Java Edition predicate, item modifier and value provider
+  evaluator that loot, advancements and enchantments call. It implements the 20 loot condition types,
+  42 loot function types, 23 int and 28 float context providers, 7 enchantment level based values and
+  23 of the 25 entity sub-predicate types of Java 26.3, all read out of the 26.3 server jar. One
+  helper resolves 26.3's composition rule, where every field of a composable type takes an inline
+  value, a namespaced id, a list mixing both, or a `#tag`. A `PredicateContext` carries the 16 loot
+  context parameters and declares which of the 31 context key sets it belongs to, so reading a
+  parameter that set does not provide reports a diagnostic instead of quietly passing. The random
+  source, reference resolver, level view, item stack operations, enchantment view and content view
+  are all injected, and a grammar member the package does not implement reports a diagnostic and
+  evaluates false rather than throwing.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`815800d`](https://github.com/JSPrismarine/JSPrismarine/commit/815800d3410bfd829fc583eb9bcd896369812247) Thanks [@filiphsps](https://github.com/filiphsps)! - Run data-defined interaction loot tables, resolve legacy Bedrock item variants, and preserve item counts and drop offsets.

package/LICENSE

@@ -0,0 +1,373 @@
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+    means each individual or legal entity that creates, contributes to
+    the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+    means the combination of the Contributions of others (if any) used
+    by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+    means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+    means Source Code Form to which the initial Contributor has attached
+    the notice in Exhibit A, the Executable Form of such Source Code
+    Form, and Modifications of such Source Code Form, in each case
+    including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+    means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+    means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+    means a work that combines Covered Software with other material, in
+    a separate file or files, that is not Covered Software.
+
+1.8. "License"
+    means this document.
+
+1.9. "Licensable"
+    means having the right to grant, to the maximum extent possible,
+    whether at the time of the initial grant or subsequently, any and
+    all of the rights conveyed by this License.
+
+1.10. "Modifications"
+    means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+    means any patent claim(s), including without limitation, method,
+    process, and apparatus claims, in any patent Licensable by such
+    Contributor that would be infringed, but for the grant of the
+    License, by the making, using, selling, offering for sale, having
+    made, import, or transfer of either its Contributions or its
+    Contributor Version.
+
+1.12. "Secondary License"
+    means either the GNU General Public License, Version 2.0, the GNU
+    Lesser General Public License, Version 2.1, the GNU Affero General
+    Public License, Version 3.0, or any later versions of those
+    licenses.
+
+1.13. "Source Code Form"
+    means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+    means an individual or a legal entity exercising rights under this
+    License. For legal entities, "You" includes any entity that
+    controls, is controlled by, or is under common control with You. For
+    purposes of this definition, "control" means (a) the power, direct
+    or indirect, to cause the direction or management of such entity,
+    whether by contract or otherwise, or (b) ownership of more than
+    fifty percent (50%) of the outstanding shares or beneficial
+    ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+    Licensable by such Contributor to use, reproduce, make available,
+    modify, display, perform, distribute, and otherwise exploit its
+    Contributions, either on an unmodified basis, with Modifications, or
+    as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+    for sale, have made, import, and otherwise transfer either its
+    Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+    or
+
+(b) for infringements caused by: (i) Your and any other third party's
+    modifications of Covered Software, or (ii) the combination of its
+    Contributions with other software (except as part of its Contributor
+    Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+    its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+    Form, as described in Section 3.1, and You must inform recipients of
+    the Executable Form how they can obtain a copy of such Source Code
+    Form by reasonable means in a timely manner, at a charge no more
+    than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+    License, or sublicense it under different terms, provided that the
+    license for the Executable Form does not attempt to limit or alter
+    the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+*                                                                      *
+*  6. Disclaimer of Warranty                                           *
+*  -------------------------                                           *
+*                                                                      *
+*  Covered Software is provided under this License on an "as is"       *
+*  basis, without warranty of any kind, either expressed, implied, or  *
+*  statutory, including, without limitation, warranties that the       *
+*  Covered Software is free of defects, merchantable, fit for a        *
+*  particular purpose or non-infringing. The entire risk as to the     *
+*  quality and performance of the Covered Software is with You.        *
+*  Should any Covered Software prove defective in any respect, You     *
+*  (not any Contributor) assume the cost of any necessary servicing,   *
+*  repair, or correction. This disclaimer of warranty constitutes an   *
+*  essential part of this License. No use of any Covered Software is   *
+*  authorized under this License except under this disclaimer.         *
+*                                                                      *
+************************************************************************
+
+************************************************************************
+*                                                                      *
+*  7. Limitation of Liability                                          *
+*  --------------------------                                          *
+*                                                                      *
+*  Under no circumstances and under no legal theory, whether tort      *
+*  (including negligence), contract, or otherwise, shall any           *
+*  Contributor, or anyone who distributes Covered Software as          *
+*  permitted above, be liable to You for any direct, indirect,         *
+*  special, incidental, or consequential damages of any character      *
+*  including, without limitation, damages for lost profits, loss of    *
+*  goodwill, work stoppage, computer failure or malfunction, or any    *
+*  and all other commercial damages or losses, even if such party      *
+*  shall have been informed of the possibility of such damages. This   *
+*  limitation of liability shall not apply to liability for death or   *
+*  personal injury resulting from such party's negligence to the       *
+*  extent applicable law prohibits such limitation. Some               *
+*  jurisdictions do not allow the exclusion or limitation of           *
+*  incidental or consequential damages, so this exclusion and          *
+*  limitation may not apply to You.                                    *
+*                                                                      *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+  This Source Code Form is subject to the terms of the Mozilla Public
+  License, v. 2.0. If a copy of the MPL was not distributed with this
+  file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+  This Source Code Form is "Incompatible With Secondary Licenses", as
+  defined by the Mozilla Public License, v. 2.0.

package/README.md

@@ -0,0 +1,150 @@
+# @jsprismarine/predicates
+
+The Java Edition predicate, item modifier and value provider evaluator. Loot tables, advancements
+and enchantments all compile their conditions and functions through this package. It parses
+Mojang's JSON once into closures and evaluates them against a `PredicateContext` that carries the
+loot context parameters, an injected random source, and the views a host plugs its own registries
+into.
+
+Every grammar member here was read out of the Java 26.3 server jar rather than from a wiki page.
+Parsing never throws: faults land in a `DiagnosticCollector` as errors or warnings, and the
+evaluation gives the safe answer instead.
+
+## Install
+
+```bash
+pnpm add @jsprismarine/predicates
+```
+
+## Using it
+
+```typescript
+import { PredicateContext, parsePredicate } from '@jsprismarine/predicates';
+
+const { value: survivesExplosion, diagnostics } = parsePredicate({ type: 'minecraft:survives_explosion' });
+
+const context = new PredicateContext({
+    parameterSet: 'block',
+    parameters: { block_state: { name: 'minecraft:stone' }, origin: { x: 0, y: 64, z: 0 }, explosion_radius: 4 }
+});
+
+survivesExplosion(context);
+context.diagnostics.entries;
+```
+
+`parseItemModifier`, `parseIntProvider`, `parseFloatProvider` and `parseLevelBasedValue` follow the
+same shape: they return the compiled value together with the diagnostics from parsing it.
+
+## Grammar coverage
+
+| Registry | 26.3 registers | This package |
+| --- | --- | --- |
+| `loot_condition_type` | 20 | 20 |
+| `loot_function_type` | 42 | 42 |
+| `context_int_provider_type` | 23 | 23 |
+| `context_float_provider_type` | 28 | 28 |
+| `enchantment_level_based_value_type` | 6 plus the bare-number constant | 7 |
+| `loot_score_provider_type` | 2 | 2 |
+| `loot_nbt_provider_type` | 2 | 1, `storage` reported |
+| `entity_sub_predicate_type` | 25 | 23, with `nbt` and `slots` reported |
+| `data_component_predicate_type` | 15 | 4 typed, the rest reported, plus the presence fallback |
+
+Three names in the original brief for this package do not exist in 26.3, and the table above
+follows the jar. `block_state_property` is now `match_block` and carries the block predicate
+inline. `value_check` split into `int_value_check` and `float_value_check`. `reference` was removed
+when every field learned to take a bare id, which is the composition rule below. The jar also adds
+`environment_attribute_check`, which the brief did not list.
+
+The entity sub-predicates implemented are the 14 vanilla's own loot tables and advancements use
+(`entity_type`, `location`, `components`, `type_specific/sheep`, `equipment`, `flags`, `vehicle`,
+`distance`, `type_specific/player`, `type_specific/cube_mob`, `type_specific/fishing_hook`,
+`type_specific/raider`, `type_specific/lightning`, `stepping_on`) plus `entity_tags`, `movement`,
+`movement_affected_by`, `effects`, `periodic_tick`, `team`, `passenger`, `targeted_entity` and
+`predicates`. `nbt` and `slots` need an NBT matcher and a slot model that live elsewhere, so they
+warn and evaluate false.
+
+## The composition rule
+
+26.3 made every field of a composable type accept four forms: an inline value, a namespaced id, a
+list mixing both, and a hash-prefixed tag id. One helper, `parseComposed`, implements it for all
+eight composable registries, and every predicate, modifier and provider field in this package goes
+through it.
+
+```json
+{ "condition": "minecraft:tool/can_silk_touch" }
+{ "condition": [{ "type": "minecraft:survives_explosion" }, "minecraft:tool/can_shear"] }
+{ "modifier": [{ "type": "minecraft:set_count", "count": 2 }, "minecraft:some_modifier"] }
+```
+
+A list of predicates reads as an `and`, and a list of modifiers applies in order, which is what
+Java does. `resolveMembers` covers the sibling member form, used by fields such as an item
+predicate's `items`, which name registry members instead of elements. A reference that points at
+itself reports a cycle rather than recursing.
+
+## Injectable seams
+
+All of these are optional. A member a host leaves out makes the predicate that needs it report a
+diagnostic and evaluate false, rather than failing the whole parse.
+
+- `ReferenceResolver` on the parse options resolves namespaced ids to element JSON and tags to
+  member ids. Without it, inline grammar still works and a reference is an error.
+- `RandomSource` on the context is the only randomness the evaluator uses, so `random_chance`,
+  `uniform`, `binomial`, `explosion_decay` and the weighted list reproduce exactly in a test.
+  `scriptedRandom`, `constantRandom` and `seededRandom` are built in.
+- `LevelView` answers weather, the world clock, biomes, structures, light, blocks, fluids, command
+  storage, scoreboards and environment attributes.
+- `ItemStackOps` owns stack construction, Bedrock auxiliary data, component writes, the stack size
+  limit, and the durability limit, so a host keeps its own item type behind the minimal
+  `{ id, count, components, meta? }` shape this package reads.
+- `EnchantmentView` answers enchantment levels, maximum levels and the enchanting table draw.
+- `ContentView` answers the few content questions the modifiers need and this package cannot own:
+  smelting results, player profiles, exploration map search, loot entry rolls and the dye table.
+- `GrammarExtensions` on the parse options registers entity sub-predicate and data component
+  predicate types this package does not implement, keyed by namespaced id, merged over the built-in
+  tables.
+
+## Loot context parameters
+
+`CONTEXT_PARAMETER_SETS` holds the 31 context key sets of 26.3 with the required and optional
+parameters of each, read from `LootContextParamSets` in the server jar. Reading a parameter the
+declared set does not provide reports
+
+```
+the chest loot context does not provide block_state
+```
+
+and yields undefined, so a predicate attached to the wrong loot table fails loudly instead of
+quietly passing. A required parameter the host forgot to supply reports as well; an absent optional
+parameter does not.
+
+## Decisions worth knowing
+
+**The item stack shape is fixed and its operations are injectable.** Threading a generic stack type
+through 20 conditions and 42 modifiers adds type noise without changing behavior, so a host adapts
+its own stack to `{ id, count, components }` at the edge and controls allocation, component
+defaults and limits through `ItemStackOps`.
+
+**Float providers round to 32 bits.** Java's float registry is `float`, not `double`, and the
+difference is visible: `set_damage` with a damage of 0.9 floors to 10 in Java and would floor to 9
+in double arithmetic. `Math.fround` on every float draw reproduces Java's value.
+
+**An unregistered key in a `predicates` map is a presence check.** 26.3 falls back to `AnyValue`
+when the key names a data component type rather than a predicate type, which is how vanilla writes
+`{"minecraft:map_id": {}}`. This package follows that and warns only when the ignored body is
+non-empty.
+
+**A tag that no resolver can expand is not an error in a member field.** The subject often carries
+its own tag list, so `resolveMembers` keeps the tag name and matches against it.
+
+## Corpus test
+
+`corpus.test.ts` parses the real Java 26.3 vanilla datapack out of the cached server jar and
+asserts the grammar reports nothing at all, neither errors nor warnings. It measures 3 predicate
+files, 26 int provider files, 4 float provider files, 1302 condition fields and 1098 modifier
+fields across 1447 loot tables, and 263 loot conditions across 1866 advancements. It needs the
+cache that `pnpm --filter @jsprismarine/bedrock-data run fetch:sources` populates, so it only runs
+with `JSP_VANILLA_DATAPACK` set and CI without the cache skips it.
+
+## License
+
+MIT