@desplega.ai/agent-swarm 2.4.1 → 2.4.3

package/templates/skills/apps/content.md

@@ -220,6 +220,7 @@ Each column is `{ "kind": ..., "required"?: boolean, "default"?: ..., "index"?:
 | `boolean` | Boolean; set `index: true` only when equality lookups need it. |
 | `date` | ISO-8601 string; never indexed. |
 | `enum` | String from the non-empty unique `enum` list; always indexed, without `index: true`. |
+| `json` | Any JSON value (object, array, nested) up to 256 KB serialized by default (`APPS_JSON_COLUMN_MAX_BYTES`); never indexed, and a named query cannot `filter` or `sort` on it. Not allowed for `userConfig` fields or element props. |
 
 `default` must match the column kind (and be one of the enum values). `required: true` rejects missing/null values unless a default supplies the value. `id`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy` — and the sync envelope `source`, `syncedAt`, `stale` — are system columns and reserved names. An app created before the sync envelope that declared ordinary columns with these names surfaces `definitionError` after upgrade until they are renamed: patch in a fresh column with a `{from}` migration directive, then purge the old one. Rows always expose `id`/`createdAt`/`updatedAt`; `createdBy`/`updatedBy` record the acting principal (`user:<id>`, `agent:<id>`, `operator`, or `sync:<source>` for engine writes) and are system-managed on every row write.
 
@@ -316,7 +317,7 @@ A named query is:
 }
 ```
 
-`filter` is a strict AND of equality checks. A filter may target a declared model column or a system column (`id`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`, and on synced models `source`, `syncedAt`, `stale`) — filtering on `id` is the universal way to select one row for a detail view, and `{ "stale": true }` selects rows a complete pull stopped confirming. A literal value must match the column's kind; date filters compare the stored raw ISO string, not parsed instants. Omit `limit` for the default 200 rows, or set an integer from 1 through 1000. `sort.column` is a model column, `createdAt`, `updatedAt`, or `syncedAt`; `dir` is `asc` or `desc`. Query runtime state is `{ data, loading, error }` under `/queries/<queryName>`.
+`filter` is a strict AND of equality checks. A filter may target a declared model column or a system column (`id`, `createdAt`, `updatedAt`, `createdBy`, `updatedBy`, and on synced models `source`, `syncedAt`, `stale`) — filtering on `id` is the universal way to select one row for a detail view, and `{ "stale": true }` selects rows a complete pull stopped confirming. A literal value must match the column's kind; date filters compare the stored raw ISO string, not parsed instants. Omit `limit` for the default 200 rows, or set an integer from 1 through 1000. `sort.column` is a non-`json` model column, `createdAt`, `updatedAt`, or `syncedAt`; `dir` is `asc` or `desc`. Query runtime state is `{ data, loading, error }` under `/queries/<queryName>`.
 
 A filter value may instead be exactly `{ "$param": "<name>" }`. At execution, the caller supplies that name and the server coerces its value to the filtered column's kind before equality matching:
 
