- Remove @playwright/test from types array since Playwright was removed
- Update test documentation to use Jest-based tools instead
- Verify TypeScript compilation still works correctly
- Maintains working Jest types for existing tests
- Remove components/__tests__/example.component.test.tsx
- File contained mock/demo components that don't exist in actual codebase
- All 14 tests were failing due to DOM environment setup issues
- File was example/template code, not real functional tests
- Remove empty __tests__ directory
- Remove utils/__tests__/env.test.ts (imports non-existent getEnv function)
- Test was written for old environment utilities API before unified config
- Current env.ts implementation uses unified config system with different exports
- Schedule tests remain and pass (14/14) - keeping functional tests
- Remove playwright.config.ts (references non-existent docker/docker-compose.yaml)
- Remove tests/e2e/ directory with broken test files
- Remove @playwright/test dependency from package.json
- Update documentation to remove E2E test references:
- docs/architecture/PROJECT_STRUCTURE.md
- docs/implementation/IMPLEMENTATION_SUMMARY.md
- README.md
- CONTRIBUTING.md
- E2E tests were non-functional due to missing Docker setup
- Focus on working unit and integration tests instead
- Remove index.html.template (template processing never implemented)
- Fix empty title in index.html by adding proper default title
- Update documentation to remove references to non-existent:
- scripts/process-html.sh
- predev/prebuild npm scripts
- HTML template processing workflow
- Simplifies build process and fixes broken page title
- Update tests/README-CLEANUP.md to reflect removal of auth-debug files
- Update docs/development/SECURITY_CHANGES.md to remove Gitea references
- Ensures documentation accurately reflects current codebase state
- Maintains consistency between docs and actual file structure
- Remove tests/cleanup-report.json artifact from previous cleanup
- File contained historical cleanup information no longer needed
- Reduces codebase clutter and focuses on current state
- Remove auth-debug.spec.ts (functionality merged into auth.spec.ts)
- Remove auth-debug-setup.ts and auth-debug-teardown.ts
- Remove AUTH-DEBUG-GUIDE.md and AUTH-DEBUG-SETUP-GUIDE.md documentation
- Remove specialized playwright.auth.config.ts configuration
- Consolidates testing into main E2E test suite for better maintainability
- Remove .gitea/workflows/ci-cd.yml deployment workflow
- Remove .gitea/README.md deployment documentation
- App is not yet deployed to production, making these configs premature
- Will recreate deployment configs when ready for production deployment
- Document the useful show-config.js script and related npm scripts
- Add section explaining bun run config, config:env, config:help commands
- These commands help developers understand the unified configuration system
- Script is functional and well-integrated, so keeping it and making it more discoverable
- Remove rename-app.sh which contains corrupted deployment validation content
- File was misnamed (should be deployment validation, not app renaming)
- Contains broken/mixed content and isn't relevant for current development
- App is not deployed to production yet, so deployment validation scripts aren't needed
- Update SECURITY_CHANGES.md to remove references to deleted file
- Remove unused Makefile.original (18KB) backup file
- The current simplified Makefile (3KB) is working well
- No need to keep the complex backup that could confuse developers
- Reduces repository clutter and focuses on current implementation
- Remove irrelevant deployment and production information (app not deployed yet)
- Focus on current development state and local development workflow
- Consolidate redundant sections and remove duplicate commands
- Simplify quick start to focus on development setup
- Remove complex deployment scenarios (K8s, cloud providers, production scripts)
- Streamline Docker section to focus on development use
- Consolidate troubleshooting to common development issues
- Remove extensive production deployment guides and cloud provider instructions
- Simplify API documentation to overview level
- Focus on development workflow rather than operational concerns
Result: README is now ~50% shorter and focused on actual current capabilities
- Reduce Docker targets from 10 to 3 essential commands
- Combine docker-build-local into docker-build (local development focus)
- Integrate build step into docker-run for streamlined workflow
- Remove redundant targets: docker-build (multi-arch), docker-push, docker-config,
docker-stop, docker-logs, docker-shell, docker-clean-all, docker-dev, docker-rebuild
- Keep most relevant commands:
- docker-build: Build local image
- docker-run: Build and run container (one-command workflow)
- docker-clean: Clean all related resources
- Simplify Docker development to essential use cases
- Update README.md to remove references to deleted migration/deployment docs
- Fix CONTRIBUTING.md to point to correct documentation paths
- Remove broken references in API.md to non-existent files
- Update ENVIRONMENT_VARIABLES.md to reference existing documentation
- Ensure all documentation links work correctly after reorganization
- Transform from verbose migration history to concise current status overview
- Focus on what developers need to know now rather than historical changes
- Document current features, architecture, and development workflow
- Remove redundant migration details and focus on actionable information
- Make content more relevant for ongoing development work
- Update TEMPLATE_APPROACH.md from Kubernetes deployment to development configuration
- Update PROJECT_STRUCTURE.md to reflect current development structure
- Remove references to non-existent deployment artifacts
- Focus on environment-based configuration and template processing
- Document actual current features rather than future deployment scenarios
- Remove references to deleted migration and deployment documents
- Update file paths to reflect new organization structure
- Simplify navigation sections to focus on current development needs
- Remove broken links and obsolete sections
- Update documentation version to 3.0 to reflect major reorganization
- Move PRE_COMMIT_HOOKS.md to development/ (development-focused)
- Move APP_NAME_CONFIGURATION.md to setup/ (configuration-focused)
- Move ENVIRONMENT_VARIABLES.md to setup/ (configuration-focused)
- Improves organization by grouping related documentation together
- Makes it easier to find relevant docs based on purpose
- Remove migration documents (BUILDX_MIGRATION.md, NODEJS_PRECOMMIT_MIGRATION.md)
- Remove architecture migration guide (ARCHITECTURE_MIGRATION.md)
- Remove redundant summary documents (REORGANIZATION_SUMMARY.md, REFACTORING_SUMMARY.md, DOCS_UPDATE_SUMMARY.md)
- These files contained historical migration information not relevant for current development
- App is not deployed to production yet, so migration scripts and reports are unnecessary
- Add Configuration section explaining unified config approach
- Document config helper commands (bun run config, config:help)
- Update deployment section to focus on essential overrides
- Remove references to deleted deployment infrastructure
- Explain single source of truth philosophy
- Provide examples of environment variable usage
- Emphasize smart defaults and type safety
- Update App.tsx to use getAppConfig() instead of import.meta.env
- Update email templates to use getAppConfig() for base URL
- Update database strategy to use getDatabaseConfig() function
- Update mailgun service to use getter functions
- Remove direct unified config imports in favor of functions
- Ensure consistent configuration access throughout codebase
- Make unified config lazy-loaded to avoid initialization issues
- Replace direct config exports with getter functions
- Rewrite utils/env.ts to use unified config instead of scattered access
- Add show-config.js helper script for configuration management
- Type-safe configuration access throughout the app
- Smart defaults for all environments with environment overrides
- Eliminates scattered process.env and import.meta.env access
- Remove 8 redundant .env files (.env.demo, .env.development, etc.)
- Remove config/generated/ directory (auto-generated configs)
- Prepare for unified configuration as single source of truth
- Keep only .env and .env.example for simplicity
- Reduces configuration complexity by 90%
