Document D&D item event support

docs/internal/llm.md

@@ -39,7 +39,7 @@ without exposing Scriptorium types through stage contracts.
 7. injecting that one shared client into complete pipeline preparation before
    the source file is read or the runner is invoked.
 
-The D&D scene chunker and spell, NPC, combat-turn, NPC-interaction, and
+The D&D scene chunker and spell, NPC, combat-turn, item-event, NPC-interaction, and
 scene-description extractors retain this
 injected client and use it for every structured completion. Operation requests
 do not carry an LLM client.
@@ -99,7 +99,7 @@ D&D prompt content. `internal/framework/promptfs` provides the domain-neutral
 filesystem composition helper used to combine module-owned files with shared
 domain prompt fragments.
 
-The D&D scene chunker and spell, NPC, combat-turn, NPC-interaction, and
+The D&D scene chunker and spell, NPC, combat-turn, item-event, NPC-interaction, and
 scene-description extractors each declare an
 ordered prompt asset manifest. The manifest lists the package-owned YAML and
 Markdown files, then the exact shared fragments rendered by that prompt; the
@@ -134,12 +134,13 @@ prompt places its final boundary on its lane-specific instructions, immediately
 before the transcript. The transcript does not carry cache control because no
 reusable content follows it.
 
-Accordingly, the common prefix of the spell, NPC, combat, and interaction
+Accordingly, the common prefix of the spell, NPC, combat, item-event, and interaction
 extraction prompts is system,
 extraction evidence, identity, and campaign references. The NPC prompt then
 renders task, instructions, and transcript. Spell renders the NPC registry,
 catalog, task, instructions, and transcript. Combat renders the NPC registry,
-task, instructions, and transcript. NPC interaction renders the names-only NPC
+task, instructions, and transcript. Item-event renders task, instructions, and
+transcript without a generated-artifact input. NPC interaction renders the names-only NPC
 registry, task, instructions, and transcript. The
 scene chunker is not an extraction lane: it retains its separate system,
 transcript, campaign-reference, task, and instruction order and marks its
@@ -166,7 +167,7 @@ return defensive copies, and expose a diagnostics map that omits schema bytes.
 The small framework registry contains only generic test schemas; production
 schemas remain package-owned.
 
-The spell, NPC, combat, NPC-interaction, and scene-description extractors'
+The spell, NPC, combat, item-event, NPC-interaction, and scene-description extractors'
 package-owned prompts declare their
 structured JSON inputs and private response schemas. Each private response
 schema remains separate from its durable artifact codec schema; this work does

docs/internal/modules.md

@@ -17,16 +17,16 @@ validator registry. Package-family registrars compose those leaf registrations
 into the production catalog and own family-level policy such as default
 validator chains and prompt asset collection.
 
-Production input, chunk, output, and D&D spell-, NPC-, combat-, interaction-, and scene-description-extract packages
+Production input, chunk, output, and D&D spell-, NPC-, combat-, item-event-, interaction-, and scene-description-extract packages
 register strict option decoders and run-local builders. Preparation decodes their options into
 implementation-owned values and injects dependencies plus the materialized
 reference set for the selected target. Each builder receives an isolated clone
 of that set; input and output builders receive no references. The spell, NPC,
-combat, interaction, and scene-description extractors are typed over the canonical D&D model. D&D validators, merge,
+combat, item-event, interaction, and scene-description extractors are typed over the canonical D&D model. D&D validators, merge,
 and normalize use typed variants; JSON representation validators use serialized
 requests; and unconditional validators expose separate chunk and typed
 variants. The D&D production registrar registers the canonical typed spell,
-NPC, combat, interaction, and scene-description implementations, including their kind-specific merge and
+NPC, combat, item-event, interaction, and scene-description implementations, including their kind-specific merge and
 normalize behavior.
 
 For D&D artifact defaults, generic JSON syntax validation runs first. Rejecting
@@ -56,7 +56,7 @@ declarations, prompt-input assembly, and source-unit/citation helpers belong in
 `internal/modules/dnd/shared`, which owns operation-scoped indexed
 source-reference validation, citation traversal, ordering and canonicalization,
 plus bounded D&D diagnostics. The
-D&D scene chunker and spell, NPC, combat-turn, NPC-interaction, and scene-description extractors use ordered
+D&D scene chunker and spell, NPC, combat-turn, item-event, NPC-interaction, and scene-description extractors use ordered
 package-local prompt manifests for both rendering and prompt fingerprinting, so
 only the shared fragments each prompt actually renders participate in either
 operation. Extraction prompts place stable shared and lane-specific context
@@ -67,7 +67,7 @@ contracts expose only Notarius structured-completion types, not Scriptorium
 public types.
 
 The shared `PrepareChunkExtraction` helper owns common extraction preflight and
-transcript material preparation for the spell, NPC, combat-turn,
+transcript material preparation for the spell, NPC, combat-turn, item-event,
 NPC-interaction, and scene-description extractors. It validates common request
 state, clones supplied source metadata, falls back to the materialized chunk
 when content is absent, checks that content remains chunk-identical, and fills
