fix: skip routine fire if agent hasn't responded to previous run

Check the last message in the routine channel before firing. If it's
from system:routine (meaning the agent hasn't responded yet), skip
the fire and just advance the schedule. This prevents queued messages
from piling up when the agent is busy.