docs: rename to NAS Burn-In + version bump in spec/context

Catches the README, SPEC, and CLAUDE.md that were missed in the
1.0.0-38 product rename. Infrastructure identifiers (paths,
container, repo URL) deliberately stay as truenas-burnin.

Also refreshes SPEC.md version (1.0.0-8 → 1.0.0-39) and CLAUDE.md
last-updated stamp (1.0.0-12 → 1.0.0-39).
This commit is contained in:
Brandon Walter 2026-05-03 18:53:33 -05:00
parent 8033161efb
commit afe7d60f25
3 changed files with 6 additions and 6 deletions

View file

@ -1,7 +1,7 @@
# TrueNAS Burn-In Dashboard — Project Context
# NAS Burn-In Dashboard — Project Context
> Drop this file in any new Claude session to resume work with full context.
> Last updated: 2026-04-29 (v1.0.0-12 — live against TrueNAS SCALE 25.10)
> Last updated: 2026-05-03 (v1.0.0-39 — live against TrueNAS SCALE 25.10)
---

View file

@ -1,4 +1,4 @@
# TrueNAS Burn-In Dashboard
# NAS Burn-In Dashboard
Web dashboard for running disciplined burn-in tests on TrueNAS drives.
Sits next to the NAS, not on it — orchestrates `smartctl`, `badblocks`, and

View file

@ -1,6 +1,6 @@
# TrueNAS Burn-In — Project Specification
# NAS Burn-In — Project Specification
**Version:** 1.0.0-8
**Version:** 1.0.0-39
**Status:** Active Development
**Audience:** Public / Open Source
@ -8,7 +8,7 @@
## Overview
TrueNAS Burn-In is a self-hosted web dashboard that runs on a separate machine or VM and connects to a TrueNAS system via SSH to automate and monitor the drive burn-in process. It is designed for users who want to validate new hard drives before adding them to a ZFS pool — where reliability is non-negotiable.
NAS Burn-In is a self-hosted web dashboard that runs on a separate machine or VM and connects to a TrueNAS system via SSH to automate and monitor the drive burn-in process. It is designed for users who want to validate new hard drives before adding them to a ZFS pool — where reliability is non-negotiable.
The app is not a TrueNAS plugin and does not run on TrueNAS itself. It connects remotely over SSH to issue smartctl and badblocks commands, polls results, and presents everything through a dark-themed real-time dashboard. It is deployed via Docker Compose and configured through a Settings UI and `.env` file.