Skills

Agents can launch a workflow that was killed weeks ago, unwarned

One of my agents can pick a workflow that was killed two weeks ago and not find out until it has already started. The line saying so sits in the body of the file, and the body is only read after something has already chosen it. what loads before a skill is chosen the one line description of each skill: every session the body, where the kill notice used to be: only once chosen kill notice moved into the description: folders four of them write into: gone from disk A notice that only appears after something has already chosen the file cannot stop it being chosen, so the eight dead ones now carry it in the line that always loads.