feat: show storage usage and restart traffic

- Report mount-aware state and database-root capacity with role
  assignments
- Separate role allocation from PostgreSQL and Redis-compatible live
  usage
- Restart only Traefik and wait for container health after confirmation

Author: evannotfound

openspec/changes/archive/2026-08-21-show-storage-and-restart-traffic/.openspec.yaml

@@ -0,0 +1,2 @@
+schema: spec-driven
+created: 2026-08-21

openspec/changes/archive/2026-08-21-show-storage-and-restart-traffic/design.md

@@ -0,0 +1,74 @@
+## Context
+
+`status._host()` currently measures only free space for `Paths.state`, even though configuration now
+contains an ordered `Host.data_roots` catalog and every role selects one root. The guided Host choice is
+a read-only screen, while database roles already have lifecycle actions. `database.info()` knows the role
+data path and delegates live facts to concrete engine modules, but it does not measure directory usage or
+engine-native data totals.
+
+## Goals / Non-Goals
+
+**Goals:**
+
+- Identify every managed storage path and the filesystem that currently backs it.
+- Keep frequent root-menu status checks bounded while providing richer on-demand database details.
+- Report physical role storage separately from engine-native logical or in-memory data.
+- Provide one deliberate guided action that actually restarts Traefik and verifies its health.
+
+**Non-Goals:**
+
+- No expected-device configuration, mount creation, mount repair, or startup ordering.
+- No per-table, per-key, or per-logical-database breakdown.
+- No direct host restart command or change to database lifecycle behavior.
+- No storage quotas, cleanup, forecasting, or background metric collection.
+
+## Decisions
+
+### Read the current Linux mount table and retain separate storage concepts
+
+Host assessment reads `/proc/self/mountinfo`, decodes its escaped fields, and selects the longest mount
+point containing each managed path. It reports mount point, source, filesystem type, and
+`shutil.disk_usage()` capacity without exposing mount options. The canonical state path remains
+`host.storage`; an additive `host.database_storage` list contains one item per configured root plus exact
+role assignments. Existing structured status fields remain present, so the status version does not
+change. Host health includes every configured storage location, and failures remain partial and
+path-specific.
+
+Using only the configured path was rejected because it cannot reveal that an intended custom mount is
+currently backed by `/`. Calling `findmnt` was rejected because the kernel mount table provides the
+required facts without adding another host tool dependency.
+
+### Measure role files only in database Details
+
+Database Details recursively sums allocated blocks under the selected role's data directory without
+following symlinks. It combines that value with the same backing-filesystem facts used by host status.
+The root menu does not scan role trees, because a large PostgreSQL data directory could make every guided
+refresh slow.
+
+Filesystem allocation and engine data are labeled separately. PostgreSQL reports the sum of
+`pg_database_size` for connectable non-template databases and their count. Redis and Dragonfly report
+dataset memory and total keys from `INFO memory` and `INFO keyspace`. A stopped role still reports path,
+directory allocation, and filesystem capacity while explicitly marking live data unavailable.
+
+### Restart only the installed Traefik service
+
+The Host submenu presents Restart traffic, warns that active database connections may briefly drop, and
+requires confirmation. The host operation takes the exclusive host lock, requires the installed Traefik
+Compose file, invokes `docker compose restart traefik`, and polls the owned container's health within the
+existing health timeout. It does not render files, run initialization, renew certificates, or touch
+database Compose projects.
+
+A Compose `up` was rejected because an unchanged service may not restart. Full initialization was
+rejected because it performs unrelated DNS, certificate, repository, and systemd convergence.
+
+## Risks / Trade-offs
+
+- [Two configured paths use the same filesystem] -> Show both exact paths and assignments; repeated
+  capacity values truthfully describe their shared backing filesystem.
+- [A configured mount is absent] -> Show the actual fallback mount and source; evdb does not infer the
+  intended device or repair it.
+- [A role contains many files] -> Restrict recursive allocation measurement to an explicit Details view.
+- [Live engine metrics fail] -> Preserve filesystem facts and report live data unavailable with a bounded
+  error instead of hiding the rest of Details.
+- [Traefik restart interrupts clients] -> Require confirmation, restart only Traefik, and wait for health
+  before reporting completion.

openspec/changes/archive/2026-08-21-show-storage-and-restart-traffic/proposal.md

