From e4e82b3b517dd57d2648b38524c47b5a4c7bd39f Mon Sep 17 00:00:00 2001 From: Joey Yakimowich-Payne Date: Tue, 21 Apr 2026 19:17:04 -0600 Subject: [PATCH] docs(chess): correct trigger count from 11 to 10 (3 existing + 7 new) F4 scope-fidelity audit flagged a plan-text vs implementation count drift. Only three trigger primitives existed before Wave 2 (on-turn-start, on-capture, on-damaged) plus one non-trigger conditional primitive, NOT four trigger primitives. Wave 2 added seven more, so the correct total is 10 trigger primitives, not 11. This commit corrects the RULES.md intro paragraph from 11 trigger primitives (4 existing + 7 added in Wave 2) to 10 trigger primitives (3 existing + 7 added in Wave 2) matching the actual file-system count under packages/chess/src/modifiers/primitives/on-*.ts. No structural docs reorganization needed (the section already tabulates the 3 existing triggers under Existing triggers (pre-Wave 2) and the 7 new ones under New triggers (Wave 2) individually). --- packages/chess/RULES.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/chess/RULES.md b/packages/chess/RULES.md index 8059520..b65cf3d 100644 --- a/packages/chess/RULES.md +++ b/packages/chess/RULES.md @@ -499,7 +499,7 @@ Variant of FIDE with queens removed and replaced by a second king per side. Whit Custom modifier descriptors compose **trigger primitives** that wire nested effect primitives into specific points of the engine's per-move dispatch. Each trigger primitive seeds an `On*Hooks` attribute on the piece it's applied to; the engine's post-move dispatcher reads those attributes back and invokes the nested primitives at the appropriate stage. -This section documents the **11 trigger primitives** (4 existing + 7 added in Wave 2), the order in which the engine fires them, and the `PrimitiveApplyContext` extensions (target redirection + event payload) that nested primitives can read. +This section documents the **10 trigger primitives** (3 existing + 7 added in Wave 2), the order in which the engine fires them, and the `PrimitiveApplyContext` extensions (target redirection + event payload) that nested primitives can read. For the broader context-object types referenced below (`PrimitiveApplyContext`, `TargetResolver`, `PrimitiveEvent`, `resolveTargets`), see [`docs/PRESET-API.md`](./docs/PRESET-API.md#primitive-context-target-redirection--event).