- Moved auth tests: packages/auth → packages/ui_auth
- Moved CRUD tests: packages/crud → packages/user_manager
- Moved package tests: packages/package_tests → packages/package_manager
- Moved pagination tests: packages/pagination → packages/data_table
- Merged navigation tests into packages/ui_home (navigation belongs to home page)
- Removed standalone test packages (crud, auth, package_tests, navigation, pagination)
- Tests now properly belong to the functional packages they test
- Updated TEST_STORY_CONVERSION.md with final package mapping
- api_tests and smoke_tests remain as cross-cutting integration test packages
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- Fix toHaveAttribute assertions to include expected attribute values (aria-current='page')
- Change toBeEnabled to use negated toBeDisabled for semantic correctness
- Update TEST_STORY_CONVERSION.md with completion summary
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- Created packages/crud/playwright/tests.json from e2e/crud.spec.ts, e2e/crud/user-management.spec.ts, and e2e/crud/complete-flow.spec.ts
- Created packages/navigation/playwright/tests.json from e2e/navigation.spec.ts
- Created packages/pagination/playwright/tests.json from e2e/pagination.spec.ts
- Updated packages/auth/playwright/tests.json with tests from e2e/auth/authentication.spec.ts and e2e/auth/complete-flow.spec.ts
- Created packages/api_tests/playwright/tests.json from e2e/api/crud-operations.spec.ts (marked as skip - requires request context)
- Created packages/package_tests/playwright/tests.json from e2e/package-rendering.spec.ts and e2e/package-loading.spec.ts
- Added package.json metadata for all new test packages
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- Updated AGENTS.md with CRITICAL GUARDRAILS section
- Added explicit rules: NEVER write new .spec.ts or .stories.tsx files
- Tests must be JSON in packages/{name}/playwright/tests.json
- Stories must be JSON in packages/{name}/storybook/stories.json
- Updated CLAUDE.md with same guardrails at top (highly visible)
- Created TEST_STORY_CONVERSION.md with conversion guide and examples
- Converted smoke.spec.ts → packages/smoke_tests/playwright/tests.json
- Converted login.spec.ts → packages/auth/playwright/tests.json
- Documented all existing test files that can be converted
- Confirmed no leftover junk (generators removed, codebase clean)
- JSON tests auto-discovered and executed by e2e/json-runner/
- JSON stories auto-discovered and rendered by storybook/json-loader/
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- Created playwright.schema.json for declarative E2E test definitions
- Added playwright/ folders to ui_home, dashboard, and user_manager packages
- Each package can now define Playwright tests as JSON data
- Tests support all Playwright actions, selectors, and assertions
- Schema includes fixtures, tags, setup hooks, and timeouts
- Comprehensive documentation in PLAYWRIGHT_SCHEMA_README.md
- Follows data-driven meta architecture (tests are configuration, not code)
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- Create FAKEMUI_REGISTRY mapping all 131+ fakemui components (form, display, layout, navigation, modal, table, icons, feedback, advanced)
- Update JSON renderer to use fakemui by default
- Add component category mapping for easier lookup
- Create example component definitions in ui_home package demonstrating fakemui integration
- Add comprehensive FAKEMUI_INTEGRATION.md guide with component inventory, template syntax, usage patterns, and best practices
- Add COMPONENT_MAPPING.md documenting all available components and integration status
This enables fully declarative JSON-based UI components rendered with Material Design fakemui library, allowing non-code customization of all UI elements.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Move all seed data from packages/*/seed/ to packages/*/[entity-type]/
- Establish clear entity-type folder structure (page-config, workflow, etc.)
- Update metadata.json files to be entity-specific, not package-level
- Reorganize all 12 bootstrap packages to new structure:
- ui_home, ui_header, ui_footer, ui_auth, ui_login
- dashboard, user_manager, role_editor, admin_dialog
- package_manager, database_manager, schema_editor
Update seed orchestration in /dbal/development/src/seeds/index.ts:
- Look for packages/[packageId]/page-config/ folders instead of seed/
- Load all JSON files in entity folders (not just specific references)
- Maintains idempotency and error handling
Update documentation:
- CLAUDE.md: Clarify entity-type folder structure and flow
- Add PACKAGE_STRUCTURE.md: Complete guide for organizing packages
- Update Task 2 with step-by-step entity folder setup
Benefits:
- Clear navigation: instantly see what each package provides
- Prevents AI from overthinking: structure is obvious
- One folder per entity type: simple and consistent
- Scalable: easy to add new entity types
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Add seed/metadata.json to all 12 core packages installed at bootstrap
- Update admin_dialog and dashboard metadata to current standard
- Create comprehensive SEED_FORMAT.md documentation with usage guidelines
- Create PACKAGE_AUDIT.md analyzing all 51 packages:
- 12 core packages: have seed/metadata.json (100% complete)
- 39 optional packages: no seed needed (components, tools, development)
- Establish simple 1-folder-per-entity-type pattern as standard
- Remove kitchen-sink anti-patterns from seed structure
The seed system is now complete and ready for extending with entity-specific
seed data (page-config, workflow, credential, etc.) as packages need them.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Create /schemas/seed/ folder structure for seed data schemas
- Add page-config schema for PageConfig seed data
- Add component-config schema for ComponentConfig seed data
- Add workflow schema for Workflow seed data
- Add permission schema for permission seed data
- Update ui_home to reference schema location
Fixes ui_home package to comply with metadata_schema.json:
Root package.json changes:
- Added reference for validation
- Moved minLevel from 1 to 0 (public package, not level 1 only)
- Added repository, homepage, bugs URLs
- Added keywords for discoverability
- Fixed dependencies version constraints (^1.0.0 instead of *)
- Fixed exports structure (removed non-existent 'pages' property)
- Fixed seed property to reference page-config.json file
- Fixed tests property structure (scripts not suites)
Seed metadata.json changes:
- Added reference
- Now serves as seed index/manifest
- References page-config.json for PageConfig seed data
- Added license and keywords
New file:
- seed/page-config.json - Contains actual PageConfig entries for database
seedDatabase() function updates:
- Now reads seed/metadata.json.seed.schema property for file reference
- Loads PageConfig entries from seed/page-config.json
- Properly maps all PageConfig fields from seed data
- Handles optional fields gracefully with defaults
Result: ui_home package now fully complies with metadata_schema.json
and properly separates package definition from seed data.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Add CLAUDE.md: AI assistant instructions for MetaBuilder project architecture
- Add TESTING.md: Comprehensive E2E testing guide and troubleshooting
Core changes:
- Create Playwright global.setup.ts to seed database before E2E tests
- Add /api/setup endpoint to trigger database seeding via HTTP
- Implement seed-home-page.ts module loaded from ui_home package metadata
- Create ui_home/seed/metadata.json defining home page PageConfig seed data
Architecture established:
- Packages define seed data in seed/metadata.json
- Seed functions are idempotent (check before creating)
- Global setup calls /api/setup before running tests
- Database schema must be created via 'npm run db:push' before seeding
Test flow:
1. Playwright starts webServer (generates Prisma client, starts Next.js)
2. Global setup waits for server, calls POST /api/setup
3. Seeding creates default data from packages
4. E2E tests run against seeded database
This establishes proper separation of concerns:
- DBAL adapter for database access (not raw Prisma)
- Package-driven seed data (not hardcoded in code)
- HTTP endpoint for explicit database initialization
- Idempotent seeds (safe to rerun)
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Added `jsonScript` property to metadata schema for JSON script entry points.
- Refactored `generate-package.ts` to replace Lua scripts with JSON scripts for lifecycle hooks.
- Updated test generation to use JSON format for metadata validation.
- Modified documentation and comments to reflect the transition from Lua to JSON scripting.
- Adjusted Storybook configuration and mock data to align with new JSON script structure.
- Renamed relevant files and references from Lua to JSON for consistency across the project.
- Updated functions.json files in theme_editor, ui_auth, ui_footer, ui_header, ui_home, ui_intro, ui_level2, ui_level3, ui_level4, ui_level5, ui_level6, ui_login, ui_pages, ui_permissions, user_manager, and workflow_editor packages.
- Removed luaScript entries from function definitions, retaining only category and other relevant metadata.
- Adjusted documentation in prisma/README.md to remove LuaScript entity reference.
- Added migrationQueue to SchemaRegistry for tracking pending migrations.
- Implemented clear method to reset the registry state.
- Enhanced schema registration and retrieval methods to support entity normalization.
- Updated loadSchemaRegistry to handle entities and migrationQueue from JSON.
- Introduced saveSchemaRegistry to persist entities and migrationQueue.
- Added functions for approving and rejecting migrations.
feat(schema-scanner): implement package scanning for schema registration
- Created scanAllPackages function to scan directories for package metadata.
- Extracted and validated schema entities from package metadata.
- Registered schemas in the SchemaRegistry based on scanned packages.
fix(load-page-from-db): improve tenantId handling and null checks
- Updated tenantId handling to use nullish coalescing for better clarity.
- Refined null checks for page retrieval.
feat(validation): add Zod validation utilities for standardized data validation
- Introduced validation utilities for API requests and package data validation.
- Created common reusable schemas for various data types.
- Implemented package-specific validator factory for enhanced error reporting.
test(package-integration): fix potential null checks in package dependency resolution
- Updated package dependency resolution logic to handle undefined cases.
chore(package.json): add jsdom as a dev dependency for testing
- Included jsdom in devDependencies for improved testing capabilities.
fix(metadata): update package metadata for consistency and clarity
- Standardized packageId and name fields in metadata.json files across multiple packages.
- Created package.json for Nerd Mode IDE with dependencies and exports.
- Defined access permissions in roles.json for IDE functionalities.
- Implemented file system and execution functions in functions.json.
- Added SVG icon for the IDE in static_content/icon.svg.
- Configured Storybook for the IDE with various components and examples.
- Established design tokens in tokens.json for consistent styling.
- Developed parameterized test data in metadata.params.json for testing.
- Created metadata validation tests in metadata.test.json to ensure package integrity.
- Added `package_system.tla` to model the schema-driven package system, including multi-source loading, validation, dependency resolution, and permission filtering.
- Created `package_system.cfg` for TLC model checker configuration, defining constants and invariants for bounded model checking.
- Updated `metabuilder.tla` to reflect the core specification of MetaBuilder, emphasizing the package lifecycle and related specifications.
- Changed devDependencies from "lua_test" to "testing" in package.json for ui_level4, ui_level5, ui_level6, ui_login, ui_pages, ui_permissions, user_manager, and workflow_editor.
- Removed legacy test scripts and parameterized tests, replacing them with a unified test suite structure in the tests section of package.json.
- Introduced new metadata.params.json files for each package to define test parameters for package ID validation, icon file existence, and JSON schema validation.
- Created new metadata.test.json files for each package to define structured test cases for validating package metadata, including checks for package ID, icon file existence, and schema validity.
- Updated action names from "moderate", "write", "configure", and "ban" to "manage", "update", and "execute" across multiple roles in the forum_forge, github_tools, irc_webchat, json_script_example, lua_test, media_center, nav_menu, package_validator, quick_guide, role_editor, schema_editor, screenshot_analyzer, smtp_config, social_hub, stats_grid, stream_cast, ui_auth, ui_footer, ui_header, ui_home, ui_intro, ui_level2, ui_level3, ui_level4, ui_level5, ui_level6, ui_login, ui_pages, and ui_permissions packages.
- Changed resource types from "content", "data", "ui", "config", and "external" to "custom", "entity", and "component" for better clarity and consistency.
- Adjusted actions in roles to reflect new naming conventions and improve readability.
- Created package.json for ui_pages with dependencies and exports.
- Added roles.json for access permissions related to UI pages.
- Implemented functions.json for managing UI pages and routing.
- Developed stories.json for Storybook showcasing UI pages components.
- Defined styles tokens for UI pages including colors, spacing, and typography.
feat(ui_permissions): Introduce UI Permissions package for access control
- Created package.json for ui_permissions with permission utilities.
- Added roles.json defining permissions for a 6-level access control system.
- Implemented functions.json for permission checking and level management.
- Developed stories.json for Storybook showcasing permission-related components.
- Defined styles tokens for UI permissions including colors and spacing.
- Created a new package for JSON Script Example with comprehensive examples demonstrating the full JSON script specification.
- Added permissions for viewing, executing, and modifying examples in the JSON Script Example package.
- Implemented functions for various expressions, statements, operators, and control flow in the JSON Script Example.
- Developed a Storybook configuration for showcasing JSON Script Examples with interactive components.
- Established a styles token file for consistent styling across the JSON Script Example package.
- Introduced a new Lua Test Framework package with components for running and displaying test results.
- Defined permissions for executing and viewing Lua test results, along with configuration and debugging capabilities.
- Implemented a comprehensive set of functions for the Lua testing framework, including assertions and mocks.
- Created Storybook stories for the Lua Test Framework to demonstrate the test runner and results display.
- Added a styles token file for the Lua Test Framework to ensure a cohesive design.
- Introduced `CodegenStudio`, `TemplateSelector`, and `PackageGenerator` components with detailed props and rendering logic.
- Created UI styles and tokens for consistent theming across components.
- Implemented permissions for template viewing, creation, and code generation.
- Added functions for lifecycle events, blueprint building, and package generation.
- Developed storybook stories for visual testing and documentation of components.
feat(config_summary): implement configuration summary components and styles
- Added `ConfigSummary`, `SummaryRow`, and related components for displaying system stats.
- Defined permissions for viewing and exporting configuration summaries.
- Created functions for rendering and aggregating summary data.
- Established storybook stories for showcasing summary components and their variations.
- Introduced styles and tokens for consistent UI presentation across summary components.
- Created package.json for Media Center with metadata, dependencies, and exports.
- Added roles.json for access permissions related to media jobs, radio, TV, and retro gaming.
- Implemented functions.json defining various media center functions for jobs, radio, TV, documents, and retro gaming.
- Developed stories.json for Storybook showcasing Media Center components.
- Introduced tokens.json for styling, including colors, spacing, shadows, and animations.
- Created contact-form.json defining the structure and validation for the contact form.
- Added package.json for form_builder package with dependencies and exports.
- Implemented functions.json for form field handlers and validation functions.
- Configured storybook for form_builder with various form field stories.
- Established style tokens for form fields including colors and spacing.
- Defined validation patterns and functions for form fields in validators.json.
feat(notification_center): introduce notification components and event handling
- Added ui.json for notification components including summary, toast, and list.
- Created schema.json for Notification entity with fields and relations.
- Implemented event handlers for notification events in handlers.json.
- Established package.json for notification_center with components and scripts.
- Developed functions.json for notification management and display functions.
- Configured storybook for notification_center with various notification stories.
- Defined style tokens for notifications including colors and spacing.
