Download the PHP package padosoft/eval-harness-ui without Composer
On this page you can find all versions of the php package padosoft/eval-harness-ui. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package eval-harness-ui
Eval Harness UI Admin
Package: padosoft/eval-harness-ui
Target stack: Laravel 13.x + PHP 8.3+
Purpose: Read-only admin panel for consuming padosoft/eval-harness report APIs.
eval-harness-ui is a host-driven SPA package that gives QA teams and ops teams a ready dashboard without touching the eval-harness backend repository.
Backend API repository: padosoft/eval-harness
Table of contents
- What this package gives you
- Screen list
- Why this package exists
- Architecture in plain words
- Runtime contract
- Production install (beginner-proof, copy/paste)
- Minimal security wiring
- Environment and config reference
- API mapping the UI expects
- Local development setup
- Release process (what is expected in PR flow)
- Constraints and behavior notes
- Roadmap (current status aligned with AGENTS docs)
- Contributing and support
- License
What this package gives you
- 7 operational screens shipped as a SPA
- Fast route-based admin integration in the host app
- Clear errors for
404,422,503response cases - English/Italian translations
- Accessibility checks integrated in CI (
seriousandcriticalgates) - Playwright e2e coverage for all major flows
- Zero API mutations: read-only by design
Screen list
- Dashboard
- Reports list
- Report detail
- Compare
- Trend
- Adversarial manifests
- Adversarial manifest details
- Live batches
Why this package exists
eval-harness can keep domain logic and API concerns.
This package adds only UI surfaces and route mounting for admin consumption.
- No internal
eval-harnessstorage or processing code is copied into this package. - No destructive/POST/PUT/PATCH/DELETE calls are part of this UI flow.
- Host app owns auth, tenancy, and policy decisions.
Architecture in plain words
Runtime contract
EVAL_HARNESS_UI_PREFIXdefines where the panel is mounted. Default:admin/eval-harness.EVAL_HARNESS_API_BASEdefines the host base path for report APIs. Default:/admin/eval-harness/api.- Optional tenant header is sent when needed:
X-Eval-Harness-Tenant. - Frontend reads bootstrap info (version/labels/version contract hints) from package endpoints.
Production install (beginner-proof, copy/paste)
1) Install the package
2) Publish package files
3) Configure environment
Add to your .env:
4) Clear caches and test route exposure
5) Open the UI
Navigate to http://your-app.test/admin/eval-harness.
If login is required, use a user that can pass eval-harness.viewer policy.
Minimal security wiring
This package does not define authorization policy defaults. You must define who can access these routes in your host app.
Example Gate setup
If you are not using policies, replace this with any Closure logic that matches your project auth model.
Environment and config reference
API mapping the UI expects
| Screen | Endpoint(s) |
|---|---|
| Dashboard | /reports, /batches/live, /adversarial/manifests, /datasets/{name}/trend?limit=30 |
| Reports list | /reports |
| Report detail | /reports/{id}, /reports/{id}/cohorts, /reports/{id}/histograms, /reports/{id}/rows.csv, /reports/{id}/download |
| Compare | /reports/{id}/diff/{otherId} |
| Trend | /datasets/{name}/trend |
| Adversarial | /adversarial/manifests, /adversarial/manifests/{name} |
| Live batches | /batches/live, /batches/{id}/progress |
Local development setup
Requirements
- PHP 8.3+ (
8.4recommended for CI parity) - Node.js 20+ (LTS)
- Composer and npm
- Laravel 13.x app shell
Install dependencies and run checks
If all commands are green, your local environment matches the repository quality gates.
Project structure (quick map)
src/: package service provider and route registration.config/: package config defaults.routes/web.php: mount entrypoint for the admin panel.resources/js/: React application source.resources/views/: Blade bootstrap template.tests/Featureandtests/Unit: backend regression tests.tests/e2e: Playwright and accessibility test suites.docs/: roadmap, progress and operating rules..github/: workflows and PR policy docs.
Release process (what is expected in PR flow)
- Implementa in branch
task/<macro>-.... - Apri PR per quel subtask.
- Esegui local gates e richiedi Copilot review.
- Merga nel macro branch dopo review e test pass.
- Merga in
mainsolo con CI verde e checklist completata. - Tagga e push per rilascio automatico.
release.yml in .github/workflows can create the GitHub release automatically if configured.
Constraints and behavior notes
- No mutation endpoints are required by this package.
- Schema compatibility is enforced when
schema_versionis expected and missing data is treated as legacy/empty state. - Large trend datasets may be rate-limited by host-side API limits and can return
503.
Roadmap (current status aligned with AGENTS docs)
- v0.1.0 completed with dashboard, reports, compare, trend, adversarial, and live batches.
- v0.2.0 planned for future release: chart unification and export reporting improvements.
- v0.3.0 planned for future release: runtime i18n switching and policy cache improvements.
- v0.4.0 planned for future release: richer release notes and host extension points.
Contributing and support
If you are joining as a junior contributor:
- Read
docs/PROGRESS.mdanddocs/PLAN.mdbefore touching code. - Follow the required tests before opening a PR.
- Keep modifications small and scoped.
- Respect hard anti-zombie server rules when running local checks (no dangling PHP/Vite/Node processes).
License
MIT