[ataibarkai]

What this changes

Ordinary questions such as “Which two emails need my attention?” were encouraged into generated cards, and notice cards displayed Markdown links as literal text.

• Make direct Markdown replies the default for questions, summaries, recommendations, and short lists. Reserve notices for distinct actionable alerts or explicit requests; use other components when their visual or interactive behavior adds value.
• Render notice bodies and supporting points with the existing Streamdown components, code-highlighting plugins, and streaming context. Avoid duplicate bullets when a point already contains a Markdown list.
• Replace the sidebar's plus-only new-conversation action with a compose icon and “New thread” beside the OpenBot name.

Existing installations: component descriptions are saved on first announcement. The shared prompt changes apply to subsequent runs, but this PR does not overwrite saved administrator descriptions. Update and publish the Notice and Checklist descriptions through component administration to match the new defaults. Those settings were updated separately in the local development installation.

Where it runs

• New state that outlives a request? None.
• What happens on the second replica? It builds the same shared prompt; each browser uses the same renderer. Existing published component descriptions remain in Postgres.
• Anything serialised? No new writes or coordination.
• Anything fanned out to a browser? Existing tool-call delivery is unchanged.
• New listener, port, or schedule? None in the product.

Boundary and audit

• Acting calls continue through the existing gateway and component grants.
• No new refusal or failure paths.
• No new client trust or permissions.

Changelog

• Added entries under Unreleased, including the saved-description rollout note.

Proof

• 222 tests passed across 12 focused prompt, gallery, Markdown, and sidebar test files on the latest main.
• bun run typecheck passed for all workspaces.
• bun run typecheck:tests passed against the repository's existing baseline.
• Biome formatting and lint checks passed for all changed TypeScript files; git diff --check passed.
• Live local browser checks: a three-email prioritization question produced a normal numbered reply without a card; an explicit notice-card request still produced a card. Notice links, emphasis, inline code, and numbered lists rendered correctly. Screenshots are attached to the originating Codex chat.
• This changes model guidance, not a hard prohibition on notice tools; behavior can still vary by model.