Domios v1.17.0

Domios 1.17.0

Domios 1.17.0 gives each friend a receiving machine and a concierge whose
access follows the friendship's grants, with clearer conversation status
and controls throughout the app. Changes since v1.16.0:

Neighbors

• Choose where each friend is received. Receive one friend on this
  machine from the sidebar, concierge row or conversation, with explicit
  takeover confirmation. Other friends can keep receiving on their current
  machines. The all-friends control identifies this machine and the number
  of friends affected. Moving receiving away retires that friend's local
  concierge and its delegated access.
• Concierge access follows the friendship grant. Scope, memory,
  workspace, file and machine-access permissions govern the concierge and
  its delegated agents. Applying permissions starts a fresh concierge
  session with the new instructions; the friend's conversation remains.
  Restoring an unchanged grant resumes the existing session.
• General can edit the complete grant. Partial changes preserve other
  fields, including memory enabled/disabled, allowed memory areas,
  workspace access, files, tab requests, interactive content, machine
  access and folder scope. Memory can be turned off explicitly.
• Empty messages are refused before sending. Empty or whitespace-only
  text returns empty_body without queueing a submission. File-only
  messages remain supported. Receiver-takeover and non-receiving-machine
  errors explain why the operation was refused.
• Read receipts reflect actual reading or handling. A visible incoming
  message or confirmed concierge handling advances the read state after
  delivery acknowledgement is committed. Delivery alone does not mark a
  message read; reconnects preserve newer read status.
• See and stop concierge work. Conversations show incoming handling
  status and provide Stop for the friend's active concierge. Replies to an
  owner-stopped request are refused before sending and are not offered as
  retryable submissions.
• Flag suspicious incoming messages. Owners and authorized agents can
  flag instructions, requests for private data, malicious links, spam or
  other concerns. Flags stay local and appear with the message; they are
  not sent to the friend or forwarded to bridges.
• Choose concierge model, effort and speed from the providers and
  options that support concierge work. The selected model appears below
  the concierge in the sidebar.

Agents and interface

• Codex Cloud is available in the new-session picker. Environment
  discovery refreshes after sign-in and on request, so the picker can
  offer the available Cloud environments and execution modes.
• The bundled control skill is now named domios. Agent guidance and
  skill mirroring use the new name.
• Consistent loading states across the app, including terminal boot,
  with shared activity indicators and a Mesh card that keeps its size
  while loading.
• Clearer session controls: readable program names in command lines,
  and improved model and destination pickers. After a connection drops,
  the loaded app stays usable with a quiet reconnect pill while updates
  are paused; initial connection still has a loading state.
• Mesh discovery improvements include passive detection of macOS
  system-extension Tailscale and framed LocalAPI response handling.
• Jobs is easier to navigate. Import Blueprints from a file or
  repository through a dialog with a drop area; select General, a
  workspace or a Team with the shared destination picker. Jobs show as
  working only while a run executes, and an empty list has a clear empty
  state.

Upgrade note

• Upgrade both ends of a Mesh connection to 1.17.0. The running app's
  version is the peer minimum, so a 1.17.0 installation refuses older
  peers. Official plugins keep their independently managed versions and
  minimum-host requirements; the app version bump does not bump plugins.

Release candidate and qualification

Release head: 755d9e39d4b2874043387935cf0e759e18fa5834.
Source: pinned next 5d17471d8ad3e674d1ff8c0602524b2490677fcd, analytics key guard eba7a979bdb3550748417f655b225fffef906728, privacy fixture repair ae47075a5b1f383eae5337c65ac4527ced670531, and reset-confirmation pointer fix 8344312ba67df0c27f60e031ecb3bef80db37eb6. No unrelated 1.18 work is included. All lanes and prior unpublished release ancestry are preserved through real merges.

Product version: 1.17.0, with internal crates at 0.0.0. Plugin versions are independently managed; the app bump does not rewrite them. Bundled Codex 1.14.57 requires Domios 1.17.0. Both Mesh peers need 1.17.0.

