AttachReport ​

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 { AttachReport } from '@holostep-configurators/runtime-client/contract'; · stable · since 2.0.0 · section 12. Assembly

attached: false comes with outcome: 'refused' and a reason of 'no-candidate', 'occupied', 'rejected' or 'not-loaded': the first that applies, in the order of spec section 6.12, A2. Narrow on attached first. Re-attaching a pair that is already connected and in place is an equal write: it resolves attached: true with that connection, outcome: 'committed', changed: false and seq: null, and makes no undo step and no event (spec section 6.1, O15).

Inherited from ReportFields: op, origin, seq, revision, changed, matched, pending, completed, problems.

Declaration ​

ts
export type AttachReport = Report & ({
  readonly attached: true;
  readonly connection: Connection;
} | {
  readonly attached: false;
  readonly connection?: undefined;
});

Generic-API test (spec 3.1) ​

Rule Result
1. Neutral name pass: AttachReport 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: 5 apps (fleet cross-check: app-04c2774145, app-37356bf09f, app-4762caacdc, app-ceb4eccc72, app-f9a32142f1)
4. The cheaper fix first not recorded per member (Appendix B decides it per need)