@@ -0,0 +1,37 @@
+## Why
+
+Host details currently report only free space under `/var/lib/evdb`, hiding configured database roots and
+the filesystem that actually backs each path. Operators also cannot restart the dedicated Traefik traffic
+proxy from the guided Host section or see how much disk and live data one database role uses.
+
+## What Changes
+
+- Show state storage and every configured database root with its exact path, backing mount and source,
+  filesystem type, used/total/free capacity, and assigned database roles.
+- Show each database role's allocated directory size and backing filesystem in Details without scanning
+  every database during routine host status refreshes.
+- Show live PostgreSQL logical size and database count, or Redis/Dragonfly dataset memory and key count;
+  retain filesystem facts and identify live data as unavailable when a role is stopped.
+- Add a confirmed Restart traffic action under Host that performs a real Traefik Compose restart, warns
+  about a brief connection interruption, and waits for Traefik health without restarting databases or
+  rerunning initialization.
+
+## Capabilities
+
+### New Capabilities
+
+None.
+
+### Modified Capabilities
+
+- `jobs`: Expand host status from canonical state storage to mount-aware state and database-root storage.
+- `operator-cli`: Add the guided Host traffic action and storage presentation behavior.
+- `http`: Expand detailed database information with physical and engine-native data usage.
+- `deploy`: Define the dedicated proxy restart operation and its health requirement.
+
+## Impact
+
+The change affects host and database status collection, terminal rendering, Traefik Compose lifecycle
+helpers, PostgreSQL and Redis-compatible engine information, and focused unit tests. Structured status
+gains additive credential-free storage fields; no runtime dependency, direct CLI command, database
+restart, configuration schema, or backup format changes.

openspec/changes/archive/2026-08-21-show-storage-and-restart-traffic/specs/deploy/spec.md

@@ -0,0 +1,15 @@
+## ADDED Requirements
+
+### Requirement: Dedicated traffic proxy restart
+The guided Host interface SHALL provide a confirmed Restart traffic operation that takes the exclusive
+host operation lock, restarts only the installed Traefik Compose service, and waits for the owned Traefik
+container to become healthy within the host health timeout. It SHALL preserve source, generated files,
+database services, database data, credentials, and certificate state and SHALL NOT rerun initialization.
+
+#### Scenario: Traffic restart succeeds
+- **WHEN** the operator confirms Restart traffic and Traefik becomes healthy
+- **THEN** evdb reports completion without restarting any database Compose project
+
+#### Scenario: Traffic restart remains unhealthy
+- **WHEN** Traefik does not become healthy before the timeout
+- **THEN** evdb reports the failed host operation and does not claim that traffic restart completed

openspec/changes/archive/2026-08-21-show-storage-and-restart-traffic/specs/http/spec.md

@@ -0,0 +1,18 @@
+## MODIFIED Requirements
+
+### Requirement: Detailed database view
+`evdb database info PROJECT/ROLE` SHALL display configured role and concrete engine, live image version
+and health, data and Compose paths, latest backup summary, native connection fields, and HTTP fields when
+enabled. Details SHALL show the data directory's allocated bytes and backing filesystem capacity, mount,
+source, and type. A running PostgreSQL role SHALL show total logical database bytes and connectable
+database count; a running Redis or Dragonfly role SHALL show dataset memory bytes and total key count.
+The command SHALL deliberately retrieve credentials from private host files and print them only to the
+terminal.
+
+#### Scenario: Running database is shown
+- **WHEN** the selected role is running
+- **THEN** info distinguishes allocated directory storage from engine-native data size and count
+
+#### Scenario: Stopped database is shown
+- **WHEN** the selected role is configured but stopped
+- **THEN** info still shows settings, storage and connection details, clearly identifies stopped state, and marks live data unavailable

openspec/changes/archive/2026-08-21-show-storage-and-restart-traffic/specs/jobs/spec.md

@@ -0,0 +1,37 @@
+## MODIFIED Requirements
+
+### Requirement: Host status
+Status SHALL include host identity, running evdb version, Traefik and network health, native listeners,
+one backup timer state, repository availability, source validation, and storage assessment. Storage SHALL
+cover `/var/lib/evdb` and every configured database root with exact path, backing mount point and source,
+filesystem type, used/total/free capacity, and assigned project/roles. It SHALL NOT assess machine-state
+compatibility, tool-version match, generated contract hashes, transaction directories, restore state, or
+maintenance timers.
+
+#### Scenario: Disk space is below policy
+- **WHEN** free space for state storage or a configured database root is below the configured minimum
+- **THEN** host status identifies the affected path and backing filesystem and marks the host unhealthy
+
+#### Scenario: Several database roots are configured
+- **WHEN** roles select database roots backed by different mounted filesystems
+- **THEN** host details show every root, its actual mount facts and capacity, and the roles assigned to it
+
+#### Scenario: Backup timer is inactive
+- **WHEN** the one packaged backup timer is not loaded, enabled, and active
+- **THEN** host details report the inactive timer without listing per-database unit names
+
+### Requirement: Structured status output
+`evdb status --json` SHALL emit one credential-free JSON object containing integer `version`, boolean
+`healthy`, a host object, a databases object keyed by exact project/role, and an errors array. Host fields
+SHALL cover identity, tool version, infrastructure, state storage, configured database-root storage,
+repository, and the one timer. Database fields SHALL cover project, role, engine, running, health,
+configured image, latest backup, and bounded error. Output SHALL omit machine state, contract comparison,
+operation history, restore, backup tests, and maintenance units.
+
+#### Scenario: Automation requests JSON
+- **WHEN** status runs with `--json`
+- **THEN** stdout contains exactly one parseable document with additive mount-aware storage facts and no terminal presentation or credentials
+
+#### Scenario: Human contract changes incompatibly
+- **WHEN** a future release removes or changes a required structured field
+- **THEN** the top-level status version changes