The analytics guard separates cached builds by non-secret key fingerprints and verifies the production fingerprint in the staged server binary in every release build workflow. The reset confirmation stays mounted through pointerdown before redemption; canonical UsageBubble runtime regression, TypeScript and Biome passed (Elgar relay).

Read-only included-history resolution on this exact head passed: 796 commits, 8 remote calls, published v1.16.0 boundary 488b42f79477746e34d5d7ff9b10140cb5fd6fd1. Public-Issue and Repository-Issue sets are empty. Generated closing metadata reconciliation and commit audit passed; no invented closing claims.

Exact-head CI: https://github.com/domios-dev/domios/actions/runs/40779417247 . The full fast/Rust/native/embeddings qualification and signed six-platform dry-run packaging must pass together. The owner assigned broad qualification to CI; no local build, Rust test or release-preflight was run for this cut.

Witness live PASS was relayed on product source 59ab9136351726bcb98d6fdb55d8bf135a7449f4: a read-only concierge read outside cwd without approval and sent one non-empty linked answer (one send/ACK/read/delete, no duplicates); cold General became ready without UI activation or a stale concierge; earlier per-friend items passed. Subsequent additions above have explicit owner approval. Publication is authorized after exact-release CI and release gates pass.

Coordinate the production accounts/analytics default-on and per-friend receiving deployment with Turner at publication. Verify served updater bytes, signatures, legacy refusals, mirror and issue-closure evidence afterward. Scoop/Homebrew definitions remain unpublished templates; verify available release inputs without creating external package repositories.

Domios v1.16.0

Domios 1.16.0

Domios 1.16.0, the first public release from domios-dev/domios.

Carries the 1.16.0 release head merged in #671 plus the qualification fix that publication needs.

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.

🤖 Generated with Claude Code

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.

CodeTerm v1.15.1

Domios 1.15.1 release PR. Draft: the release SHA follows once the remaining P0 lanes land; publication and tags need the owner's GO.

CodeTerm 1.15.1

• Updates show per-component progress in a clean panel, and an update that cannot install says why
  before it stops anything. Install refusals reach the CLI with their code and how to recover.
• Plugin installs and updates swap atomically: a failed step rolls back and names the exact step.
• Account, sign-in and update failures appear as toasts instead of a titlebar slot. Small surfaces
  show compact errors; plugin rows take one line with one channel notice.
• Attachments appear at once with an uploading state and clearer kind labels.
• A tab previews files in its own AgentPad, with a shared viewport viewer and edge-aware touch previews.
• The sidebar shows each section as LABEL N with live working activity and a one-line worker summary.
• Memory Activity lists configured agents, Workers and Services, with details on click.
• Claude model and effort switches apply mid-turn when the provider supports it.
• The tray shows Admin from the server's authority.
• Immediate deliveries skip the queue, heartbeats get their own chip, and the feed never blanks.
• Escape closes the Mesh peer drawer before the view.
• The Browser surface stays stable while the window resizes.

Fixes

• Runtime launches send only the assigned-task starter; the brief travels as developer instructions (P0).
• Restored tabs bound to their own session no longer show Starting while they work, and interrupted
  tabs and routed messages wake restored tabs.
• Chat runtimes keep their declared agent runtime, and worker failures record their real reason.
• Agent provider listing never waits on a plugin VM.
• Codex edit cards read path-keyed change maps; unknown edits show their raw payload.
• Telegram file sends deliver the document or fail loudly; bridge inject failures stay typed and never replay.
• Agent notifications stay in the bell, with no strip above Chat.
• Updater template placeholders and flag values are never treated as prerequisites; relocation
  tolerates a stray provider-update.lock.
• Review hooks do nothing without checklist storage; Workers close seeded criteria by id.
• Retained exit evidence is rechecked when a process identity is lost.
• An isolated verify server opens loopback-only sockets.

Internals

