Repository navigation
docs(hooks): align calibration input and fixture requirements - #1348
Merged
NandhaKishorM merged 1 commit intoOct 24, 2026
Merged
NandhaKishorM merged 1 commit into
NandhaKishorM merged 1 commit into
Conversation
NandhaKishorM
added a commit
that referenced
this pull request
Oct 24, 2026
33 PRs. Server hardening (#1331, #1332, #1333), TypeScript parity (#1330, #1336, #1337, #1338, #1339, #1340, #1341, #1342, #1343), fail-closed input handling in evals and the integrations (#1317, #1318, #1319, #1320, #1321, #1322, #1326, #1335), exact and faster script detection (#1334, #1349), JVM and .NET resource handling (#1327, #1328, #1329, #1346), port goldens and clipping (#1324 excluded, #1325, #1344, #1345), CI (#1323, #1347, #1348). Verified before tagging: all 92 suites pass, 610 tests. ruff clean on both lists. laya-ts 1247 tests across 44 files, tsc --noEmit clean. Version agrees across pyproject.toml, laya.__version__ and nix/package.nix. README carries 0.4.15 only. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Document the current
calibrate_reliabilitycontract: finitenumbers.Realinputs, Python/NumPy boolean labels, sized sequences, and plain Python float cutoffs. Correct the fixture generator's NumPy requirement and describe its committed provenance in the past tense.Why
The follow-up to #1314 added NumPy support, but
docs/hooks/api.mdstill excludes those inputs and the generator still claims to need only the standard library. This brings both descriptions in line with the shipped implementation. Runtime behavior and fixture data are unchanged.How it was verified
On Python 3.11, from the repository root:
python -B tests/test_option_stability.py python -B tests/test_hooks_api.py python -B laya-ts/scripts/option_stability_fixtures.py --python-root . --check ruff check laya/ laya-ts/scripts/option_stability_fixtures.py --select=E9,F63,F7,F82,F401,F811 --line-length=120 python -m compileall -q laya/ tests/ laya-ts/scripts/option_stability_fixtures.py python -m zensical build --strict --clean git diff --checkThe stability suite passed 200 checks; the hook API suite passed 645. All committed stability fixtures matched the Python reference. The strict docs build used the versions pinned in
requirements-docs.txtand emitted nogriffe:diagnostics.Model inference and the full TypeScript suite were not run for these documentation-only edits.
Checklist
mainRelated to #1314.