Implement P0-P2 spec compliance tasks from SPEC_COMPLIANCE_EVALUATION.md

[Copilot]

Addresses all P0, P1, and key P2 gaps identified in the spec compliance evaluation across 12 packages.

P0 — Critical

• DataScope module (core): New DataScopeManager implementing DataContext with row-level filtering (9 operators), read-only scopes, change listeners
• AI plugin handlers (plugin-ai): Replaced console.log placeholders with proper callback props (onApply, onRefresh, onSelect, onDismiss, onSubmit) across AIFormAssist, AIRecommendations, NLQueryInput
• Validators export (core): Removed stale TODO comments — already exported via validation module

P1 — High

• DetailView/RelatedList API fetch (plugin-detail): Implemented fetch() and dataSource.find() integration with error handling
• ReportViewer (plugin-report): Added onRefresh callback; extracted computeAggregation helper supporting count/sum/avg/min/max
• ReportBuilder cancel (plugin-report): onCancel now actually invokes the callback
• Map coordinates (plugin-map): Added isFinite validation + UI warning for excluded records
• String formulas (core): FIND, REPLACE, SUBSTRING, REGEX, LEN
• useTheme hook (react): New ThemeContext + useTheme() for component-level theme access

P2 — Medium

• Statistical formulas (core): MEDIAN, STDEV, VARIANCE, PERCENTILE
• DATEFORMAT (core): Token-based date formatting (YYYY/MM/DD/HH/mm/ss)
• Custom validator registration (core): registerValidator(name, fn) / registerAsyncValidator(name, fn) on ValidationEngine

// DataScope — row-level filtering
const manager = new DataScopeManager();
manager.registerScopeWithConfig('contacts', {
  dataSource: myDataSource,
  filters: [{ field: 'status', operator: 'eq', value: 'active' }],
  readOnly: false,
});
const filtered = manager.applyFilters('contacts', records);

// New formula functions
FIND('world', 'hello world')        // 6
STDEV(2, 4, 4, 4, 5, 5, 7, 9)      // ~2.138
DATEFORMAT('2026-02-10', 'YYYY/MM') // '2026/02'

Tests

• 35 new tests (19 DataScopeManager, 16 formula functions)
• All 136 test files pass (2749+ tests), zero regressions

Original prompt

On SPEC_COMPLIANCE_EVALUATION.md, 按照 SPEC_COMPLIANCE_EVALUATION.md
文件的要求，完成全部开发任务

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
objectui	Error		Feb 10, 2026 2:53pm
objectui-console	Ready	Preview, Comment	Feb 10, 2026 2:53pm
objectui-storybook	Canceled		Feb 10, 2026 2:53pm

[Copilot]

Pull request overview

Implements multiple P0–P2 spec-compliance gaps across core and several plugins, adding missing runtime capabilities (DataScope, formulas, validator registration) and replacing placeholder UI behaviors with real callback-driven integrations.

Changes:

• Added DataScopeManager (DataContext implementation) with filtering, read-only scopes, listeners, and exports/tests.
• Expanded formula engine with string-search, statistical functions, and DATEFORMAT + tests.
• Updated several plugins to wire real callbacks / data fetching paths (AI components, report viewer refresh & aggregations, detail/related list fetching, map coordinate validation).

Reviewed changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
packages/react/src/hooks/useTheme.ts	Adds a theme hook/context in hooks layer (currently duplicates existing theme context API).
packages/react/src/hooks/index.ts	Re-exports the new useTheme hook.
packages/plugin-report/src/ReportViewer.tsx	Adds onRefresh prop and aggregation helper for KPI cards.
packages/plugin-report/src/ReportBuilder.tsx	Ensures onCancel callback is invoked.
packages/plugin-map/src/ObjectMap.tsx	Filters invalid coordinates, counts exclusions, and displays a warning banner.
packages/plugin-detail/src/RelatedList.tsx	Adds DataSource integration and fetch fallback for related list data loading.
packages/plugin-detail/src/DetailView.tsx	Implements detail fetching (DataSource.findOne and fetch fallback) and passes dataSource to RelatedList.
packages/plugin-ai/src/NLQueryInput.tsx	Adds onSubmit callback prop and keeps simulated behavior when callback not provided.
packages/plugin-ai/src/AIRecommendations.tsx	Replaces console logs with onSelect/onDismiss callback props.
packages/plugin-ai/src/AIFormAssist.tsx	Replaces console logs with onApply/onRefresh callback props.
packages/core/src/validation/validation-engine.ts	Adds custom validator registration (sync/async) and resolves validators by rule.type.
packages/core/src/index.ts	Exports the new data-scope module from core.
packages/core/src/evaluator/tests/FormulaFunctions.test.ts	Adds tests for new string/stat/date functions.
packages/core/src/evaluator/FormulaFunctions.ts	Adds FIND/REPLACE/SUBSTRING/REGEX/LEN, MEDIAN/STDEV/VARIANCE/PERCENTILE, and DATEFORMAT.
packages/core/src/data-scope/index.ts	Public entrypoint for data-scope exports.
packages/core/src/data-scope/tests/DataScopeManager.test.ts	Adds DataScopeManager unit tests.
packages/core/src/data-scope/DataScopeManager.ts	Implements DataScopeManager with filters, read-only enforcement, and listeners.

