release v1.1.1

CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## [1.1.1] - 2026-08-18
+
+### Summary
+
+Template image bump: generated claws now default to the `hermes-1.9.11` container image (was `hermes-1.9.3`). The `HarnessImageTag` CloudFormation parameter default and the `manage-dispatch` skill documentation are updated to match. No CLI or generator behavior changes; already-deployed agents are unaffected — roll them with the `manage-dispatch` upgrade procedure.
+
+### Changes
+
+- c19aa27 bump: harness image tag to hermes-1.9.11
+
 ## [1.1.0] - 2026-08-15
 
 ### Summary

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@boldblackai/create-dispatch",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "CLI to generate dispatch agent repositories",
   "type": "module",
   "publishConfig": {

template/.agents/skills/manage-dispatch/SKILL.md

@@ -690,7 +690,7 @@ Use `ask_user_question` to ask whether to restart now.
 
 Roll the running claw onto a new `ghcr.io/boldblackai/harness` tag. The image
 tag is a CloudFormation parameter (`HarnessImageTag`, default
-`hermes-1.9.3`); bumping it and redeploying creates a new task-definition
+`hermes-1.9.11`); bumping it and redeploying creates a new task-definition
 revision and ECS rolls the task — **no image rebuild** (the signed upstream
 image is used as-is). EBS-backed state (sessions, memories, `~/.config/gh`)
 survives the roll; only the container image changes.
@@ -710,7 +710,7 @@ aws ecs describe-tasks --cluster "$CLAW_NAME" \
     --query 'taskArns[0]' --output text)" \
   --region "$AWS_REGION" \
   --query 'tasks[0].containers[0].image' --output text
-# → ghcr.io/boldblackai/harness:hermes-1.9.3
+# → ghcr.io/boldblackai/harness:hermes-1.9.11
 ```
 
 And what the stack is parameterized with:
@@ -770,7 +770,7 @@ version bump is just this edit plus the redeploy in Step 4, then commit:
 # .agents/skills/setup-dispatch/template.yaml
 HarnessImageTag:
   Type: String
-  Default: hermes-1.9.4     # ← was hermes-1.9.3
+  Default: hermes-1.9.11     # ← was hermes-1.9.3
 ```
 
 > To roll without touching the repo, skip this edit and add
@@ -788,7 +788,7 @@ aws cloudformation deploy \
   --capabilities CAPABILITY_NAMED_IAM \
   --role-arn arn:aws:iam::$(aws sts get-caller-identity \
     --query 'Account' --output text):role/${CLAW_NAME}-cfn-exec \
-  --parameter-overrides $OVERRIDES HarnessImageTag=hermes-1.9.4
+  --parameter-overrides $OVERRIDES HarnessImageTag=hermes-1.9.11
 ```
 
 > If you edited the `Default` in Step 3, passing `HarnessImageTag` here is
@@ -825,7 +825,7 @@ aws ecs describe-tasks --cluster "$CLAW_NAME" --tasks "$TASK_ARN" \
   --output table
 ```
 
-Expect `Image` ending in `:hermes-1.9.4`, `Status = RUNNING`. Tail the gateway
+Expect `Image` ending in `:hermes-1.9.11`, `Status = RUNNING`. Tail the gateway
 log to confirm the bot reconnected:
 
 ```bash
@@ -999,7 +999,7 @@ aws ec2 terminate-instances --instance-ids "$INSTANCE_ID" --dry-run --region "$A
   container instance directly, independent of the task or stack.
 
 - **Image upgrades are stack updates, not overlays.** Mode 4 bumps
-  `HarnessImageTag` (a CloudFormation parameter, default `hermes-1.9.3`)
+  `HarnessImageTag` (a CloudFormation parameter, default `hermes-1.9.11`)
   and redeploys, creating a new task-definition revision; ECS recreates the
   task (stop-old-then-start-new).
   It does not touch EBS state — sessions, memories, and `~/.config/gh` survive.

template/.agents/skills/setup-dispatch/template.yaml

@@ -32,7 +32,7 @@ Parameters:
 
   HarnessImageTag:
     Type: String
-    Default: hermes-1.9.3
+    Default: hermes-1.9.11
     Description: >
       Tag of the ghcr.io/boldblackai/harness image to run. Bump to upgrade
       the claw — no image rebuild (use the signed upstream image as-is).