/**
 * SMI-5897 (C-15): Unit coverage for `SkillsmithApiClient.toSkill()`'s
 * security-status field derivation.
 *
 * Previously `toSkill()` hardcoded `riskScore: null, securityFindingsCount: 0,
 * securityScannedAt: null, securityPassed: null` for every API-sourced skill,
 * discarding the real `security_score`/`quarantined`/`last_scanned_at`/
 * `security_findings` fields already present on the `ApiSearchResult` it
 * received — this is why CLI `info`/`search` (which both route through
 * `toSkill()`) could show "Not scanned" for a skill MCP correctly reported
 * as passed. `toSkill()` now derives these fields via the same shared
 * `deriveSecuritySummaryFromApiSkill()` MCP's tools use, so the two surfaces
 * can't re-diverge (see `api/security-summary.test.ts` for derivation-logic
 * coverage — this file only asserts `toSkill()` wires it through correctly).
 *
 * SMI-5897 (Wave 4 fix): imports `ApiSearchResult` from `./client.types.js` —
 * `toSkill()`'s ACTUAL parameter type — not `./types.js`, which declares a
 * different, same-named type (a pre-existing naming collision elsewhere in
 * this codebase, not something fixed globally here). Importing the wrong
 * type, combined with the `as ApiSearchResult` cast this fix also removes,
 * meant the fixture below was never actually type-checked against
 * `toSkill()`'s real input contract.
 */
export {};
//# sourceMappingURL=client.toSkill.test.d.ts.map