T023/T024/T025: OK to build the RecognitionResult adapter now? #77

@scrimshawlife-ctrl: the recognition adapter (T023, plus T024 Apple Vision and T025 ML Kit behind it) is the next app-side blocker. T102 confirm-only and T105 retry reasons (#74) both need it.

Where it stands:

• zzThis docs: tick built tasks and clear stale text after v1.1 app work #89 merged the upstream ZZ-OCR-QUAL-001 contract.
• spec(apps): consume ZZ-OCR-QUAL-001 recognition boundary #44 and Draft: align native capture with V1 no-upload decision #45 merged recognition-adapter.md and the capture changes here.
• Pin zzThis fd99d27 (main): retry-reason copy keys #76 moves the app pin to zzThis main, which includes docs: tick built tasks and clear stale text after v1.1 app work #89.

Two questions before anyone starts:

1. recognition-adapter.md still says "Status: proposed app contract; implementation waits for this spec and the upstream contract to be accepted and pinned." Is it accepted for implementation once Pin zzThis fd99d27 (main): retry-reason copy keys #76 merges? Recommend: yes, with its "open gates" (numeric detector limits, baseline tolerance, ROI inset, reason-code mapping) left as configuration values that qualification freezes later, and conservative defaults that fail closed until then.
2. Is anyone on your side already building T023 to T025? If not, I'll take it on both platforms: the RecognitionResult boundary, the Vision and ML Kit adapters behind it, and the shared band logic reading only normalized evidence (T022). One PR per platform, with confirm-only (T102) as the default until a PASS receipt exists. PP-OCR (T026) and qualification runs (T027 to T029) stay out of scope.

A yes or no on each is enough.