@@ -150,6 +150,11 @@ The `internal/modules/dnd/codec/combatturns` package owns the durable
 is registered by the production D&D family registrar for the selectable combat
 lane.
 
+The `internal/modules/dnd/codec/itemevents` package owns the durable
+`dnd/item-event-list` schema and candidate versus approved JSON boundary. It is
+registered by the production D&D family registrar. Its external contract is
+defined in the [D&D item-event artifact contract](../integrations/dnd-item-event-artifacts.md).
+
 The `internal/modules/dnd/codec/npcinteractions` package owns the durable
 `dnd/npc-interaction-list` schema and candidate versus approved JSON boundary.
 It is registered by the production D&D family registrar for the selectable
@@ -348,6 +353,23 @@ The combat normalizer accepts only the optional structured NPC registry.
 Campaign references remain extractor-only LLM context and are not materialized
 for deterministic normalization.
 
+### `internal/modules/dnd/extract/itemevents`
+
+The item-event extractor prepares one structured request from the accepted
+chunk and optional campaign references, then maps private records to
+`dnd.ItemEventList` with the current source identity. It declares only optional
+`glossary`, `party`, `players`, and deprecated `roster` reference slots; these
+can disambiguate names but never supply evidence. It has no NPC,
+scene-description, or item-registry dependency.
+
+The private response schema owns structural transport validation. The extractor
+preserves candidate category, holder, quantity, and source-range values for the
+deterministic validators, removes exact duplicate ranges, and source-orders
+events. The source-reference validator requires citations to fit the current
+accepted chunk. Prompt, response-schema, and mapping identities participate in
+checkpoint identity. The durable schema is owned separately by
+`internal/modules/dnd/codec/itemevents`.
+
 ### `internal/modules/dnd/extract/npcinteractions`
 
 The NPC interaction extractor requires the structured `npcs` registry slot. It
@@ -384,7 +406,7 @@ normalization warnings.
 ### `internal/modules/generic/merge/appendorder`
 
 The merger passes typed values to an injected combine function in framework
-source-chunk order. The D&D registrar specializes it for all five artifact
+source-chunk order. The D&D registrar specializes it for all six artifact
 lists; each append merger preserves collection presence and order while giving
 the result independently owned nested source-reference slices.
 
@@ -432,6 +454,16 @@ digest/count metadata; generated identity is retained in framework provenance
 and dependency fingerprints. The normalizer is included in the production D&D
 registrar with the default combat normalization chain.
 
+### `internal/modules/dnd/normalize/itemevents`
+
+The item-event normalizer accepts no options or references and makes no LLM
+calls. It trims display-edge whitespace in names and holders, canonicalizes
+source references, source-orders events, and collapses only exact duplicates
+with complete valid evidence. It does not create a ledger, calculate balances,
+resolve aliases, infer quantities or holders, or reconcile nearby events. Its
+policy fingerprint and bounded warnings identify deterministic normalization;
+the matching invariant validator checks the resulting order and duplicate rule.
+
 ### `internal/modules/dnd/normalize/npcinteractions`
 
 The interaction normalizer requires the same immutable NPC registry. It
@@ -541,6 +573,21 @@ expose local policy fingerprints. In the registered defaults, JSON syntax runs
 first; combat shape, normalized invariants when applicable, and source-reference
 validation precede JSON Schema validation; warning-only relatedness runs last.
 
+## D&D Item-Event Validators
+
+Item-event shape validation owns the required list, non-empty name, supported
+category, category-and-holder combination, positive optional quantity, and
+non-empty source-reference collection. Source-reference validation defers
+malformed shapes, checks current-source identity and ordered ranges, and during
+extraction requires every citation to fit the accepted chunk. Relatedness is
+advisory and warning-only: it checks the event name against cited transcript
+text while deferring malformed candidates and invalid ranges to their blocking
+owners. The normalized-invariants validator owns display normalization,
+canonical source-reference order, chronology, and exact duplicate identity.
+All four validators are deterministic and expose policy fingerprints. The
+registered chains run syntax and blocking checks before durable JSON Schema;
+relatedness remains last.
+
 ## D&D NPC Interaction Validators
 
 Interaction shape validation owns the required list, registry name, supported
@@ -573,7 +620,7 @@ complete framework registry set and one LLM asset registry. It invokes
 `internal/modules/seriatim/register`, and `internal/modules/dnd/register` in
 that order, then exposes the matching catalog for resolution. The generic and
 Seriatim registrars own their production leaf registrations. The D&D registrar
-owns D&D leaf registrations, typed spell, NPC, combat, interaction, and scene-description default-validator
+owns D&D leaf registrations, typed spell, NPC, combat, item-event, interaction, and scene-description default-validator
 chains, typed append-order specializations, and D&D prompt/schema asset
 collection. Its registration helpers group module, validator, prompt-asset, and
 chain composition while retaining artifact-specific merge and clone behavior in

