User directive: 'update the plan. v14 only'. Implementation:
**scope change (Foundry v14 only):**
- registered-hooks.js: renderChatInput entry drops the v13
renderChatLog name. Single subscription to the v14 name.
- anti-corruption.js: combatRound arg-normalization no longer
detects the v13 round-num position. v14's updateOptions.round
is the only path. Removed the v13 comments from the other
arg shapes (combatEnd, combatTurn).
- module.json: compatibility.minimum is now 14 (was 13).
verified stays 14.
- package.json: version 0.3.0 -> 0.4.0 (semver-breaking: dropping
v13 support is a breaking change for v13 consumers).
- package.json description: 'Foundry VTT v14-only module' prefix.
**test plan:**
- tests/PLAN.md: v14-only scope documented at the top of the file
and in Section E. Status line bumps 554 to 546 assertions
(v13-only assertions dropped). Test files table re-scoped to
v0.4.0.
- tests/verify-hooks-lib.mjs: dropped the v13-only assertions
(E.2 'renderChatLog in installed', E.3's 'both v13 and v14
produce' check, E.4's v13 round shape). Kept the v14-only
assertions + added an inverse assertion: 'renderChatLog is NOT
in installed raw hooks' to lock the v14-only scope.
- tests/verify-hooks-lib.mjs: stub table at line ~520 drops
renderChatLog (dead in production now).
**doc updates:**
- README.md: new 'v0.4.0 — Foundry v14 only' section explaining
the change + migration note for v13 consumers.
- docs/HOOK_CONTRACT.md: v0.3.0 header. §9 marks the v13 column
as historical. §10 example uses the v14 shape only.
**artifact:**
- foundry-hooks-lib-0.4.0.zip built (82KB, 46 entries, inner
version 0.4.0, inner compatibility.minimum 14).
**verified:**
- npm test: 546/546 assertions passed
- npm run test:foundry: 30/30 assertions passed
- npm run test:perf: 6/6 assertions passed (median 0.0003ms/fire)
- battle-focus E2E (consumer): 125/125 still green
- its-achievable smoke (consumer): 75/75 still green
**consumer follow-up (separate commits in their own repos):**
- battle-focus/module.json: relationships.requires[0].version
bumped to ^0.4.0
- its-achievable/module.json: relationships.requires[0].minimum
bumped to 0.4.0
User callout: 'Hax' is Kaysser's nickname. The module id should
not use it. Rename the Foundry module id from 'hax-hooks-lib' to
'foundry-hooks-lib'. Gitea repo name stays as 'hooks-lib' (kept
for the user-facing URL); the Gitea manifest URL is unchanged.
**Scope of rename:**
- module.json: id, title, version (0.2.0 -> 0.3.0), download URL
- package.json: name
- README.md, HOOK_CONTRACT.md, LICENSE: branding text
- All 6 production JS files: MODULE_ID constant + comments
- 4 active test files: console.log strings + test descriptions
- Rename of release zips in git: hooks-lib-X.Y.Z.zip ->
foundry-hooks-lib-X.Y.Z.zip (preserves the v0.1.0 and v0.2.0
zips as historical artifacts; the v0.3.0 zip is the new
release artifact)
- .gitignore: glob + un-ignore lines updated to match
**Out of scope (deliberate):**
- Gitea repo name 'kaykayyali/hooks-lib' stays. Per the user's
direction, only the module id is renamed; the Gitea URL path
is preserved for the existing 'url', 'manifest', 'download'
fields.
- scripts/_archive/v0.1.0/*: historical v0.1.0 code is left
as-is. Those files tested 'hax-hooks-lib v0.1.0'; rewriting
the history would be misleading.
- tests/_archive_v0.1.0_*.mjs: same reason, left untouched.
- .hermes/plans/* session-historian plans that reference
'Hax's Tools split': session artifact, not a release asset.
**Verification:** 554/554 smoke assertions pass, 6/6 perf
assertions pass, median 0.0004ms/fire (well under 0.1ms
budget). No logic change; rename is string-only.
**Consumer action required:** battle-focus and its-achievable
both declare 'relationships.requires' pointing to
'hax-hooks-lib'. The next commits on those repos will update
their relationships to 'foundry-hooks-lib' + bump their
versions. Foundry instances with v0.2.0 of the old id
installed will need to be reinstalled as v0.3.0 of the new
id.
