Capability ​

Contract 2.0.0 · package sha256 a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e · generated from configurator-runtime.d.ts by services/onsite-scripter/scripts/build-contract-docs.mjs; edit the source, not this file.

Type · import type { Capability } from '@holostep-configurators/runtime-client/contract'; · stable · since 2.0.0 · section 19. Info and capabilities

Open, so an app built against a newer contract can ask about ids this runtime lacks. An id not in this runtime's KnownCapability answers false and records 'unknown-capability' once per id per session: a 1.4 id such as 'idle', and a newer contract's id, where it is information only.

Declaration ​

ts
export type Capability = KnownCapability | (string & {});

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: Capability names no product
2. A precedent not recorded: no ledger row (coverage.json) names this member or its owner
3. Two apps, or labs pass: 17 apps (fleet cross-check: app-37356bf09f, app-4f16d2f6da, app-4fd23bc869, app-822bb9d6aa, app-8675b3225c, app-bcb7ef21da, app-c1384707fc, app-ceb4eccc72 and 9 more)
4. The cheaper fix first not recorded per member (Appendix B decides it per need)