docs/internal/overview.md

@@ -69,9 +69,9 @@ constructs input, chunk, validators, ordered lanes, and output before source
 parsing. Production modules use strict construction-time option decoding, and
 LLM-backed modules retain the injected shared client. The D&D family registers
 the canonical `dnd/spell-list`, `dnd/npc-list`, `dnd/combat-turn-list`,
-`dnd/npc-interaction-list`, and `dnd/scene-description-list` codecs, typed
-spell, NPC, combat, interaction, and scene-description extractors and
-normalizers, validators,
+`dnd/item-event-list`, `dnd/npc-interaction-list`, and
+`dnd/scene-description-list` codecs, typed spell, NPC, combat, item-event,
+interaction, and scene-description extractors and normalizers, validators,
 plus kind-specific generic merge strategies; generic JSON validators use the
 serialized-validation contract. The runner executes lanes through
 private exact-type-checked closures, coordinates extract results independently
@@ -90,22 +90,26 @@ Configuration. The implemented module packages are:
 | `internal/modules/seriatim/input/transcript` | Parses the supported Seriatim transcript format into the generic source model. |
 | `internal/modules/generic/chunk/units` | Splits ordered source units by unit count and overlap. |
 | `internal/modules/dnd/chunk/scenes` | Produces contiguous D&D scene chunks from structured model output. |
-| `internal/modules/dnd` | Owns the canonical D&D spell-list, spell-cast, NPC-list, NPC, combat-turn-list, combat-turn, NPC-interaction-list, and scene-description-list artifact types. |
+| `internal/modules/dnd` | Owns the canonical D&D spell-list, spell-cast, NPC-list, NPC, combat-turn-list, combat-turn, item-event-list, item-event, NPC-interaction-list, and scene-description-list artifact types. |
 | `internal/modules/dnd/codec/spells` | Strictly decodes and stably encodes the durable D&D spell-list representation. |
 | `internal/modules/dnd/codec/npcs` | Strictly decodes and stably encodes the durable D&D NPC-list representation. |
 | `internal/modules/dnd/codec/combatturns` | Strictly decodes and stably encodes the durable D&D combat-turn-list representation. |
+| `internal/modules/dnd/codec/itemevents` | Strictly decodes and stably encodes the durable D&D item-event-list representation. |
 | `internal/modules/dnd/codec/npcinteractions` | Strictly decodes and stably encodes the durable D&D NPC-interaction-list representation. |
 | `internal/modules/dnd/codec/scenedescriptions` | Strictly decodes and stably encodes the durable D&D scene-description-list representation. |
 | `internal/modules/dnd/extract/spells` | Maps private structured model output to canonical source-grounded D&D spell lists. |
 | `internal/modules/dnd/extract/npcs` | Maps private structured model output to canonical source-grounded D&D NPC lists. |
 | `internal/modules/dnd/extract/combatturns` | Uses exact scene eligibility to select combat chunks, then maps private structured model output to source-grounded D&D combat-turn candidates. |
+| `internal/modules/dnd/extract/itemevents` | Maps private structured model output to source-grounded D&D item-event candidates. |
 | `internal/modules/dnd/extract/npcinteractions` | Maps private structured model output to current-source NPC interaction candidates grounded by a required registry. |
 | `internal/modules/dnd/extract/scenedescriptions` | Maps one private scene description to the current accepted chunk's ID and exact range. |
 | `internal/modules/dnd/npcinteractions` | Owns interaction occurrence ordering, valid-evidence checks, and exact interaction identity shared by normalization and invariant validation. |
 | `internal/modules/dnd/normalize/combatturns` | Canonicalizes and orders merged combat turns, applies exact NPC identity matches, and collapses only exact valid-evidence duplicates. |
+| `internal/modules/dnd/normalize/itemevents` | Trims, source-orders, and removes only exact valid-evidence item-event duplicates. |
 | `internal/modules/dnd/normalize/npcinteractions` | Canonicalizes required-registry names, orders interaction occurrences, and collapses only exact valid-evidence duplicates. |
 | `internal/modules/dnd/normalize/scenedescriptions` | Trims, source-orders, and removes only exactly identical scene descriptions while rejecting ID and range conflicts. |
 | `internal/modules/dnd/validate/combatturns` | Provides deterministic shape, source-reference, source-relatedness, and normalized-invariant validation for the production combat chains. |
+| `internal/modules/dnd/validate/itemevents` | Provides deterministic shape, source-reference, source-relatedness, and normalized-invariant validation for item-event chains. |
 | `internal/modules/dnd/validate/npcinteractions` | Provides deterministic shape, registry, source-reference, source-relatedness, and normalized-invariant validation for interaction chains. |
 | `internal/modules/dnd/validate/scenedescriptions` | Provides deterministic shape, exact extraction attachment, source-relatedness, and normalized-invariant validation for scene-description chains. |
 | `internal/modules/dnd/npcs/registry` | Resolves validated normalized NPC references into immutable grounding data and exact identity lookup. |