Qtangl native discovery depth — host sensor + code/binary orchestration

Qtangl now ships partial native discovery depth per ADR-009:

• Host / endpoint — Qtangl Unified Sensor (cert stores, crypto libraries, TLS listeners) with fleet enrollment
• Source code / binary — CryptoScan, CryptoDeps, and CBOMkit-theia orchestration into the same CBOM merge and signed evidence pipeline

Why partial, not "yes" yet

Enterprise ship gates G3/G5 require 500+ agent pilots, mTLS agent identity, bundled OSS engines in CI, and production registry connectors. We label capabilities partial on the vendor comparison matrix until those gates clear.

What you can do today

1. Enable discovery.hostSensor, discovery.codeScan, and discovery.binaryScan per tenant (or QTANGL_DISCOVERY_ENABLE_ALL=true in dev)
2. Dashboard → Integrations → Discovery depth — hosts, code, images tabs with inventory counts
3. Assess wizard → Discovery scope — external baseline plus optional fleet/repos/images
4. GitHub Action qtangl-scan with mode: code|binary|external

Evidence layer unchanged

Discovery depth expands inventory; the moat remains signed, publicly verifiable evidence — the Readiness Passport auditors can check offline.

See deployment guides: host sensor deploy, code scan CI, and the enterprise pilot playbook in product docs.