Instructions are now reusable, typed blocks instead of one field per agent version

Agent instructions are no longer one growing text box per version. They're now instruction blocks: named, reusable pieces of guidance that live at the site level and that any agent version on that site can select and reorder, instead of retyping (or copy-pasting) the same rules into every agent's instructions field.

A block has a type, fixed when you create it:

• Always active: composed into every conversation, every time.
• Conditional: held back until the assistant itself decides it's relevant, based on a condition you write (e.g. "the shopper asks about returns"), so it only takes up room in the conversation when it actually applies.

Every site now gets a mandatory Général block automatically: always active, can't be renamed or deleted, and forced into every agent version's selection. It's the direct replacement for "just type your instructions like before." Manage all of a site's blocks from the new Instructions page, reachable from Agents → Instructions: create, edit, delete (with a warning if a live agent still uses the block), and draft or adjust a block's wording with AI assistance; you always review the draft before saving. Every edit to a block's content is kept as a numbered revision, so you can see who wrote what and why.

An agent version now picks which blocks it uses and in what order, and pins the exact revision of each at creation: editing a block later never changes what a version that already shipped is doing, including your live champion. A newer revision only reaches shoppers once you build a new version (or explicitly update to it while drafting one).

This replaces the old instructions field outright; it isn't carried over. Any text that was previously typed into an agent version's instructions field is not migrated into a block; every existing site starts with an empty Général block instead. If your agents relied on that field, add the same guidance back as your site's Général block (or split it into several typed blocks) before your next version.

See Instructions for the full authoring flow, and Configuration versions for how a version selects and pins blocks.