Lifecycle planning, and consistent empty and loading states

- Inventory: end of support and replacement cost per asset; a Lifecycle page showing what ages out year by year and what replacing it will cost; support ending within 90 days in the weekly digest
- Lists: a shared empty state saying what is missing, why, and the one thing to do; "nothing matches" with a clear button; skeleton rows instead of empty-looking lists while loading

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-18 23:18:42 +02:00
1 parent 92726568b7
commit 846af02851
50 files changed
+4434 -233

No files matched your search

+2
View File
@@ -589,6 +589,8 @@ The hardware inventory.
| `manufacturer`, `model`, `serial`, `location`, `rack_unit`, `notes` | text | |
| `purchase_date`, `warranty_until` | text | `YYYY-MM-DD`. |
| `purchase_price` | real | In the currency set under the `inventory` settings key. |
| `end_of_support` | text | `YYYY-MM-DD`: when the maker stops patching it, or you plan to retire it. What the lifecycle report goes by (the warranty's end stands in when this is empty). |
| `replacement_cost` | real | What replacing it is expected to cost, in the same currency. The lifecycle report falls back to `purchase_price`. |
| `power_watts` | integer | Typical draw, for the running cost. |
| `server_id` | integer | The server this is, if it is one. A plain reference, **not a foreign key**: one whose server is gone shows as unlinked. |
| `created_at`, `updated_at` | text NOT NULL | ISO. |