Initial import: open-design source for helix-mind.ai distribution

This repository contains the open-design daemon CLI source code, built and packaged at https://helix-mind.ai/cli/open-design/latest.tgz for use by the HelixMind /design slash command. Licenses: Apache-2.0 (root) + MIT (skills/*)
2026-05-06 20:50:24 +02:00
commit 5dd70b5016
1336 changed files with 287186 additions and 0 deletions
--- a/skills/live-artifact/SKILL.md
+++ b/skills/live-artifact/SKILL.md
@@ -0,0 +1,135 @@
+---
+name: live-artifact
+description: |
+  Create refreshable, auditable Open Design artifacts backed by connector or local data.
+  Trigger when the user asks for live dashboards, refreshable reports, synced views, or reusable data-backed artifacts.
+triggers:
+  - "live artifact"
+  - "live dashboard"
+  - "refreshable dashboard"
+  - "live report"
+  - "refreshable report"
+  - "synced view"
+  - "可刷新"
+  - "实时看板"
+od:
+  mode: prototype
+  preview:
+    type: html
+    entry: index.html
+    reload: debounce-100
+  design_system:
+    requires: true
+  outputs:
+    primary: index.html
+    secondary:
+      - template.html
+      - artifact.json
+      - data.json
+      - provenance.json
+  capabilities_required:
+    - shell
+    - file_write
+---
+
+# Live Artifact Skill
+
+Create an Open Design live artifact: a project-scoped, previewable HTML artifact whose data can later be refreshed without redesigning the presentation.
+
+## Resource map
+
+```
+live-artifact/
+├── SKILL.md
+└── references/
+    ├── artifact-schema.md      ← `references/artifact-schema.md`: artifact files, DTO shape, template binding rules
+    ├── connector-policy.md     ← `references/connector-policy.md`: connector safety, redaction, credential boundaries
+    └── refresh-contract.md     ← `references/refresh-contract.md`: source metadata, refresh execution, snapshots
+```
+
+## Current status
+
+Use the references in this directory as the source of truth for the live artifact file contract. Prefer daemon wrapper commands over raw HTTP when registering or updating live artifacts.
+
+## When to use this skill
+
+Use this skill when the user asks for a data-backed view that should remain useful after the first render, for example a live dashboard, refreshable report, synced status page, auditable data view, or artifact that can later be refreshed from local/project data or connectors.
+
+Before creating files, decide whether the user actually wants a live artifact or a normal static artifact:
+
+- Use a live artifact when the user mentions refresh, sync, recurring updates, connector-backed data, source/provenance tracking, dashboards, reports, or reusable data-backed views.
+- Use a normal static artifact when the user only wants a one-off HTML/mockup/image/file and does not need refresh, source metadata, or data/provenance panels.
+- If the intent is ambiguous, ask one short question: “Should this be refreshable/live, or just a static artifact?”
+
+## Workflow
+
+1. **Resolve scope and data source without blocking on connected connectors**
+   - Identify the preview goal, audience, data freshness expectations, and whether refresh should be possible later.
+   - If the user explicitly names a connector/source such as Notion, GitHub, Slack, or Google Drive, do not ask “where should the data come from?” before checking daemon connector tools.
+   - Prefer local/project sources or daemon connector tools when available.
+   - Do not call provider APIs directly when a daemon connector/wrapper exists.
+   - If connector data is needed, first list connectors with `"$OD_NODE_BIN" "$OD_BIN" tools connectors list --format compact`. If the named connector is present with `status: "connected"`, choose an appropriate read-only `auto` tool from its catalog and execute it through the connector wrapper.
+   - For Notion specifically, a connected `notion` connector plus a user brief that names Notion is enough to start with `notion.notion_search` using a query derived from the requested artifact/topic. Use `notion.notion_fetch_database` only when the user supplied a database id or the search result clearly identifies one.
+   - Ask the user a data-source question only when no matching connected connector exists, multiple connected candidates fit equally well, or the requested artifact has no usable topic/query to search for. If you must ask, be specific: ask for the page/database/topic or permission to search broadly, not “where is the Notion data source?”
+
+2. **Author the source files**
+   - Write `template.html` as the human-designed HTML template.
+   - Write `data.json` as the canonical preview data used by `{{data.path}}` bindings.
+   - Write `artifact.json` with the live artifact metadata, preview declaration, document declaration, and safe source descriptors.
+   - Write `provenance.json` with concise source notes, timestamps, non-sensitive connector references, and transformation notes.
+   - Do not author `index.html` as source. The daemon derives `index.html` from `template.html` and `data.json`.
+
+3. **Keep data compact and preview-oriented**
+   - Store only normalized values needed by the preview.
+   - Summarize large lists, provider responses, or logs before writing them into `data.json`.
+   - Stay within the bounded JSON rules in `references/artifact-schema.md`.
+
+4. **Apply safety rules before registration**
+   - Never store credentials, OAuth tokens, API keys, cookies, auth headers, raw provider responses, HTTP envelopes, full payloads, or secret-like fields in `artifact.json`, `data.json`, `provenance.json`, or source metadata.
+   - Avoid forbidden key names such as `raw`, `rawResponse`, `payload`, `body`, `headers`, `cookie`, `authorization`, `token`, `secret`, `credential`, and `password` anywhere in persisted JSON.
+   - Use escaped `html_template_v1` interpolation only. Raw/unescaped HTML interpolation is not allowed.
+
+5. **Register or update through daemon wrappers**
+   - Use the Open Design daemon wrapper commands via `"$OD_NODE_BIN" "$OD_BIN"` instead of raw `curl`, bare `node`, or bare `od`:
+
+     ```bash
+     "$OD_NODE_BIN" "$OD_BIN" tools live-artifacts create --input artifact.json
+     "$OD_NODE_BIN" "$OD_BIN" tools live-artifacts list --format compact
+     "$OD_NODE_BIN" "$OD_BIN" tools live-artifacts update --artifact-id "$ARTIFACT_ID" --input artifact.json
+     ```
+
+   - The wrapper reads injected `OD_NODE_BIN`, `OD_BIN`, `OD_DAEMON_URL`, and `OD_TOOL_TOKEN`; do not print, persist, or override token values.
+   - Do not include or invent `projectId`; the daemon derives project/run scope from the token.
+   - Use raw HTTP only for daemon development/debugging when explicitly requested.
+
+6. **Use connector wrappers for connector data**
+   - Discover available connectors and tools:
+
+     ```bash
+     "$OD_NODE_BIN" "$OD_BIN" tools connectors list --format compact
+     ```
+
+   - Execute a read-only connector tool with a JSON object input file:
+
+     ```bash
+     "$OD_NODE_BIN" "$OD_BIN" tools connectors execute --connector "$CONNECTOR_ID" --tool "$TOOL_NAME" --input input.json
+     ```
+
+   - Persist only the compact normalized fields needed by the preview plus non-sensitive connector references (`connectorId`, `toolName`, `accountLabel`). Never persist connector credentials, transport metadata, or raw provider output.
+   - Do not ask for connector secrets or duplicate setup. If `status` is `connected`, use the listed tools; if it is not connected, tell the user to connect it in the UI.
+   - See `references/connector-policy.md` for listing/execution and credential boundaries, and `references/refresh-contract.md` for read-only refresh source metadata.
+
+7. **Report concise results**
+   - On success, return the artifact ID/title and note that `index.html` is daemon-derived.
+   - On validation failure, fix the source files and retry through the wrapper. Do not bypass validation.
+
+## Required files
+
+Every live artifact creation flow must produce these source files before registration:
+
+- `template.html` — declared skill output and source template for the preview.
+- `data.json` — compact, canonical preview data.
+- `artifact.json` — create/update input for daemon validation.
+- `provenance.json` — safe source and transformation summary.
+
+`index.html` is the primary preview entry declared in frontmatter, but it is derived daemon output rather than agent-authored source.
--- a/skills/live-artifact/references/artifact-schema.md
+++ b/skills/live-artifact/references/artifact-schema.md
@@ -0,0 +1,99 @@
+# Live Artifact Schema Reference
+
+Live artifacts are stored as daemon-owned project files under `.live-artifacts/<artifactId>/`. Agents author the source files, then register them through daemon tooling. The daemon assigns IDs, project scope, timestamps, run scope, and refresh status.
+
+## Source files
+
+| File | Owner | Purpose |
+| --- | --- | --- |
+| `artifact.json` | agent-authored input, daemon-validated | Artifact metadata, preview settings, document metadata, and source descriptors. Must not contain daemon-owned fields. |
+| `template.html` | agent-authored | `html_template_v1` template used to render the preview. |
+| `data.json` | agent-authored then refresh-runner-updated | Canonical preview data. API `document.dataJson` is only a derived cache. |
+| `provenance.json` | agent-authored then refresh-runner-updated | Source summary and generation notes. |
+| `index.html` | daemon-derived | Generated preview output. Do not treat as source of truth. |
+
+## Create/update input
+
+`artifact.json` should match `LiveArtifactCreateInput` or `LiveArtifactUpdateInput` from `packages/contracts/src/api/live-artifacts.ts`.
+
+Allowed agent-owned top-level fields:
+
+- `title`
+- `slug`
+- `sessionId`
+- `pinned`
+- `status`
+- `preview`
+- `document`
+
+Daemon-owned fields are rejected in agent input:
+
+- `id`
+- `projectId`
+- `createdAt`
+- `updatedAt`
+- `createdByRunId`
+- `schemaVersion`
+- `refreshStatus`
+- `lastRefreshedAt`
+
+## HTML document contract
+
+MVP documents use `html_template_v1`:
+
+```json
+{
+  "format": "html_template_v1",
+  "templatePath": "template.html",
+  "generatedPreviewPath": "index.html",
+  "dataPath": "data.json",
+  "dataJson": {}
+}
+```
+
+`template.html + data.json` is rendered by the daemon into `index.html` and the preview route.
+
+### Binding rules
+
+- Use escaped interpolation: `{{data.path.to.value}}`.
+- Paths must start with `data` and use dot-separated keys; numeric array indexes are allowed as path segments.
+- Supported structural directive: `data-od-repeat="item in data.items"` for one-level array repeats.
+- Nested repeats, conditionals, filters, helper functions, partials, and expression evaluation are not supported.
+- Raw HTML insertion is forbidden: no triple braces, ampersand interpolation, `data-od-html`, `data-od-raw`, or equivalent.
+- Interpolation in text and ordinary attributes is HTML-escaped by default.
+- Do not interpolate inside tag names, attribute names, comments, `<script>`, `<style>`, `<iframe srcdoc>`, event-handler attributes, or unsupported URL-bearing attributes.
+
+## Bounded JSON limits
+
+All persisted JSON values must fit the shared bounded JSON envelope:
+
+| Limit | Value |
+| --- | ---: |
+| Maximum object/array depth | 8 |
+| Maximum keys per object | 100 |
+| Maximum array length | 500 |
+| Maximum string length | 16 KiB |
+| Maximum serialized JSON size | 256 KiB |
+
+Forbidden keys anywhere in persisted JSON include `raw`, `rawResponse`, `payload`, `body`, `headers`, `cookie`, `authorization`, `token`, `secret`, `credential`, and `password`.
+
+## Minimal static artifact input
+
+```json
+{
+  "title": "Release Status",
+  "preview": { "type": "html", "entry": "index.html" },
+  "document": {
+    "format": "html_template_v1",
+    "templatePath": "template.html",
+    "generatedPreviewPath": "index.html",
+    "dataPath": "data.json",
+    "dataJson": {
+      "summary": {
+        "title": "Release Status",
+        "status": "On track"
+      }
+    }
+  }
+}
+```
--- a/skills/live-artifact/references/connector-policy.md
+++ b/skills/live-artifact/references/connector-policy.md
@@ -0,0 +1,119 @@
+# Connector Policy Reference
+
+Live artifacts may use connector or local data, but they must persist only compact, preview-oriented data and provenance. Never persist credentials or raw provider envelopes inside live artifact files.
+
+## Connector safety model
+
+Connector tools are classified by side effect and approval requirement:
+
+- `read` + `auto`: eligible for agent preview and potential refresh.
+- `write` + `confirm`: not refreshable; requires explicit user confirmation if exposed later.
+- `destructive` + `disabled`: never refreshable.
+- `unknown` + `confirm` or `disabled`: fail closed until classified.
+
+If a tool name, scope, or description suggests write/create/update/delete/admin/send/post/manage behavior, treat it as write-capable unless the daemon catalog explicitly proves otherwise. Destructive hints must be disabled for refresh.
+
+## Execution boundaries
+
+- Use daemon wrapper commands or `/api/tools/connectors/*`; do not call provider APIs directly from the artifact workflow when a daemon connector exists.
+- Tool endpoints require the injected `OD_TOOL_TOKEN`; do not invent or pass `projectId`.
+- Agent calls and refresh-runner calls must share the same daemon connector execution service.
+- Re-check connector status, allowlists, current scopes, tool safety, and refresh eligibility at execution time.
+- For connector-backed refresh, saved `connectorId`, `accountLabel`, tool name, input shape, and approval policy must still match current connector state.
+
+## Connector listing
+
+List connectors before using connector-backed data:
+
+```bash
+"$OD_NODE_BIN" "$OD_BIN" tools connectors list --format compact
+```
+
+The compact result includes each connector's `id`, display metadata, `status`, optional `accountLabel`, and callable tool summaries with `name`, `description`, `safety`, and `inputSchema`. Use this output to select a connector and tool; do not guess tool names.
+
+Only execute tools from connectors whose status is `connected`. Local/public connectors may already be connected by the daemon; OAuth-backed connectors must be connected by the user through the UI before agent execution.
+
+If the user already named a connector or app, treat that as the intended data source. For example, “create a Notion live artifact” means: list connectors, find `notion`, and if it is `connected`, use its read-only tools instead of asking where the Notion data comes from. Ask a follow-up only when the matching connector is missing/unconnected, when several connected matches are equally plausible, or when there is no searchable topic/page/database clue in the user’s request.
+
+For Notion, prefer this selection order:
+
+1. Use `notion.notion_search` with a concise query derived from the user’s requested artifact/topic.
+2. Use `notion.notion_fetch_database` only when the user provided a database id or a prior search result identifies a specific database.
+3. If the user simply says “Notion live artifact” with no topic, ask what Notion page/database/topic to visualize or whether to search broadly.
+
+## Connector execution
+
+Create a bounded JSON object input file that matches the selected tool's `inputSchema`, then execute through the wrapper:
+
+```bash
+"$OD_NODE_BIN" "$OD_BIN" tools connectors execute --connector "$CONNECTOR_ID" --tool "$TOOL_NAME" --input input.json
+```
+
+The wrapper reads `OD_NODE_BIN`, `OD_BIN`, `OD_DAEMON_URL`, and `OD_TOOL_TOKEN`, sends the request to `/api/tools/connectors/execute`, and prints compact JSON. Successful output includes `connectorId`, optional `accountLabel`, `toolName`, `safety`, `outputSummary`, redacted `output`, and daemon metadata. On failure, fix the input/schema/connection issue and retry; do not bypass connector validation with direct provider calls.
+
+Execution is fail-closed:
+
+- connector and tool IDs must be in the daemon catalog allowlist;
+- the connector must still be connected and not disabled;
+- current runtime safety must be `read` + `auto` for agent execution;
+- input must match the current tool schema;
+- run rate limits and total call limits apply;
+- output is size-bounded and redacted before the agent receives it.
+
+Use execution output as an intermediate source only. Normalize it into `data.json` and provenance, keeping only fields the preview needs.
+
+## Read-only refresh rules
+
+Connector-backed live artifact refresh is allowed only for tools that remain read-only and refresh-eligible at refresh time. A saved refresh source must include non-sensitive connector metadata and permission state, for example:
+
+```json
+{
+  "type": "connector_tool",
+  "toolName": "github.public_repo_summary",
+  "input": { "owner": "open-design", "repo": "open-design" },
+  "connector": {
+    "connectorId": "github_public",
+    "accountLabel": "public",
+    "toolName": "github.public_repo_summary"
+  },
+  "outputMapping": {
+    "dataPaths": [{ "from": "summary", "to": "repository" }],
+    "transform": "metric_summary"
+  },
+  "refreshPermission": "manual_refresh_granted_for_read_only"
+}
+```
+
+During refresh, the daemon revalidates `connectorId`, `accountLabel`, tool name, saved input schema, and allowlist membership. If anything drifts, the refresh fails without changing the previous valid preview.
+
+Never mark write, destructive, unknown, confirmation-required, disabled, unconnected, or schema-drifted connector tools as refreshable.
+
+## Persistence rules
+
+Persist only:
+
+- compact normalized values needed by the preview in `data.json`;
+- high-level provenance in `provenance.json`;
+- connector references and refresh metadata in `sourceJson`.
+
+Never persist:
+
+- OAuth tokens, API keys, cookies, headers, authorization values, or session material;
+- raw provider HTTP bodies, envelopes, payloads, or full responses;
+- credential-like values under alternate names;
+- connector credentials under `.live-artifacts/`.
+
+Credential storage is daemon-controlled and outside project artifact directories. Artifacts may contain connector IDs and non-sensitive account labels only.
+
+## Credential handling constraints
+
+- Do not ask the user for connector secrets inside the artifact workflow.
+- Do not ask the user to re-specify a data source that is already named and connected; inspect the connector catalog first.
+- Do not write OAuth material, API keys, cookies, sessions, HTTP request metadata, or provider auth state into `artifact.json`, `data.json`, `provenance.json`, tile JSON, snapshots, refresh history, or `.live-artifacts/`.
+- Do not include secret-like values in connector tool inputs or source metadata. If a connector requires credentials, the daemon-owned connector UI/storage must handle them outside project artifacts.
+- Safe persisted connector references are limited to catalog IDs, tool names, non-sensitive account labels, selected normalized output fields, and concise provenance notes.
+- If connector output contains unredacted sensitive or envelope-like fields, stop and return a validation/safety error instead of storing it.
+
+## Output protection
+
+Connector outputs must be bounded and redacted before returning to agents or entering artifact files. Use compact summaries and selected fields. If redaction cannot prove the result is safe, fail with a validation error instead of storing it.
--- a/skills/live-artifact/references/refresh-contract.md
+++ b/skills/live-artifact/references/refresh-contract.md
@@ -0,0 +1,78 @@
+# Refresh Contract Reference
+
+Refresh updates live artifact data without redesigning the presentation. The refresh runner updates `data.json`, provenance, and audit history; it does not allow arbitrary template rewrites.
+
+## Refreshable source metadata
+
+Refreshable documents use `sourceJson`:
+
+```json
+{
+  "type": "connector_tool",
+  "toolName": "list_releases",
+  "input": {},
+  "connector": {
+    "connectorId": "github",
+    "accountLabel": "example/org",
+    "toolName": "list_releases"
+  },
+  "outputMapping": {
+    "dataPaths": [{ "from": "items", "to": "releases" }],
+    "transform": "compact_table"
+  },
+  "refreshPermission": "manual_refresh_granted_for_read_only"
+}
+```
+
+Supported source types:
+
+- `local_file`
+- `daemon_tool`
+- `connector_tool`
+
+Supported output transforms:
+
+- `identity`
+- `compact_table`
+- `metric_summary`
+
+## Source execution model
+
+- `refreshPermission` is retained for backward compatibility with older artifacts, but the refresh runner does not require a separate connector approval step.
+- If a safe source descriptor exists, manual refresh executes it through daemon-owned local or connector wrappers.
+- Write, destructive, unknown, disabled, unconnected, or schema-drifted connector tools should not be authored as refresh sources.
+
+## Connector-backed refresh
+
+Connector-backed refresh sources use the same connector execution service as agent-initiated connector calls. Do not call provider APIs directly from refresh logic or from skill-authored scripts.
+
+Before creating a connector-backed refresh source:
+
+1. List connectors with `"$OD_NODE_BIN" "$OD_BIN" tools connectors list --format compact`.
+2. If the user named a connector/source and it is connected, select that connector directly instead of asking where the source is. Then select a tool whose safety is `read` + `auto` and whose catalog metadata marks it refresh-eligible.
+3. Execute once with `"$OD_NODE_BIN" "$OD_BIN" tools connectors execute --connector <id> --tool <name> --input input.json` to produce compact normalized preview data.
+4. Store only non-sensitive connector references, the bounded input object, output mapping, and compatibility `refreshPermission` in `sourceJson`.
+
+On each refresh, the daemon must re-check connector status, account label, allowlist membership, input schema, and output protection. If any check fails or output protection rejects the result, refresh fails all-or-nothing and preserves the previous valid preview.
+
+Persisted connector refresh metadata may include `connectorId`, `toolName`, non-sensitive `accountLabel`, bounded `input`, `outputMapping`, and compatibility `refreshPermission`. It must not include credentials, auth/session material, raw provider envelopes, or unbounded provider responses.
+
+## Commit behavior
+
+Refresh is all-or-nothing:
+
+1. Acquire one active refresh lock per artifact.
+2. Execute each refreshable source with timeouts and current safety checks.
+3. Build candidate `data.json`, provenance, and preview.
+4. Validate all candidates with the same schemas used for create/update.
+5. Commit only if every refreshable source succeeds.
+6. Preserve the previous valid preview if any step fails.
+
+Refresh IDs must be monotonic so stale runs cannot overwrite newer committed data.
+
+## Audit storage
+
+- Append compact records to `refreshes.jsonl`.
+- Successful refresh snapshots live under `snapshots/<refreshId>/` and may include `data.json` and provenance.
+- Failed refreshes are summarized in `refreshes.jsonl` without leaking raw provider output or credentials.
+- On daemon startup, stale running refreshes should be marked failed or timed out while preserving the last valid preview.