feat(chat): render KB pages & hosted apps inline in the chat window (v0.221.0)

[vikasprogrammer]

What

Follow-up to #365. Extends the inline-deliverable cards in the plain-language Chat window beyond Library artifacts to the other two things agents produce mid-conversation:

• kb_write → a titled KB tile deep-linking to #/kb/<section>/<slug>
• app_create / app_update → a hosted-app tile deep-linking to #/apps/<id>, plus an Open link to the live app when it's published (a proposed app only links for review — it isn't routable yet)

So a non-technical teammate sees "here's the page I wrote / the app I built" right in the thread, one click from opening it.

How

• src/edge/conversation.ts — unlike artifact ids (minted server-side, parsed from the tool result), the KB section/slug and app id live in the tool input, so they're captured directly at tool_use time via refsFromInput() and attached to the activity card. A failed tool_result (is_error) clears them, so a broken write never renders a card. New ChatKbRef/ChatAppRef types + clearer labels ("Updated the knowledge base", "Built an app", "Updated an app").
• src/server.ts — GET /api/sessions/:id/conversation resolves the refs via os.kb.read(tenant, …) / os.apps.get(id) into viewer-safe cards. KB pages and hosted apps are tenant-wide surfaces every member can already browse, so no per-viewer gate beyond the existing canViewSession; an unknown/deleted ref is dropped.
• web/src/App.tsx — KbCard + AppCard render inline under the activity, alongside the existing ArtifactCard.

Verification

• npm run typecheck ✓ · cd web && npm run build ✓ · npm run test:governance → 68/68 ✓
• Unit-drove readConversation on a synthetic transcript: a nested-section kb_write (section preserved), an app_create (id normalized Mini-CRM→mini-crm), and a failed kb_write (refs correctly dropped).

Deploy note: touches src/server.ts (the /conversation route), so making it live needs a build + server restart plus a fresh web build.

🤖 Generated with Claude Code