# Bugs Found

## BF-001: Laravel log contains historical application exceptions

- Severity: Low
- Module: Logging
- Reproduction: Inspect `storage/logs/laravel.log`.
- Expected: Recent log should be clean after audit.
- Actual: Log contains old parse/route errors from earlier development iterations.
- Root cause: Previous broken intermediate states were logged and not rotated.
- Fix: Current root causes were already fixed before this audit; local historical log was cleared during the follow-up cleanup.
- Test added: Existing full suite confirms current code path passes.
- Status: Resolved locally; production still needs log rotation/monitoring.

## BF-002: Composer is unavailable in PATH

- Severity: Low
- Module: Tooling
- Reproduction: Run `composer validate`.
- Expected: Composer validates `composer.json`.
- Actual: PowerShell reports `composer` is not recognized.
- Root cause: Composer executable is not installed or not on PATH for this environment.
- Fix: Not fixed in code; install Composer or add it to PATH.
- Test added: Not applicable.
- Status: Open environment issue.

## BF-003: Production readiness risks remain

- Severity: Medium
- Module: Production configuration
- Reproduction: Run `php artisan about` and inspect `.env.example`.
- Expected: Production deployment guidance should enforce debug off, secure cookies, configured queue/scheduler/storage.
- Actual: Local environment uses debug enabled; `.env.example` is local-development oriented.
- Root cause: Project is still configured as a local development CRM.
- Fix: Add production deployment checklist and production `.env` guidance before release.
- Test added: Not applicable.
- Status: Open.
