app-lifecycle

# App lifecycle Read `system:app_management` with `read_action` before calling it through `execute_action`. For new app scaffolding, also read `coding:app_creation`. ## Install or reinstall a standalone app Use this path for a custom app under `~/.rome/<profile>/projects/apps/<id>/` or another standalone checkout outside the Rome monorepo. 1. Call `system:app_management` with the app repository as the source: ```json { "op": "install", "source": { "mode": "source", "path": "<absolute app repo path>" } } ``` 2. Pass the same source object on every reinstall after edits. The daemon rebuilds and repacks each time. 3. After the call succeeds, validate the app immediately. Do not poll deployment files or the `active` symlink. The daemon derives the app ID from `app.yaml`, runs the workspace's build, and packs it into `<repo>/.rome/artifact`. It installs the bundle and awaits the runtime reload before returning. The guardian can also use Install/Upgrade on the Apps dashboard. The `bundle` source mode accepts an already-packed artifact, not a raw source workspace. A raw workspace fails with "not a packed artifact". For a Rome App Store install, discover the listing with `system:app_store_search` and follow the `appstore` source schema in `system:app_management`. ## First-party apps First-party apps under the monorepo's `rome_apps/<appId>/` ship with Rome. The action cannot install or uninstall them. Only enable/disable applies through the action. 1....