docs backend evidence cd ZD 00

ZD-00 — Read-only staging inventory

Status: LOCAL_DONE Validation: PASS (read-only inventory, 2026-11-03 11:03 UTC)

Owner selected the private VPS control repository and restricted all work to the existing teste.abastevo.com.br staging site. No remote mutation occurred. Private connection details and filesystem locations are intentionally omitted.

• Timer enabled/active/waiting; service last result success, restart count 0. Last six receipts, every two minutes through 11:03:54Z, are no-change. Last twenty journal events show normal verification/plan completion, no error.
• Apply enabled, surge disabled, configured CPU surge threshold 2000m. No checked latch or operator hold exists in this older agent.
• Current signed release c19f0bdefc8770efebcc4a0686c136f9d53c8828, migration chain 000145, compatibility floor 000132.
• k3s v1.35.4+k3s1. API one available replica, zero unavailable; RollingUpdate 0 surge / 1 unavailable, min-ready 0, grace 30 seconds. Readiness initial delay 15s, period 10s, timeout 1s, threshold 3; no startup probe. API/worker pull policy IfNotPresent (Git drift confirmed).
• Storage image abastevo-storage:dev-preview, policy Never, same API pod, readiness marker probe, shared hostPath. Private control-repository image source starts MinIO RELEASE.2025-04-22T22-12-26Z bound to loopback, one data directory, private bucket, no anonymous policy. Concurrent process safety has no proof: treat as single writer. The public S3 proxy currently targets loopback; moving storage requires preserving its signed public host/path and changing only internal forwarding, plus a network listener in storage.
• Quota CPU limits 3500m / 6000m; CPU requests 400m / 2000m; memory limits 3840Mi / 8192Mi; requests 1088Mi / 4096Mi. Existing extra three-container pod fits (2000m limits, 250m requests, 2560Mi limits, 768Mi requests). This is allocation headroom, not measured capacity.
• Web has one available replica; 25%/25% rounds to surge 1/unavailable 0.
• Only the Abastevo nginx server block was examined. Private upstreams redacted; HTTP/1.1, route read timeouts 60/10/15s, no explicit retry directives found. Cloudflare headers present. HEAD readiness returns 405; this is a method check, not a readiness failure.

Next: ZD-01 source guards. Storage separation, probe campaigns, drills, timer changes and surge activation still require individual owner approval.