@@ -515,7 +516,7 @@ Tones: Badge, Metric and Progress `tone` take `neutral`, `success`, `active`, `e
 
 Table details:
 
-- `columns[]`: `{ key, label?, kind?, tones?: {value: badgeTone}, width?: number, pinned?: "left" or "right", align?: "start" or "end", truncate?: "end" or "middle", icon?, tooltip?: "<row field>", max?: number, onChange?: chain }`. `kind` is `text`, `string`, `enum`, `number`, `boolean`, `date`, `badge`, `status`, `user`, `agent`, `relative`, `duration`, `progress`, `copy`, `switch`, or `link`; `string` and `enum` render as text. Pin id/actions columns so they survive horizontal scroll on narrow viewports.
+- `columns[]`: `{ key, label?, kind?, tones?: {value: badgeTone}, width?: number, pinned?: "left" or "right", align?: "start" or "end", truncate?: "end" or "middle", icon?, tooltip?: "<row field>", max?: number, onChange?: chain }`. `kind` is `text`, `string`, `enum`, `number`, `boolean`, `date`, `badge`, `status`, `user`, `agent`, `relative`, `duration`, `progress`, `copy`, `switch`, `link`, or `json`; `string` and `enum` render as text, and `json` renders a truncated single-line `JSON.stringify` preview. Pin id/actions columns so they survive horizontal scroll on narrow viewports.
   - `status`: lifecycle values (`pending`, `in_progress`, `running`, `completed`, `failed`, `cancelled`, `paused`, `reviewing`, ...) render the dashboard status chip with its icon; other values use `tones` like `badge`.
   - `user` / `agent`: avatar plus name. `relative` (and `date`): smart time, exact time on hover. `duration`: milliseconds as `1m 23s`. `progress`: a bar against `max` (default 100). `copy`: the value plus a copy button. `link`: an http(s) URL opening in a new tab (other values render as text).
   - `switch`: a toggle. `onChange` runs with `$row` = the row with this column already set to the new value, e.g. `[{ "action": "app.mutate", "params": { "model": "m", "op": "update", "rowId": { "$row": "id" }, "values": { "enabled": { "$row": "enabled" } } } }]`. Without `onChange` the switch is read-only.
@@ -784,6 +785,7 @@ The tool returns `{ appId, url: "/apps/<id>" }`. Open that URL to verify the liv
 - Logged-in browser: a fresh dashboard has no connection and redirects to /setup. Seed the localStorage key `agent-swarm-connections` with `{connections:[{id,name,apiUrl,apiKey}],activeId}`. Build the value from an env var and pipe it to `agent-browser eval --stdin`, so the key never reaches a command line. Reload, then pick a user in the "Who are you?" dialog.
 - Apps scroll inside an inner canvas, so a full-page screenshot captures only the viewport. Scroll the canvas or raise the viewport height. For mobile, set a 375px-wide viewport before the screenshot.
 - App definitions: `GET /api/apps` and `GET /api/apps/<id>` with the API key as Bearer.
+- Follow-up edit to a live app: list in the brief the control numbers the edit must not move, and assert them from the backing script before publishing. Take a signed-in screenshot of each changed selector at 1440px wide, save the shots to agent-fs, critique, and repeat at least 3 times. If the backing script caches results, bump its version or force a fresh run so the shots show new data.
 
 
 ### Rows from agents and scripts

package/templates/skills/code-quality/content.md

@@ -82,27 +82,22 @@ The review body is the verdict line: at most about 60 tokens. Each inline commen
 - Swarm PR, nit fixed: ``**Approve** at `3d4f34a` · 0 blocking · set `Risk: high` (billing) in the body``
 - Re-review: ``**Approve** at `661327f` · B1 fixed · N1 won't fix (author)``, new findings inline.
 
-Never on GitHub: test counts, CI lists (unless a red check changes the verdict), what you read, how the code works, or why GitHub refused a formal verdict. Those go to your task output and the ledger.
+Never on GitHub: test counts, CI lists (unless a red check changes the verdict), what you read, how the code works, or why GitHub refused a formal verdict. Those go to your task output.
 
-### Post through the gate
+### Post the review
 
-Nothing reaches GitHub without passing `review-post-gate`.
-
-1. Draft the review as JSON: `{ pr: "<owner>/<repo>#<n>", head, swarmAuthored, risk, round, priorFindings: [{ id, state, text }], findings: [{ id?, tag, path?, line?, text, fix? }], body? }`. Write `fix` so it reads as done in the verdict line, for example "set `Risk: high` (billing) in the body". When you ran `code-reviewing`, its Standards/Spec report stays in your task output; only its findings go into the draft.
-2. Run `script-run name="review-post-gate" scope="global" args=<draft>`. It checks token limits, the nit cap, tallies and CI lists, turns swarm-PR nits into `fixes`, and asks Jev to keep, drop or relabel each finding against the live `rules.md`. Every decision is logged with its reason. With `jev: "unavailable"` the deterministic result still stands.
-3. Apply every entry in `fixes`, then post exactly `postable`, never your draft:
+1. Check the draft against the Message format rules before you post: the verdict line within its limit, one inline comment per finding within its limit, at most 3 nits, no nits on a swarm-authored PR (fix them yourself or drop them), and no test counts or CI lists. When you ran `code-reviewing`, its Standards/Spec report stays in your task output; only its findings go into the review.
+2. Post the verdict line and every inline comment as one review:
 
    ```bash
