@bbingz/polycli-timing
v1.0.1
Published
Capability-aware timing schema, percentile aggregation, and four-state (measured / zero / missing / unsupported) validation for cross-provider AI CLI comparison.
Maintainers
Readme
@bbingz/polycli-timing
Capability-aware timing schema, validation, percentile calculation, and aggregation for comparing AI CLI providers without pretending every provider supports the same measurements. This package is not a provider framework: it does not run CLIs, parse provider protocols, manage sessions, or define a shared runtime.
Install
npm install @bbingz/polycli-timingRoot Exports
The root export mirrors src/index.js:
TIMING_SCHEMA_VERSIONTIMING_METRIC_NAMESTIMING_METRIC_STATUSESTIMING_RUNTIME_PERSISTENCETIMING_MEASUREMENT_SCOPESTIMING_SCHEMA_URLreadTimingSchemavalidateTimingRecordcalculatePercentilesaggregateTimingRecords
Subpath Exports
@bbingz/polycli-timing/schema
Semantics
unsupported,missing,zero, andmeasuredare distinct states and must not be collapsed.runtimePersistencedistinguishesephemeral,session, anddaemonruntimes.measurementScopedistinguishesrequest,turn, andjobmeasurements.- Aggregation preserves capability-aware metric summaries plus
runtimePersistenceCountsandmeasurementScopeCounts.
Example
import {
validateTimingRecord,
aggregateTimingRecords,
} from "@bbingz/polycli-timing";Semver Policy
v1.x is the first stable line. Additive exports and backward-compatible schema/aggregation behavior are minor releases. Removing exports, changing documented output shapes, or collapsing the four metric states requires a major version.
The authoritative v1 surface reference is docs/polycli-v1-public-surface.md.
