InkKit 0.0.10

InkKit 0.0.10 adds optional wiki links and host-resolved image, audio, video, PDF and file-card views. Hosts own opaque references, permissions, storage, lookup and opening. Existing ImageAdapter consumers and feature-disabled source behaviour remain compatible.

Named/path image widths preserve authored spelling, fragments and one-gesture undo. Asynchronous resolution/export supports cancellation, retry, missing/error states and stale-result rejection. Every supported kind has documented text, HTML, Markdown and printable output. Portable images retain bytes and widths; nonimage kinds use descriptive fallbacks without private display URLs.

Protected PDF preview depends on platform support. A visible fallback and host Open action remain available when the embedded viewer is blocked. Composition fixtures verify guards rather than complete IME interoperability. No app adoption or external-app matrix was performed.

Verification: 578 regressions; required TypeScript/build/format/playground and packed-consumer checks; nine selected Chromium cases; six selected WKWebView scenarios/114 steps. Frozen native PDF printing retains all descriptive fallbacks and three verified image placements. The protected AppKit pasteboard probe retains exact text/HTML and three ordered attachments with exact bytes. Scoped print preferences and clipboard restoration pass.

Independent reviews resolved host-action error reporting, newly folded request cancellation and blocked PDF fallback findings. PR #52 merged after hosted Linux/macOS CI. Release commit: 3ff5f9cf69f55c4db1cc2144e42240135ea59642.

The archive was packed from clean 6adcbe23c8109d7099ad9bf047fd4a0602ee1f51; later fixture/documentation commits leave package inputs unchanged. Passing unchanged native cases were reused, affected cases rerun, and failed attempts retained separately.

Release publication succeeded through npm OIDC with signed provenance. Registry processing caused temporary 404 responses; publication was not repeated. The actual registry archive matches the hosted archive exactly, SHA-512 integrity passes, and decompressed content matches the native-tested candidate. A fresh isolated exact-version registry consumer passes declarations, CSS and offline bundling; its bundle hash matches the candidate consumer.

Registry SHA-256: 9d8fb9e6b16c2858227ff832f58e91b86f548f7c802fcae62a3f9ba453bbbcb0.

Decompressed tar SHA-256: 96449bb5c57b4b3207d59927b23136712c209b9cbf87844e6ddec69d5302ede1. Only gzip compression differs from the candidate.

Offline consumer SHA-256: 9d3bce746b3c80e29d79d0839a61df15594d6a22d429baf1127245df14bbd9b7.

Attached machine-readable evidence records the tested/published archive identity, clean consumers, native cases and protected copy/print checks. Raw attempts remain retained on Atlas in _local/release/0.0.10/.