Use canonical delegated connection guidance across feature maps

Co-Authored-By: Paperclip <noreply@paperclip.ing>

maps/feature-map/app-permissions.md

@@ -109,16 +109,4 @@ Production: Exercise catalog refresh and new-tool review with permitted/denied a
 Sources: Source: [PermissionsPanel.tsx](../../ui/src/pages/apps/app-detail/PermissionsPanel.tsx), [AppDetail.tsx](../../ui/src/pages/apps/AppDetail.tsx), [tool-access.ts](../../server/src/routes/tool-access.ts). Tests: [AppDetail.test.tsx](../../ui/src/pages/apps/AppDetail.test.tsx), [tool-access-service.test.ts](../../server/src/__tests__/tool-access-service.test.ts), [tool-access-policy-service.test.ts](../../server/src/__tests__/tool-access-policy-service.test.ts)
 ### `delegated-configuration`
 
-A fresh standard agent can use the existing REST API and default native
-`search_api` / `call_api` to perform requested configuration within its responsible
-user's authority. Personal ownership stays with that user; audit attribution stays
-with the acting agent. Existing agents retain their explicit grants and restrictions.
-Human authentication and identity confirmation open the exact saved setup; local
-host administration and action approval retain their own boundaries. See the
-operation inventory in the companion and the [qualification record](../../doc/plans/2026-10-13-connection-api-parity.md).
-
-Automated: [agent-authenticated integration](../../server/src/__tests__/connection-management.integration.test.ts)
-uses normal creation defaults, persistent agent keys, run JWTs, native tool bindings,
-real database persistence, and deterministic provider fixtures. It separately checks
-user/agent revocation, trust, company/ownership scope, work modes and attribution.
-This is API reachability evidence, not a live provider setup or an LLM success rate.
+See the canonical [delegated configuration guidance and acceptance evidence](connection-setup.md#delegated-configuration).

maps/feature-map/chat-channels.md

@@ -219,16 +219,4 @@ Sources: Source: [TaskChatBubble.tsx](../../ui/src/components/task-chat/TaskChat
 Shared recipes name provider checks; each provider transport/thread/identity/file-size/type combination needs separate live evidence and deeper instructions.
 ### `delegated-configuration`
 
-A fresh standard agent can use the existing REST API and default native
-`search_api` / `call_api` to perform requested configuration within its responsible
-user's authority. Personal ownership stays with that user; audit attribution stays
-with the acting agent. Existing agents retain their explicit grants and restrictions.
-Human authentication and identity confirmation open the exact saved setup; local
-host administration and action approval retain their own boundaries. See the
-operation inventory in the companion and the [qualification record](../../doc/plans/2026-10-13-connection-api-parity.md).
-
-Automated: [agent-authenticated integration](../../server/src/__tests__/connection-management.integration.test.ts)
-uses normal creation defaults, persistent agent keys, run JWTs, native tool bindings,
-real database persistence, and deterministic provider fixtures. It separately checks
-user/agent revocation, trust, company/ownership scope, work modes and attribution.
-This is API reachability evidence, not a live provider setup or an LLM success rate.
+See the canonical [delegated configuration guidance and acceptance evidence](connection-setup.md#delegated-configuration).

maps/feature-map/gateways-profiles.md

@@ -81,16 +81,4 @@ Production: Issue bounded token via POST /tool-gateway/gateways/{id}/tokens; cal
 Sources: Source: [TokensPanel.tsx](../../ui/src/pages/apps/gateways/panels/TokensPanel.tsx), [tool-gateway.ts](../../server/src/routes/tool-gateway.ts), [tools.ts](../../ui/src/api/tools.ts). Tests: [TokensPanel.test.tsx](../../ui/src/pages/apps/gateways/panels/TokensPanel.test.tsx), [tool-gateway-service.test.ts](../../server/src/__tests__/tool-gateway-service.test.ts), [tool-gateway.test.ts](../../server/src/__tests__/tool-gateway.test.ts)
 ### `delegated-configuration`
 
-A fresh standard agent can use the existing REST API and default native
-`search_api` / `call_api` to perform requested configuration within its responsible
-user's authority. Personal ownership stays with that user; audit attribution stays
-with the acting agent. Existing agents retain their explicit grants and restrictions.
-Human authentication and identity confirmation open the exact saved setup; local
-host administration and action approval retain their own boundaries. See the
-operation inventory in the companion and the [qualification record](../../doc/plans/2026-10-13-connection-api-parity.md).
-
-Automated: [agent-authenticated integration](../../server/src/__tests__/connection-management.integration.test.ts)
-uses normal creation defaults, persistent agent keys, run JWTs, native tool bindings,
-real database persistence, and deterministic provider fixtures. It separately checks
-user/agent revocation, trust, company/ownership scope, work modes and attribution.
-This is API reachability evidence, not a live provider setup or an LLM success rate.
+See the canonical [delegated configuration guidance and acceptance evidence](connection-setup.md#delegated-configuration).

maps/feature-map/runs-adapters.md

@@ -249,16 +249,4 @@ cleanup before hire and retains its unconfirmed recovery state.
 
 ### `delegated-configuration`
 
-A fresh standard agent can use the existing REST API and default native
-`search_api` / `call_api` to perform requested configuration within its responsible
-user's authority. Personal ownership stays with that user; audit attribution stays
-with the acting agent. Existing agents retain their explicit grants and restrictions.
-Human authentication and identity confirmation open the exact saved setup; local
-host administration and action approval retain their own boundaries. See the
-operation inventory in the companion and the [qualification record](../../doc/plans/2026-10-13-connection-api-parity.md).
-
-Automated: [agent-authenticated integration](../../server/src/__tests__/connection-management.integration.test.ts)
-uses normal creation defaults, persistent agent keys, run JWTs, native tool bindings,
-real database persistence, and deterministic provider fixtures. It separately checks
-user/agent revocation, trust, company/ownership scope, work modes and attribution.
-This is API reachability evidence, not a live provider setup or an LLM success rate.
+See the canonical [delegated configuration guidance and acceptance evidence](connection-setup.md#delegated-configuration).