@jsprismarine/items 0.0.0 → 0.16.0-unstable-20261029134110

package/CHANGELOG.md

@@ -0,0 +1,59 @@
+# @jsprismarine/items
+
+## 0.16.0-unstable-20261029134110
+
+### Minor Changes
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`440e164`](https://github.com/JSPrismarine/JSPrismarine/commit/440e164b88f43548c9c4fe8ae896387157f21701) Thanks [@filiphsps](https://github.com/filiphsps)! - Expose merged Java datapack tag memberships on resolved block and item types.
+
+### Patch Changes
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`d5dc760`](https://github.com/JSPrismarine/JSPrismarine/commit/d5dc760107a1dbc9c5ba9eb5fc9fb544d725c02d) Thanks [@filiphsps](https://github.com/filiphsps)! - Project explicit Bedrock item display names into item registry component data.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`c140ef6`](https://github.com/JSPrismarine/JSPrismarine/commit/c140ef6e3072eb97c7a8b123876ea08726ed9910) Thanks [@filiphsps](https://github.com/filiphsps)! - Use scalar Bedrock item components when projecting item registry properties.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`b3a2a6f`](https://github.com/JSPrismarine/JSPrismarine/commit/b3a2a6f2d8baca370c541439257bfb4dc4786902) Thanks [@filiphsps](https://github.com/filiphsps)! - Preserve Bedrock item components and tags
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`2c459cd`](https://github.com/JSPrismarine/JSPrismarine/commit/2c459cd2ab8822f0364c1ce8e473cf0487b294a8) Thanks [@filiphsps](https://github.com/filiphsps)! - Project Java tool rules to Bedrock digger data
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`2d20fee`](https://github.com/JSPrismarine/JSPrismarine/commit/2d20fee23b5fd58cf78dfa12b266f074dab110b8) Thanks [@filiphsps](https://github.com/filiphsps)! - Expose Bedrock tag queries on item stacks
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`bbda9ea`](https://github.com/JSPrismarine/JSPrismarine/commit/bbda9ea5c0ed57fe60e93c25d6131234a7e8e049) Thanks [@filiphsps](https://github.com/filiphsps)! - New package: the item definition and component runtime. It implements all 122 of Java 26.3's item
+  data component types as parsed components for `@jsprismarine/content`, with the value shapes checked
+  against Mojang's own per-item reports, and evaluates the `context_int_provider` trees 26.3 moved
+  fuel, compost and brewing numbers behind. `ItemStack` is Java's model, a type reference plus a
+  component patch over the type's defaults, with the `!component` removal marker representable and
+  stacking decided by the patch rather than by NBT comparison. A committed table maps the 1658 Java
+  items onto 1605 of Bedrock's 1606 item identifiers, each carrying its Java-sourced components, with
+  the 53 items that lose a row listed in a reviewed exception list the generator checks.
+  `projectItemToBedrock` turns a type into the component compound `ItemRegistryPacket` carries, shaped
+  against a Bedrock Dedicated Server capture, and `flattenItemFacts` precomputes stack size, damage,
+  food, tool and burn time into typed arrays. The seven `ItemCustomComponent` hook names are declared
+  for the behavior families that come next.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`f198a15`](https://github.com/JSPrismarine/JSPrismarine/commit/f198a156a8c307c941efd01a4bd4604eba0f5626) Thanks [@filiphsps](https://github.com/filiphsps)! - Send Bedrock item tag memberships and declared icon textures in the item registry component data.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`c1591b1`](https://github.com/JSPrismarine/JSPrismarine/commit/c1591b1e567a51dc80ecbbdfdbdc8e7c7f4f6c42) Thanks [@filiphsps](https://github.com/filiphsps)! - Add the Java data generator step the pipeline was missing. `pnpm --filter
+  @jsprismarine/bedrock-data run datagen:java` re-checks the fetched server jar's sha1, runs
+  Mojang's `net.minecraft.data.Main` against it, and writes the vanilla datapack to
+  `node_modules/.cache/jsprismarine/vanilla-datapack/<version>/` and the data reports to
+  `node_modules/.cache/jsprismarine/java-reports/<version>/generated/reports/`, the two
+  directories every Java-data reader already looks in. A re-run is a no-op unless `--force` is
+  passed.
+  
+  Nothing produced those directories before, so the data-driven overworld generator failed on
+  every server start with a message naming `fetch:sources` and `dump:java`, neither of which
+  writes them. Those messages now name `datagen:java`, and so does the pack stack diagnostic for
+  a missing Java vanilla datapack.
+  
+  The mapping and item table generators read `java -version` from stdout, which is empty
+  because the banner goes to stderr, so their own fallback run of the data generator always
+  threw "No JDK >= 25 found". They read `java --version` now.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`b96ce93`](https://github.com/JSPrismarine/JSPrismarine/commit/b96ce93238f3efd66c709f213cd8d5d42fc8f425) Thanks [@filiphsps](https://github.com/filiphsps)! - Spawn eggs now work on targeted entities, and matching eggs create babies for entity data that enables `minecraft:spawn_egg_interaction`.
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`ef39583`](https://github.com/JSPrismarine/JSPrismarine/commit/ef395830d28b1b242b20a7246c8bb6ec781f5f4c) Thanks [@filiphsps](https://github.com/filiphsps)! - Project Bedrock block placer components
+
+- [#2628](https://github.com/JSPrismarine/JSPrismarine/pull/2628) [`cd01052`](https://github.com/JSPrismarine/JSPrismarine/commit/cd01052548178421cd323b316d77d87374cee9dc) Thanks [@filiphsps](https://github.com/filiphsps)! - Project Java repair materials into Bedrock item components
+- Updated dependencies [[`d4a2a0b`](https://github.com/JSPrismarine/JSPrismarine/commit/d4a2a0b2787e171583e6db0aec1b750e8aeb1e95), [`d220519`](https://github.com/JSPrismarine/JSPrismarine/commit/d220519e2e460148a90cbde9d643033e27bf8f5e), [`bffe7a8`](https://github.com/JSPrismarine/JSPrismarine/commit/bffe7a89abe4151001fe7a8c323f5ce31ad55d1c)]:
+  - @jsprismarine/content@0.16.0-unstable-20261029134110

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,208 @@
+# @jsprismarine/items
+
+The item definition and component runtime. It implements Java Edition 26.3's item data component
+system on top of `@jsprismarine/content`, and hands the result out under Bedrock item identifiers.
+
+Two sentences describe the whole package. An item type is a Bedrock identifier carrying the Java
+default components of the Java item that maps onto it. An item stack is a reference to one of those
+types, a count, and a component patch layered over the type's defaults.
+
+## Why identity is Bedrock and properties are Java
+
+The client decides identity. A Bedrock client knows an item by the identifier the server sends in
+`ItemRegistryPacket`, and it will not render or name an item it has no entry for, so the server's
+item table has to be Bedrock's. The server decides properties. Nothing in either Bedrock pack
+format publishes nutrition, durability, mining speed or burn time for vanilla items, while Mojang's
+Java data generator publishes all of them for all 1658 Java items. That is
+[the plan's decision](../../docs/plans/data-driven-vanilla.md) in sections 2 and 4, and this package
+is the join: 1658 Java items go in through `@jsprismarine/mapping`, 1605 Bedrock identifiers come
+out with components attached.
+
+Nothing here knows that two editions exist at runtime. The join runs once in the generator and the
+committed table is Bedrock-keyed, so the mapping package is a development dependency rather than a
+runtime one.
+
+The item loader also keeps Bedrock behavior pack data separate: `ItemType.bedrockComponents` holds
+the raw component bodies, and `ItemType.tags` plus `hasTag(name)` expose the active Bedrock tags.
+`ItemStack.getTags()` and `ItemStack.hasTag(name)` read the same tags from the stack's type. These
+do not replace or reinterpret Java's default components, and retaining a body does not imply that
+the server executes its behavior.
+Java datapack item memberships are available as `ItemType.javaTags` and `hasJavaTag(name)`, and as
+`ItemStack.getJavaTags()` and `hasJavaTag(name)` on a stack.
+
+## The Java component model
+
+Java 1.20.5 replaced the `tag` NBT blob with structured components, and 26.3 registers 122 of them
+in `minecraft:data_component_type`. The catalog in `src/components/` implements all 122, split the
+way vanilla uses them, with each number measured from the pinned data generator output rather than
+chosen:
+
+| Group | Count | File |
+| --- | --- | --- |
+| A default on every one of the 1658 items | 13 | `components/universal.ts` |
+| A default on some items | 56 | `components/defaults.ts` |
+| Only ever on an individual stack | 53 | `components/stackOnly.ts` |
+
+Each component is a `ComponentFactory` with a parser for its value, built from the combinators in
+`schema.ts`. The parsers are strict about the fields they know and lenient about fields they do
+not, because Mojang adds a field to a component within a release and a schema that rejected one
+would turn a data refresh into a load failure. Two components, `minecraft:sulfur_cube_content` and
+`minecraft:waxed`, have no vanilla default and appear in no vanilla data file, so their shape is
+unverified against the pinned sources; they are listed in `UNVERIFIED_SHAPE_COMPONENTS`.
+
+26.3 also moved fuel, compost and brewing numbers behind the `context_int_provider` and
+`context_float_provider` registries, so `minecraft:cooking_fuel` on a boat reads
+`{"burn_time": "minecraft:cooking/time_boats"}` and that file is a division by a conditional over
+two more files. The generator copies the 30 definitions item components reach into the table, and
+`numberProvider.ts` evaluates one: `minecraft:cooking/time_boats` is 1200 ticks in a furnace and
+600 in a smoker, and `minecraft:compostable/low` is 0.3, the expected value of its weighted list.
+
+## Item stacks and the component patch
+
+An `ItemStack` is a `content` `Instance`: a holder for its type, a count, and a patch. Reading a
+component reads the patch first and the type's defaults second, which is Java's
+`PatchedDataComponentMap`. A patch entry can also remove a default, which is the `!component` marker
+Java's command grammar writes, and removal is a separate entry rather than an absence so it survives
+a round trip.
+
+```typescript
+import { food, ItemStack, loadItemTypes } from '@jsprismarine/items';
+
+const { registry } = loadItemTypes();
+const apple = new ItemStack(registry.holder('minecraft:apple'), 16);
+
+apple.params(food); // { nutrition: 4, saturation: 2.4 }, from the type
+apple.remove('minecraft:food'); // now undefined, and the patch records the removal
+```
+
+Equality follows from the patch, not from comparing NBT. `sameItemSameComponents` compares the item
+and then the patch, which is what `ItemStack.isSameItemSameComponents` does in the pinned 26.3
+server jar: it calls `Objects.equals` on two `PatchedDataComponentMap`s, whose own `equals` compares
+the prototype and the patch map. One consequence is worth stating because it looks like a bug.
+Setting a component to the value the type already defaults to produces a stack that reads the same
+as an untouched one and does not stack with it. That is Java's behavior, verified by disassembly,
+and `canStack` and `mergeStacks` inherit it.
+
+## The hook seam
+
+Item behavior does not live in this package. The seven hooks in `hooks.ts` are the seam the behavior
+families plug into, and they carry Mojang's `ItemCustomComponent` names unchanged so a future script
+host maps onto them one name at a time:
+
+```typescript
+interface ItemHooks {
+    onUse: (event: ItemUseEvent) => ItemUseResult | undefined;
+    onUseOn: (event: ItemUseOnEvent) => ItemUseResult | undefined;
+    onMineBlock: (event: ItemMineBlockEvent) => void;
+    onHitEntity: (event: ItemHitEntityEvent) => void;
+    onBeforeDurabilityDamage: (event: ItemBeforeDurabilityDamageEvent) => number | undefined;
+    onCompleteUse: (event: ItemCompleteUseEvent) => ItemUseResult | undefined;
+    onConsume: (event: ItemConsumeEvent) => ItemUseResult | undefined;
+}
+```
+
+Two deliberate differences from Mojang's interface. Each event carries this package's `ItemStack`
+rather than a scripting handle, and the hooks a caller can cancel return a value instead of mutating
+the event, because `HookTable.dispatchFirst` decides who handled an interaction by the first result
+that is not undefined. The event types name the world with the smallest interfaces that work,
+`ItemSource` and `BlockReference`, so this package depends on no world implementation and a behavior
+that needs more narrows the value itself.
+
+None of the 122 components declares a hook. Components are parsed data and behavior arrives as a
+`Behavior` attached by identifier or by tag, which is how one bucket behavior covers twelve buckets.
+Dispatch order is component order, then behaviors in attachment order, so the server's own code has
+the last word over what a pack declared.
+
+The research counted roughly 30 item behaviors with no data expression in either edition, among them
+buckets, bows, crossbows, compasses, maps, leads, name tags, spyglasses, bone meal and fireworks.
+Those are the behavior agent's work; the components cover food, tools, weapons, armor, shields,
+gliders, totems, spears, fuel, compost and block transformation.
+
+## The Bedrock projection
+
+`projectItemToBedrock` turns one resolved type into the component compound the Bedrock client needs.
+It does not send anything; `ItemRegistryPacket` belongs to the protocol package.
+
+The two editions name the same facts differently, so every shape the projection writes is read off a
+Bedrock Dedicated Server 1.26.51.1 capture, the `item_components.nbt` golden in
+`@jsprismarine/bedrock-data`, rather than written from documentation. Java's `max_damage` becomes
+`minecraft:durability.max_durability`. Java's absolute `food.saturation` becomes Bedrock's
+`saturation_modifier`, the ratio it is computed from. Java has no enchanting category at all, so
+`enchantableSlotOf` derives one from the `mineable/*` tag in the item's tool rules, the equipment
+slot, or the spear, shield and glider components. The apple comes out with the same
+`max_stack_size`, `use_duration`, `use_animation` and food values the real server sends.
+
+Keys with no Java source are left out rather than guessed, so the protocol layer can tell a derived
+value from a placeholder. `BEDROCK_ONLY_ITEM_PROPERTIES` lists the seven `item_properties` keys that
+come from the creative catalog, the resource pack or nothing at all.
+`UNPROJECTED_BEDROCK_COMPONENTS` remains as an explicit coverage list and is currently empty.
+The active Bedrock item definition's `minecraft:block_placer` body is also projected, including its
+block selector list and default behavior flags. Its explicit display name and icon, plus the type's
+resolved Bedrock tags, pass through as `minecraft:display_name`, `minecraft:icon`, and `item_tags`;
+Java `minecraft:repairable` item sets expand through the loaded Java item tags and map each member to
+its Bedrock identifier. Java `minecraft:tool` rules become Bedrock `minecraft:digger` rules: block
+tags expand through the loaded Java block tags, then each block maps to a Bedrock identifier. Bedrock
+documents digging speeds as integers, so the client projection rounds Java's fractional speeds and
+caps values above the signed integer range; server mining continues to use the original Java rules
+and speeds. Java tags are not emitted as Bedrock `item_tags`. The definition's scalar item components
+override the corresponding Java-derived registry values when present. The food remainder is
+available through an injected `mapIdentifier`.
+
+## Flattened facts
+
+`flattenItemFacts` precomputes the five numbers a hot path reads into typed arrays indexed by the
+registry's dense item id: maximum stack size, maximum damage, whether the item is food, whether it
+is a tool, and the burn time in ticks. A furnace tick reads `facts.burnTimeTicks[id]` instead of
+walking a component list and evaluating a provider tree.
+
+## The exception list
+
+Mapping 1658 Java items onto 1606 Bedrock identifiers loses rows two ways, and `exceptions.ts`
+accounts for both in nine reviewed rows covering 53 Java items.
+
+Five rows are reviewed losses, the six items `@jsprismarine/mapping` already lists: the spectral
+arrow, the debug stick, the knowledge book, the furnace minecart and the two test blocks. A loss
+never contributes components, because writing the debug stick's properties onto the plain stick
+would give the fallback item the wrong behavior.
+
+Four rows are merges, the 47 items that share a Bedrock identifier with another: 16 structure
+locator maps onto `minecraft:filled_map`, the tipped arrow onto `minecraft:arrow`, and 15 banner and
+15 bed colors onto `minecraft:banner` and `minecraft:bed`. One Java item supplies each shared
+identifier's properties, picked by a deterministic rule: the item whose own identifier matches, then
+the lowest Bedrock damage value, then the first identifier alphabetically. The others are listed with
+the damage value that selects them, so nothing is dropped silently.
+
+That leaves `minecraft:unknown` as the one Bedrock identifier of 1606 with no row, because the only
+Java items that reach it are the two test blocks.
+
+The generator recomputes the set and refuses to emit when it disagrees with the file, so adding a row
+is how a maintainer accepts a new gap, and a row that stops matching fails the build.
+
+## Regenerating the table
+
+`src/tables/itemTypes.json` is generated and committed. After a Java or Bedrock version bump:
+
+```sh
+pnpm --filter @jsprismarine/bedrock-data run fetch:sources
+pnpm exec turbo run build --filter=@jsprismarine/mapping
+pnpm --filter @jsprismarine/items run generate:item-types
+```
+
+The generator runs Mojang's data generator against the hash-verified server jar when its reports are
+missing from the cache, which needs a JDK of at least version 25 (`JAVA_HOME` or `JSP_JAVA_HOME`).
+It refuses to emit when a Java item has neither a mapping nor a reviewed exception, when a component
+name is not in the pinned registry report, when a produced Bedrock identifier is missing from the
+captured item table, or when the computed exceptions disagree with `src/exceptions.ts`.
+
+## Tests
+
+`vitest run` covers the catalog, the patch model, hook dispatch order, the generated table, the
+flattened facts and the projection against the documented Bedrock component names. One test is
+gated: setting `JSP_JAVA_REPORTS` to the absolute path of the data generator's `generated`
+directory reparses all 1658 real item component files and asserts zero parse errors. From the
+repository root:
+
+```sh
+JSP_JAVA_REPORTS="$PWD/node_modules/.cache/jsprismarine/java-reports/26.3/generated" \
+  pnpm --filter @jsprismarine/items exec vitest run
+```