Say that a remote Bot hands work on, and drop the extraEnv note the chart replaced

architecture doc no longer describes every such hop as refused. #717
gives the delivery, SCIM, inbound email and OTel settings their own chart
values, which supersedes the extraEnv guidance.

Author: davidmckayv

charts/openbot/README.md

@@ -344,16 +344,6 @@ delivers anything. `config.learning.containerId` sets the initial default contai
 Automatic Learning take precedence, including switching it off. See
 [docs/automatic-learning.md](../../docs/automatic-learning.md).
 
-## Settings with no value of their own
-
-Several server settings have no dedicated chart value and are passed through `config.extraEnv` or
-`config.extraEnvFrom`: OpenTag delivery to Slack and Teams (`OPENTAG_URL`, `OPENTAG_SHARED_SECRET`),
-text messages (`TWILIO_*`), mobile push (`EXPO_ACCESS_TOKEN`, `EXPO_PROJECT_ID`), inbound email for
-Responsibilities (`OPENBOT_INBOUND_EMAIL_DOMAIN`, `OPENBOT_INBOUND_EMAIL_SNS_TOPIC_ARNS`), SCIM
-(`SCIM_*`), OpenTelemetry export (`OPENBOT_OTEL_EXPORT`, `OTEL_*`) and `DELIVERY_PUBLIC_URL`.
-`.env.example` describes each. Put the secret ones in a Secret and name it in `config.extraEnvFrom`
-rather than writing them into a values file.
-
 ## Slack, Teams, text messages, push, SCIM, inbound email and OpenTelemetry
 
 Each is off until its values are set, and each is the same setting [docs/configuration.md](../../docs/configuration.md)

docs/architecture.md

@@ -271,9 +271,10 @@ through the signed callback route is dispatched the same way as one from a Bot r
 handed work is not the same as being able to hand it on, so the target of a grant may live at
 its own endpoint.
 
-One limit remains on the asking side. The grant check a hop goes through (`botsReachableFrom`) counts
-only grants held by built-in Bots, so a Bot at its own endpoint can be granted another Bot and can ask
-its person, but every hop it attempts is refused as not granted.
+The asking side works the same way. The grant check a hop goes through (`botsReachableFrom`) counts a
+grant whatever the asking Bot's type, so a Bot at its own endpoint hands work on through the signed
+callback, the same grant check, caps and audit rows as a built-in one, to a built-in Bot or to another
+Bot at its own endpoint.
 
 A coworker created through the UI with an endpoint is a remote one. Created without one, it runs at
 the managed Bot's endpoint when the deployment has one, and otherwise runs here as a built-in Bot on