ActionItem now carries optional targetPaths so plan.execute can use plan-carried targets instead of reconstructing execution intent from findings. This improves execution reliability and enables proper restore mappings for recovery items. - Add targetPaths field to ActionItem domain model - Update plan execution to prefer plan-carried targets with finding fallback - Expand safe cache path fragments for direct-trash execution - Add gate review documentation for ATL-211/212/215 - Bump protocol version to 0.3.0
4.3 KiB
Local Protocol
Goals
- Provide a stable local contract between UI, worker, and helper components.
- Avoid parsing terminal-oriented text output.
- Support progress, execution, history, recovery, settings, and helper handoff.
Protocol Version
- Current implementation version:
0.3.0
UI ↔ Worker Commands
health.snapshotpermissions.inspectscan.startplan.previewplan.executerecovery.restoreapps.listapps.uninstall.previewapps.uninstall.executesettings.getsettings.set
Worker ↔ Helper Models
AtlasHelperAction
idkindtargetPathdestinationPath(required for restore-style actions)
AtlasHelperActionResult
actionsuccessmessageresolvedPath
Response Payloads
accepted(task)health(snapshot)permissions(permissionStates)apps(appFootprints)preview(actionPlan)settings(settings)rejected(code, reason)
Error Codes in Current Use
unsupportedCommandpermissionRequiredhelperUnavailableexecutionUnavailableinvalidSelection
Event Payloads
taskProgress(taskID, completed, total)taskFinished(taskRun)permissionUpdated(permissionState)
Core Schemas
Finding
idcategorytitledetailbytesrisktargetPaths(optional structured execution targets derived from the scan adapter)
ActionPlan
idtitleitemsestimatedBytes
ActionItem
idtitledetailkindrecoverabletargetPaths(optional structured execution targets carried by the current plan)
TaskRun
idkindstatussummarystartedAtfinishedAt
AppFootprint
idnamebundleIdentifierbundlePathbytesleftoverItems
RecoveryItem
idtitledetailoriginalPathbytesdeletedAtexpiresAtpayloadrestoreMappings(optional original-path ↔ trashed-path records for physical restoration)
AtlasSettings
recoveryRetentionDaysnotificationsEnabledexcludedPathslanguageacknowledgementTextthirdPartyNoticesText
Protocol Rules
- Progress must be monotonic.
- Rejected requests return a stable code plus a user-facing reason.
- Destructive flows must end in a history record.
- Recoverable flows must produce structured recovery items.
- Helper actions must remain allowlisted structured actions, never arbitrary command strings.
- Fresh Smart Clean preview plans should carry
ActionItem.targetPathsfor executable items so execution does not have to reconstruct destructive intent from UI state.
Current Implementation Note
-
health.snapshotis backed bylib/check/health_json.shthroughMoleHealthAdapter. -
scan.startis backed bybin/clean.sh --dry-runthroughMoleSmartCleanAdapterwhen the upstream workflow succeeds. If it cannot complete, the worker now rejects the request instead of silently fabricating scan results. -
apps.listis backed byMacAppsInventoryAdapter, which scans local app bundles and derives leftover counts. -
The worker persists a local JSON-backed workspace state containing the latest snapshot, current Smart Clean plan, and settings, including the persisted app-language preference.
-
Atlas localizes user-facing shell copy through a package-scoped resource bundle and uses the persisted language to keep summaries and settings text aligned.
-
App uninstall can invoke the packaged or development helper executable through structured JSON actions.
-
Structured Smart Clean findings can now carry executable target paths, and a safe subset of those targets can be moved to Trash and physically restored later.
-
Structured Smart Clean action items now also carry
targetPaths, andplan.executeprefers those plan-carried targets. Older cached plans can still fall back to finding-carried targets for backward compatibility. -
The app shell communicates with the worker over structured XPC
Datapayloads that encode Atlas request and result envelopes. -
executePlanis fail-closed for unsupported targets, but now supports a real Trash-based execution path for a safe structured subset of Smart Clean items. -
recovery.restorecan physically restore items whenrestoreMappingsare present; otherwise it falls back to model rehydration only.