docs: remove reactivity section from foundation composables

Author: johnleider

apps/docs/src/pages/composables/foundation/create-context.md

@@ -99,16 +99,4 @@ Click the buttons to add notifications. Click a notification to dismiss it.
 
 :::
 
-## Reactivity
-
-`createContext` is a **factory function** that returns plain functions. It does not introduce reactivity itself—reactivity comes from the values you provide.
-
-| Return | Reactive | Notes |
-| - | :-: | - |
-| `useContext()` | <AppErrorIcon /> | Function, returns injected value |
-| Injected value | <AppSuccessIcon /> | If you provide refs/reactive objects |
-
-> [!TIP] Reactivity is what you provide
-> The context system is a transport layer. If you provide `ref()` or `reactive()` values, consumers get reactive access. Plain objects remain plain.
-
 <DocsApi />

apps/docs/src/pages/composables/foundation/create-plugin.md

@@ -100,11 +100,4 @@ flowchart LR
   install --> app.runWithContext
 ```
 
-## Reactivity
-
-`createPlugin` is a **factory function** that returns a Vue plugin object. It does not introduce reactivity—it's a vehicle for providing contexts at app level.
-
-> [!TIP] Reactivity lives in what you provide
-> The plugin is just the delivery mechanism. Reactive state comes from the contexts you provide via `provideContext()`.
-
 <DocsApi />

apps/docs/src/pages/composables/foundation/create-trinity.md

@@ -81,15 +81,4 @@ flowchart LR
   C --> Fallback
 ```
 
-## Reactivity
-
-`createTrinity` is a **factory function** that returns a tuple of functions and a default context. It does not introduce reactivity—it structures access to contexts you create.
-
-| Return | Reactive | Notes |
-| - | :-: | - |
-| `defaultContext` | <AppSuccessIcon /> | If the context object contains refs/reactive |
-
-> [!TIP] Trinity is a pattern, not a reactive primitive
-> The trinity pattern organizes your context into a consistent tuple. Reactivity depends on what you put in `defaultContext`.
-
 <DocsApi />