[AmrMsCLL]

Everything asked of the console since #24, in one PR. It includes #25 (chart hover) and #26 (Backups alignment, scrollbar gutter); close those two. Goes with Project-Graphite/platform#46.

Secrets

• A Filters menu (project, type, missing a required secret) with removable chips replaces the path and text fields.
• Create is the right-most button, Delete beside it, and copying the selected names is an icon.
• Each project header collapses its secrets with a chevron; on a Project page the whole Secrets section is collapsible, closed by default and remembered.
• Redeploy and its hint leave the Secrets list (they stay on the Project page and the Overview).

Redeploy

• The button is the status: Redeploy, Redeploying…, Redeployed (two seconds), back to Redeploy; a failure turns it red with the unit's last log lines in its tooltip. It has a fixed width and announces changes to screen readers.
• A redeploy that finishes marks .applied with its exit time, so "needs redeploy" clears even when nothing had to be recreated (for example, secrets imported with the same values). The pill means: the project's env file is newer than its last rollout.

Logs

• The console follows every running container and keeps every line for seven days (LOGS_KEEP_DAYS) in /logs/logs.db, on its own volume so it stays out of the nightly backup (platform#46), with level and stream. It resumes from the last stored line after a restart.
• The Logs page browses them newest first: a filter-icon menu with nested filters (project, expanding to its containers; level; stream; time window), search, a Live tail, and Load older.

Alerts

• Rule saves and the test email use action buttons that show Saving…, Saved and failure on themselves instead of a note that shifts the row.

Backups

• The schedule is set on the page: on or off, every 1 to 168 hours from an hour in UTC, and days kept. The backup service reads it (platform#46). The late-backup alert follows it and stays quiet while backups are off.
• Back up now and Upload are action buttons; Import picks the file with a button.

Volumes

• Owners can create a volume, browse its files and download one, and delete an unused one. Every path is resolved and must stay inside the volume, links included. Docker has no way to rename or relabel a volume.
• Each volume shows its size as a bar against the largest and an in-use pill.

Shell

• The host shell now runs as the unprivileged graphite-ops user. Its sudo rule allows only read-only docker commands (ps, stats, logs, top, images, volume ls, network ls, compose ls, system df); the console creates the user and the rule on first use, checking the rule with visudo.
• Owners can switch to a root shell after a confirmation.
• Both run a bash guard (/usr/local/share/graphite/shell-guard.bash) on a DEBUG trap that blocks commands that would take down the VPS or the console (deleting system or Graphite paths, formatting disks, power, stopping docker, ssh or the agent, removing the console's container, volume or the edge network, pruning volumes, firewall flushes, removing users) and attempts to leave the guard (trap, a bare bash/sh, su, sudo -i); asks for "yes" before destructive ones (rm -r, docker rm/stop/prune, compose down, systemctl stop, kill, package removal, git reset --hard, overwriting /etc); and logs every command to the journal as graphite-shell with the login. The guard is a guard rail for the root shell; the operator user is the boundary.

UI

• A stats rail with status pills on Alerts, Logs, Backups, Volumes and Admin.
• Admin is a member table (role, last seen, access as pills) with an access dialog: area switches and a searchable table of projects with Operate and Secrets switches.
• The descriptions under the page titles are gone. The page is wider (up to 120 rem) and reserves the scrollbar gutter.

Checks

tsc (server and web), oxlint, npm run build, and test/alerts.spec.ts, test/backups.spec.ts, test/logstore.spec.ts, test/volumes.spec.ts, test/shell.spec.ts, test/secrets.spec.ts, test/access.spec.ts, test/terminal.spec.ts, test/live.spec.ts, test/history.spec.ts. The guard was also parsed with bash -n, its 59 sample commands classified identically by GNU grep -E, and run interactively: a blocked command never ran and trap - DEBUG was refused. Not run: anything on the VPS (log following, volume browsing, the operator user, sudo), and the pages in a browser.