-   jq -n --argjson p "$POSTABLE" --arg sha "$HEAD" \
-     '{commit_id: $sha, event: $p.event, body: $p.body, comments: [$p.comments[] | {path, line, side: "RIGHT", body}]}' \
+   jq -n --arg sha "$HEAD" --arg event "$EVENT" --arg body "$VERDICT" --argjson comments "$COMMENTS" \
+     '{commit_id: $sha, event: $event, body: $body, comments: [$comments[] | {path, line, side: "RIGHT", body}]}' \
      | gh api repos/<owner>/<repo>/pulls/<n>/reviews --input -
    ```
 
-   On a PR the reviewing account authored, the gate returns `event: "COMMENT"`, because GitHub refuses APPROVE and REQUEST_CHANGES there. Post it as is.
-4. Record the evidence (tests run, controls, "checked, fine" notes, the gate's `logKey`) in your task output and with `script-run name="pr-review-ledger-write" scope="global"` (`action: "round"`). Never on the PR. If the ledger write fails, keep the exact payload and the error in your task output, report it to the lead once, and finish the review. Read the PR's existing ledger rounds before any retry so a round is never written twice.
-5. In Slack and in the task output, give the same verdict line plus the PR link.
-
-If the gate cannot run, post nothing to GitHub. Keep the draft in your task output and report the gate failure (the error and the time) to the lead.
+   `EVENT` is `APPROVE` or `REQUEST_CHANGES`. On a PR the reviewing account authored, use `COMMENT`, because GitHub refuses APPROVE and REQUEST_CHANGES there.
+3. Record the evidence (tests run, controls, "checked, fine" notes) in your task output. Never on the PR.
+4. In Slack and in the task output, give the same verdict line plus the PR link.
 
 ### Capture pushback as a rule
 

package/dist/handlers-mqrym347.js

@@ -1,39 +0,0 @@
-import {
-  isUserAllowed2,
-  registerMessageHandler2
-} from "./cli-p6argxh9.js";
-import"./cli-3kh4kpqy.js";
-import"./cli-3r448dqn.js";
-import"./cli-kr2pmfqx.js";
-import"./cli-smvcw9z5.js";
-import"./cli-sv5gb0yb.js";
-import"./cli-qz93y3x5.js";
-import"./cli-3h26v7yj.js";
-import"./cli-7a91w22y.js";
-import"./cli-k9z4zd4p.js";
-import"./cli-0bh477zn.js";
-import"./cli-3ggwdtb0.js";
-import"./cli-sjyetj21.js";
-import"./cli-s48yvzb8.js";
-import"./cli-3p8fqcnh.js";
-import"./cli-qje9k2nh.js";
-import"./cli-kmqgmcnb.js";
-import"./cli-tbhwrxpt.js";
-import"./cli-8nyhf7za.js";
-import"./cli-ejs3m1sx.js";
-import"./cli-z071fb95.js";
-import"./cli-13p25grh.js";
-import"./cli-0adyhvq2.js";
-import"./cli-vy0fay6k.js";
-import"./cli-mfe7f7b5.js";
-import"./cli-bn5kevnf.js";
-import"./cli-fz9kewbh.js";
-import"./cli-445c1vp7.js";
-import"./cli-kvzgak7c.js";
-import"./cli-nx462e4v.js";
-import"./cli-rqqsfz30.js";
-import"./cli-wt645v7q.js";
-export {
-  isUserAllowed2 as isUserAllowed,
-  registerMessageHandler2 as registerMessageHandler
-};

package/dist/index-pqfwh9nn.js

@@ -1,41 +0,0 @@
-import"./cli-ns59dc6r.js";
-import {
-  startHeartbeat2,
-  stopHeartbeat2
-} from "./cli-rdq7tzwm.js";
-import"./cli-axh29tyr.js";
-import"./cli-hqhzg1qq.js";
-import"./cli-kr2pmfqx.js";
-import"./cli-smvcw9z5.js";
-import"./cli-sv5gb0yb.js";
-import"./cli-qz93y3x5.js";
-import"./cli-3h26v7yj.js";
-import"./cli-7a91w22y.js";
-import"./cli-k9z4zd4p.js";
-import"./cli-0bh477zn.js";
-import"./cli-3ggwdtb0.js";
-import"./cli-sjyetj21.js";
-import"./cli-s48yvzb8.js";
-import"./cli-3p8fqcnh.js";
-import"./cli-qje9k2nh.js";
-import"./cli-kmqgmcnb.js";
-import"./cli-tbhwrxpt.js";
-import"./cli-8nyhf7za.js";
-import"./cli-ejs3m1sx.js";
-import"./cli-z071fb95.js";
-import"./cli-13p25grh.js";
-import"./cli-0adyhvq2.js";
-import"./cli-vy0fay6k.js";
-import"./cli-mfe7f7b5.js";
-import"./cli-bn5kevnf.js";
-import"./cli-fz9kewbh.js";
-import"./cli-445c1vp7.js";
-import"./cli-kvzgak7c.js";
-import"./cli-b2mz5mjc.js";
-import"./cli-nx462e4v.js";
-import"./cli-rqqsfz30.js";
-import"./cli-wt645v7q.js";
-export {
-  startHeartbeat2 as startHeartbeat,
-  stopHeartbeat2 as stopHeartbeat
-};