Sprint 10.6 — Document v0.1 security and compatibility contract

[maruson08]

Problem / motivation

Consumers need a precise pre-1.0 contract describing supported operations, limitations, privacy boundaries, and browser/npm consumption.

Scope

• document JPEG/PNG/WebP inspection, cleaning, and verification support
• document EXIF/MakerNote/compression/status/unknown/ICC/verification/provenance limitations
• label the project pre-1.0 and define breaking-change documentation expectations
• document verified same-origin browser artifact integration path

Non-goals

• stronger marketing claims than implementation evidence
• CDN or Secure Tools integration

Acceptance criteria

• release-facing docs accurately state capabilities and limitations
• npm and browser consumption paths are clear
• security claims remain conservative