• Rename phase 2: crates, packages and the contract bridge move to Domios (Herald). Phases 3-5 ship in 1.15.2.
• Envelope grammar v1 with typed segments and shared fixtures.
• Stage timing instrumentation for providers, chat start, preview and PTY.
• Typed GitHub blueprint node and reuse-first blueprint prompting.
• Release CI runs in tiers: fast checks, then tests behind them; builds start at once. Qualified dry runs
  publish through release-publish.yml; RELEASE_AUTO_PROMOTE stays off.
• The platform test classifier caches results by source digest; platform jobs compile only packages
  with platform-specific tests.
• PR-time script, gateway and frontend workflows are gone: their guards run in release-preflight and
  the fast Linux tier.
• ConPTY shell-exit diagnostics report session, host and shell context.

Plugins

Plugins release on their own train. plugins/channel.json and the manifests agree
(node scripts/release-plugin.mjs check: 7 checked):

Plugin	Version	minCodeterm	Tag
provider-claude	1.14.15	1.15.1	plugin-claude-v1.14.15 to create on master after this release
provider-codex	1.14.49	1.14.9	plugin-codex-v1.14.49 to create on master after this release

provider-claude 1.14.15 needs this app version, so its tag waits for 1.15.1 to publish.

Issues

Public issues fixed by this release are resolved from the release range with
release_issue_contract.py on the final SHA and close only after served-byte verification.

Qualification (on the release SHA)

• Canonical full regression once, then ./build.sh release-preflight.
• release.yml dry run with tests on release/1.15.1.
• Publication from the qualified run through release-publish.yml after the owner's GO.

Still to land before the release SHA

• Ember (task_bc5sz3): P0 lane-scan CPU.
• Sentry (task_ml70hr): P0 background loops.
• Possibly Herdsman (one toast system) and Tempo (--speed).

🤖 Generated with Claude Code

CodeTerm v1.15.0

CodeTerm 1.15.0

Release 1.15.0: runtime identity moves to Domios (data, config, logs, mesh), plus release pipeline repairs. Installer, crate and CLI names stay CodeTerm until 1.15.1.

