Needs attention
Confirmed faults in current observations. Admission waits and historical outcomes are shown separately.
INFRASTRUCTURE WORKSPACE
What is running, and what waits?
Jobs across the workspace. The VPS queue has one shared slot; remote runners have their own capacity.
Loading workspace status…
Jobs
Waiting for observationsCurrent workload is not observed yet.
Running
Waiting
Loading the queue…
Server queue
FIFO order
Runner or workflow dependency
Oldest first · start order unknown
Queue detailsRetry and timing
- Head of queue
- Unconfirmed
- Scheduled retry
- Unconfirmed
- Estimated turn
- Unknown
- Next useful observation check
- Unconfirmed
Retry times are checks, not promised start times.
Last seen work
Current state unconfirmed. These observations do not count as running or upcoming. Open the source to check its latest status.
Foreground jobs and observed agents. Background services may also be active.
Where resources are going
Top five accounting groups. CPU is a share of the whole host.
Workload measurements have not loaded.
Background servicesNo service observations
Observed service state, independent of the build lane. A running service does not establish CPU use or active user work.
Health
Runners by host
Repository-visible registrations and explicit host intent. VPS admission capacity is separate from remote execution capacity.
Runner evidence has not loaded.
No registered runners in the complete configured inventory.
Container evidence has not loaded.
Managed Compose containers · collected every five minutes. Counts overlap. CPU is a share of the whole host; memory includes cgroup cache. Restart counts are cumulative. Reload reads saved evidence.
Current faults, capacity and evidence quality are assessed separately.
Observation freshness unknown
Evidence coverage unknown
Source diagnosticsCollection details and saved evidence
History
Recorded outcomes · last 48 hoursWorkload resource historyOne hour · one-minute samples · expand to load
Workspace
Projects, worktrees, and observations that need a durable work link.
COLLECTOR HEALTHEvidence feeds have not loadedShow feed details
WaitingSource coverage has not loaded
WORK REVIEWWork review has not loadedReview waits, unfinished work and cleanup candidates
Inactivity prompts review; it does not prove abandonment or completion. Cleanup candidates require a separate safety check.
No matching records.
Refresh schedule and observation ages
BUILD OPERATIONS
Runner fleet and build queue
Recent Forgejo workflow runs, runner service health, the one-at-a-time build and deployment lane, and anything that needs operator attention.
Operations waitingEvidence waiting
Waiting for activity observations.
Current admission status not observed.
Detailed observations have not loaded
Shared capacity queue
Queue observation continues during heavy work; updates target every five minutes.
Authoritative host status: sudo hosted-deploy queue.status </dev/null
Local runner services healthy—Fleet evidence not loaded
Open workflow runs—Forgejo run evidence not loaded
Shared slots active—Capacity evidence not loaded
Capacity queue depth—Queue evidence not loaded
Next admission—Queue evidence not loaded
Resource readiness—Resource evidence not loadedView resource gates
No evidence loaded
Observed runner-service health
Each segment is one visible service. Healthy means online, not that a job is running or a slot is available.
Shared lane occupancy
All hosted builds and deployments serialize through this lane.
Local runner servicesService observations on polinaria.world. Registered runners and explicit host intent appear in Runners by host.No runners loaded
No runner data in view
Work activity
A global view of Forgejo workflows and local heavy work before, during, and after the shared capacity lane.
Now
No current workNo current activity in view
Last 48 hours
No history loadedNo recent activity in view
Work needs attentionExpired admission waits · expand to load
Idea to solutionIssue and PR timing · twice daily · expand to load
Job timingAverage wait and runtime · expand to load
Capacity reconciliation
Checks for stranded allocations and isolated test resources. This maintenance check uses the shared lane but is not a build.
- Latest attempt
- Unavailable
- Last success
- Unavailable
- Result
- Unavailable
- Duration
- Unavailable
- Timer
- Unavailable
Reconciliation evidence has not loaded.
Host resources and admission
Local samples roughly every five minutes. Optional collector updates may defer under pressure.
Waiting for resource evidenceLane unknown
Resource admission evidence has not loaded.
No sample
Filesystem headroom and cleanup preview
Storage evidence has not loaded.
Resource history and queue correlation
The selector changes the main VPS resource graph. Queue depth and head-wait graphs always show VPS admission context. Points use recorded times; gaps show missing evidence. Short spikes between samples may be missed. Recorded thresholds can change with admission mode. Weekly summaries show means and ranges without gate classifications.
Recorded measurements as a table
All signals and collector updates
Forgejo and capacity evidence are joined only by exact repository and run identity. Local remediation remains unlinked unless it already has a Forgejo run. Individual workflow jobs remain outside this view.
Repositories—
Open issues—
Open PRs—
Open work—
Untracked work—
Projects needing attention—
Codex task storage—
Task workspace evidence gaps—
ISSUES AND PULL REQUESTS
Work in progress
Work stage, observed execution and delivery are shown separately. Routine unlinked activity is retained in diagnostics.
PROJECT OVERVIEW
Repository portfolio
Expand a repository to see current work, untracked activity, open issues whose work status is unknown, and delivery details.
Your projects at a glance
The latest authorized snapshot will appear here.
DIAGNOSTICSCollector relations and raw inventoriesCollapsed by default
EXECUTION OWNERSHIP
Conversation relation diagnostics
Lifecycle evidence remains separate from completion and from broader executor coverage.
Ownership gaps—
Running—
Waiting—
Execution unknown—
Blocked—
No lifecycle records in view
Authorized lifecycle evidence will appear here.
OTHER OBSERVED ACTIVITY
Unlinked activity
Activity without an issue or PR link. A missing link does not mean abandoned work; older observations remain in history.
No unlinked observations in view
HOST SERVICES
Service outcomes
No host services in view
CODEX TASK STORAGE
Task workspaces
Privacy-safe storage measurements. Handles are opaque; lifecycle is never inferred from age, and this view cannot delete data.
No task workspaces in view
DELIVERY STATE
Deployments
Read-only deployment status derived from exact-head Forgejo workflow evidence. This dashboard cannot dispatch a deployment.
No deployments in view
Raw Git inventory
Observed Git facts. Upstream comparisons use cached remote references.