SKILL UPDATES · CHANGE RECORD ·

Website/app content contracts, caching and evidence boundaries

Adds shared website/native-app content contracts, compatible evolution, caching and offline acceptance.

Check stable IDs, revisions/hashes of original UTF-8 body bytes, requested locale and actual text language. Treat richText as optional enhancement and retain the blocks compatibility path.

Website/client integration acceptance requirements: Validate responses, identity, language and bytes, then check request generation and cancellation before disk writes and state commits. Late responses must not overwrite valid caches.

Website/client integration acceptance requirements: Use bounded retries during fixed-URL publication windows and fall back if inconsistency persists. Restart with networking genuinely unavailable to verify old offline packages, bookmarks and reading positions survive; precise position migration across revisions needs separate evidence.

Website fields do not prove installed-client support. Distinguish logic, integration, simulator, physical-device and release evidence. Public APIs must exclude private material. Existing PDF V1.2 remains a historical reference and was not updated.

This Skill owns website-side content/APIs, versions, publication, compatibility contracts and client integration checks. Native UI, client cache implementation and device delivery belong to the separate App Planning & Delivery Skill.

Back to updates Explore this Skill
SEARCH