eve-hub 0.6.2 → 0.6.3

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # eve-hub
 
+## 0.6.3
+
+### Patch Changes
+
+- A hosted bot's execution-context prompt says memory is built into each deployment: an entry takes effect when the deployment that contains it is live, not on the next turn, and with no repository it cannot last. Hosted main's page says how to add one (commit the file to the workspace repo, or write nothing and tell the human to link one). The "Changing it" line says `git` and `gh` are already signed in and sign as the owner, and not to set an author, only when the build has a `GITHUB_TOKEN`; otherwise it says the shell cannot push.
+
 ## 0.6.2
 
 ### Patch Changes

package/execution-context.mjs

@@ -33,6 +33,7 @@ export function deploymentFacts(env = process.env) {
     repo,
     branch: env.VERCEL_GIT_COMMIT_REF,
     sha: env.VERCEL_GIT_COMMIT_SHA,
+    githubToken: Boolean(env.GITHUB_TOKEN),
   };
 }
 
@@ -57,8 +58,9 @@ export function hostedContext({ bot, roster, kit, removed, deployment: d }, opti
     ].filter(Boolean).join(", ") || "no Vercel facts were available to this build"}. Each bot is its own service at \`/eve/<name>\` in that one project.`,
     `- **Source:** ${d.repo ? `built from \`${d.repo}\`${d.branch ? ` on \`${d.branch}\`` : ""}${d.sha ? ` at commit \`${d.sha}\`` : ""}` : "no git repository: the hub uploaded these files"}. You are made of files in it: \`agents/${bot}/\`, \`memory/\` and \`hub.workspace.json\`.`,
     d.repo
-      ? "- **Changing it:** commit to that repository; Vercel builds and deploys the commit."
+      ? `- **Changing it:** commit to that repository; Vercel builds and deploys the commit. ${d.githubToken ? "`git` and `gh` in your shell are already signed in and set to sign commits as the owner; do not set your own author or identity, or GitHub rejects the push." : "No GitHub credential is set up in your shell, so you cannot push."}`
       : "- **Changing it:** there is no repository to commit to. The hub replaces these files on its next deploy, so an edit made only in this deployment does not last.",
+    "- **Memory:** the standing decisions you recall are the `memory/` and `agents/<bot>/memory/` files, built into each deployment. An entry takes effect when the deployment that contains it is live, not on your next turn; with no repository it cannot last.",
     "- **Limits:** there is no `hub` CLI, you cannot restart yourself or any bot, and there are no host paths: your shell is a Vercel Sandbox with its own filesystem, not the owner's machine.",
     `- **Kit tools this build removed:** ${removed.length ? list(removed) : "none"}. They need the hub's machine, or change the roster, which a deployment does by commit.`,
     `- **Logs:** ${dashboard ? `[runtime logs](${dashboard}/logs)${d.deployment ? ` and [this deployment](${dashboard}/${d.deployment.replace(/^dpl_/, "")})` : ""} in the Vercel dashboard` : "the Vercel project's runtime logs in the dashboard"}.`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve-hub",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "license": "Apache-2.0",
   "description": "Bot-side code shared by every hub agent: registry tools, the roster hook, the eve channel, the host sandbox and browser, and model helpers.",
   "type": "module",

package/templates/execution-context-hosted-main.md

@@ -1,4 +1,4 @@
 - **Team.** There is no `create_agent` or `remove_agent`: the roster is `hub.workspace.json`, and a deployment changes it by commit. If nobody on the team covers the work well, ask the human before going on.
 - **Restarts.** There is no `restart_agent` or `restart_hub`: you cannot restart a bot or the hub. A new deployment replaces the running bots.
-- **Memory.** The standing decisions every bot recalls are the `memory/` and `agents/<bot>/memory/` files built into each deployment. A new entry takes effect when the deployment that contains it is live, not on the next turn.
+- **Memory.** Add an entry as your Memory section says, by committing the file to the workspace repository (see Changing it above). With no repository, write nothing and tell the human to link one first.
 - **Schedules.** The build removes the kit's schedules (`dash`, `compact`, `prune`), so no classifier runs, no tick posts, and nothing rewrites track summaries. What you write with `set_summary` and `dash_update` stands until you change it.