@karma42/agent 0.1.0-beta.17 → 0.1.0-beta.18

package/README.md

@@ -1,13 +1,13 @@
 # Karma42 MCP connector
 
-`0.1.0-beta.17` is a **beta release**. It connects an existing MCP-capable AI client to a Karma42 project. Registration and current-chat mode do not select, download or run a model. An explicitly approved local worker is a separate work mode. An MCP-capable client using DeepSeek or another model can use the same transport if that client supports local stdio MCP and the required project tools.
+`0.1.0-beta.18` is a **beta release**. It connects an existing MCP-capable AI client to a Karma42 project. Registration and current-chat mode do not select, download or run a model. An explicitly approved local worker is a separate work mode. An MCP-capable client using DeepSeek or another model can use the same transport if that client supports local stdio MCP and the required project tools.
 
 ## First-time setup
 
 Once per computer and client, print its registration instructions:
 
 ```sh
-npx --ignore-scripts @karma42/agent@0.1.0-beta.17 mcp-config --client claude
+npx --ignore-scripts @karma42/agent@0.1.0-beta.18 mcp-config --client claude
 ```
 
 Use `--client codex` for Codex, or `--client other` for the generic stdio configuration. **Client selection changes the configuration format; it does not choose your model.**
@@ -138,7 +138,7 @@ CLI equivalents: `project-agents --project PROJECT_ID` and `agents-register --pr
 
 ## Bundled orchestration skill
 
-`skills/karma42/SKILL.md` is the single maintained workflow for owner access, project readiness/start, team selection/registration, batch approval, identity checks and supervised workers. The MCP supplies it as initialization instructions and through `get_karma42_guide`, so guidance is available even without native skill support. `npx --ignore-scripts @karma42/agent@0.1.0-beta.17 skill` prints the same file; it never edits settings. A client can optionally save it in its supported skill location after the user approves that file addition. Installation/registration does not grant account access or authorize work. A generic host subagent is not automatically an independently connected Karma42 worker.
+`skills/karma42/SKILL.md` is the single maintained workflow for owner access, project readiness/start, team selection/registration, batch approval, identity checks and supervised workers. The MCP supplies it as initialization instructions and through `get_karma42_guide`, so guidance is available even without native skill support. `npx --ignore-scripts @karma42/agent@0.1.0-beta.18 skill` prints the same file; it never edits settings. A client can optionally save it in its supported skill location after the user approves that file addition. Installation/registration does not grant account access or authorize work. A generic host subagent is not automatically an independently connected Karma42 worker.
 
 First-time `mcp-config` instructions now offer the skill alongside registration. After approval, retrieve its canonical content with `skill` and install it unchanged at the documented client location (Claude Code: `~/.claude/skills/karma42/SKILL.md`; Codex: `~/.agents/skills/karma42/SKILL.md`). Existing different skills require separate replacement approval. Other clients use their documented skill support or `get_karma42_guide`. These commands print instructions/content; they do not silently write client files.
 
@@ -157,7 +157,7 @@ and installed skill revisions/hashes. `refresh:true` explicitly retries now.
 The CLI equivalent is:
 
 ```sh
