Domios v1.15.2

Domios 1.15.2

The app becomes Domios

• The installed application is Domios: product name Domios, identifier com.domios.app, GUI
  executable domios-app. The packaged CLI ships as domios and codeterm from identical bytes;
  domios is the primary command in help, docs and prompts.
• This is a manual move. CodeTerm 1.15.1 cannot update itself into Domios: install Domios fresh,
  then remove the old app. The per-OS steps follow below. Data stays in ~/.domios; nothing is migrated.
• New clients read only domios-latest*.json. The old latest*.json channels carry the manual move
  notes with no platform payloads: a 1.15.1 client reports this release as incompatible, and a forced
  install fails before any download or server shutdown.

What changes for you

• Plans are stored as relational task, milestone and attempt rows with an incremental recall index;
  deleting a plan never waits for indexing, and deleted plans leave every index. The schema change is
  forward-only: do not downgrade to 1.15.1 after running 1.15.2.
• Curator rounds run in a visible read-only tab under the team manager, render system deliveries and
  timeline events, and can be finished by hand.
• Blueprint runs receive bounded previous results on stdin and run without instance credentials;
  Blueprint recall uses vectors with a relevance floor.
• The composer has scoped mention sources with a caret-aware picker, live-scope mention chips and
  grouped background subagents.
• Chat copies attachments as complete files, shows their names, shares fullscreen camera, supports
  image galleries and keeps following the session after tab switches.
• Agent input is framed: routed reports and large messages arrive as one paste, and typed inputs
  reconcile across transports.
• Mesh artifacts enforce the private-path policy for outgoing files.
• Lane worktrees clean themselves up completely when their work lands.
• Billing signs you in at purchase; plans stay browsable and checkout opens in the app's theme.
• Product analytics deliver with consent in production.

Fixes

• Chat-backend bridge deliveries report backend errors and uncertain deliveries instead of
  swallowing them.
• Team close and plan deletion no longer hang; Workers report their Team on spawn.
• Tab restart delivers its input; restored tabs wake on transcript changes.
• Startup recovers stale sockets, rewrites relocated stored paths under the legacy data root and
  reports stale root references.
• Updates scrub the relaunch environment, verify Debian staging, explain privileged Debian updates
  and recover interrupted updater handoffs.
• Chat task ids keep their links where no mention host exists; Curator refusals show the server's
  message; the zoom canvas works without ResizeObserver.
• domios test plans are no longer flagged as vague by plan doctor.
• The sidebar keeps visible rows in place when lists shrink.
• Worker checklist review cards stay out of the parent chat; report task chips and references render.
• Bundled plugins ship only runtime files; shipped prompts no longer carry repository procedures; the
  remaining CodeTerm naming in docs, help and health is gone.

Removed

• The retired 1.14.9 upgrade path.

Move from CodeTerm 1.15.1 to Domios 1.15.2

Install Domios fresh by hand, then remove the old application. Do not use
CodeTerm's in-app installer for this release. Data already lives in ~/.domios
and stays there; no data move, migration script or compatibility shim is needed.
Do not run both applications together.

• Windows: quit CodeTerm, including its tray process. Disable its autostart
  in Settings before quitting. Download and run the Domios setup executable;
  the default destination is %LOCALAPPDATA%\Domios. Run the old uninstaller
  from %LOCALAPPDATA%\CodeTerm (normally uninstall.exe); remove only the old
  app, keeping ~/.domios. Remove any remaining CodeTerm-Autostart task in
  Task Scheduler. Launch Domios and re-enable autostart there if wanted. Remove
  old Start-menu/desktop shortcuts and pins, then pin Domios. In a new terminal,
  where.exe domios and where.exe codeterm must resolve the CLI in
  %USERPROFILE%\.domios\bin; the GUI is domios-app.exe. Remove old CodeTerm
  directories from the user PATH. Both CLI names run the same installed CLI.
• macOS: disable CodeTerm autostart, quit it, then open the Domios DMG and
  install Domios.app in /Applications. Delete /Applications/CodeTerm.app
  and any duplicate old bundle. Remove the old Login Item and unload/remove
  ~/Library/LaunchAgents/com.codeterm.app.plist if it remains. Launch Domios
  and re-enable autostart if wanted. Remove the old Dock icon and add Domios.
  Open a new terminal: command -v domios and command -v codeterm must select
  ~/.domios/bin or the links in ~/.local/bin, both targeting the current CLI.
  Remove custom PATH entries or links into CodeTerm.app.
• Linux: disable CodeTerm autostart and quit it. The old package is named
  code-term, and it owns /usr/bin/domios, which the new domios package also
  ships, so installing first and removing afterwards fails with a dpkg file
  conflict. Install and remove in one transaction:
  sudo apt-get install ./Domios_1.15.2_amd64.deb code-term- (on arm64,
  ./Domios_1.15.2_arm64.deb). For an AppImage install, use the new AppImage and delete
  the old CodeTerm image and its custom desktop launcher. Disable/remove the
  old codeterm.service user unit if still present, then launch Domios and
  re-enable autostart if wanted. In a new terminal, command -v domios and
  command -v codeterm must select the package-owned /usr/bin/domios and
  /usr/bin/codeterm CLI commands, or the current CLI links under
  ~/.domios/bin / ~/.local/bin. The GUI is /usr/bin/domios-app. Remove old
  custom PATH entries, desktop launchers and icons. Do not force-overwrite
  package-owned files.

After removing the old app, check autostart, shortcuts, and the default handler
for domios:// links and any file associations you configured. Set them to
Domios; remove old codeterm:// associations or custom file handlers. On Linux,
xdg-mime query default x-scheme-handler/domios must name the Domios desktop
entry. On Windows check Default apps and Task Scheduler; on macOS check Login
Items and open a domios:// link. Linux Deb/RPM packages install both CLI
commands in /usr/bin. For macOS and AppImage, start Domios once to repair
both CLI links in ~/.local/bin; verify that directory is already in your shell
PATH, or add it yourself using your shell settings. On Windows first launch
registers ~/.domios/bin on user PATH. No user shell dotfiles are edited by
Domios. Open a new terminal afterwards. Application data stays in place.

Without the release guard, the 1.15.1 updater would launch a separate Domios
NSIS install on Windows, replace the current bundle in place on macOS (leaving
the old CodeTerm.app path with a new identity), or install a differently named
Linux package alongside the old package, conflicting on shared paths such as
/usr/bin/domios. An AppImage update replaces the current image while retaining its old filename.
These mixed states are unsupported. New Domios clients use
domios-latest*.json; the old latest*.json paths publish these manual steps
with no platform payloads. The 1.15.1 discovery shows the release notes as
incompatible and cannot offer an install. A forced old install fails at missing
platform selection, before download, shutdown or installation; the old binary
cannot gain a new custom error dialog from release metadata.

The bundle identifier changes to com.domios.app. macOS treats Domios as a new
app for TCC permissions, including microphone and Accessibility: grant access
again when requested, or enable Domios in System Settings → Privacy & Security.
Old Keychain items may prompt for access by the newly signed app; approve the
prompt or sign in again if access is denied. No Keychain ACL is silently copied.
Windows notification identity/AUMID and notification preferences are new too;
allow notifications for Domios again. Existing denial/fallback and permission
request paths remain available; the old app's OS grants are not inherited.