[jakthom]

Summary

• make connector delivery boundaries truthful with pending versus retained queue state, delivery classes, checkpoint/headroom visibility, and explicit drop/retry/prune stages
• persist a stable, standards-honest N2K appliance identity and enrich discovered devices with decoded NAME, product/configuration data, and supported PGN lists
• add semantic, transparent, and observe-only connector modes, including SocketCAN wire-preserving forwarding and management-PGN safeguards
• add the runtime PGN catalog, provenance-rich envelopes, precision-safe hexadecimal Device NAMEs, physical engineering values, and corresponding CEL fields
• add persistent commissioning inventory, expected-device baselines, labels, CAN diagnostics, reports, and dashboard controls
• document the N2K domain language and architectural decisions

Verification

• go test ./...
• go vet ./...
• go test -race ./internal/connector ./internal/sink ./internal/bus ./internal/source ./internal/inventory ./internal/ui
• npm test -- --reporter=line (2 Playwright tests passed)
• gofmt and git diff checks

Scope boundary

Security and write-governance item #7 is intentionally not implemented in this PR. The existing admin exposure and authentication behavior is unchanged.

Transparent forwarding currently supports SocketCAN single-frame and fast-packet payloads up to 223 bytes. ISO transport-protocol forwarding and address-claim proxying remain future gateway work.