docs(service-automation): the Exports section covers the whole published surface (#9532)

The value exports were listed but the 30 type exports were not, so the README's
export list was a subset rather than the surface. A rerunnable set-equality check
over the built `.d.ts` now reports 50/50 for this package (104/104 across all five),
in BOTH directions — the gate proves every documented name resolves, it cannot prove
nothing was omitted.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Y26DJEHSBhhAQ6wwfsHNza

Author: claude

packages/services/service-automation/README.md

@@ -431,6 +431,19 @@ import {
 } from '@objectstack/service-automation';
 ```
 
+Types: `AutomationEngineOptions`, `AutomationServicePluginOptions`, `RunSummaryLogLevel`,
+`NodeExecutor`, `NodeExecutionResult`, `SuspensionRelease`, `SuspensionReleaseReason`,
+`FlowTrigger`, `FlowTriggerBinding`, `RegisteredConnector`, `SuspendedRun`,
+`SuspendedRunStore`, `SuspendedRunStoreEngine`, `ObjectStoreSuspendedRunStoreOptions`,
+`RunRecord`, `StepLogEntry`, `UnknownNodeTypeAuditEntry`, `RunDataContext`,
+`RunIdentityContext`, `RunProvenanceContext`, `ConnectorProviderFactory`,
+`ConnectorProviderContext`, `ConnectorMaterialization`, `ConnectorMaterializationHandler`,
+`ConnectorOrigin`, `ConnectorState`, `ConnectorDescriptor`, `ConnectorActionDescriptor`,
+`ConnectorActionHandler`, `ConnectorActionContext`.
+
+The connector types are re-exports from `@objectstack/spec/integration` — connector
+plugins should import them from there rather than coupling to this engine.
+
 `AutomationEngine` is the engine underneath the plugin, exported for hosts that build
 their own kernel integration; `AutomationServicePlugin` is the entry point for everyone
 else. The built-in node installers are functions, not plugins — the platform's