@rudderhq/agent-runtime-opencode-local 0.6.6-canary.9 → 0.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/package.json +2 -2
  2. package/skills/app-builder/SKILL.md +31 -14
  3. package/skills/app-builder/agents/openai.yaml +2 -2
  4. package/skills/app-builder/evals/evals.json +12 -0
  5. package/skills/app-builder/references/scaffold-contract.md +17 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rudderhq/agent-runtime-opencode-local",
3
- "version": "0.6.6-canary.9",
3
+ "version": "0.7.0",
4
4
  "license": "SEE LICENSE IN LICENSE",
5
5
  "homepage": "https://github.com/Undertone0809/rudder",
6
6
  "bugs": {
@@ -67,7 +67,7 @@
67
67
  "typecheck": "tsc --noEmit"
68
68
  },
69
69
  "dependencies": {
70
- "@rudderhq/agent-runtime-utils": "0.6.6-canary.9",
70
+ "@rudderhq/agent-runtime-utils": "0.7.0",
71
71
  "picocolors": "^1.1.1"
72
72
  },
73
73
  "devDependencies": {
package/skills/app-builder/SKILL.md CHANGED
@@ -1,12 +1,17 @@
1
1
  ---
2
2
  name: app-builder
3
- description: "Build and iteratively improve full-stack apps from natural-language requests with Rudder's maintained scaffold, app runtime, SQLite data workflow, and Browser verification. Use for websites, dashboards, CRM, cold-email, marketing-data, trackers, admin tools, and other requests to create or modify an application that runs on the user's device."
3
+ description: "Create and iteratively improve local web products from natural-language requests, then prepare them to run as Rudder Apps. Use Rudder's maintained scaffold for new websites and preserve the existing stack for Next.js, React, Vue, Astro, SvelteKit, Nuxt, and other local web projects."
4
4
  ---
5
5
 
6
6
  # App Builder
7
7
 
8
- Build a useful first version for a non-technical user without asking them to
9
- choose a framework, database, package manager, or process topology.
8
+ Create or improve a useful local web product without making a non-technical
9
+ user choose a framework, database, package manager, or process topology.
10
+
11
+ A Rudder App is an ordinary local website presented as an App inside Rudder.
12
+ This Skill owns requirements, source changes, and product verification. Rudder
13
+ Desktop owns folder selection, launch-definition review, process lifecycle,
14
+ loopback attestation, and embedded opening.
10
15
 
11
16
  ## Build Workflow
12
17
 
@@ -14,11 +19,15 @@ choose a framework, database, package manager, or process topology.
14
19
  essential screens, durable data, external integrations, constraints, and
15
20
  exclusions. Ask at most three grouped questions, and only when an answer
16
21
  materially changes behavior, real-data safety, or external authority.
17
- 2. For a new app, use the maintained scaffold in `assets/scaffold/`. Prefer the
18
- Apps workspace flow when it is available. Otherwise run
19
- `scripts/scaffold.mjs` with an explicit workspace root and target, then ask
20
- the operator to use the App entry's `Register & preview` action. Never
21
- recreate the foundation from memory or overwrite a non-empty directory.
22
+ 2. Choose the source path:
23
+ - For a new App, use the maintained scaffold in `assets/scaffold/`. Prefer
24
+ the Apps workspace flow when it is available. Otherwise run
25
+ `scripts/scaffold.mjs` with an explicit workspace root and target. Never
26
+ recreate the foundation from memory or overwrite a non-empty directory.
27
+ - For an existing web project, inspect its current framework, package
28
+ manager, development script, data boundary, and tests before editing.
29
+ Preserve its stack and conventions; never replace it with the maintained
30
+ scaffold merely to make it a Rudder App.
22
31
  3. Read [references/scaffold-contract.md](references/scaffold-contract.md)
23
32
  before changing the runtime, database foundation, manifest, health endpoint,
24
33
  import/export contract, or background-job runner.
@@ -32,10 +41,18 @@ choose a framework, database, package manager, or process topology.
32
41
  dashboard assembled from decorative cards.
33
42
  7. Run migrations against development or snapshot data, then run typecheck,
34
43
  unit tests, build, and relevant app E2E tests.
35
- 8. Start a development preview through the App entry in the Apps workspace. The Agent
36
- writes and verifies source; Desktop alone owns runtime approval and process
37
- start. Do not invent a public URL, tunnel, cloud deployment, or unreviewed
38
- launch command.
44
+ 8. Prepare the website for its Rudder Apps handoff:
45
+ - A new managed App created from Apps Home keeps its typed manifest and
46
+ returns to that App's **Register & preview** action. Do not load the same
47
+ source again through the manual Local App path.
48
+ - An independently authored existing project keeps a direct supported
49
+ development script. Add the `package.json` `rudder` readiness or open-path
50
+ fields only when discovery cannot infer them safely, then direct the
51
+ operator to **Apps + > Add local web project** to select the folder and
52
+ review the launch definition.
53
+ The Agent writes and verifies source; Desktop alone owns runtime approval and
54
+ process start. Do not invent a public URL, tunnel, cloud deployment, or
55
+ unreviewed launch command.
39
56
  9. Read [references/verification.md](references/verification.md), then verify
40
57
  the rendered app with Rudder Browser. Exercise the main workflow plus at
41
58
  least one production-shaped edge case and inspect console errors.
@@ -77,9 +94,9 @@ controls and least-data workflow choices; explain the boundary honestly.
77
94
 
78
95
  Do not call the app complete until:
79
96
 
80
- - source and manifest are durable in the assigned organization-workspace App directory;
97
+ - source and any required manifest or `package.json` Rudder configuration are durable;
81
98
  - typecheck, unit tests, and build pass;
82
- - the health endpoint is ready on an attested loopback process;
99
+ - the reviewed readiness path is ready on an attested loopback process;
83
100
  - Browser verification covers the primary workflow and a relevant edge case;
84
101
  - persistence behavior is verified against development or snapshot data;
85
102
  - current screenshot evidence is attached to the work;
package/skills/app-builder/agents/openai.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  interface:
2
2
  display_name: "App Builder"
3
- short_description: "Build and verify full-stack apps in Rudder"
4
- default_prompt: "Use $app-builder to build this app with Rudder's maintained scaffold and verify it in the Browser."
3
+ short_description: "Create or improve local web Apps for Rudder"
4
+ default_prompt: "Use $app-builder to create or improve this local web product, prepare it as a Rudder App, and verify it in the Browser."
5
5
 
6
6
  dependencies:
7
7
  tools:
package/skills/app-builder/evals/evals.json CHANGED
@@ -48,6 +48,18 @@
48
48
  "Does not describe localhost as private, offline, or shareable.",
49
49
  "Continues with a useful local app option if that still serves the user."
50
50
  ]