openspec/changes/archive/2026-08-21-show-storage-and-restart-traffic/specs/operator-cli/spec.md

@@ -0,0 +1,19 @@
+## ADDED Requirements
+
+### Requirement: Guided host actions
+Selecting Host from the guided root SHALL show mount-aware state and database-root storage, routing
+infrastructure, repository, timer, and current host errors followed by Restart traffic and Back actions.
+Restart traffic SHALL warn that active database connections may briefly drop and require confirmation
+before changing Traefik runtime state.
+
+#### Scenario: Operator reviews custom storage
+- **WHEN** the host configures several database roots
+- **THEN** the Host view shows every exact path, backing mount and source, capacity, and assigned roles
+
+#### Scenario: Operator declines traffic restart
+- **WHEN** the operator selects Restart traffic and declines confirmation
+- **THEN** Traefik and every database remain unchanged
+
+#### Scenario: Operator confirms traffic restart
+- **WHEN** the operator confirms Restart traffic
+- **THEN** the Host view reports completion only after the dedicated Traefik container becomes healthy

openspec/changes/archive/2026-08-21-show-storage-and-restart-traffic/tasks.md

@@ -0,0 +1,13 @@
+## 1. Host Storage And Traffic
+
+- [x] 1.1 Report mount-aware state and configured database-root capacity with exact role assignments.
+- [x] 1.2 Add the confirmed guided Traefik restart action and verify container health after a real Compose restart.
+
+## 2. Database Storage
+
+- [x] 2.1 Add on-demand role directory allocation and backing-filesystem facts to Database Details.
+- [x] 2.2 Report PostgreSQL logical bytes and database count and Redis-compatible dataset memory and key count.
+
+## 3. Verification
+
+- [x] 3.1 Cover storage, stopped/live engine details, restart confirmation and health, partial failures, and structured output with focused tests.

openspec/specs/deploy/spec.md

@@ -32,6 +32,20 @@ evdb SHALL manage one dedicated Traefik Compose project that owns host ports 543
 - **WHEN** a PostgreSQL client connects through the native proxy and advertises the `postgresql` ALPN protocol
 - **THEN** Traefik completes TLS negotiation and routes the connection through the matching Postgres SNI router
 
+### Requirement: Dedicated traffic proxy restart
+The guided Host interface SHALL provide a confirmed Restart traffic operation that takes the exclusive
+host operation lock, restarts only the installed Traefik Compose service, and waits for the owned Traefik
+container to become healthy within the host health timeout. It SHALL preserve source, generated files,
+database services, database data, credentials, and certificate state and SHALL NOT rerun initialization.
+
+#### Scenario: Traffic restart succeeds
+- **WHEN** the operator confirms Restart traffic and Traefik becomes healthy
+- **THEN** evdb reports completion without restarting any database Compose project
+
+#### Scenario: Traffic restart remains unhealthy
+- **WHEN** Traefik does not become healthy before the timeout
+- **THEN** evdb reports the failed host operation and does not claim that traffic restart completed
+
 ### Requirement: ACME DNS certificates
 Dedicated Traefik SHALL use a configured ACME DNS-01 resolver for native database certificates, a scoped DNS-provider credential in a private host file, and persistent `acme.json` with mode `0600`. It SHALL NOT require or bind ports 80 or 443.
 

openspec/specs/http/spec.md

@@ -64,11 +64,21 @@ Disposable integration tests SHALL run Redis and Dragonfly HTTP sidecars and pro
 - **THEN** each value appears only in its matching KV engine
 
 ### Requirement: Detailed database view
-`evdb database info PROJECT/ROLE` SHALL display configured role and concrete engine, live image version and health, data and Compose paths, latest backup summary, native connection fields, and HTTP fields when enabled. The command SHALL deliberately retrieve credentials from private host files and print them only to the terminal.
+`evdb database info PROJECT/ROLE` SHALL display configured role and concrete engine, live image version
+and health, data and Compose paths, latest backup summary, native connection fields, and HTTP fields when
+enabled. Details SHALL show the data directory's allocated bytes and backing filesystem capacity, mount,
+source, and type. A running PostgreSQL role SHALL show total logical database bytes and connectable
+database count; a running Redis or Dragonfly role SHALL show dataset memory bytes and total key count.
+The command SHALL deliberately retrieve credentials from private host files and print them only to the
+terminal.
+
+#### Scenario: Running database is shown
+- **WHEN** the selected role is running
+- **THEN** info distinguishes allocated directory storage from engine-native data size and count
 
 #### Scenario: Stopped database is shown
 - **WHEN** the selected role is configured but stopped
-- **THEN** info still shows settings, storage and connection details and clearly identifies stopped state
+- **THEN** info still shows settings, storage and connection details, clearly identifies stopped state, and marks live data unavailable
 
 ### Requirement: Complete Postgres connection details
 The Postgres information view SHALL show hostname, port, username, database name, TLS requirement, and a complete percent-encoded `postgresql://` URL containing the current host-owned password. The hostname SHALL be the project hostname `<project>.<host-id>.<base-domain>`.