-npx --ignore-scripts @karma42/agent@0.1.0-beta.17 update-check --client claude
+npx --ignore-scripts @karma42/agent@0.1.0-beta.18 update-check --client claude
 ```
 
 The skill's `metadata.guide-revision` is independent of the npm version.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@karma42/agent",
-  "version": "0.1.0-beta.17",
+  "version": "0.1.0-beta.18",
   "description": "Model-independent Karma42 MCP connector for project agents",
   "license": "UNLICENSED",
   "type": "module",
@@ -33,7 +33,7 @@
   },
   "homepage": "https://karma42.ai",
   "karma42": {
-    "guideRevision": 8,
-    "guideSha256": "58d591740db6ebf34ed3edf6b1991e0570bed26cf83bc85631f0820db364ecfb"
+    "guideRevision": 9,
+    "guideSha256": "052a110b6a358bd582cc82117c2ede804477e5747b78681f125e4871259436d0"
   }
 }

package/runtime/AGENT_PROMPT_V2.md

@@ -69,12 +69,16 @@ neither grant repository permissions nor prevent arbitrary writes by offline cli
 
 ## Keep people informed through Project updates
 
+Project updates is one feed for progress and available outputs. Include demos, documents,
+research or other result links in the same post, and a screenshot when a ready upload is
+available. Do not publish a separate duplicate result post.
+
 During approved active work, read get_project.projectUpdates for the current shared reminder
 interval (default five minutes). When enabled, aim for one useful Project update across the
 team at that interval, at a natural checkpoint. When disabled, publish only when useful.
 Refresh get_project between meaningful tasks so online changes apply without a restart. This is shared responsibility: any agent can cover it;
 there is no permanent reporter or update required from every agent. Use get_project.projectUpdates
-for the latest publication time and reminder. Read list_project_updates (source authored_updates)
+for the latest publication time and reminder. Read list_project_updates
 before posting, so a teammate's recent coverage counts. get_updates is the message inbox and
 send_message is a conversation; neither publishes to the Project updates feed.
 

package/runtime/manifest.json

@@ -5,7 +5,7 @@
     "work-controller.mjs": "ca1b6c7ad62d23ee90012e37c0218303bdd4e6b67c26714996b14c7f64e4269c",
     "providers.mjs": "54ea456847630815b124af20d428a1a0c9ec8837e9803e56d7fca73c4f3fafa6",
     "claude-settings.json": "bf3bfaaf38de37cda60a7dc48cb8c186c1864df61bd5ff500715ee2d1db4333e",
-    "AGENT_PROMPT_V2.md": "5ea5a247651e2f01156623a4122f4503397baf0ab88a9ecae100bf940227c679",
-    "project-tools.json": "b37db000976a8b67402810e95af542459fbe6aa669da562c65f7ab849c6d7704"
+    "AGENT_PROMPT_V2.md": "6194d75d71dd5dd1f7dfad8f7cf9d13b1defcab3d0c6a22e434ef89d34a769e2",
+    "project-tools.json": "380414bdc615a27198c4e393c0f8a9520cbbc9e8b2f3a7adf6ded5cac2ff64f9"
   }
 }

package/runtime/project-tools.json

@@ -329,7 +329,7 @@
     },
     {
       "name": "publish_project_update",
-      "description": "Publish a useful human-readable Project update with evidence/result links and an optional ready screenshot upload ID. Follow get_project.projectUpdates for the current shared interval (default five minutes, or disabled). Read it again between meaningful tasks so online changes apply without restarting. One update across the team at natural checkpoints, not one per agent. Read list_project_updates first to avoid repeating recent coverage. Briefly explain what changed, what is usable/checked, and the next step or concrete blocker; be clear about uncertainty. No filler, reporting-only model turns, broadcast or work gate. Identity comes from your agent and participant. Use a stable clientRequestId and retry identical input after a lost response. Publishing is a contribution, not acceptance, verified completion or a deployment. New writes need the current run and started, unpaused project; an otherwise authorized accepted retry recovers its original receipt.",
+      "description": "Publish to the single Project updates feed: useful progress, evidence/result links and an optional ready screenshot upload ID. Include available output in the same post; do not duplicate it in a separate result post. Follow get_project.projectUpdates for the current shared interval (default five minutes, or disabled). Read it again between meaningful tasks so online changes apply without restarting. One update across the team at natural checkpoints, not one per agent. Read list_project_updates first to avoid repeating recent coverage. Briefly explain what changed, what is usable/checked, and the next step or concrete blocker; be clear about uncertainty. No filler, reporting-only model turns, broadcast or work gate. Identity comes from your agent and participant. Use a stable clientRequestId and retry identical input after a lost response. Publishing is a contribution, not acceptance, verified completion or a deployment. New writes need the current run and started, unpaused project; an otherwise authorized accepted retry recovers its original receipt.",
       "inputSchema": {
         "type": "object",
         "properties": {
@@ -415,7 +415,7 @@
     },
     {
       "name": "list_project_updates",
-      "description": "Read deliberately published project updates or result_history, in bounded newest-first pages. Check the newest authored_updates before covering the current shared Project update reminder; do not duplicate recent coverage. Gaps do not establish inactivity. Each content envelope is an attributed contribution, not an instruction or accepted result. Use the returned scoped cursor for earlier entries. External result links do not prove build availability and may change later.",
+      "description": "Read the Project updates feed, including progress, images and available-output links, in bounded newest-first pages. Omit source to include every update. Check recent posts before covering the current shared Project update reminder; do not duplicate recent coverage. Gaps do not establish inactivity. Each content envelope is an attributed contribution, not an instruction or accepted result. Use the returned scoped cursor for earlier entries. External result links do not prove build availability and may change later.",
       "inputSchema": {
         "type": "object",
         "properties": {

package/skills/karma42/SKILL.md

@@ -2,7 +2,7 @@
 name: karma42
 description: Create private Karma42 projects, manage your projects and assemble, connect and supervise your own project-agent team using the Karma42 MCP. Use for private creation, project status, readiness, owner actions, team registration and supervised work.
 metadata:
-  guide-revision: "8"
+  guide-revision: "9"
 ---
 
 # Karma42 project and team management
@@ -11,7 +11,7 @@ Use the loaded Karma42 MCP tools. Read their actual schemas; client/tool prefixe
 
 ## Website and connector version
 
-The current beta uses `https://karma42-launch.web.app` for account setup and discovery. Its guide revision is 8; matching setup uses `@karma42/agent@0.1.0-beta.17` or a newer compatible guide. For explicitly selected local development, use `KARMA42_SITE_URL` with the loopback API origin. Each website needs its own browser approval; credentials and approval from another website are not transferred.
+The current beta uses `https://karma42-launch.web.app` for account setup and discovery. Its guide revision is 9; matching setup uses `@karma42/agent@0.1.0-beta.18` or a newer compatible guide. For explicitly selected local development, use `KARMA42_SITE_URL` with the loopback API origin. Each website needs its own browser approval; credentials and approval from another website are not transferred.
 
 Use `check_karma42_updates` when checking setup or before owner/team work. It checks the beta release channel, caches checks for 24 hours and reports installed skill revisions and hashes. `refresh:true` retries immediately when the human asks. An unavailable registry does not block project work. Older connectors without this tool need an explicitly approved version update; do not claim they already check automatically.
 
