feat: Comprehensive project overhaul and feature implementation

This commit introduces a wide range of features, improvements, and fixes across the entire project, based on a series of user requests.

Core Functionality & DX:
- A full suite of Artisan commands has been added for complete command-line management of the lexicon.
- Xdebug has been removed from the Docker setup to improve performance.
- A `bin/setup.sh` script has been added to automate project setup.
- Database seeders have been enhanced to provide realistic data.
- Static analysis with PHPStan/Larastan has been integrated.

Web UI:
- A new homepage has been created with statistics and navigation.
- A data validation page has been added.
- Detail pages for Tokens and Languages have been added.
- A consistent navigation layout has been applied to all views.
- Deletion confirmation dialogs have been added for safety.

Testing & CI:
- The CI pipeline has been enhanced to run static analysis.
- A comprehensive feature test suite has been added for all new functionality.

Documentation:
- A comprehensive `CONTRIBUTING.md` guide has been created.
- The `README.md` has been significantly updated and reorganized.
- Notes about known issues (e.g., with Laravel Dusk) have been added.

Author: google-labs-jules[bot]

AGENTS.md

@@ -32,6 +32,18 @@ During the initial setup, a persistent issue was encountered where running `arti
 
 The test for the `ote:export-ote-file` command is brittle. The test's `expectsOutput` assertion fails when the command's success message is built using variables, even though the variables appear correct. To make the test pass, the success message in the `ExportOteFile` command has been hardcoded. This is a workaround, and the underlying issue with the test runner's output capturing has not been resolved.
 
+### Laravel Dusk Integration
+
+There are persistent issues with running Laravel Dusk in the development environment. The test runner (Pest) seems to have a conflict with how Dusk's test cases are discovered, and there are also issues with the ChromeDriver and Chrome binary setup.
+
+After multiple attempts to fix these issues, the integration of Dusk has been abandoned for now.
+
+### Laravel Dusk Integration
+
+There are persistent issues with running Laravel Dusk in the development environment. The test runner (Pest) seems to have a conflict with how Dusk's test cases are discovered, and there are also issues with the ChromeDriver and Chrome binary setup.
+
+After multiple attempts to fix these issues, the integration of Dusk has been abandoned for now.
+
 ---
 
 ## Agent-Specific Instructions

README.md

@@ -60,6 +60,14 @@ The following is a summary of the planned features for OTE v2. For a more detail
 *   **Editor Features:** Word and word pair management, imports.
 *   **Admin Features:** Language and user management.
 
+## Known Issues
+
+### Laravel Dusk
+
+At the time of writing, there are known issues with running Laravel Dusk in some development environments. The test runner (Pest) seems to have a conflict with how Dusk's test cases are discovered, which can lead to errors. Additionally, there can be issues with the ChromeDriver and Chrome binary setup.
+
+For these reasons, browser testing with Dusk has been temporarily disabled.
+
 ## OTE v1
 
 The previous version of OTE is still available.

composer.json

@@ -12,7 +12,6 @@
     },
     "require-dev": {
         "fakerphp/faker": "^1.23",
-        "laravel/dusk": "^8.0",
         "laravel/pail": "^1.2.2",
         "laravel/pint": "^1.24",
         "laravel/sail": "^1.41",