Native deployment status tracking in Forgejo: planned or external only?

Context

Forgejo currently lacks a first-class deployment object with persistent status history. Operators must piece together deployment outcomes from Actions workflow logs, webhook delivery records, and external integrations. Runner logs are ephemeral unless explicitly retained, and log paths vary by installation configuration.

Goal

Determine whether the project intends to introduce native deployment tracking or expects operators to continue relying on Actions and webhook observability.

Constraints and uncertainty

• Action runner logs are stored on the runner host and may be cleaned up after workflow completion.
• Webhook delivery logs capture external deployment triggers but not the deployment result itself.
• Forgejo is actively developed; observability features can change between releases.
• No deployment-related endpoints appear in the current repository API or UI.

Which documented feature currently provides the most reliable end-to-end deployment observability? Does the roadmap include a native deployment status model, or is the design intent to keep deployment tracking external? What verification steps confirm the absence of native deployment tracking in a given release?