docs: drop accessibility from Ink-divergences (it's parity, not a divergence) (#72)

The "Accessibility props — AriaRole / AriaState" entry claimed "Ink: no
equivalent" and filed aria/screen-reader support under additive features. That
is incorrect: Ink has full accessibility support at this doc's own baseline
(v7.0.4, commit 40b3a75) — aria-label/aria-hidden/aria-role/aria-state on
Box/Text, useIsScreenReaderEnabled, and screen-reader linearization in
render-node-to-output. vue-tui's implementation is a faithful port of it; the
parity commits G03–G59 align the linearization with Ink (e.g. G22's parent-role
dedup matches Ink's `role !== parentRole`).

Accessibility is parity-by-default, so it does not belong in a doc that records
only intentional divergences. Remove the entry; the feature itself is unchanged.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

.agents/docs/ink-divergences.md

@@ -76,13 +76,6 @@ deliberate. Divergences fall into a few kinds:
 
 ## Additive features (vue-tui is a strict superset)
 
-### Accessibility props — `AriaRole` / `AriaState`
-
-- **Ink:** no equivalent.
-- **vue-tui:** `<Box>` / `<Text>` accept `AriaRole` / `AriaState` props that feed the
-  screen-reader linearization.
-- **Why:** additive accessibility surface; does not change visual (non-SR) rendering.
-
 ### Multiple `<Static>` regions
 
 - **Ink:** keeps a single `staticNode`; only one `<Static>` is honored.