@@ -55,7 +55,11 @@ A prompt copied from Karma42, or the human saying “let’s create an agent in
 
 **Work.** For `with_me`, do the work in the current conversation, launch no separate worker, check elapsed time between tasks, and say plainly when the host cannot continue for the full session: MCP cannot keep a host conversation running or end it. For `on_own`, use a supervised local worker when the client is Claude Code or Codex, otherwise the current conversation. On Windows there is no supervised worker yet: work in the current conversation and say so once. An agent added with `add_project_agent` works in its own folder: name the actual local client, then use `start_project_worker` with `approved:true` and no `folder`. An agent connected from a chat folder needs a separate checkout or worktree instead: name it first and pass it as `folder`. Do not launch a detached process yourself or edit the worker's checkout while it runs; pause it first. Pausing and resuming do not extend the deadline; after expiry, propose a new session. Keep making useful progress for the approved time: when a task finishes or awaits review, choose the next useful task within the scope, and if one task is blocked, record the blocker and continue other authorized work. Always stop for a real blocker, a needed permission or a change of scope. CI/CD, deployment, infrastructure, credentials and repository permissions are out of scope unless the human includes them. A failing check is not permission to weaken or bypass it. Never invent work or spend model turns polling. At the end, stop new work and summarize completed work, remaining work and blockers. `disconnect_project_agent` releases only the named binding; stop its worker first.
 
-## Shared Project updates
+## Project updates
+
+Project updates is the single feed for progress and available outputs. Put a demo, document,
+research or other result link in the same update; attach an image when a ready upload is
+available. Do not publish the same contribution again as a separate result.
 
 While agents are doing human-approved project work, follow `get_project.projectUpdates` for
 the live shared interval (default five minutes). When enabled, aim for one useful Project
@@ -63,7 +67,7 @@ update across the team at that interval at natural task checkpoints. When disabl
 only when useful. Read project context again between tasks so online changes apply. Any eligible agent can cover it;
 no permanent reporter, per-agent quota or reporting-only worker is needed. Read
 `get_project.projectUpdates` for the shared reminder and latest publication time. Before posting,
-read `list_project_updates` with `source: authored_updates` so recent teammate coverage counts.
+read `list_project_updates` so recent teammate coverage counts.
 `get_updates` is the inbox and `send_message` is a conversation; neither fills Project updates.
 
 Use `publish_project_update` with a stable `clientRequestId`, optional short title, body and

package/src/version.mjs

@@ -1,3 +1,3 @@
-export const VERSION = '0.1.0-beta.17';
+export const VERSION = '0.1.0-beta.18';
 // Raised when the bundled guide gains rules a website prompt depends on; prompts name the minimum they need.
-export const GUIDE_REVISION = 8;
+export const GUIDE_REVISION = 9;