refactor: replace overloaded surface terminology

packages/client/ui-permission/README.i18n.yaml

@@ -2,5 +2,5 @@
 # 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 packages/client/ui-permission/README.md
-README.md: 742e82d767152073ab963dc74c0565d6e8f8e5c4
+README.md: cf3981d66745bd5a65c83e09daeb8463023f447b
 README.zh.md: 70bbbb2d14358cbe52a6fc27deb7ce01d5f3679b

packages/client/ui-permission/README.md

@@ -6,7 +6,7 @@ Permission browser surfaces for two different lifetimes. The General-settings ro
 
 The current-session surface remains a popupSelect DECORATION hung on the host `/permission` command (`ctx.command.decorate`). A decoration is not a second command — the host command keeps its slash-menu row, the argued path (`/permission <preset>` switches directly), and the durable lifecycle logging; the decoration replaces only the bare invocation with the picker: one flat preset list with the current value marked active and kebab-case preset names rendered as title-case labels (`workspace-write` → `Workspace Write`, the composer chip's display transform twin), where a pick submits the `/permission <preset>` command line. Options and the active mark read the session's `permissions` projection (the same host-computed select the composer chip renders), so both current-session surfaces share one read source and one write path, and the pushed projection frame is the single confirmation both follow. The decoration is available exactly while the projection key is present; a permission-less composition shows neither picker nor Settings row.
 
-The `/client` export surface is the plugin body (`apply`/`inject`).
+The `/client` exports are the plugin body (`apply`/`inject`).
 
 ## Model Experience