Candidate: 6f6095552 (rename/domios, fast-forwarded). A push to release/** is a dry run while RELEASE_PUBLISH_ENABLED is unset.

Pipeline repairs on this branch:

• Every distributable retained by dry runs (DMG, headless, updater payloads).
• Private-store outage falls back to GitHub Actions artifacts and a job-local sccache; the endpoint is defined once in scripts/ci-store.sh.
• Size-aware evidence-store deadline with one logged retry.
• Build receipts name the real first failure.
• A qualified dry run promotes to the release from its retained bytes (promote_run_id); it refuses missing, changed or foreign evidence.
• The frontend is built once per run; every platform installs it by sha256.
• macOS arm64 and x64 build in parallel (RELEASE_MACOS_X64_LABEL).

Qualification: release.yml dry run on this head, plus canonical release-preflight on 6f6095552.

🤖 Generated with Claude Code

CodeTerm v1.14.9

Domios 1.14.9

Agent runtime

• Codex runtime events are reduced in batches: the subscriber drains the frames already queued into one reducer call. A lagged event channel or a failed reducer pass is now a warning plus a resync, not a killed turn; the provider process closes only on exit, a protocol failure or 8 consecutive bookkeeping failures. The event queue is 8192 frames, and the Codex reducer state has a total budget.
• Worker launches no longer fail on an unproven exit: a PowerShell "command finished" marker with exit 0, seen before the provider process appears, no longer ends a launch whose session then binds.

Delivery

• Chat sends to Claude PTY tabs: a > in the transcript above a filled composer is no longer mistaken for a menu, so Enter is pressed.
• Domios pastes are followed by a pasted by Domios marker instead of the <tip>Handle the message above.</tip> and "Handle the paste as my request." follow-ups; the shared rule tells agents what the marker means.
• Voice notes carry their transcript in a <transcript> element.

Coordination

• System heartbeats appear in the tab's recurring list as read-only entries with a delivery log.
• The Orchestrator heartbeat no longer repeats the owner's own messages.
• Worker provider errors (rate limits, usage limits, server errors) reach the Orchestrator as incidents.
• Claude's cancel-only permission prompt ("Esc to cancel") is recognized by tab respond.

Build and structure

• ./build.sh check-queue: a warm per-machine cargo check of a lane SHA, returning bounded file:line errors. Build verbs report success or early failure to the calling tab with --notify-tab; install-local runs its fmt, file-size and clean-tree gates first.
• scripts/ catalogue with caller headers and a CI gate.
• First crate splits out of the app crate and codeterm-types: codeterm-wire, -decision, -provider-signals, -blueprint-types, -local-recording, -notify-types, -events, -config, -secrets, -keepawake, -cron, -shutdown and -sentinel-ports, plus the socket rpc bridge. The app crate's tangle went from 162 to 142 modules.

Release notes for reviewers

• Built from develop 6dfe8cb22, the same SHA the owner installed and used as 1.14.9-dev.6 on BLACKSTAR.
• BLACKSTAR is paused as a CI build machine for this release (its runner labels are parked, and windows-x64-build is served by ROG). By the owner's decision, no local release-preflight or core-journeys run was done on BLACKSTAR; the CI release run is the gate.

Signed and notarized macOS DMGs and headless archives for all six platforms are available alongside the updater packages.

Apple notarization: aarch64 2a3fa275-bcc3-45ed-bc99-7d54273e6065 (Accepted); x64 80501837-d526-4721-ac77-a6c023bb832a (Accepted). Both DMGs are stapled and signed with Developer ID Application: ANDREY KOVALEV (JMMWQ9LWF7).

codeterm-core plugin channel

Official core plugin channel, published from verified plugin release tags.

CodeTerm v1.14.7

Domios 1.14.7

Plan pl_xq9cj4. Codex moves to the Chat-only agent runtime and into the provider-codex plugin.

CodeTerm 1.14.7

• Codex runs on the stdio app-server runtime with no PTY: start, resume, history (with a thread/read fallback for Codex 0.160), sends, approvals and questions, interrupt with completion wait, model, effort and mode controls (CLI, self and cross-tab), usage.
• Codex sign-in without a PTY: browser (system browser), device code, API key over stdin or a masked field, terminal fallback; the same thread resumes without restart.
• The role identity of every role (Orchestrator, Planner, Worker, General, cron, memory workers, dreamer) is composed into the runtime system prompt and refreshed on resume and after compaction.
• Legacy PTY Codex tabs migrate to the runtime on restore; plan task dispatch, cron and memory workers, agent restart (resume and fresh) and tab stop work on runtime tabs.
• Unmapped provider server requests get correlated error replies; human-readable runtime errors; compact one-row Chat status banner.
• Account tray with provider and action icons.
• Release pipeline: independent per-artifact jobs and runner labels, structural bundle smoke checks, signature verification before publish, serialized publication, dry runs include tests.
• Gate and dev reports alert the Orchestrator on the first failure.
• Test isolation: no unit test reads the machine config or the shared lifecycle journal; platform-scoped recording tests; subsecond closed-tab cap tests.

Investigated, not fixed

• Refs #604 (CI archive and shard work continues).
• Refs #153.

Deferred, with reasons

• Isolated release execution smoke, Windows arm64 native smoke, Windows Authenticode signing: post-release tasks.
• Deleting the old codex_rpc path: after the live parity gates, next release.
• OpenCode on the same runtime: next release.

Licensed under PolyForm Shield 1.0.0 from 2026-10-16

CodeTerm v1.14.6

CodeTerm 1.14.6

Release 1.14.6.

Updates

• Windows updates no longer fail as "busy". The updater waited on the Windows job handle after TerminateJobObject, which Windows never signals when the processes exit normally, so a successful kill timed out and the first attempt failed (introduced by c7ec00529). It now waits on each process's own exit. Before installing, Restart Manager finds who holds the install files: Domios's own processes are stopped, foreign ones are named by executable and PID in the failure notice, which offers Retry. Errors name the blocking tab.
• Frontend updates: an unattended window takes a new frontend at once; a window someone is looking at shows "A new version of the interface is out — Update". Drafts and scroll are saved before the reload.

Reliability

• Codex RPC sidecars no longer outlive their daemon: a lifetime lease kills the sidecar group when the daemon dies (process-exit watch on macOS, parent-death signal on Linux, the existing kill-on-close job on Windows), and ./build.sh kill reaps only its own dev instance's sidecars.
• Remote Workers on mesh peers can acknowledge and report again (remote ACK and report are authenticated by attempt, worker tab and binding nonce); a dispatch whose response is lost but whose Worker spawned is recorded instead of reported as offline. Structured sidecars no longer receive a startup-ack instruction without a startup attempt. The CLI and daemon socket protocol moves to version 5, so a remote Worker needs both machines on 1.14.6.
• Load-flaky sentinel, tailer and socket tests prove child or listener readiness before their timed phase; product deadlines are unchanged.

Build

• The frontend updater is its own crate, codeterm-frontend-bundle, with 17 isolated tests.

Release process

• Work lands on develop; a push to release/X.Y.Z is the release; the release run decides app or frontend release from the diff since the last app release and runs the full test matrix in parallel with every installer build.

🤖 Generated with Claude Code

Licensed under PolyForm Shield 1.0.0 from 2026-10-16

CodeTerm v1.14.4

CodeTerm 1.14.4

Release 1.14.4: the 1.14.3 bug-fix plan plus the first app that can receive independent frontend releases.

Frontend updates

• Frontend downloads follow GitHub's signed asset redirect. Apps up to 1.14.2 rejected the redirect URL because of its query string and could not receive any frontend release. Discovery and manifest URLs stay query-free.
• The desktop app update check (30-minute cadence) now also checks frontend-latest, as the HTTP update route already did.
• Bundled frontend and the frontend contract move to 1.14.4.

Chat and UI (already in master through frontend-v1.14.3)

• Messages keep transcript source order; one bounded message width; running replies render markdown; one inline chip per pasted image; render directives in every message surface; the bell admits only notifications; provider-less glance receivers show a neutral state; surfaces follow the owning daemon; Main tab provider switch is one restart transaction.

Backend

• Updater waits for PTY process termination, not console cleanup, before installing on Windows.
• REST handlers run nested-runtime work off the async workers; fixes the tab close and memory deletion panic.
• Restored Main launches register their resume target, so Codex Main binds and replies.
• Image and mixed tool results keep their bytes; the 100 000 character attachment cap is gone.
• Glance returns an empty view for receivers without a provider.
• The mesh stream relay admits surface streams; routed messages transfer standalone file directives to the target machine.
• Codex prompt detection ignores numbered lists in delivered message text.
• LARK first enable emits setup status and asks the plugin for a device proposal (host part; plugin lark 0.1.1 is on codeterm-plugins main).

Plugins in this tree: provider-codex 1.14.4, provider-claude 1.14.3.

CI and release tooling

• scripts/ci-scope.mjs scopes frontend and Rust checks separately; Docs source of truth runs only when its inputs change (from the closed PR 629).
• Frontend release runs on any light Linux runner and installs pinned minisign and gh when missing; publish reads back drafts and large archives.
• Release skill covers choosing between frontend, plugin and app releases.

Release process (new in this release)

• Work lands on develop; pull requests run fast checks only. master takes only release/X.Y.Z.
• A push to release/X.Y.Z by the owner account is the release: the full test matrix on every platform and every installer build run in parallel; publication waits for all of them, then the release PR merges into master and back into develop.
• Hand-run evaluator qualifications moved from tests.yml to qualification.yml; air is a macOS CI runner.

🤖 Generated with Claude Code

Licensed under PolyForm Shield 1.0.0 from 2026-10-16