courthive-components 6.10.0 → 6.10.2

package/dist/components/inline-scoring/inlineScoringManager.d.ts

@@ -27,6 +27,10 @@ export declare class InlineScoringManager {
     addGame(matchUpId: string, winner: 0 | 1, baseMatchUp: MatchUp): MatchUp | undefined;
     /**
      * Add a set score. Used in 'entry' mode.
+     *
+     * The factory judges the total by its segment's rule and refuses a total that is not a fact (a negative
+     * or non-integer score): that refusal records nothing and returns undefined, as input on a completed
+     * match does. An input the engine ignores (`recorded: false`) returns undefined too.
      */
     addSet(matchUpId: string, side1Score: number, side2Score: number, baseMatchUp: MatchUp): MatchUp | undefined;
     undo(matchUpId: string, baseMatchUp: MatchUp): MatchUp | undefined;

package/dist/components/scoring/logic/combinedPointTie.d.ts

@@ -8,3 +8,12 @@ import { SetScore } from '../types';
  * deciding-point or win-by format (`P32DP`, `P32WB2`) never ends level, so it is never a completed tie.
  */
 export declare function isCompletedCombinedPointTie(sets: SetScore[], matchUpFormat?: string): boolean;
+/**
+ * A match the factory completes with no winner: the combined-point tie above, and (factory 7.16, #5612)
+ * an exactly or aggregate count that closes level with no declared decider, such as `HAL2X-S:TB11` at one
+ * half each or `SET2XA-S:T10` level on games. The score dialogs judge completion by a winner, so they ask
+ * the factory: the entered sets are played through its ScoringEngine as set totals, and the result is a
+ * tie when the engine completes the match and names no winner. A set the engine refuses or ignores (one
+ * past the close) is not a completed tie.
+ */
+export declare function isCompletedLevelClose(sets: SetScore[], matchUpFormat?: string): boolean;

package/dist/components/scoring/scoreEntryCard.d.ts

@@ -159,9 +159,8 @@ export type ScoreEntryCardParams = {
     /**
      * Whether a recorded outcome may be REMOVED. Only the draw knows whether a later match depends on the
      * result, so the host reads it from the engine (the factory's `CLEAR_SCORE` matchUp action) rather than
-     * the dialog guessing. `false` disables `[Clear]` on a reopened result and says why in its
-     * tooltip (`labels.clearRefused`), so the dialog never offers a
-     * submission the engine will refuse. Omitted, `[Clear]` behaves as it always has.
+     * the dialog guessing. `false` disables submitting an empty replacement for a recorded result.
+     * `[Clear]` still resets the entry form so the operator can type a replacement score.
      */
     clearable?: boolean;
     /** Scoped statuses refused by the factory SCORE action. */

package/dist/components/scoring/types.d.ts

@@ -73,8 +73,8 @@ export type ScoringModalParams = {
     /**
      * Whether a recorded outcome may be REMOVED. Only the draw knows whether a later match depends on the
      * result, so the host reads it from the engine (the factory's `CLEAR_SCORE` matchUp action) rather than
-     * the dialog guessing. `false` withholds `[Clear]` on a reopened result, so the dialog never offers a
-     * submission the engine will refuse. Omitted, `[Clear]` behaves as it always has.
+     * the dialog guessing. `false` disables submitting an empty replacement for a recorded result.
+     * `[Clear]` still resets the entry form so the operator can type a replacement score.
      */
     clearable?: boolean;
     /** Scoped statuses refused by the factory SCORE action. Omitted preserves the unrestricted vocabulary. */