eve-hub 0.16.56 → 0.16.57

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eve-hub",
-  "version": "0.16.56",
+  "version": "0.16.57",
   "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/reaching-others.md

@@ -21,3 +21,5 @@
   - A note goes through `update_thread`'s `note`, together with a `status` (the current phase, to stay in it), and the hub refuses a verdict, a done status or a plan artifact without one.
   - Coordinator writes `problem` and `goal` when the human opens a thread; `decision`, `cleared` or `question`, with `about`, when the human answers or corrects something; and a `summary` (2 to 3 plain sentences: the goal, where it stands, what is next) after each human decision and each merge report.
   - Planner writes a `finding` on a brief. Reviewer writes an `adjustment` on fix-first and an `outcome` on ship. Builder writes an `outcome` on a merge and on real-path checks, and an `adjustment` when CI or a check changes the plan.
+  - Keep the Artifacts pane in step with the chat. A post that changes where the thread's work stands (a CI result, a merge, a check passing or failing, a step started, blocked or done) is paired with an `update_thread` call in the same turn: the `tracker` row with that row's id, or a `note` with a `status` that keeps the current phase. A chat-only update leaves the pane stale.
+  - Coordinator sends each sitrep through `update_thread`'s `artifacts` as a `sitrep` entry, with a `summary` note, and in that same call refreshes any stale `tracker` rows.