docs: close Android guides accuracy and reader-experience gaps (NT-3944)

[Felipe Mamud (fmamud)]

Summary

• Newcomer + technical-foundation review of both Android integration guides (integrating-the-optimization-android-sdk-in-a-compose-app.md, ...-views-app.md) per NT-3944, a sub-task of NT-3896 (Mobile SDK doc accuracy pass ahead of GA).
• No interface or SDK behavior claims were contradicted by source, but one behavioral claim had no backing knowledge-base fact and both guides had real reader-experience defects, including one genuinely broken quick-start step in the Views guide (missing TextView layout instruction).
• Corrected documentation/internal/sdk-knowledge/native/android.md: the missing-metadata → silent-baseline-fallback behavior is driven by the shared JS-core isResolvedContentfulEntry type guard, not a Kotlin CTEntry.from parse failure as previously implied.
• Funneled three durable rules into skills/optimization-guide-authoring/references/authoring-checklist.md: silent-degradation behaviors must be a callout, multi-axis boolean/enum semantics must be tabulated, and code-block warnings must precede (not follow) their block.
• Cross-checked both guides against the iOS SwiftUI guide for family consistency; removed a one-off "How to read these examples" label-taxonomy explainer that the Compose guide-writer pass had added, since no other guide in the family (iOS included) carries it and the skill already states the convention once at the skill level.

Test plan

• pnpm knowledge:check — source pointers resolve, no ESCALATE markers
• pnpm guides:check — guide structure/links valid
• pnpm exec prettier --check on all touched files
• Standard guide review process (this PR is the artifact of that review; awaiting maintainer read)

🤖 Generated with Claude Code