Initial release.

• AmSemnat.readIdentity, AmSemnat.sign, AmSemnat.verifyPassiveOffline, AmSemnat.isNfcAvailable, AmSemnat.isNfcEnabled, AmSemnat.cancelCurrentOp, and the injectable AmSemnat.logger / AmSemnatLogger protocol.
• AmSemnat.cancelCurrentOp() invalidates the in-flight session-owned readIdentity / sign NFCTagReaderSession; the awaiting call throws AmSemnatError.sessionCancelled. No-op for the tag: overloads (caller owns the session). Safe to call from any context, including UIKit/SwiftUI lifecycle callbacks.
• RomanianIdentity, RomanianSignature, PassiveVerificationResult result structs and the DataGroup / ReadProgress / SignProgress public enums.
• Full 14-case AmSemnatError taxonomy including the structured pinVerifyFailed(retriesRemaining:) and invalidInput(parameter:detail:) variants.
• NfcMessages carries authenticating (shown during PACE / chip-auth / eData / AA phases) and progressFormat (template controlling how the reader's live percentage is composed into the sheet). The default template is "{phase} — {percent}%" and uses token substitution rather than String(format:) so malformed values from consumer code cannot crash the SDK. Set progressFormat = "" to hide the percentage and display scanning verbatim.

• readIdentity now always requests .COM + .SOD from the vendored reader alongside the caller-selected DataGroup set. Previously, any non-empty dataGroups argument caused the vendored reader to skip the SOD entirely, so RomanianIdentity.rawSod was nil on every read and verifyPassiveOffline had no input to operate on. Matches the Android SDK's behavior (which reads EF_SOD explicitly).