37 lines
1.4 KiB
Markdown
37 lines
1.4 KiB
Markdown
# Agent — Current State
|
|
|
|
This file records what is believed to be implemented now.
|
|
|
|
## Lifecycle / readiness
|
|
- readiness-aware server start is centralized.
|
|
- manual start/restart, autostart, and supervisor crash restart use the same readiness-aware path.
|
|
- duplicate/dead crash monitor path was removed.
|
|
- `/ready` exists and is the semantic readiness gate.
|
|
- `/status` includes operation and maintenance state fields.
|
|
- guarded operation locking exists for mutating/stateful flows.
|
|
|
|
## Control hardening
|
|
- `/start`, `/stop`, `/restart` are POST-only.
|
|
- `/console/command` is POST-only and JSON-based with validation/limits.
|
|
|
|
## Backup support
|
|
- local Minecraft backups exist for:
|
|
- create
|
|
- list
|
|
- restore
|
|
- delete
|
|
- backups are local under `/opt/zlh-agent/backups`.
|
|
- retention is currently simple local max-count pruning.
|
|
- pre-restore checkpoint hardening has been added so restore creates a safety checkpoint before destructive restore begins.
|
|
- restore exposes both restored backup metadata and checkpoint metadata.
|
|
|
|
## Runtime / dev environment base
|
|
- runtime installs are artifact-backed.
|
|
- dev user/workspace model exists.
|
|
- code-server install/start baseline exists.
|
|
|
|
## Important boundary
|
|
- agent does not own remote/offsite backup syncing.
|
|
- local app-aware backups are agent responsibility.
|
|
- PBS / platform backup strategy is separate from agent implementation.
|