integration.osint-transport

@lssm-tech/integration.osint-transport

Provider-neutral transport projections generated from the OSINT contract registry: REST/OpenAPI, TypeScript SDK, MCP tools, signed webhook delivery, verified/scoped webhooks, resumable SSE/WebSocket event sessions, and CLI parsing.

The host supplies authentication and a single scoped operation handler. Every adapter enforces the binding grant before dispatch, so a surface cannot silently broaden ecosystem, tenant, shared-base owner, dataset, deployment, jurisdiction, purpose, export, or restricted-field authority. OpenAPI and MCP also expose source registration, entity history/diff, research status/cancel, and evidence/entity resource templates from the same registry.

The same registry now exposes governed operational recovery for dead-letter listing and exact-attempt replay, durable webhook delivery status and replay, and job-listing revalidation and closure reconciliation. Mutation schemas make scope, idempotency, expected revision and attempt, authority/policy/contract fingerprints, and evidence mandatory. OpenAPI and MCP required fields are projected directly from those canonical input schemas; SDK and CLI operation availability is projected from the canonical transport bindings.