fix: resolve CI test failures in spec and objectql packages

[Claude]

CI tests failed in @objectstack/spec and @objectstack/objectql packages due to validation changes and missing registry methods.

Changes

packages/spec/src/stack.test.ts

• Updated test to check individual manifest properties instead of deep equality, accounting for defaultDatasource: "default" being added during validation

packages/objectql/src/engine.ts

• Use object's FQN (object?.name) when calling SchemaRegistry.getObjectOwner() instead of objectName, which may be a short name

packages/objectql/src/engine.test.ts

• Added missing getObjectOwner() method to SchemaRegistry vitest mock with proper contributor tracking

packages/objectql/src/datasource-mapping.test.ts

• Renamed SchemaRegistry.clear() → reset()
• Renamed engine.create() → insert() (correct API method)

// Before: getObjectOwner called with potentially short name
const owner = SchemaRegistry.getObjectOwner(objectName);

// After: use FQN from resolved object
const fqn = object?.name || objectName;
const owner = SchemaRegistry.getObjectOwner(fqn);

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
objectstack-demo	Ready	Preview, Comment	Apr 14, 2026 1:26pm
spec	Ready	Preview, Comment	Apr 14, 2026 1:26pm

[Copilot]

Pull request overview

Fixes CI failures in @objectstack/spec and @objectstack/objectql by aligning tests/mocks/docs with recent validation + registry behavior, and by correcting ownership lookup to use fully-qualified object names.

Changes:

• Updated defineStack() test expectations to avoid failing on validator-added manifest defaults.
• Fixed ObjectQL driver resolution to call SchemaRegistry.getObjectOwner() with the resolved object’s registry key (FQN) rather than a potentially-short name.
• Updated ObjectQL tests/mocks to include getObjectOwner(), use SchemaRegistry.reset(), and call the correct CRUD API (insert()).

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
packages/spec/src/stack.test.ts	Makes the strict-mode defineStack() test resilient to validator-applied defaults.
packages/objectql/src/engine.ts	Uses resolved object name (FQN) for ownership-based manifest datasource lookup.
packages/objectql/src/engine.test.ts	Extends the SchemaRegistry mock to support getObjectOwner() and resets contributor state.
packages/objectql/src/datasource-mapping.test.ts	Updates tests to use SchemaRegistry.reset() and the engine’s insert() API.
content/docs/references/kernel/manifest.mdx	Updates generated manifest reference docs to include defaultDatasource.
content/docs/references/api/auth-endpoints.mdx	Updates generated auth endpoint reference docs (expanded sections + usage snippet).

Comments suppressed due to low confidence (1)

content/docs/references/api/auth-endpoints.mdx:32

• The TypeScript usage snippet appears to import schema values that aren’t actually exported under these names. In packages/spec/src/api/auth-endpoints.zod.ts, the runtime Zod schemas are AuthEndpointSchema, AuthFeaturesConfigSchema, etc., while AuthEndpoint, AuthFeaturesConfig, etc. are type-only exports. As written, AuthEndpoint.parse(...) and the value import list will not typecheck/compile; update the snippet (or the docs generator) to import the *Schema values for .parse() and only import the inferred types as type if needed.

import { AuthEndpoint, AuthFeaturesConfig, AuthProviderInfo, EmailPasswordConfigPublic, GetAuthConfigResponse } from '@objectstack/spec/api';
import type { AuthEndpoint, AuthFeaturesConfig, AuthProviderInfo, EmailPasswordConfigPublic, GetAuthConfigResponse } from '@objectstack/spec/api';

// Validate data
const result = AuthEndpoint.parse(data);

</details>

[Copilot]

This test no longer asserts the key behavior that changed (the defaulting of manifest.defaultDatasource). Since ManifestSchema sets defaultDatasource via .default('default'), it would be better to explicitly expect result.manifest.defaultDatasource to be 'default' (and optionally keep a stronger structural assertion like toMatchObject(config) for the rest) so the test still guards against unintended validation transforms.

Suggested change

	// Validation may add defaults like defaultDatasource
	expect(result.manifest).toBeDefined();
	expect(result.manifest.id).toBe(baseManifest.id);
	expect(result.manifest.name).toBe(baseManifest.name);
	expect(result.manifest.version).toBe(baseManifest.version);
	expect(result.manifest.type).toBe(baseManifest.type);
	// Validation preserves the provided structure while applying schema defaults
	expect(result).toMatchObject(config);
	expect(result.manifest).toBeDefined();
	expect(result.manifest.defaultDatasource).toBe('default');

[Copilot]

These datasource-mapping tests don’t currently verify which driver was selected (both mock drivers return the same shape), so the assertions will pass even if routing is broken. Consider asserting on memoryDriver.create/tursoDriver.create call counts (and ensure the registered object definition includes whatever fields the routing logic matches on, e.g. namespace, so the namespace rule can actually trigger).