The Prisma schema is the single source of truth for the entire system
and should live in shared, not in development-specific location.
MOVED:
- /dbal/development/prisma/schema.prisma → /dbal/shared/prisma/schema.prisma
UPDATED:
- DBAL package.json: db:* scripts reference ../shared/prisma/schema.prisma
- config package.json: schema reference updated
- gen_prisma_schema.js: outputs to shared location
STRUCTURE NOW:
- /dbal/shared/prisma/ - Prisma schema (source of truth)
- /dbal/shared/seeds/ - Seed data (YAML files)
- /dbal/development/ - Uses shared schema via relative path
This ensures:
✅ Single source of truth for schema
✅ Schema is shared across all implementations (Phase 2 TypeScript, Phase 3 C++)
✅ Development just references the shared schema
✅ Independent deployability maintained
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
MOVED:
- /seed/ → /dbal/shared/seeds/
- database/ (installed_packages.yaml, package_permissions.yaml)
- config/ (bootstrap.yaml, package-repo.yaml)
- packages/ (core-packages.yaml)
- /prisma/schema.prisma → /dbal/development/prisma/schema.prisma
UPDATED:
- Root package.json: db:* scripts delegate to dbal/development
- Frontend package.json: db:* scripts delegate to dbal/development
- DBAL package.json: Added db:migrate and db:seed scripts
- /dbal/development/src/seeds/index.ts: Updated paths to new seed location
- /dbal/shared/tools/codegen/gen_prisma_schema.js: Output to new schema location
- /config/package.json: Updated schema path references
DELETED:
- /seed/ folder (moved to DBAL)
- /prisma/ folder (moved to DBAL)
BENEFITS:
- DBAL is now self-contained and independently deployable
- Single source of truth for seeds and schema
- Clear separation: database logic in DBAL, frontend in /frontends/
- All db:* commands now go through DBAL, not duplicated in frontend
This restructure is MANDATORY FIRST STEP before CODEBASE_RECOVERY_PLAN execution.
Architecture must be fixed before code cleanup happens.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Enable strict TypeScript mode in tsconfig.json
- Update ESLint rules to be stricter (error instead of warn)
- Implement useDBAL hook with fetch-based DBAL API
- Implement useKV hook with key-value store operations
- Implement use-mobile hook with media query detection
- Implement logout function with session clearing
- Add permission check comments in app/page.tsx
- Replace throwing stub in user$file with placeholder returns
- Complete entity-specific fields in generate-package.ts
- Add database operation templates in generate-package.ts
Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>
- Successfully organized all MetaBuilder documentation into a clear, hierarchical structure.
- Created new navigation files including a master index and a new contributor path.
- Updated existing documentation files to reflect the new structure.
- Reduced root-level clutter by organizing configuration files into dedicated directories.
- Added new configuration files for ESLint, Next.js, Playwright, and Vite.
- Created example schemas and size limits reports for better project insights.
- Removed deprecated Vite config backups to streamline the project.
