v4.1.0

Minor Changes

• f0642b4: Structured failures, request cancellation, TLS options and startup validation.- Failure is now structured. Every failure carries code ('HTTP' | 'AUTH' | 'TIMEOUT' | 'ABORTED' | 'NETWORK' | 'PARSE' | 'UNKNOWN'), plus status and details ({ code, message } parsed from SharePoint's error body) for HTTP responses. Branch on code instead of matching error text. code is a required property of Failure; code that constructs Failure objects by hand must add it.- Error messages no longer include a redundant Error: prefix and now read Error in <action>: HTTP <status>: <SharePoint message> for server responses.- signal?: AbortSignal is accepted by every action; aborting yields a Failure with code ABORTED. timeout is documented as a socket inactivity timeout.- agentOptions?: https.AgentOptions on SiteConnectionOptions passes ca, rejectUnauthorized, client certificates, lookup, etc. to the HTTP agent, so internal CAs no longer need NODE_TLS_REJECT_UNAUTHORIZED=0.- createSiteConnection validates its options and throws a TypeError for a protocol or path inside site, a serverRelativeUrl without a leading slash or with a trailing slash, or an unknown protocol.- SpRestError and parseSharePointError are exported.- Supported Node.js range widened to >=20.- Published with npm provenance.
• f0642b4: Structured failures, request cancellation, TLS options and startup validation.