Comments suppressed due to low confidence (1)

packages/plugin-map/src/ObjectMap.tsx:424

• This adds UI changes in the same area where the map container uses inline styles (style={{ ... }}), which is explicitly forbidden by repo conventions in .github/copilot-instructions.md:13-16. Please convert these to Tailwind classes (e.g., fixed height via h-* / min-h-* and w-full) and avoid passing style objects unless absolutely required by the library.

      <div className="relative border rounded-lg overflow-hidden bg-muted" style={{ height: '600px', width: '100%' }}>
         <Map
            initialViewState={initialViewState}
            style={{ width: '100%', height: '100%' }}

[Copilot]

When an external onSubmit handler is provided, the component still sets internal loading true and then immediately false, which can cause a spinner flicker and doesn’t actually wait for external work. Additionally, result is initialized from schema.result once and won’t update if the parent provides a new result after onSubmit; that makes the new callback integration hard to use. Consider deriving result from schema.result (controlled) or syncing state via useEffect and using schema.loading as the source of truth when onSubmitProp is provided.

[Copilot]

This component stores schema.suggestions into local state once (useState(initialSuggestions)) and never re-syncs when schema changes. With the new onRefresh callback, a parent is likely to update schema.suggestions, but the UI won’t reflect those updates. Consider rendering from schema.suggestions directly (controlled) or adding a useEffect to update local state when initialSuggestions changes; also consider making onRefresh async-aware instead of always clearing loading after a fixed timeout.

[Copilot]

DataSource.find() expects a resource name and returns a QueryResult with a required .data array (packages/types/src/data.ts). Passing api (a URL string) into dataSource.find() and then treating the result as either an array or { data } is incompatible with the DataSource contract and will break for standard DataSource implementations. Consider changing this to use a resource prop (or derive the resource from schema) and read result.data from the QueryResult.

[Copilot]

The fetch branch doesn’t check res.ok before calling res.json(), so non-2xx responses will be treated as successful JSON and may cause confusing runtime errors. Consider handling non-OK responses explicitly (e.g., throw with status/message) so the error state is accurate.

[Copilot]

The useEffect uses schema.data, dataSource, and schema.objectName in its logic, but the dependency array only includes schema.api and schema.resourceId. This can leave stale data/loading if dataSource or schema.data/objectName changes. Please include all referenced reactive inputs (or refactor) so the effect re-runs correctly.

Suggested change

	}, [schema.api, schema.resourceId]);
	}, [schema.api, schema.resourceId, schema.data, schema.objectName, dataSource]);

[Copilot]

Similar to RelatedList, this introduces a raw fetch() path inside a UI component. Project guidance prefers routing data access through the DataSource abstraction for backend-agnostic behavior and consistent auth/error handling (.github/copilot-instructions.md:183-185). Consider using a DataSource-based implementation (or injecting a RestDataSource) instead of calling fetch directly here.

[Copilot]

DATEFORMAT uses String.prototype.replace for each token, which only replaces the first occurrence. Formats that repeat tokens (e.g., 'YYYY/MM/DD HH:mm:ss [YYYY]') won’t be formatted correctly. Consider using a single global token-regex replacement or per-token global replacements so all occurrences are handled.

