tods-competition-factory 5.1.0 → 5.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -42,7 +42,7 @@ Beyond pre-defined draw types, the factory's linked structure architecture enabl
42
42
 
43
43
  Two complementary scheduling approaches: **Garman scheduling** for automated multi-day distribution respecting recovery periods, daily limits, and court availability; and **Pro scheduling** for grid-based control with fixed time slots, follow-on support, and comprehensive conflict detection.
44
44
 
45
- The **Temporal Engine** extends this by modelling court availability as continuous capacity streams, enabling "what-if" scenario simulation before committing to the tournament record.
45
+ The **Availability Engine** extends this by modelling court availability as continuous capacity streams, enabling "what-if" scenario simulation before committing to the tournament record. (Renamed from `TemporalEngine` in 5.0.0 — the `Temporal` name was vacated for the TC39 `Temporal` global; existing call sites continue to work via the engine assemblies.)
46
46
 
47
47
  ## Publishing and Embargo
48
48
 
@@ -80,9 +80,9 @@ Full documentation with interactive examples: **[courthive.github.io/competition
80
80
 
81
81
  ## Testing
82
82
 
83
- 8,200+ tests covering draws, scheduling, scoring, participants, publishing, and ranking points.
83
+ 9,800+ tests covering draws, scheduling, scoring, participants, publishing, and ranking points.
84
84
 
85
85
  ```bash
86
- npm test # run all tests
87
- npm run coverage # coverage report (thresholds: 95/95/83/95%)
86
+ pnpm test # run all tests (Vitest)
87
+ pnpm coverage # coverage report (thresholds: 95/95/83/95%)
88
88
  ```