docs(boost): fix inaccurate zero-deps claim for boost-responses-api-toolkit

boost-responses-api-toolkit depends on boost-common which transitively
pulls in @backstage/plugin-permission-common. Update documentation to
say 'minimal Backstage dependencies' instead of 'zero'.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: gabemontero <gmontero@redhat.com>

Author: gabemontero

workspaces/boost/specifications/boost-context.md

@@ -37,13 +37,13 @@ workspace/boost/plugins/
 ├── boost-backend                     — Core routes, services, middleware, ProviderManager, cross-cutting entity providers
 ├── boost-backend-module-llamastack   — Llama Stack agentic provider (composes llamastack-entity-provider)
 ├── boost-backend-module-kagenti      — Kagenti agentic provider (composes kagenti-entity-provider)
-├── boost-responses-api-toolkit       — Shared Responses API utilities (zero Backstage dependencies)
+├── boost-responses-api-toolkit       — Shared Responses API utilities (minimal Backstage dependencies via boost-common)
 ├── boost-toolscope                   — Standalone tool-scope resolution (zero Backstage dependencies, injectable CacheAdapter)
 ├── llamastack-entity-provider        — Backstage backend service: Llama Stack catalog entities (independently deployable)
 └── kagenti-entity-provider           — Backstage backend service: Kagenti catalog entities (independently deployable)
 ```
 
-The core packages (`boost-frontend`, `boost-common`, `boost-node`, `boost-backend`) mirror augment's structure with the addition of `boost-node` for service refs and extension points (following the Backstage `plugin-catalog-common`/`plugin-catalog-node` pattern). `boost-responses-api-toolkit` and `boost-toolscope` are standalone utility packages with zero Backstage dependencies — they can be consumed by provider modules or used outside Backstage entirely. Provider modules and entity providers are additive — deployers install only what they need. Entity providers are independently deployable as RHDH dynamic plugins for catalog-only use cases.
+The core packages (`boost-frontend`, `boost-common`, `boost-node`, `boost-backend`) mirror augment's structure with the addition of `boost-node` for service refs and extension points (following the Backstage `plugin-catalog-common`/`plugin-catalog-node` pattern). `boost-toolscope` is a standalone utility package with zero Backstage dependencies. `boost-responses-api-toolkit` has minimal Backstage dependencies (transitive via `boost-common` → `@backstage/plugin-permission-common`). Both can be consumed by provider modules or used outside Backstage with minor shims. Provider modules and entity providers are additive — deployers install only what they need. Entity providers are independently deployable as RHDH dynamic plugins for catalog-only use cases.
 
 ## Local Development
 

workspaces/boost/specifications/prd/platform-operations-deployment.md

@@ -71,7 +71,7 @@ All packages live at `rhdh-plugins/workspaces/boost/plugins/`:
 | `boost-backend`                   | Backend plugin  | Core routes, services, middleware, `ProviderManager`, cross-cutting entity providers (MCP, vector stores)     |
 | `boost-backend-module-llamastack` | Backend module  | Llama Stack agentic provider (composes `llamastack-entity-provider`)                                          |
 | `boost-backend-module-kagenti`    | Backend module  | Kagenti agentic provider (composes `kagenti-entity-provider`)                                                 |
-| `boost-responses-api-toolkit`     | Utility library | Shared Responses API utilities (zero Backstage dependencies)                                                  |
+| `boost-responses-api-toolkit`     | Utility library | Shared Responses API utilities (minimal Backstage dependencies via boost-common)                              |
 | `boost-toolscope`                 | Utility library | Standalone tool-scope resolution (zero Backstage dependencies, injectable `CacheAdapter`)                     |
 | `llamastack-entity-provider`      | Backend service | Llama Stack model + agent catalog entities (independently deployable)                                         |
 | `kagenti-entity-provider`         | Backend service | Kagenti agent + tool catalog entities (independently deployable)                                              |