Benjamin Taylor b13fa63cb5 docs(examples): call them Channels, not managed Channels ...

The starter READMEs, channel-host.mts headers, and the host's own log
lines described the feature as a "managed Channel". Managed is an
implementation detail of how Intelligence attaches the provider edge,
not part of the name — the product surface is just a Channel.

Renames every occurrence across the 15 starters. Section headings become
"Running a Channel", the host header becomes "Channel host", and the
setup_required log reads "no provider is attached yet".

"managed Intelligence" in the .env.example comments is left alone: that
one distinguishes hosted Intelligence from a self-hosted deployment and
is unrelated to Channel naming.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-02 12:17:13 -05:00

..

app

feat(examples): add a managed Channel host to the langgraph-python starter

2026-08-01 23:58:17 -05:00

components

fix(examples): unify header controls + even toggle padding [ENT-1051]

2026-07-08 12:23:35 -05:00

hooks

fix: convert starter templates from pnpm/Turborepo to flat npm projects

2026-04-16 13:23:30 +02:00

lib

chore(examples): oxlint --fix north-star + parity-sync all instances

2026-05-20 13:07:52 -07:00

agent.ts

docs(examples): call them Channels, not managed Channels

2026-08-02 12:17:13 -05:00