docs: defer the provider typing note to #409, which made fixtures required where providers do not run

Author: ScriptedAlchemy

docs/framework-mode.md

@@ -105,12 +105,7 @@ and augments `@agent-bundle/runtime`'s `AgentProviderValues`, so
 `(await agent()).providers.library` is a `LibraryContext` with no cast once
 the file is part of the project's TypeScript program (add
 `".agent-bundle/routes.d.ts"` to `tsconfig.json` `include`). Undeclared keys
-stay `unknown`. The augmentation describes the generated request scopes, which
-always mount every conventional provider before user code runs; it is not a
-runtime guarantee for hand-rolled `runAgentRequest` invocations or for route
-tests that omit a fixture — those contexts install exactly the providers they
-pass, and a declared key they leave out is `undefined` at runtime. Route-unit
-and CLI-dispatch tests inject fixture values through
+stay `unknown`. Route-unit and CLI-dispatch tests inject fixture values through
 `renderRoute(id, { context: { providers: { library } } })`; the harness never
 executes provider modules on a test's behalf. Because the augmentation makes
 declared keys required, the same program also requires `context.providers`