51
+ },
52
+ {
53
+ "id": 5,
54
+ "prompt": "I already have a Vue project on this computer. Help me improve the onboarding flow and make it easy to open as a Rudder App.",
55
+ "expected_output": "Preserves the existing Vue project, improves the requested product workflow, prepares a direct supported development script and only the minimal Rudder discovery metadata, then routes the operator through Apps + > Add local web project for review.",
56
+ "files": [],
57
+ "assertions": [
58
+ "Does not replace the existing project with the maintained Next.js scaffold.",
59
+ "Inspects and preserves the project's framework, package manager, data boundary, and test conventions.",
60
+ "Uses a direct supported development script and adds package.json Rudder readiness or open-path fields only when inference is insufficient.",
61
+ "Requires the operator to review the discovered launch definition before Desktop runs it."
62
+ ]
51
63
  }
52
64
  ]
53
65
  }
package/skills/app-builder/references/scaffold-contract.md CHANGED
@@ -3,8 +3,23 @@
3
3
  ## Purpose
4
4
 
5
5
  The maintained scaffold is the default foundation for non-technical users. Do
6
- not offer a framework chooser. Technical users may leave this workflow and use
7
- their own project.
6
+ not offer a framework chooser. It is not a requirement for existing websites
7
+ that will be loaded as Rudder Apps.
8
+
9
+ ## Existing Web Projects
10
+
11
+ When the user already has a local web project, preserve its framework, package
12
+ manager, data model, scripts, and test conventions. Do not copy scaffold files
13
+ or add `rudder.app.json` to make an independently authored project appear
14
+ managed.
15
+
16
+ Rudder Desktop discovers a direct `dev`, `start`, `serve`, or `preview` script
17
+ from `package.json`. It recognizes common direct framework commands for Next.js,
18
+ Vite-based React or Vue, Astro, SvelteKit, Nuxt, Vue CLI, and `react-scripts`.
19
+ When the ordinary inference is insufficient, the project may add a `rudder`
20
+ object to `package.json` with `readiness.path`, `readiness.timeoutMs`, or
21
+ `openPath`. The operator still reviews the complete structured launch
22
+ definition through **Apps + > Add local web project** before anything runs.
8
23
 
9
24
  ## Fixed Foundation
10
25