viber-channel 0.8.30 → 0.8.31

package/lib/capabilities.ts

@@ -8,7 +8,8 @@
  * chooses to call it; the channel instructions carry just a one-line pointer.
  *
  * This is the HOME of "how to USE Viber" for every project (TaskMan points here,
- * #651). Every claim below was checked against the code at #651; keep it that way.
+ * #651). Every claim below was checked against the code at #651 (launch path: #660);
+ * keep it that way.
  *
  * Pure (no I/O) so it is trivially testable and identical across hosts.
  */
@@ -44,8 +45,9 @@ export function capabilitiesText(channelVersion: string | null = null): string {
 		"  viber-gateway launch-team <template> --prefix <p> [--team <t>] [--env dev|staging]",
 		"                            [--cwd <dir>]",
 		"  → --env defaults to staging (the stable channel: agents register with no trust",
-		"    prompt; use it for working teams). Built-in template: dev-team (dev lead + 2",
-		"    reviewers). NAMES: each agent is <prefix>-<role>, the team is --team, else the",
+		"    prompt; use it for working teams). <template> is the NAME of one of the owner's",
+		"    WEB templates, e.g. dev-team (dev lead + 2 reviewers). NAMES: each agent is",
+		"    <prefix>-<role>, the team is --team, else the",
 		"    prefix. Example: template dev-team, --prefix i700 → agents i700-dev-lead,",
 		"    i700-review-opus, i700-review-codex, all in team \"i700\".",
 		"  ⚠ TRAP — --team DEFAULTS TO THE PREFIX. If you launch a child with a prefix that",
@@ -57,11 +59,13 @@ export function capabilitiesText(channelVersion: string | null = null): string {
 		"    the full LABEL <prefix>-<role>: same label = same identity and lock (#293).",
 		"    E.g. w651-agent (prefix w651) may launch a role child with --prefix w651: label",
 		"    w651-child differs, so that is fine — but pass a distinct --team (w651-child).",
-		"WHICH \"dev-team\"? The name is resolved per path, not globally:",
-		"  launch-team → the entry of .viber/agent-teams.json with that name if any (it",
-		"  REPLACES the built-in entirely), else the built-in. The web (New team / Add agent)",
-		"  → the owner's database template of that name. Same name, possibly three rosters.",
-		"  When you copy a web template into agent-teams.json, give it a DISTINCT name.",
+		"WHERE DO TEMPLATES COME FROM? ONE source (#660): the owner's templates on the web.",
+		"  launch-team reads <template> from the web at launch time (with the folder's",
+		"  project token); the web's New team / Add agent use the same templates. No local",
+		"  file, no built-in, no cache, no fallback: web unreachable, token refused or name",
+		"  unknown = an error, and NOTHING is launched (an unknown name lists the available",
+		"  ones). A leftover .viber/agent-teams.json is IGNORED (launch-team says so).",
+		"  A template the spawn would refuse (its warnings, see below) is refused up front.",
 		"  Output is verbose; only these lines matter:",
 		"    team: verdict COMPLETE|INCOMPLET — N member(s)",
 		"    member <agent-name>: launch <launch-id> — spec … (<runtime>)",
@@ -81,20 +85,17 @@ export function capabilitiesText(channelVersion: string | null = null): string {
 		"  after launching is NOT a failure. Wait simply: call list_agents with",
 		"  label_prefix \"<prefix>-\" and online: true every ~10 s, for at most ~60 s; past",
 		"  that, check that the Viber app is running.",
-		"ONE AGENT ALONE = a one-role team. KNOWN LIMIT: launch-team has no --name and no solo",
-		"shortcut: add a one-role template to .viber/agent-teams.json (merged with the",
-		"built-ins; an entry with a built-in's name REPLACES it entirely), then launch it:",
-		"  {\"teams\":{\"solo\":{\"roles\":[{\"role\":\"dev\",\"runtime\":\"claude\",",
-		"   \"permission\":\"read-write\",\"rolePrompt\":\"You are the dev of {prefix}.\"}]}}}",
+		"ONE AGENT ALONE = a one-role WEB template. KNOWN LIMIT: launch-team has no --name:",
+		"the owner creates the template on the web (or an orchestrator agent does, with",
+		"team_templates create, ONLY on the owner's explicit request), then you launch it:",
+		"  spec {\"roles\":[{\"role\":\"dev\",\"runtime\":\"claude\",\"permission\":\"read-write\",",
+		"        \"rolePrompt\":\"You are the dev of {prefix}.\"}]}  named e.g. solo",
 		"  viber-gateway launch-team solo --prefix g1 --team g1-solo",
 		"                                   → agent \"g1-dev\", team \"g1-solo\"",
 		"  runtime: claude|codex|gemma · permission: read-only|read-write (gemma: read-only",
 		"  only; all roles of one template must share one permission) · count optional;",
 		"  model/effort: leave them OUT (runtime default) UNLESS the owner explicitly asks",
 		"  for one; claude only: model opus|sonnet|haiku|fable, effort low|medium|high|xhigh|max.",
-		"  CLEAN UP: .viber/agent-teams.json is SHARED by everyone launching from that",
-		"  folder — once launched, remove the entry you added (the running agent does not",
-		"  need it; only a new launch-team would).",
 		"  (On the web, sidebar ⋯ → Add agent launches ONE named agent without a template edit.)",
 		"",
 		"DISSOLVE (stops the processes, then revokes the proven-stopped instances):",
@@ -159,18 +160,18 @@ export function capabilitiesText(channelVersion: string | null = null): string {
 		"    A template in use CAN be deleted: running agents keep running, but a queued web",
 		"    launch of it fails (\"template no longer exists\"); so does an edit after the",
 		"    launch was queued (template_changed).",
-		"LAUNCHING A WEB/DB TEMPLATE: launch-team does NOT read these templates (only built-ins",
-		"+ .viber/agent-teams.json), and agents cannot launch through the API. Either the owner",
-		"launches it from the web (sidebar ⋯ → New team / Add agent), or you copy its spec",
-		"(team_templates get) into .viber/agent-teams.json under a name, then launch-team it.",
+		"LAUNCHING ONE OF THESE TEMPLATES: launch-team reads exactly these (the web is the only",
+		"source, #660) — an edit here is what the next launch-team launches. Agents still cannot",
+		"launch through the API: launch-team on a machine, or the owner from the web (sidebar",
+		"⋯ → New team / Add agent).",
 		"",
 		"CODEX agents, observed today: their Viber MCP calls, message_agent included, have",
 		"been rejected by their approval policy (#609), so they cannot open an exchange — write",
 		"to them FIRST and read their reply on that DM. Their `gh` has no usable token in",
 		"the sandbox (#525): run gh (labels, PR comments) for them.",
 		"",
-		"Low level, not relaunchable from the web: `vibe-master spawn --permission <p>",
-		"[--runtime codex|claude|gemma] [--name <id>]` (`vibe-master --help`).",
+		"Never launch agents by calling vibe-master yourself: launch-team (or the web) is the",
+		"ONLY launch path (#660), the one the runner supervises and relaunches.",
 		"viber-gateway has no --help: an unknown verb runs the startup command (exit 2",
 		"without --dir; with --dir it runs startup on that registry).",
 	].join("\n");

package/lib/runner_exec.ts

@@ -250,7 +250,8 @@ export type TeamSpawnRunner = (
    * that crossed this boundary carried neither the provenance nor the proof
    * (`gwl10-review-codex-2`). Each runner now proves its own claim: the gateway through
    * {@link gatewayNothingToDo} (roster coverage **and** verdict), `vibe-master` through
-   * `classifyCollision`, which emits this word only when NO roster member is missing.
+   * `classifyCollision`, which emitted this word only when NO roster member was missing
+   * (removed in #660 with `vibe-master team spawn`; no vibe-master command emits it now).
    *
    * ⚠ **OPTIONAL, and the reader FAILS CLOSED on absence** (`?? false`): an omitted field is *no
    * claim*, never *nothing to do*. ▶ This is deliberately unlike the `nonce` above, which is
@@ -332,7 +333,8 @@ export const execFileTeamSpawn: TeamSpawnRunner = (args, nonce) => {
         resolve({
           ok: !err,
           // ▶ #590: vibe-master's OWN guarantee, stated by the launcher that holds it.
-          // ⚠ MEASURED (`vibe-master/lib/teams.ts`, `classifyCollision`): this word is emitted only
+          // ⚠ MEASURED before #660 (`vibe-master/lib/teams.ts`, `classifyCollision`, removed with
+          // `team spawn`; `spawn` never emits a marker, so this now only reads an absent one): this word was emitted only
           // when `missing.length === 0` — every roster name live — and a non-colliding call returns
           // `null` before it, so an empty roster cannot produce it either. A partial team is
           // `partial_team` and stays a failure. ▶ **The same roster-coverage property as the

package/lib/spawn_reason.ts

@@ -7,9 +7,11 @@
  * had nowhere to go. The cause existed — it was on the runner's stderr — and was
  * thrown away here.
  *
- * `vibe-master` now emits a machine line (`VIBEMASTER_RESULT {"reason":…}`,
- * see vibe-master/lib/spawn_result.ts). This module extracts it and turns a
- * reason into a sentence the web can show. The runner's OWN refusals (policy,
+ * `vibe-master team spawn` emitted a machine line (`VIBEMASTER_RESULT {"reason":…}`);
+ * #660 removed that command and its emitter. The live emitter of a team outcome is
+ * now `viber-gateway/lib/result_marker.ts` (`VIBERGATEWAY_RESULT`, read by
+ * `gateway_result.ts`); the reasons below remain its vocabulary. This module
+ * extracts the old line and turns a reason into a sentence the web can show. The runner's OWN refusals (policy,
  * unsafe input, a prior partial run) carry reasons from the same vocabulary, so
  * the web never has to speak two languages.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "viber-channel",
-  "version": "0.8.30",
+  "version": "0.8.31",
   "description": "Voice + text MCP channel between a Claude Code session and the Viber UI (https://viber.dgypx.dev). Push transcripts to Claude; send_message tool delivers text back to the UI.",
   "type": "module",
   "bin": {