create-open-autonomy 2.4.3 → 2.4.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-open-autonomy",
-  "version": "2.4.3",
+  "version": "2.4.4",
   "description": "The default Open Autonomy starter kit: a complete repository that runs its own Hermes agent against the platform, with the SDK wired in. `bun create open-autonomy <dir>` scaffolds one.",
   "license": "Apache-2.0",
   "repository": {

package/src/kit.ts

@@ -9,7 +9,7 @@
 import { existsSync, mkdirSync, readFileSync, readdirSync, rmSync, writeFileSync } from 'node:fs';
 import { dirname, join, relative, resolve } from 'node:path';
 
-export const KIT = { name: 'hermes', version: '2.4.3' } as const;
+export const KIT = { name: 'hermes', version: '2.4.4' } as const;
 export const KIT_FILE = '.open-autonomy/kit.json';
 const TEMPLATE = resolve(import.meta.dir, '..', 'template');
 

package/template/hermes/skills/open-autonomy/community/SKILL.md

@@ -35,4 +35,7 @@ what is new, and every word you say in public is a published session on the proj
    answered, what was filed (with ids), what was declined and why.
 
 In the channel you are simply yourself: answer a question when it is asked; when someone asks there for something
-that fits, file it the same way and say so. The desk without a GitHub door (`poll` says so) reads the channel alone.
+that fits, file it the same way and say so.
+
+A desk without a GitHub door (`poll` exits saying there is no `GITHUB_TOKEN`) is not blocked and not news: it reads
+the channel alone, answers there, and when nothing is new it reports `[SILENT]` like any other quiet look.

package/template/hermes/skills/open-autonomy/develop/SKILL.md

@@ -35,7 +35,9 @@ is not done.
    it when the checks pass. Never wait for it; never open a pull request; never push to `main`; never rewrite
    history. If the branch exists from an earlier attempt, push to `agent/<task id>-<YYYYMMDD-HHMM>`.
 7. Hand off: `kanban_request_review` naming the branch and the commit, and what is verified how. Name no reviewer:
-   the review lane takes the task itself, and a profile the home does not have would hold it forever.
+   the review lane takes the task itself, and a profile the home does not have would hold it forever. This call is
+   how a task ends; a turn that ends without it marks the task done with nothing reviewed, which is never right —
+   even when the work is already on main, hand it off.
 
 If a line cannot be made true from here, `kanban_block` with exactly what is missing, and stop. Never file,
 split or decompose tasks, and never create one: the board is the owner's. Do not loop on a failure you cannot