Skip to content

Commit acaeaa5

Browse files
committed
Merge remote-tracking branch 'origin/main' into claude/issue-13809-min-approvals-default-describe
2 parents cebff4f + e5812fa commit acaeaa5

22 files changed

Lines changed: 406 additions & 646 deletions
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
'@objectstack/spec': patch
3+
---
4+
5+
Reference pages no longer open with the `@module` marker line. That tag is what
6+
tells the docs generator which doc block describes the module, but it is
7+
machinery for the selector, not prose — and the renderer emitted it verbatim, so
8+
fourteen published pages opened on the literal text `@module ui/sharing` instead
9+
of on their first sentence. `renderFileDescription` now drops the marker at prose
10+
level, exactly as it already drops the `check:skill-examples` opt-in marker, and
11+
as the skill-index extractor has always done. The marker stays in the source and
12+
still selects the block; only `@module` is dropped, because `@example` and
13+
`@category` carry prose a line-drop would take off the page. No schema behavior
14+
changes.

content/docs/ai/skills-reference.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -49,10 +49,10 @@ ObjectStack ships **11 skills** — one per authoring domain, plus process skill
4949
| 4 | [UI](#ui) | `ui` | `skills/objectstack-ui/` | Author ObjectStack UI metadata — Views (list/form/kanban/calendar/gantt), Apps (navigation), Pages (structured plus the HTML and React source-authoring tiers, ADR-0080/0081), Dashboards, Reports, Charts, Actions, and package Docs (`src/docs/*.md`). |
5050
| 5 | [Automation](#automation) | `automation` | `skills/objectstack-automation/` | Design ObjectStack automation — Flows (visual logic), Triggers, Approvals, state machines, scheduled jobs, and webhooks. |
5151
| 6 | [AI](#ai) | `ai` | `skills/objectstack-ai/` | Design ObjectStack AI skills, tools, knowledge sources, conversations, model registry entries, and MCP integrations. |
52-
| 7 | [API](#api) | `api` | `skills/objectstack-api/` | Design the server-side API surface that an ObjectStack runtime exposes — REST endpoints, auth providers, realtime channels, error envelopes, batch/versioning contracts. |
52+
| 7 | [API](#api) | `api` | `skills/objectstack-api/` | Design the server-side API surface that an ObjectStack runtime exposes — REST endpoints, auth providers, realtime channels, error envelopes, batch contracts. |
5353
| 8 | [i18n](#i18n) | `i18n` | `skills/objectstack-i18n/` | Author ObjectStack translation bundles — object/field labels, view text, app navigation strings, automation messages — and configure locale fallback, coverage reporting, and the per-locale source layout. |
5454
| 9 | [Formula](#formula) | `expression` | `skills/objectstack-formula/` | Author CEL expressions used across ObjectStack — formula fields, field conditional rules (`visibleWhen`, `readonlyWhen`, `requiredWhen`), validation / sharing / visibility predicates, flow conditions, and dynamic seed values. |
55-
| 10 | [PM Dispatch](#pm-dispatch) | `process` | `skills/objectstack-pm-dispatch/` | Run a project-manager dispatch loop over a GitHub backlog: triage and queue ready issues, claim each one, dispatch it to a parallel developer agent that returns a structured JSON report, review the results against GitHub, and drive accepted pull requests to landing — escalating to the maintainer only what genuinely needs a human decision. Ships the developer-agent operating template the loop injects into every dispatch (no custom agent types required) and the upstream-reporting procedure for platform defects an app project finds. |
55+
| 10 | [PM Dispatch](#pm-dispatch) | `process` | `skills/objectstack-pm-dispatch/` | Run a project-manager dispatch loop over a GitHub backlog: triage and queue ready issues, claim each one, dispatch it to a parallel developer agent that returns a structured JSON report, review the results against GitHub, and drive accepted pull requests to landing — escalating to the maintainer only what genuinely needs a human decision. Ships the developer-agent operating template the loop injects into every dispatch (no custom agent types required). |
5656
| 11 | [Upgrade](#upgrade) | `process` | `skills/objectstack-upgrade/` | Upgrade an ObjectStack metadata project across a protocol major — run the deterministic conversion chain, then work the semantic residue the chain cannot express (intent choices, custom code on retired APIs, stale prose) to a decision with the project's owner, and finish with a green `validate` plus a human-readable upgrade report. |
5757

5858
---
@@ -145,7 +145,7 @@ Do not use for general LLM prompting questions unrelated to ObjectStack metadata
145145

146146
**Domain** `api` · **Path** `skills/objectstack-api/`
147147

148-
Design the server-side API surface that an ObjectStack runtime exposes — REST endpoints, auth providers, realtime channels, error envelopes, batch/versioning contracts.
148+
Design the server-side API surface that an ObjectStack runtime exposes — REST endpoints, auth providers, realtime channels, error envelopes, batch contracts.
149149

150150
Use when the user is adding `*.endpoint.ts`, configuring auth providers, defining custom routes, or extending the REST generator.
151151

@@ -187,9 +187,9 @@ Do not use for SQL fragments (driver-native), cron schedules (cron dialect), or
187187

188188
**Domain** `process` · **Path** `skills/objectstack-pm-dispatch/`
189189

190-
Run a project-manager dispatch loop over a GitHub backlog: triage and queue ready issues, claim each one, dispatch it to a parallel developer agent that returns a structured JSON report, review the results against GitHub, and drive accepted pull requests to landing — escalating to the maintainer only what genuinely needs a human decision. Ships the developer-agent operating template the loop injects into every dispatch (no custom agent types required) and the upstream-reporting procedure for platform defects an app project finds.
190+
Run a project-manager dispatch loop over a GitHub backlog: triage and queue ready issues, claim each one, dispatch it to a parallel developer agent that returns a structured JSON report, review the results against GitHub, and drive accepted pull requests to landing — escalating to the maintainer only what genuinely needs a human decision. Ships the developer-agent operating template the loop injects into every dispatch (no custom agent types required).
191191

192-
Use when asked to "work through the backlog", "batch-dispatch issues", "派发 issue 给开发 agent", to stand up a multi-agent delivery loop in an ObjectStack app project, or to report a platform bug found while building an app.
192+
Use when asked to "work through the backlog", "batch-dispatch issues", "派发 issue 给开发 agent", or to stand up a multi-agent delivery loop in an ObjectStack app project.
193193

194194
Do not use for authoring ObjectStack metadata (the domain skills cover that), for a single already-scoped change you can just make, or as a replacement for the project's own conventions file — that file always wins.
195195

content/docs/references/automation/bpmn-interop.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ description: Bpmn Interop protocol schemas
55

66
{/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
77

8-
@module automation/bpmn-interop
9-
108
BPMN XML Interoperability Protocol
119

1210
Defines the specification for importing and exporting BPMN 2.0 XML

content/docs/references/automation/builtin-node-config.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ description: Builtin Node Config protocol schemas
55

66
{/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
77

8-
@module automation/builtin-node-config
9-
108
Config contracts for the remaining flat builtins — the CRUD quartet
119
(`get_record` / `create_record` / `update_record` / `delete_record`),
1210
`screen`, and `map` (#4045). Sibling of `io-node-config.zod.ts`

content/docs/references/automation/control-flow.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ description: Control Flow protocol schemas
55

66
{/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
77

8-
@module automation/control-flow
9-
108
Structured control-flow constructs (ADR-0031) — the **native + AI-authored**
119
flow model: a `loop` **container**, a `parallel` **block**, and structured
1210
`try/catch/retry`. Unlike BPMN's gateway/boundary/token graph (kept in the

content/docs/references/automation/flow-function.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ description: Flow Function protocol schemas
55

66
{/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
77

8-
@module automation/flow-function
9-
108
The contract for a **named handler function a `script` node invokes**
119
contributed by `defineStack({ functions })` and resolved by name at execute
1210
time (#1870).

content/docs/references/automation/io-node-config.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ description: Io Node Config protocol schemas
55

66
{/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
77

8-
@module automation/io-node-config
9-
108
Config contracts for the flat IO builtins — `notify` and `http` (#4045).
119

1210
## Provenance — written from the executors, not from the forms

content/docs/references/automation/node-executor.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ description: Node Executor protocol schemas
55

66
{/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
77

8-
@module automation/node-executor
9-
108
Node Executor Plugin Protocol — Wait Node Pause/Resume
119

1210
Defines the specification for node executor plugins, with a focus on

content/docs/references/automation/schemaless-node-config.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ description: Schemaless Node Config protocol schemas
55

66
{/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
77

8-
@module automation/schemaless-node-config
9-
108
Config contracts for the **descriptor-schemaless** builtins whose designer
119
form lives ONLY in objectui's hand-written `FLOW_NODE_CONFIG` table —
1210
`script`, `subflow` and `decision` (#4278).

content/docs/references/automation/state-machine.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ description: State Machine protocol schemas
55

66
{/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
77

8-
@module automation/state-machine
9-
108
XState-inspired State Machine Protocol — hierarchical states, guarded
119
transitions, entry/exit actions. Used to declare strict business-logic
1210
constraints and lifecycle management, so an AI author cannot "hallucinate" a

0 commit comments

Comments
 (0)