Suggested change

	return format
	.replace('YYYY', String(date.getFullYear()))
	.replace('YY', String(date.getFullYear()).slice(-2))
	.replace('MM', pad(date.getMonth() + 1))
	.replace('DD', pad(date.getDate()))
	.replace('HH', pad(date.getHours()))
	.replace('mm', pad(date.getMinutes()))
	.replace('ss', pad(date.getSeconds()));
	const tokenRegex = /YYYY|YY|MM|DD|HH|mm|ss/g;
	return format.replace(tokenRegex, (token) => {
	switch (token) {
	case 'YYYY':
	return String(date.getFullYear());
	case 'YY':
	return String(date.getFullYear()).slice(-2);
	case 'MM':
	return pad(date.getMonth() + 1);
	case 'DD':
	return pad(date.getDate());
	case 'HH':
	return pad(date.getHours());
	case 'mm':
	return pad(date.getMinutes());
	case 'ss':
	return pad(date.getSeconds());
	default:
	return token;
	}
	});

[Copilot]

This file introduces a new ThemeContext/useTheme that conflicts with the existing theme system in packages/react/src/context/ThemeContext.tsx (which already exports ThemeProvider + useTheme and throws when missing provider). Because packages/react/src/index.ts re-exports both './hooks' and './context', this will create duplicate/ambiguous exports (e.g., two different useTheme definitions) and inconsistent ThemeContextValue shapes. Consider removing this hook, or re-exporting the existing context hook instead of defining a second ThemeContext here.

Suggested change

	import { createContext, useContext } from 'react';
	import type { Theme, ThemeMode } from '@object-ui/types';
	/**
	* Theme context value for component-level theme access.
	*/
	export interface ThemeContextValue {
	/** Current active theme */
	theme: Theme | null;
	/** Current theme mode */
	mode: ThemeMode;
	/** Set the theme mode */
	setMode: (mode: ThemeMode) => void;
	/** Set a new theme */
	setTheme: (theme: Theme) => void;
	/** Get a resolved CSS variable value */
	getCssVar: (name: string) => string;
	}
	const defaultThemeContext: ThemeContextValue = {
	theme: null,
	mode: 'auto',
	setMode: () => {},
	setTheme: () => {},
	getCssVar: (name: string) => {
	if (typeof document !== 'undefined') {
	return getComputedStyle(document.documentElement).getPropertyValue(name).trim();
	}
	return '';
	},
	};
	export const ThemeContext = createContext<ThemeContextValue>(defaultThemeContext);
	ThemeContext.displayName = 'ThemeContext';
	/**
	* Hook for component-level theme access.
	*
	* Provides the current theme, mode, and utility functions
	* for reading and modifying theme state.
	*
	* @example
	* ```tsx
	* const { theme, mode, setMode, getCssVar } = useTheme();
	* const primaryColor = getCssVar('--primary');
	* ```
	*/
	export function useTheme(): ThemeContextValue {
	return useContext(ThemeContext);
	}
	// Re-export the canonical theme hook from the context theme system
	export { useTheme } from '../context/ThemeContext';

[Copilot]

Exporting useTheme from hooks here will collide with the existing useTheme export from packages/react/src/context/ThemeContext.tsx when consumers import from '@object-ui/react' (root index re-exports both hooks and context). This is likely to cause TS/ESM duplicate export errors or confusing API resolution. Prefer re-exporting only one useTheme (ideally from the existing ThemeProvider context).

Suggested change

export * from './useTheme';

[Copilot]

This component now performs raw fetch() calls as a fallback when no DataSource is provided. Repo guidance explicitly discourages using raw fetch in components and prefers going through the DataSource abstraction to remain backend-agnostic (.github/copilot-instructions.md:183-185). Consider requiring a DataSource prop (or providing a RestDataSource adapter) instead of embedding fetch logic here.

Suggested change

	dataSource.find(api).then((result) => {
	const items = Array.isArray(result)
	? result
	: Array.isArray((result as any)?.data)
	? (result as any).data
	: [];
	setRelatedData(items);
	setLoading(false);
	}).catch((err) => {
	console.error('Failed to fetch related data:', err);
	setLoading(false);
	});
	} else {
	fetch(api)
	.then(res => res.json())
	.then(result => {
	const items = Array.isArray(result) ? result : (result?.data || []);
	setRelatedData(items);
	})
	.catch(err => {
	console.error('Failed to fetch related data:', err);
	})
	.finally(() => setLoading(false));
	dataSource
	.find(api)
	.then((result) => {
	const items = Array.isArray(result)
	? result
	: Array.isArray((result as any)?.data)
	? (result as any).data
	: [];
	setRelatedData(items);
	setLoading(false);
	})
	.catch((err) => {
	console.error('Failed to fetch related data:', err);
	setLoading(false);
	});
	} else {
	console.error(
	'RelatedList: "api" was provided but no dataSource is available. Remote loading is disabled for this component.'
	);
	setLoading(false);