fix: evict token cache in budgetPause, rebuild, and crash paths

Addresses review feedback: evictCreatureTokenCache was only called in stop()
but not in budgetPause, rebuild, or failure paths where the creature exits.
This ensures the token cache is cleaned up on all exit paths.

Author: lucamorettibuilds

src/host/supervisor.ts

@@ -98,6 +98,7 @@ export class CreatureSupervisor {
     this.status = 'sleeping';
     this.sleepReason = 'budget';
     this.creature = null;
+    evictCreatureTokenCache(this.name);
   }
 
   async restart(): Promise<void> {
@@ -153,6 +154,7 @@ export class CreatureSupervisor {
     this.healthyAt = null;
     this.destroyContainer();
     this.creature = null;
+    evictCreatureTokenCache(this.name);
     this.currentSHA = getCurrentSHA(this.dir);
     this.status = 'starting';
     await this.spawnCreature();
@@ -448,6 +450,7 @@ export class CreatureSupervisor {
     if (!this.isDockerAvailable()) {
       console.log(`[${this.name}] Docker unavailable, stopping (not rolling back)`);
       this.status = 'stopped';
+      evictCreatureTokenCache(this.name);
       this.creature = null;
       await this.emit({ t: new Date().toISOString(), type: 'host.infra_failure', reason: 'Docker unavailable' });
       return;
@@ -493,6 +496,7 @@ export class CreatureSupervisor {
     if (this.consecutiveFailures > MAX_CONSECUTIVE_FAILURES) {
       console.log(`[${this.name}] ${this.consecutiveFailures} consecutive failures, giving up`);
       this.status = 'stopped';
+      evictCreatureTokenCache(this.name);
       this.creature = null;
       return;
     }