Windows adds the install dir to PATH via the MSI, but the unix installer only
dropped the binary at /opt/executer/agent, so `executer-agent` / `which
executer-agent` did not work without the full path. `install`/`initialize` now
symlink the binary into /usr/local/bin (on the default PATH on both linux and
macOS, and writable unlike /usr/bin under macOS SIP); `remove` deletes it.
Best-effort: it never replaces a non-symlink already there and never fails the
install, and uninstall only removes a symlink pointing at our own install.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The portable agent bundled SQLitePCLRaw's e_sqlite3 native, which is built
against glibc 2.33+ and so refused to load on Ubuntu 20.04 / Debian 11
(glibc 2.31) — the agent crash-looped at startup on
Microsoft.Data.Sqlite.SqliteConnection's type initializer
(DllNotFoundException: GLIBC_2.33 not found).
- linux/macOS (net10.0): reference Microsoft.Data.Sqlite.Core +
SQLitePCLRaw.bundle_sqlite3, binding the host's own libsqlite3 instead of a
bundled native. No glibc floor; the published agent no longer ships
libe_sqlite3.so. Windows/server keep the bundled e_sqlite3 (no glibc floor
there).
- JobHistoryStore now fails soft: if SQLite cannot initialize (missing/
incompatible native, unwritable path) it logs a warning and falls back to
in-memory idempotency instead of taking the service down. Idempotency then
holds within the process lifetime but not across restarts.
Agent builds on both TFMs; the linux publish carries no sqlite native and uses
provider.sqlite3; all 60 agent tests pass (DownloadCacheTests now exercise the
system-sqlite path).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>