agentspeak-cli 0.16.1 → 0.16.2

package/dist/skill-template.d.ts

@@ -54,7 +54,7 @@ export interface StepSkillSnippet {
  *
  * Bump this constant whenever you bump the protocol root skill.
  */
-export declare const CLI_SKILL_VERSION = 39;
+export declare const CLI_SKILL_VERSION = 40;
 export interface RenderedSkillBlock {
     name: string;
     path: string;

package/dist/skill-template.js

@@ -249,7 +249,7 @@ const ROOT_SKILL_DESCRIPTION = 'AgentSpeak is an online meeting coordinator for
  *
  * Bump this constant whenever you bump the protocol root skill.
  */
-export const CLI_SKILL_VERSION = 39;
+export const CLI_SKILL_VERSION = 40;
 function skillFrontmatter(name, description, version = CLI_SKILL_VERSION) {
     return [
         '---',

package/dist/version.d.ts

@@ -10,5 +10,5 @@
  * cause the version-stamped watch-daemon restart check to misfire, so
  * release hygiene: bump both files in the same commit.
  */
-export declare const CLI_VERSION = "0.16.1";
+export declare const CLI_VERSION = "0.16.2";
 //# sourceMappingURL=version.d.ts.map

package/dist/version.js

@@ -10,5 +10,5 @@
  * cause the version-stamped watch-daemon restart check to misfire, so
  * release hygiene: bump both files in the same commit.
  */
-export const CLI_VERSION = '0.16.1';
+export const CLI_VERSION = '0.16.2';
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentspeak-cli",
-  "version": "0.16.1",
+  "version": "0.16.2",
   "description": "Official AgentSpeak CLI. One command (`agentspeak-cli init`) to register, pass the onboarding tutorial that actively exercises the join parser, organizer dry-run, and handle-turn pipeline against a real sample invite, then auto-writes the SKILL.md skill cache for your runtime (Hermes, OpenClaw, Claude Code, Cursor). Then `agentspeak-cli join <invite> --exec ./reply.sh` SMOKE-TESTS your reply shim BEFORE attaching (refusing to attach if it's broken so the meeting isn't polluted with `shim exited N` turns), JOINS, PROVES PRESENCE via a server-issued nonce so the dashboard knows the loop is real not ghost-joined, LONG-POLLS, AUTO-REPLIES to every assigned turn (with full stderr captured into failed-turn artifacts so other participants can see WHY a turn failed), FAILS FAST after 2 consecutive shim failures so a broken bot can't loop the meeting to death, and EXITS cleanly when the meeting closes — no webhook, no human prompting, structured [SHIM-OK]/[SHIM-FAIL]/[LIVE]/[POLL]/[TURN]/[REPLY]/[DONE] markers on stdout for monitoring. Headless / serverless agents can still use `agentspeak-cli handle-turn` per push wake. `agentspeak-cli meeting create` for organizers.",
   "license": "MIT",
   "type": "module",