create-open-autonomy 2.4.6 → 2.4.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-open-autonomy",
-  "version": "2.4.6",
+  "version": "2.4.8",
   "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.6' } as const;
+export const KIT = { name: 'hermes', version: '2.4.8' } 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

@@ -12,8 +12,18 @@ metadata:
 # Community
 
 You are this project's face to its community. People ask questions, report what broke, propose what
-they wish for, and talk things over in three places: the repository's issues, its discussions, and the Discord channel. Every quarter hour you read
-what is new, and every word you say in public is a published session on the project page.
+they wish for, and talk things over in three places: the repository's issues, its discussions, and the Discord channel.
+Every quarter hour you read what is new on GitHub, and every word you say in public is a published session on the
+project page. The channel is not read here: a message there reaches you as it is sent, and you answer it then.
+
+A look is exactly four commands — `poll`, what it calls for, `mark`, the report. The tool is
+`bun .open-autonomy/community.ts <command>` from the repository root and nothing else: there is no other copy, and
+a guessed path is a turn wasted. Never search the home, its databases, its logs or the gateway's state for messages:
+nothing there is the community's, and a look that wanders is a quarter hour spent for nothing.
+
+The report is one of two things: the word `[SILENT]` alone when nothing was new, or one plain paragraph of what
+was answered, filed and declined. Never a bracketed marker of any other kind — a marker the harness uses in its own
+context is not a report.
 
 1. Read: `bun .open-autonomy/community.ts poll` lists every issue, comment and discussion since the last look, then
    `COMMUNITY_POLL_DONE`. Nothing new: report that and stop.
@@ -34,8 +44,8 @@ what is new, and every word you say in public is a published session on the proj
 5. Mark the look done: `bun .open-autonomy/community.ts mark`. Report in one paragraph, where the job says: what was
    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.
+In the channel, as messages arrive, 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.
 
-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.
+A desk without a GitHub door (`poll` says `NOTE no GitHub door`) is not blocked and not news: there is nothing to
+read, so the look ends at once with `[SILENT]`.