0.6.0

[kmendell]

Disclaimer Greptiles Reviews use AI, make sure to check over its work.

To better help train Greptile on our codebase, if the comment is useful and valid Like the comment, if its not helpful or invalid Dislike

To have Greptile Re-Review the changes, mention greptileai.

Greptile Summary

This is the 0.6.0 release, a large feature update spanning most of the app. The headline changes are: docker-info replaces dashboard snapshots as the authoritative container-count source (ensuring Arcane-managed containers are included), a new app-wide activity toast monitor with progress tracking, activity batching in the Activities view, a new Events store with severity filtering, a Template Browser store, and significant expansions to Swarm, Network Topology, and Variables views.

• Fleet count refactor (DashboardView, EnvironmentDashboardCard, widgets): live states are now per-environment DashboardEnvironmentLiveState values fed from docker-info fan-outs; the aggregate is nil if any environment is offline, and a new fleetCountAvailabilityNote explains missing data. Widget refresh intent retains its 10-environment cap and adds a 4-concurrent-fetch limit.
• Activity toasts (ActivityToastMonitor, Toast): a new app-wide monitor streams activities and drives in-place progress toast updates; the toast capsule now renders a progress bar and the entire toast is tappable to open the Activity Center.
• Activity batching (ActivityCenterStore, ActivitiesView): activities sharing a batchID are grouped into collapsible ActivityBatchSummary rows with aggregate progress, status, and environment labelling.

Confidence Score: 4/5

Safe to merge; the functional changes are well-structured, but two UI-accuracy issues in the fleet-count availability display deserve a follow-up fix.

The docker-info refactor in DashboardView leaves hasLoadedFleetCounts true across reloads, so when allEnvironments is refreshed before the async fan-out finishes the availability note briefly misreports all environments as unreachable. A separate card-level concern is that EnvironmentDashboardCard.cardStatus shows Loading Docker information indefinitely for environments where the REST fetch failed but the stream has no error, since the card no longer owns its own docker error state. Both affect user-visible accuracy of the new availability UI, not underlying data or networking correctness.

Arcane Mobile/Views/Main/DashboardView.swift (fleet-count reload sequencing) and Arcane Mobile/Views/Main/EnvironmentDashboardCard.swift (offline card status text).

_{Reviews (2): Last reviewed commit: "fixes" | Re-trigger Greptile}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 82831fc743

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".