Policy, updates, heartbeat, and response
These fleet capabilities are target requirements in the agent architecture plan, not current handlers or CLI commands.
Signed policy
AG-017 requires centrally managed policy to be validated and authenticated before activation. Local configuration already activates complete valid candidates atomically; that behavior is a useful boundary, not an implementation of signed remote policy. Policy distribution must define authorization, signature trust, version/rollback handling, and failure behavior. No current policy transport schema is claimed here.
Heartbeat and connection management
AG-014 plans connection management, failover, and heartbeat. Backend last_seen currently comes from ingested telemetry rather than a heartbeat record written into the registry. A registered agent can therefore exist without evidence that an endpoint is alive. Do not build a heartbeat sender against an invented API.
Native lifecycle and upgrades
AG-031 plans native installation and service management. AG-032 plans cryptographically verified remote upgrades; AG-033 covers compatibility and fleet rollout. Current updates.enabled is fixed to false. There is no supported unattended updater or package repository in this checkout.
Installation state is intended to survive uninstall/reinstall; purge is the explicit destructive operation. Until native packaging exists, these are lifecycle requirements, not package-manager command instructions.
Restricted response
AG-034 and AG-035 plan a command channel and constrained response executor. Actions must be typed, authorized, scoped, and auditable. Arbitrary remote shell execution is prohibited by the architecture plan. There is no current command handler, allowlist format, signing key configuration, or response API to enable.
Security review before implementation
Policy and update channels can change privileged endpoint behavior. Trust distribution, replay protection, downgrade protection, bounded execution, cancellation, and audit evidence must be part of their implementation, not assumptions inferred from TLS alone. Supply-chain guidance distinguishes existing CI checks from future release controls.
Source evidence
Reviewed against the source baseline. Seagull-agent-v2/internal/config/config.go · Seagull-backend-v2/internal/control/liveness.go · Seagull-agent-v2/README.md.