ahmido
3c3daae405
## Summary - introduce a shared operator outcome taxonomy with semantic axes, severity bands, and next-action policy - apply the taxonomy to operations, evidence/review completeness, baseline semantics, and restore semantics - harden badge rendering, tenant-safe filtering/search behavior, and operator-facing summary/notification wording - add the spec kit artifacts, reference documentation, and regression coverage for diagnostic-vs-primary state handling ## Testing - focused Pest coverage for taxonomy registry and badge guardrails - operations presentation and notification tests - evidence, baseline, restore, and tenant-scope regression tests ## Notes - Livewire v4.0+ compliance is preserved in the existing Filament v5 stack - panel provider registration remains unchanged in bootstrap/providers.php - no new globally searchable resource was added; adopted resources remain tenant-safe and out of global search where required - no new destructive action family was introduced; existing actions keep their current authorization and confirmation behavior - no new frontend asset strategy was introduced; existing deploy flow with filament:assets remains unchanged Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #186 |
||
|---|---|---|
| .. | ||
| memory | ||
| scripts/bash | ||
| templates | ||
| plan.md | ||
| README.md | ||
| research_t186.md | ||
| spec.md | ||
| tasks.md | ||
.specify/ (Tooling)
This folder contains SpecKit tooling (templates, scripts, constitution, etc.).
Important
- Do not create new feature specs in
.specify/spec.md,.specify/plan.md,.specify/tasks.md. - Active feature specs live under
specs/<NNN>-<slug>/:spec.mdplan.mdtasks.mdchecklists/requirements.md
The files .specify/spec.md, .specify/plan.md, .specify/tasks.md may exist as legacy references only.