# Spec 391 Verification Notes

## Preparation Status

- Created: 2026-06-20.
- Initial branch before Spec Kit script: `platform-dev`.
- Initial latest commit: `c0c3286a feat: add restore readiness resolution adapter improvements (#461)`.
- Initial `git status --short`: clean.
- Spec Kit branch after script: `391-operations-hub-stability-debug-safe-runtime`.
- Preparation only: no application implementation, tests, migrations, seeders, provider syncs, restore jobs, exports, deletes, archives, notifications, or destructive commands were run.
- Implementation start branch: `391-operations-hub-stability-debug-safe-runtime`.
- Implementation start latest commit: `c0c3286a feat: add restore readiness resolution adapter improvements (#461)`.
- Implementation start `git status --short --branch`: branch plus untracked `specs/391-operations-hub-stability-debug-safe-runtime/`.

## Audit Evidence Source

- BUG-001: `specs/browser-productization-bug-audit/browser-bug-report.md`.
- BUG-009: `specs/browser-productization-bug-audit/browser-bug-report.md`.
- Known audited route: `http://localhost/admin/workspaces/3/operations?environment_id=4`.
- Observed audit failure: HTTP 500/timeout/debug page with `Maximum execution time of 30 seconds exceeded`.
- Observed runtime leakage: missing Filament globals, Vite dev-client failures, Debugbar requests/source links, and `phpstorm://open` links.
- Latest Laravel error inspected before implementation still showed `Maximum execution time of 30 seconds exceeded` at `Illuminate\Database\Eloquent\Concerns\HasAttributes.php:1577`.

## Root Cause

- `Operations::topOperationFromQuery()` selected up to 50 full `OperationRun` models, eager-loaded `tenant`, hydrated JSON-cast attributes, then sorted in PHP with `problemClass()`/freshness-derived accessors.
- `OperationRunResource` type and initiator filter options were workspace-only scans and did not narrow on the durable `environment_id` route prefilter.
- The fix selects one bounded workbench candidate in SQL priority order, hydrates only that selected run for presentation, and bounds filter option scans to workspace entitlement plus the requested `environment_id` where present.

## Implementation Verification

| Check | Result |
|---|---|
| Route checked | Generated canonical `/admin/workspaces/{workspace}/operations?environment_id={environment}` with safe fixture ids |
| HTTP status | 200 in feature request and browser smoke |
| Browser render time after authentication | Browser smoke command duration 4.79s / 5.54s including test harness; deterministic feature guard asserts bounded SQL candidate query instead of a hard browser threshold |
| Page title/header | `Operations Hub` visible |
| Visible table/empty state | Seeded table renders `Inventory sync`; no-run environment renders controlled `No operations need follow-up` and `No operations found` states |
| Workspace/environment context | `Environment filter: Spec391 ... Environment` visible and canonical `environment_id` query present |
| Console errors | `assertNoJavaScriptErrors()` and `assertNoConsoleLogs()` passed in browser smoke |
| Network 500s | Operations route returned 200; no direct Pest Browser network log assertion available in this harness |
| Laravel debug page visible | Not visible in feature/browser assertions |
| Stack trace / `Maximum execution time` visible | Not visible in feature/browser assertions |
| Debugbar/source-link leakage in productization-smoke mode | `_debugbar`, `phpstorm://`, source-link/debug signatures not visible; smoke session uses `SuppressDebugbarForSmokeRequests` |
| Missing Filament globals | `window.Livewire` and `window.Alpine` present; `filamentSchema is not defined` not visible; no JS/console errors |
| Vite dev-client failure in productization-smoke mode | No console errors/logs in browser smoke; `PanelThemeAsset` behavior unchanged |
| Safe OperationRun detail action | Existing Operations link tests still pass; Spec 391 render test asserts canonical Operations URL and bounded detail/action surface remains available through existing table behavior |
| Provider mutations / restore jobs / exports / deletes / archives / notifications | None executed |
| Screenshot artifact | Browser test asserts `apps/platform/tests/Browser/Screenshots/spec391-operations-hub-stability.png`; spec artifact copy is stored at `specs/391-operations-hub-stability-debug-safe-runtime/artifacts/screenshots/spec391-operations-hub-stability.png` |

