docs(policy): align every precedence statement with the override chain

Review fix (ds-review-bot on #623): the READMEs and JSDoc still stated the
pre-baseline formulas — resolve() outranking 'the session's last
sandbox/mode event', 'effective = explicit grant ?? fold(events) ??
deployment default', and the approval README's 'last approval/policy event'
opener — which contradict the shipped semantics for a delegated fork whose
seed tail differs from its header baseline. Every statement now names the
override chain (own post-seed switches ?? inherited header baseline): both
READMEs (both languages), resolve()'s JSDoc, the session-mode module and
event-declaration docs, the raw folds re-scoped as building blocks, and
the regenerated catalogs.

packages/ui/user-approval/README.i18n.yaml

@@ -1,6 +1,6 @@
 # Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
-#   pnpm run verify-translation-pairing --write
-README.md: 251782ac19de54413e6e318d141f39f964900a32
-README.zh.md: 9fab4f5cb73bb893d7c55a2e65c43c96eb9dfa4c
+#   pnpm run verify-translation-pairing --write packages/ui/user-approval/README.md
+README.md: c29ada50950cb6b40065a09bac1becbf4afb0ce4
+README.zh.md: c119f2009298edfaa101b10c7562d0c36324ec5d