Repository navigation
Expand file tree
/
Copy pathconfig-plugins-ops.json
More file actions
275 lines (275 loc) · 14.6 KB
/
Copy pathconfig-plugins-ops.json
File metadata and controls
275 lines (275 loc) · 14.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
{
"skill_name": "objectstack-platform",
"evals": [
{
"id": 1,
"prompt": "Write `objectstack.config.ts` for our CRM app: objects, views and flows under src/, namespace `crm`, protocol 18.",
"expected_output": "`defineStack` with a `manifest` of `id`, `version`, `type: 'app'`, `name`, `namespace: 'crm'`, `engines: { protocol: '^18' }`; barrel imports, `objects: Object.values(objects)` (likewise `views` / `flows`); prefixed object names (`crm_account`), no object-level `namespace`, no `tableName`; no driver in `plugins:` (the CLI resolves it); no `workflows` / `approvals` keys (refused).",
"files": [],
"assertions": {
"must_contain": [
"defineStack",
"manifest",
"engines",
"Object.values("
],
"must_not_contain": [
"workflows:",
"approvals:",
"tableName:"
]
}
},
{
"id": 2,
"prompt": "Build a plugin registering an `audit` service that records every metadata reload and every `task` insert.",
"expected_output": "A `Plugin` with `name`, `init(ctx)` calling `ctx.registerService('audit', ...)` and `ctx.hook('metadata:reloaded', ...)`, `start(ctx)`, `destroy()`. Record events are not kernel hooks — a `data:*` kernel hook registers and never fires — so the task insert is a data hook (objectstack-data). No install / enable / disable hooks.",
"files": [],
"assertions": {
"must_contain": [
"registerService",
"ctx.hook(",
"metadata:reloaded",
"init(",
"destroy"
],
"must_not_contain": [
"data:beforeInsert",
"onInstall"
]
}
},
{
"id": 3,
"prompt": "Our scheduled flows never launch, and `notify` reports success but nobody receives anything.",
"expected_output": "`requires: ['automation', 'triggers', 'job', 'messaging']` on the stack root: `triggers` alone arms record-change triggers, schedule and time-relative ones run on the `job` service, and without `messaging` notify returns success with `skipped: true`. Declaring is a demand (missing provider = hard boot error); `defineStack` rejects an unknown token at authoring time.",
"files": [],
"assertions": {
"must_contain": [
"requires",
"job",
"messaging",
"triggers"
],
"must_not_contain": [
"plugins: [new ServiceJobPlugin",
"@objectstack/adapter-"
]
}
},
{
"id": 4,
"prompt": "We deploy on Vercel serverless functions in our own Hono app; mount the ObjectStack API under /api.",
"expected_output": "`createHonoApp({ kernel })` from `@objectstack/hono` (prefix defaults to `/api`) in the host app — `HonoServerPlugin` only when ObjectStack owns the server; `LiteKernel` for a cold-start-sensitive host; `/auth/*` follows the auth `basePath`, not `prefix`; no `adapter-*` packages exist.",
"files": [],
"assertions": {
"must_contain": [
"createHonoApp",
"@objectstack/hono",
"LiteKernel"
],
"must_not_contain": [
"@objectstack/adapter-",
"HonoServerPlugin("
]
}
},
{
"id": 5,
"prompt": "I changed field types on an object with production data. Show me what the database needs, verify the metadata and give me a quality score.",
"expected_output": "`os migrate plan` previews the drift, `os migrate apply` (`--allow-destructive` for type changes / drops) reconciles, then `os validate` and `os lint --score`; not done until `os validate` passes, which `os lint` does not replace.",
"files": [],
"assertions": {
"must_contain": [
"os migrate plan",
"os migrate apply",
"os validate",
"os lint"
],
"must_not_contain": [
"os rollback",
"os data seed"
]
}
},
{
"id": 6,
"prompt": "Plan the production deployment: Docker on Kubernetes behind nginx, PostgreSQL.",
"expected_output": "`os start` as the entrypoint, `PORT` pinned (production fails loudly on a busy port), `driver-sql` by database URL (no `DriverPlugin` in `plugins:`), TLS on the proxy, app on an internal port, `OS_AUTH_URL` / `OS_TRUSTED_ORIGINS` / app `hostname` in sync; health: `GET /health`, `GET /ready`.",
"files": [],
"assertions": {
"must_contain": [
"os start",
"PORT",
"OS_TRUSTED_ORIGINS",
"driver-sql"
],
"must_not_contain": [
"new DriverPlugin",
"@objectstack/plugin-prometheus"
]
}
},
{
"id": 7,
"prompt": "Prepare a demo of our contracts app: the seed assigns matters to 'Legal Counsel 1' and 'Paralegal 1', and the demo opens signed in as Legal Counsel 1.",
"expected_output": "Both go in `demoStaff` — `name` as the seed references them, `email`, a `position` / `permissionSets` the stack declares — and `os dev` creates the accounts with the seed password: no `password` key, no `role` alias, no platform set, no hand-written `sys_user` seed row. `devLogins` creates nothing (at most a banner entry); `os build` drops `demoStaff`; production creates no demo account.",
"files": [],
"assertions": {
"must_contain": [
"demoStaff",
"position",
"permissionSets",
"os dev"
],
"must_not_contain": [
"role:",
"admin_full_access"
]
}
},
{
"id": 8,
"prompt": "In the contracts demo Paralegal 1 reports to Legal Counsel 1; the approval flow's manager step must reach the right person on a fresh `os dev`.",
"expected_output": "On Paralegal 1's `demoStaff` entry, `manager: 'counsel1@example.com'` — Legal Counsel 1's entry `email`, never the display name — and nothing else: `os dev` writes `sys_user.manager_id` once every demo account exists. No seed row or hook writing `manager_id`, no `reportsTo` / `managerEmail` alias (refused); a manager naming no entry, itself or a loop is refused at load.",
"files": [],
"assertions": {
"must_contain": [
"demoStaff",
"manager: '",
"os dev"
],
"must_not_contain": [
"manager_id:",
"reportsTo:"
]
}
},
{
"id": 9,
"prompt": "Add a `support_intake` queue staffed by the `service_agent` position and route every new `crm_case` into it (`requires: ['automation', 'triggers']`).",
"expected_output": "Two stack collections: `queues: [defineQueue({ name: 'support_intake', label: 'Support Intake', members: [{ type: 'position', value: 'service_agent' }] })]` and `assignmentRules: [defineAssignmentRule(...)]` with one entry, `assignTo: { type: 'queue', value: 'support_intake' }`; plus `'sharing'` in `requires`: the keys need `@objectstack/plugin-sharing`'s ownership-queue service (`queue` is the job queue), else the boot is refused.",
"files": [],
"assertions": {
"must_contain": [
"queues:",
"assignmentRules:",
"defineQueue",
"'sharing'"
],
"must_not_contain": [
"assigned_to",
"beforeInsert"
]
}
},
{
"id": 10,
"prompt": "We installed HotCRM (`hotcrm`, version 3.2.0). Replace its `crm_account_grid` list view with our own columns so every read of that view serves ours, and keep the change exportable to staging.",
"expected_output": "The whole view, under the same name `crm_account_grid`, authored in HotCRM's paired writable package `hotcrm.custom` (which depends on `hotcrm`) with `overrides: { package: 'hotcrm', basedOn: '3.2.0' }` in its body — the base's `manifest.id` and `manifest.version`, `basedOn` recorded and never judged. Every read of the name (no `?package`, `?package=hotcrm`, the layered read, both lists) then serves it under `_packageId: 'hotcrm'`, and `GET /packages/hotcrm.custom/export` carries it with the declaration. Not an in-place edit of HotCRM's own read-only item, not a package-unbound Setup row (that path wins only until the D11 migration), not an object extension (that adds fields and replaces no view), and no declaration from any other package (ignored).",
"files": [],
"assertions": {
"must_contain": [
"hotcrm.custom",
"overrides:",
"package: 'hotcrm'",
"basedOn"
],
"must_not_contain": [
"PUT /api/v1/meta/view/crm_account_grid",
"PUT /meta/view/crm_account_grid"
]
}
},
{
"id": 11,
"prompt": "Our partner package `com.acme.crm_addon` depends on `hotcrm` and wants to ship its own `crm_account_grid` view and a narrower `crm_sales_rep` permission set. Can it override HotCRM's?",
"expected_output": "No. Only HotCRM's paired `hotcrm.custom` declares an override (`overrides: { package: 'hotcrm', basedOn }`); a dependent package's item under a base item's name is refused at save, publish and install, by `os validate` and `os build`, and its one fix is a new name — ship the view as `com.acme.crm_addon`'s own `acme_account_grid` and reach it through its own navigation. A permission set is never overridden by anyone, the pair included: copy `crm_sales_rep` under a new name (\"new similar\"; the clone door lands a copy of a packaged set in `hotcrm.custom` unless `package` names a writable package) and narrow the copy.",
"files": [],
"assertions": {
"must_contain": [
"hotcrm.custom",
"new name",
"new similar"
],
"must_not_contain": [
"overrides: { package: 'hotcrm.custom'",
"PUT /api/v1/meta/permission/crm_sales_rep"
]
}
},
{
"id": 12,
"prompt": "Turn on push notifications for our `os serve` deployment: our own iOS and Android apps, signed with our APNs key and our Firebase project.",
"expected_output": "`requires: ['push']` on the stack root (the token mounts `@objectstack/service-push`) plus a top-level `push:` key on the stack definition; no host code, no `PushServicePlugin` in `plugins:`. Their own signed apps take `transport: 'direct'`, the transport served today, with an `apns` block (`teamId`, `keyId`, `topic`, `environment`, `credentialRef`) and an `fcm` block (`projectId`, `credentialRef`). The APNs signing key and the Firebase service-account JSON stay in the secrets layer (an environment variable in the open tier) and each `credentialRef` names one: no `.p8` key, `privateKey`, `serviceAccount` or service-account JSON written inline. Not the hosted relay, which the boot refuses until its sender ships.",
"files": [],
"assertions": {
"must_contain": [
"requires",
"'push'",
"push:",
"transport: 'direct'",
"credentialRef"
],
"must_not_contain": [
"BEGIN PRIVATE KEY",
"privateKey:",
"serviceAccount:",
"\"private_key\""
]
}
},
{
"id": 13,
"prompt": "HotCRM (`hotcrm`, 3.2.0) ships the `crm_pipeline` dataset and the `crm_sales_overview` page. Can we replace both with our own the way we replaced its `crm_account_grid` view, or is that only for views?",
"expected_output": "The same declaration, both types. In `hotcrm.custom`, an item of the same name and type with `overrides: { package: 'hotcrm', basedOn: '3.2.0' }` in its body replaces the base's dataset or page whole, and every read of the name serves it: a pair's declared override is served for a view, dashboard, report, email_template, translation, flow, action, page, app, dataset, doc, book or mapping. Not an edit of HotCRM's read-only item, not a package-unbound Setup row, and not an object extension (`__c` fields add to an object and replace no dataset or page).",
"files": [],
"assertions": {
"must_contain": [
"hotcrm.custom",
"overrides:",
"dataset",
"page"
],
"must_not_contain": [
"PUT /api/v1/meta/dataset/crm_pipeline",
"PUT /api/v1/meta/page/crm_sales_overview"
]
}
},
{
"id": 14,
"prompt": "We overrode HotCRM's `crm_account_grid` view from `hotcrm.custom`; the customer wants HotCRM's original back. How do we undo it?",
"expected_output": "Remove the pair's item: `DELETE /api/v1/meta/view/crm_account_grid?package=hotcrm.custom`, the removal naming the pair. The base's own document is served again by every read of the name (no `?package`, `?package=hotcrm`, the layered read, both lists), and the pair's export no longer carries the item. Not an edit of HotCRM's item, not a rollback of the base's row (its package-less rollback is refused), and not a second override that copies the base's body into `hotcrm.custom`.",
"files": [],
"assertions": {
"must_contain": [
"DELETE",
"?package=hotcrm.custom"
],
"must_not_contain": [
"/rollback",
"PUT /api/v1/meta/view/crm_account_grid"
]
}
},
{
"id": 15,
"prompt": "HotCRM (`hotcrm`, 3.2.0) ships the `crm_close_deal` action on `crm_opportunity` with `requiredPermissions: ['crm_close_deal']`. The customer wants it relabelled \"Mark won\", run a different script, and usable by every sales rep, including reps without that capability. How do we change it?",
"expected_output": "Relabel it and change what it runs with a declared override in the paired `hotcrm.custom`: an action of the same name on the same object (`objectName: 'crm_opportunity'`) carrying `overrides: { package: 'hotcrm', basedOn: '3.2.0' }`. Its behaviour (`label`, `type`, `body`, …) replaces the base's whole, and it runs for whoever could already run the base action. It cannot widen who that is: dropping `crm_close_deal` from `requiredPermissions` is refused `403 NOT_OVERRIDABLE` (`declared_action_widens_access`), and so is turning `ai.exposed` on or `ai.requiresConfirmation` off. Give the reps the capability through their permission set instead. Moving the action to another object is refused too (`declared_package_ships_no_such_item`). Not an edit of HotCRM's read-only action and not a copy under the same name from a dependent package.",
"files": [],
"assertions": {
"must_contain": [
"hotcrm.custom",
"overrides:",
"requiredPermissions",
"declared_action_widens_access"
],
"must_not_contain": [
"requiredPermissions: []",
"PUT /api/v1/meta/action/crm_close_deal"
]
}
}
]
}