## Commands Run

```bash
cd apps/platform && ./vendor/bin/sail php -l app/Filament/Pages/Monitoring/Operations.php
cd apps/platform && ./vendor/bin/sail php -l app/Filament/Resources/OperationRunResource.php
cd apps/platform && ./vendor/bin/sail php -l tests/Feature/Monitoring/Spec391OperationsHubStabilityTest.php
cd apps/platform && ./vendor/bin/sail php -l tests/Browser/Spec391OperationsHubStabilitySmokeTest.php
cd apps/platform && ./vendor/bin/sail artisan test tests/Feature/Monitoring/Spec391OperationsHubStabilityTest.php
cd apps/platform && ./vendor/bin/sail artisan test tests/Browser/Spec391OperationsHubStabilitySmokeTest.php
cd apps/platform && ./vendor/bin/sail artisan test tests/Feature/Monitoring/OperationsHubProductizationTest.php tests/Feature/Monitoring/OperationsTenantScopeTest.php tests/Feature/Filament/OperationRunListFiltersTest.php
cd apps/platform && ./vendor/bin/sail pint app/Filament/Pages/Monitoring/Operations.php app/Filament/Resources/OperationRunResource.php tests/Feature/Monitoring/Spec391OperationsHubStabilityTest.php tests/Browser/Spec391OperationsHubStabilitySmokeTest.php
git diff --check
```

## Final Command Results

- `Spec391OperationsHubStabilityTest`: 4 passed, 46 assertions.
- `Spec391OperationsHubStabilitySmokeTest`: 1 passed, 17 assertions.
- Adjacent feature suite (`OperationsHubProductizationTest`, `OperationsTenantScopeTest`, `OperationRunListFiltersTest`): 25 passed, 234 assertions.
- `pint`: PASS, 4 files.
- `git diff --check`: PASS.

## Changed Files

- `apps/platform/app/Filament/Pages/Monitoring/Operations.php`
- `apps/platform/app/Filament/Resources/OperationRunResource.php`
- `apps/platform/tests/Feature/Monitoring/Spec391OperationsHubStabilityTest.php`
- `apps/platform/tests/Browser/Spec391OperationsHubStabilitySmokeTest.php`
- `specs/391-operations-hub-stability-debug-safe-runtime/tasks.md`
- `specs/391-operations-hub-stability-debug-safe-runtime/artifacts/verification.md`
- `specs/391-operations-hub-stability-debug-safe-runtime/artifacts/screenshots/spec391-operations-hub-stability.png`

## Final Git Status

```text
## 391-operations-hub-stability-debug-safe-runtime
 M apps/platform/app/Filament/Pages/Monitoring/Operations.php
 M apps/platform/app/Filament/Resources/OperationRunResource.php
?? apps/platform/tests/Browser/Spec391OperationsHubStabilitySmokeTest.php
?? apps/platform/tests/Feature/Monitoring/Spec391OperationsHubStabilityTest.php
?? specs/391-operations-hub-stability-debug-safe-runtime/
```

## Safety Confirmation

- No migrations, seeders, provider syncs, provider mutations, restore jobs, exports, deletes, archives, force-deletes, notifications, customer-facing delivery actions, or destructive commands were executed.
- No PHP `max_execution_time` increase.
- No new persisted entity, enum/status family, operation type, summary-count key, lifecycle semantic, cache layer, provider registration, panel path, or global-search posture change.
- Filament v5 / Livewire v4.0+ compliance preserved; no Livewire v3 or Filament legacy APIs introduced.
- Panel provider registration remains `apps/platform/bootstrap/providers.php`.
- `OperationRunResource` remains non-globally-searchable.

## Known Limitations

- The browser test runs inside Sail with the repo mounted read-only at `/var/www/repo`, so it validates the generated Pest Browser screenshot under `apps/platform/tests/Browser/Screenshots/` instead of attempting an unreliable write into repo-level `specs/`. The spec artifact screenshot was copied from that generated browser screenshot on the host side.
- Pest Browser in this harness was used for DOM, JS, and console assertions; direct network-request introspection was not available, so route 200 plus absence of explicit debug/source-link signatures is the recorded network-adjacent proof.