BeaconTower Dropkit 0.3.0

Highlights

• Server-side NATS subject mapping (mqpr-ger4r): producer publishes to ingress.providerclient.{providerId}::{providerClientId}; the dropkit's NATS server hashes the trailing token mod 32 and rewrites to ingress.partition.{N}. Consumer (asset-processor) subscribes with FilterSubject = ingress.partition.{i}. Producer-side hashing dropped (no more XxHash64, no PartitionCount option).
• OpenAPI documentation applied to all customer-facing controllers in mqpr (mqpr-mh2q0) and onboarding (onb-9b5tb).
• Offline-restore verification in the packager (mqpr-8gil3): every csproj under source/ is verified to restore against local-nuget/ alone before the kit is built. Permanent regression guard.
• E2E harness deps (MQTTnet, Serilog.Sinks.Console, System.Security.Cryptography.Pkcs) baked into local-nuget/ so dotnet run works offline.

Image versions

• local-mqttprovider:local-1.51.0 — built from current main (post mqpr-ger4r). v1.50.1 is the last released tag; 1.51.0 not yet auto-released due to a flaky integration test on CI (mqpr-k3diw) — image content is identical to what 1.51.0 would be.
• local-onboarding:local-1.42.0

Notes

• Air-gapped customers: dotnet restore inside the unzipped kit works without auth — local-nuget feed is the only source.
• Dev/customer site without the NATS mapping deployed: pipeline will be silently empty. Make sure dropkit/infra/02-nats.yaml is applied.

Versions

• mqttprovider: 1.51.0 (current main)
• onboarding: 1.42.0