MTFDX · Kids & Family · CMK Android

R13 visual remediation, authority recovery & business integration — Owner review

Bundle: MTFDX_CMK_ANDROID_R13_VISUAL_REMEDIATION_AUTHORITY_RECOVERY_AND_VPS03_OWNER_PREVIEW_R13

R12_OWNER_VISUAL_ACCEPTANCE=APPROVED_WITH_CONDITIONS R12_ENGINEERING_ACCEPTANCE=ACCEPTED R13_DEVELOPMENT_AUTHORIZED=YES FINAL_VISUAL_ACCEPTANCE=PENDING FINAL_UI_FREEZE_AUTHORIZED=NO SECURITY_P0_CLOSED=NO PRODUCTION_AUTHORIZED=NO VPS03 staging-only · read-only · no login

Authority status: CMK_ANDROID_VISUAL_AUTHORITY = CANDIDATE_NOT_APPROVED (recovered in R13; O-5 still requires an Owner-approved visual source). R13 screens are checked against the frozen child-app usability baseline (docs/architecture/10-ui-page-spec/04-child-app.md) only. Implementation screenshots are evidence, never a design authority.

Authority recovery (R13)

Before R13 the repository had no CMK Android authority entry. R13 registers a governed candidate entry whose token table is generated from the shipping Kotlin tokens and verified on every build.

R11 → R12 → R13 对照

Left: R11 baseline. Middle: R12. Right: R13. R12 reference images are carried forward as the accepted baseline.

Business integration (R13)

Foundation Core identity/device/notification/location move from NOT_IMPLEMENTED to a labelled non-production MOCK (local fixture). Real HTTP round-trips, fail-closed parsers.

Security hardening (R13)

APK(无登录直下)

范围与边界