sliccy 6.79.1 → 6.80.1

package/README.md

@@ -174,7 +174,7 @@ SLICC shares one core across every runtime ("float"). The browser is not just wh
 
 Once the product makes sense, the ice-cream language is easier to enjoy: it maps to real architecture, not just mascot energy.
 
-- **Cone** — the main agent you interact with. It holds the broad context, owns the overall workflow, and delegates work. Experimental: with the **Multiple cones** flag on (Settings → Experimental), the **Cones** section of the left rail adds a named cone, switches between them, and removes one (together with its scoops); the last cone can never be removed. The original cone stays the default for licks and the freezer.
+- **Cone** — the main agent you interact with. It holds the broad context, owns the overall workflow, and delegates work. Experimental: with the **Multiple cones** flag on (Settings → Experimental), the left rail's action row gains **New cone** (name it; your current chat stays where it is) and **Drop cone** (its chat goes to the Freezer without memory extraction, together with its scoops; the last cone can never be dropped). Cones switch from the tab strip — all cones first, then the scoops of the one you are in. Each cone keeps its own conversation, and **New chat** / **New chat, fast** / **Discard** archive and clear the cone you are looking at. There is one Freezer for all cones; a thawed chat says which cone it came from. Licks and the first-run welcome stay with the original cone.
 - **Scoops** — isolated sub-agents with their own filesystem sandbox, shell, and conversation history.
 - **Licks** — external events that wake an agent up: webhooks, cron jobs, and other signals from the outside world.
 - **Floats** — normal engineers would call it runtimes, but would normal engineers have come up with this?