@frontera-sdk/automation 0.1.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.
package/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright 2026 Sebati
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,42 @@
1
+ # @frontera-sdk/automation
2
+
3
+ Author a Frontera automation: a named, triggered handler the platform runs on
4
+ your behalf, deployed with `frontera automation deploy`.
5
+
6
+ ```bash
7
+ bun add @frontera-sdk/automation
8
+ ```
9
+
10
+ ```ts
11
+ import { automation } from '@frontera-sdk/automation'
12
+
13
+ export default automation(
14
+ {
15
+ name: 'late-shipment-digest',
16
+ trigger: { cron: '0 8 * * 1-5' },
17
+ grants: ['blueprint:read'],
18
+ },
19
+ async (ctx) => {
20
+ const late = await ctx.blueprint.query('Shipment', {
21
+ where: { property: 'deliveryStatus', op: 'eq', value: 'late' },
22
+ })
23
+ await ctx.log(`${late.rows.length} late`, { hasMore: late.hasMore })
24
+ },
25
+ )
26
+ ```
27
+
28
+ A trigger is `{ cron }` or `{ manual: true }`, never both — the type refuses
29
+ the ambiguous shape rather than leaving the runner to decide what it means.
30
+ `ctx.log` never rejects: telemetry must not be able to fail a run.
31
+
32
+ `automation()` freezes the manifest it returns, including a copy of the
33
+ trigger — a later mutation of the object you passed in cannot silently change
34
+ the schedule the runner registers.
35
+
36
+ `validateManifest` is the same check the CLI runs before deploy, exported so
37
+ you can run it in your own tests: names are kebab-case segments, and a cron
38
+ expression is parsed rather than pattern-matched.
39
+
40
+ ## License
41
+
42
+ Apache-2.0. See [LICENSE](./LICENSE).
package/package.json ADDED
@@ -0,0 +1,40 @@
1
+ {
2
+ "name": "@frontera-sdk/automation",
3
+ "version": "0.1.0",
4
+ "description": "Author Frontera automations: manifest, triggers and the typed handler contract.",
5
+ "keywords": [
6
+ "frontera",
7
+ "automation",
8
+ "cron"
9
+ ],
10
+ "license": "Apache-2.0",
11
+ "type": "module",
12
+ "files": [
13
+ "src",
14
+ "!src/__tests__",
15
+ "!src/**/*.test.ts",
16
+ "README.md",
17
+ "LICENSE"
18
+ ],
19
+ "publishConfig": {
20
+ "access": "public"
21
+ },
22
+ "exports": {
23
+ ".": {
24
+ "types": "./src/index.ts",
25
+ "import": "./src/index.ts"
26
+ }
27
+ },
28
+ "scripts": {
29
+ "test": "bun test",
30
+ "typecheck": "bunx tsc --noEmit"
31
+ },
32
+ "devDependencies": {
33
+ "@types/bun": "latest",
34
+ "typescript": "^5.9.3"
35
+ },
36
+ "dependencies": {
37
+ "@frontera-sdk/blueprint": "0.1.0",
38
+ "cron-parser": "^5.0.6"
39
+ }
40
+ }
package/src/define.ts ADDED
@@ -0,0 +1,30 @@
1
+ import type {
2
+ AutomationDescriptor,
3
+ AutomationHandler,
4
+ AutomationManifest,
5
+ AutomationTrigger,
6
+ } from './types'
7
+
8
+ export function automation(
9
+ manifest: AutomationManifest,
10
+ handler: AutomationHandler,
11
+ ): AutomationDescriptor {
12
+ if (!manifest?.name) throw new Error('Automation name is required')
13
+ if (typeof handler !== 'function') throw new Error('Automation handler must be a function')
14
+
15
+ // Copied, not aliased. `{ ...manifest }` is shallow, so without this the
16
+ // frozen manifest would still hold a live reference to the caller's trigger
17
+ // object — and a later mutation of it would silently change the schedule the
18
+ // runner registers.
19
+ const trigger: AutomationTrigger = { ...manifest.trigger }
20
+
21
+ return Object.freeze({
22
+ manifest: Object.freeze({
23
+ ...manifest,
24
+ trigger: Object.freeze(trigger),
25
+ grants: Object.freeze([...(manifest.grants ?? [])]),
26
+ concurrency: manifest.concurrency ?? 1,
27
+ }),
28
+ handler,
29
+ })
30
+ }
package/src/index.ts ADDED
@@ -0,0 +1,4 @@
1
+ export { automation } from './define'
2
+ export { validateManifest } from './manifest'
3
+ export type { ValidationResult } from './manifest'
4
+ export type * from './types'
@@ -0,0 +1,125 @@
1
+ import { CronExpressionParser } from 'cron-parser'
2
+
3
+ const SEGMENT = '[a-z][a-z0-9]*(?:-[a-z0-9]+)*'
4
+ const NAME_RE = new RegExp(`^${SEGMENT}$`)
5
+
6
+ /**
7
+ * Runtime gate for a grant: `<namespace>:<name>[:<action>]`, every segment
8
+ * sharing NAME_RE's grammar so the whole vocabulary is consistent.
9
+ *
10
+ * WIDER than the `Grant` union on namespaces — a server must not reject
11
+ * `notify:email` merely because this build predates it. NARROWER than the
12
+ * union's `agent:${string}:run` arm on the slug, which admits `agent::run` and
13
+ * `agent:AGENT:run`; both are rejected here. No legitimate slug is affected —
14
+ * this repo's agent slugs are already lowercase-kebab.
15
+ */
16
+ const GRANT_RE = new RegExp(`^${SEGMENT}:${SEGMENT}(?::${SEGMENT})?$`)
17
+
18
+ const KNOWN_KEYS = new Set(['name', 'trigger', 'grants', 'concurrency', 'description'])
19
+
20
+ export interface ValidationResult {
21
+ valid: boolean
22
+ errors: string[]
23
+ /**
24
+ * Non-fatal. An unknown manifest key lands here rather than in `errors`:
25
+ * a newer SDK must be able to add a field without an older service refusing
26
+ * the deploy. The CLI prints these, so a typo like `concurrancy: 100` — which
27
+ * would otherwise deploy "successfully" with the default of 1 — is caught at
28
+ * author time, where the SDK and the manifest are the same version.
29
+ */
30
+ warnings: string[]
31
+ }
32
+
33
+ /**
34
+ * Takes `unknown`, on purpose.
35
+ *
36
+ * The authoritative call site is the service, validating a manifest that
37
+ * arrived over HTTP — untrusted, and not yet known to have any shape. Typing
38
+ * the parameter as `AutomationManifest` would force every honest caller to
39
+ * launder untrusted input through a cast, which is how a validator ends up
40
+ * trusting the thing it exists to check.
41
+ *
42
+ * The regexes here are deliberately wider than the `Grant` union in `types.ts`:
43
+ * that union is an author-time affordance, this is a runtime gate, and a server
44
+ * must not reject a grant merely because this build predates it.
45
+ */
46
+ export function validateManifest(input: unknown): ValidationResult {
47
+ const errors: string[] = []
48
+ const warnings: string[] = []
49
+ const m = (input ?? {}) as {
50
+ name?: unknown
51
+ trigger?: unknown
52
+ grants?: unknown
53
+ concurrency?: unknown
54
+ }
55
+
56
+ if (typeof m.name !== 'string' || !NAME_RE.test(m.name)) {
57
+ errors.push('name must be lowercase kebab-case')
58
+ } else if (m.name.length > 64) {
59
+ errors.push('name must be 64 characters or fewer')
60
+ }
61
+
62
+ const trigger = m.trigger as { cron?: string; manual?: boolean } | undefined
63
+ if (!trigger || (trigger.cron === undefined && trigger.manual !== true)) {
64
+ errors.push('trigger must be { cron } or { manual: true }')
65
+ } else if (trigger.cron !== undefined) {
66
+ if (typeof trigger.cron !== 'string') {
67
+ errors.push('invalid cron expression: must be a string')
68
+ } else {
69
+ // Both field-count branches exist because `cron-parser` accepts an
70
+ // off-count expression rather than throwing, so neither case would ever
71
+ // reach the `catch` below:
72
+ // `* * * * * *` -> reads field 1 as SECONDS and fires sub-minute.
73
+ // `0 7 * *` -> left-pads, scheduling something the author never wrote.
74
+ // Only an exactly-5-field expression means what it looks like it means.
75
+ const fields = trigger.cron.trim().split(/\s+/).length
76
+ if (fields !== 5) {
77
+ // One message shape for one class of fault. Splitting it meant a
78
+ // 7-field expression was told it was "sub-minute" — a diagnosis
79
+ // asserted rather than derived — while a 4-field one got no diagnosis
80
+ // at all.
81
+ errors.push(
82
+ `invalid cron expression: expected 5 fields, got ${fields}` +
83
+ (fields > 5 ? '; sub-minute schedules are not supported' : ''),
84
+ )
85
+ } else {
86
+ try {
87
+ CronExpressionParser.parse(trigger.cron, { tz: 'UTC' })
88
+ } catch (err) {
89
+ errors.push(`invalid cron expression: ${(err as Error).message}`)
90
+ }
91
+ }
92
+ }
93
+ }
94
+
95
+ if (m.grants !== undefined && !Array.isArray(m.grants)) {
96
+ errors.push('grants must be an array')
97
+ } else {
98
+ for (const g of (m.grants as unknown[]) ?? []) {
99
+ // String(g), not `${g}` — a template literal THROWS on a symbol, and a
100
+ // validator that exists to absorb hostile input must not have a throwing
101
+ // path. The message names the fix, not just the verdict.
102
+ if (typeof g !== 'string' || !GRANT_RE.test(g)) {
103
+ errors.push(
104
+ `malformed grant "${String(g)}" — expected "<namespace>:<action>", ` +
105
+ 'e.g. "blueprint:read" or "agent:risk-analyst:run"',
106
+ )
107
+ }
108
+ }
109
+ }
110
+
111
+ const c = m.concurrency
112
+ if (c !== undefined && (!Number.isInteger(c) || (c as number) < 1 || (c as number) > 50)) {
113
+ errors.push('concurrency must be an integer between 1 and 50')
114
+ }
115
+
116
+ if (input && typeof input === 'object' && !Array.isArray(input)) {
117
+ for (const key of Object.keys(input)) {
118
+ if (!KNOWN_KEYS.has(key)) {
119
+ warnings.push(`unknown manifest key "${key}" — ignored`)
120
+ }
121
+ }
122
+ }
123
+
124
+ return { valid: errors.length === 0, errors, warnings }
125
+ }
package/src/types.ts ADDED
@@ -0,0 +1,117 @@
1
+ // `import type`, so this is erased at compile time and adds no runtime import —
2
+ // but `@frontera-sdk/blueprint` is still a real `dependencies` entry, because
3
+ // `WhereNode` is part of this package's PUBLIC type surface: anyone consuming
4
+ // `AutomationContext` needs it to resolve. See the packaging note in
5
+ // docs/superpowers/specs/2026-07-29-automations-ctx-blueprint-query-design.md —
6
+ // a subset install that cannot resolve it aborts `bun install` outright.
7
+ import type { WhereNode } from '@frontera-sdk/blueprint/types'
8
+
9
+ /**
10
+ * Cron and manual only for now; event and webhook land with Event Triggers.
11
+ *
12
+ * The `?: never` members are load-bearing. Without them `{ cron, manual }`
13
+ * typechecks — TypeScript's excess-property check admits any key present on
14
+ * *some* member of a union — and the runner would have to decide at runtime
15
+ * what a both-shaped trigger means.
16
+ */
17
+ export type AutomationTrigger =
18
+ | { cron: string; manual?: never }
19
+ | { cron?: never; manual: true }
20
+
21
+ /**
22
+ * An author-time affordance, not a validation gate.
23
+ *
24
+ * `blueprint:read` is a literal, so the compiler completes it and offers "Did
25
+ * you mean 'blueprint:read'?" on a typo. `agent:${string}:run` admits any slug
26
+ * — including one that names no agent — so the union cannot be read as proof
27
+ * that a grant is well-formed. The runtime gate is `validateManifest` in
28
+ * `manifest.ts`; this exists to guide the author as they type.
29
+ *
30
+ * Widening it later (adding `notify:*`, `governed:*` with Governed Writes) is a
31
+ * non-breaking change. Narrowing `string` to a union later would break every
32
+ * automation already written, so it starts narrow.
33
+ */
34
+ export type Grant =
35
+ | 'blueprint:read'
36
+ | `agent:${string}:run`
37
+
38
+ export interface AutomationManifest {
39
+ name: string
40
+ trigger: AutomationTrigger
41
+ grants?: readonly Grant[]
42
+ concurrency?: number
43
+ description?: string
44
+ }
45
+
46
+ /**
47
+ * What `automation()` guarantees once defaults are applied — nothing optional
48
+ * left for a consumer to re-handle. Downstream code takes this, not
49
+ * `AutomationManifest`, so it never re-derives a fact already established.
50
+ */
51
+ export interface ResolvedAutomationManifest extends AutomationManifest {
52
+ // Every member is readonly, not just the two with defaults. `Object.freeze`
53
+ // in `define.ts` freezes the whole object at runtime, so leaving `name` or
54
+ // `description` mutable in the type means `d.manifest.name = 'x'` compiles
55
+ // and then throws — the same compile-clean/throw-at-runtime gap that the
56
+ // removed `as string[]` cast used to create.
57
+ readonly name: string
58
+ readonly trigger: Readonly<AutomationTrigger>
59
+ readonly grants: readonly Grant[]
60
+ readonly concurrency: number
61
+ readonly description?: string
62
+ }
63
+
64
+ export interface AgentHandle {
65
+ run(prompt: string): Promise<{ text: string }>
66
+ }
67
+
68
+ /** Read-only for now. `governed`/`notify` arrive with Governed Writes. */
69
+ export interface AutomationContext {
70
+ runId: string
71
+ workspaceId: string
72
+ /** Never rejects — telemetry must not be able to fail a run. */
73
+ log(message: string, data?: Record<string, unknown>): Promise<void>
74
+ agent(slug: string): AgentHandle
75
+ blueprint: {
76
+ query<T = Record<string, unknown>>(
77
+ objectType: string,
78
+ options?: BlueprintQueryOptions,
79
+ ): Promise<BlueprintQueryResult<T>>
80
+ }
81
+ }
82
+
83
+ export interface BlueprintQueryOptions {
84
+ /** The real Blueprint filter DSL, not a shorthand — `and`/`or`/`not`, ranges
85
+ * and date presets all work. A convenience subset with no escape hatch is the
86
+ * thing the first "overdue OR flagged" automation would have to work around. */
87
+ where?: WhereNode
88
+ select?: string[]
89
+ /** `dir`, not `direction` — matches `QueryRequest` exactly. */
90
+ orderBy?: Array<{ property: string; dir: 'asc' | 'desc' }>
91
+ /** Default 100, clamped to 1000. Exceeding the cap sets `hasMore`; it never
92
+ * truncates silently. */
93
+ limit?: number
94
+ /** Opaque. Pass back the previous result's `nextPageToken`; absent means the
95
+ * first page. Cursor-based, so a scan stays correct while the table moves
96
+ * underneath it — which a cron-driven automation's table always does. */
97
+ pageToken?: string
98
+ }
99
+
100
+ export interface BlueprintQueryResult<T = Record<string, unknown>> {
101
+ rows: T[]
102
+ /** True when the query matched more rows than were returned. */
103
+ hasMore: boolean
104
+ /** Present iff `hasMore`. Feed to the next call's `pageToken`.
105
+ *
106
+ * Forwarded rather than narrowed away on purpose: `hasMore` on its own is a
107
+ * fact the author can do nothing about, which is how a digest over the first
108
+ * 500 of 5,000 rows reports success. */
109
+ nextPageToken?: string
110
+ }
111
+
112
+ export type AutomationHandler = (ctx: AutomationContext) => Promise<unknown>
113
+
114
+ export interface AutomationDescriptor {
115
+ readonly manifest: ResolvedAutomationManifest
116
+ readonly handler: AutomationHandler
117
+ }