The SDK reads pack manifests and starter skills next to its own module,
which in the bundle is service.js, and no build step copied them there:
installed builds showed no packs and no starter skills. build-sidecar now
copies both folders next to service.js and Tauri bundles them (UF-066).
GET /api/agent/status returned the configured model even when it had no
key, so the status bar named Claude while chats ran on the local model.
It now resolves the model the way the chat route does (UF-067).
The release publishes the server archive and the desktop installers under
one tag, and the installer looks for the release named after its own
version, so both now carry 1.0.0.
- Key messages named a Settings > API Keys tab that does not exist; they
now point at Settings > Models (UF-061).
- The connector suggestion looked for vault.db, which never exists; it
now checks the vault for a connector entry (UF-062).
- /config and /preferences were registered with a leading slash and
never matched (UF-063).
- Pins and documents were written under ~/.waggle whatever the data
directory; they now use the server's data directory (UF-064).
- The Windows uninstaller named a Data & Privacy page that does not
exist (UF-065).
release.yml now has one build job with a matrix over the four release
targets (windows-x64, macos-arm64, macos-x64, linux-x64). Each leg stages
the sidecar, checks it, builds the web UI, packs the server archive for
the installer (ADR-0009), runs the installer smoke test, builds the
desktop installers (NSIS and MSI, app and DMG, deb and AppImage), runs
the packaged app until its sidecar answers /health, and uploads the
installers and archives. A pushed v* tag also gets a draft GitHub
release with a SHA256SUMS file, created with GITHUB_TOKEN only. Pull
requests on the desktop paths and manual runs build and test without
publishing, so tauri-build-pr.yml is removed.
Nothing is signed or notarized. The macOS app gets an ad-hoc signature
("-"), which needs no certificate; without it macOS reports a downloaded
Apple Silicon app as damaged.
Removed with the old pipeline, as nothing else used them: the Windows
signing handoff and signer (sign-windows-artifact.ps1 and its tests,
new-windows-signing-handoff.ps1), the pilot signing scripts
(sign-windows-pilot.ps1, apply-signing-config.mjs, signing-config.ts and
its test, sign-macos-adhoc.sh, tauri.build-override.conf.json and the
tauri:sign:* and tauri:build:win:pilot-signed scripts), the installer
certifier with its bootstrap-token helper, and the Windows release
publisher. check-sidecar-resources.mjs stays: tauri.conf.json runs it
before every desktop build and the workflow runs it before packing the
archive.
app/package.json gains tauri:build:linux. The tests that pinned the old
workflows, the certifier, the signer and the publisher are removed;
new tests pin the targets, the step order, the absence of signing and of
secrets other than GITHUB_TOKEN, and the draft-only, tag-only publish.
The Windows installer certifier opened a WebView2 CDP port through
WAGGLE_CERTIFIER_WEBVIEW_DEBUG_PORT. The certifier leaves with the
commercial release pipeline, so the main window is built straight from
its configuration and the shipped app never opens a debugging port.
Sample data in tests, prompts and UI placeholders uses Alex Morgan
instead of the maintainer's name; decision attributions say "owner".
Personal details in two test fixtures are replaced. Local paths
(D:/Projects/...) and paths into the maintainer's planning repository
are reworded. Clone and install URLs in CONTRIBUTING.md and the getting
started guide use placeholders until the public repository location is
decided (Q9). The Benchmarks page no longer names the maintainer's
hive-mind repository, and the upstream fixes log names the main Waggle
repository instead of an internal git host.
get_wiki_pages, get_wiki_page, get_wiki_page_content and
compile_wiki_section proxied to the sidecar's /api/wiki routes, which
served the wiki-compiler package and left with the old memory engine in
P1.5. No screen called them. Remove the commands, their TypeScript
bindings and tests. cargo check and the 32 Rust tests pass.
scripts/check-licenses.mjs (npm run check:licenses) reads the production
dependency closures of the sidecar (@waggle/server minus the packages
stage-sidecar-deps.mjs never ships) and the web UI (apps/web) from
package-lock.json and fails on GPL, AGPL, SSPL, missing and unknown
licenses. It allows permissive licenses plus MPL-2.0 and lists named
exceptions with reasons; LGPL libvips and node-webpmux, the OFL fonts and
the unlicensed buffers package are marked as pending the licensing review.
app/src-tauri/deny.toml applies the same allowlist to the Tauri crates with
cargo-deny; the npm check fails when the two lists drift apart. A new CI
job runs both, with cargo-deny 0.18.3 installed and cached in CI.
scripts/license-inventory.mjs holds the shared closure logic.
Add "license": "MIT" to the workspace manifests that lacked it (app,
apps/web, server, shared and the postponed team packages) and to the
Tauri crate. Remove the personal author and the maintainer repository,
homepage and bugs URLs; the public repository location is not decided
yet (Q9). package-lock.json is left as is and is regenerated later.
Linux packages keep resources in /usr/lib/<app> (deb) or under $APPDIR
(AppImage), not next to the executable, so the shell never found
service.js there. Setup now records Tauri's resource_dir and the lookup
prefers it, keeping the executable-relative paths as a fallback.
Drop tauri-plugin-updater: it was declared but never registered, and the
updater stays disabled until release signing exists.
On macOS and Linux the shell stopped the sidecar with Child::kill(), which is
SIGKILL, so the sidecar never ran its shutdown: the processes it started (MCP
servers, a managed Ollama, the WhatsApp browser) kept running. After an app
restart the orphaned WhatsApp browser still held the session profile, and the
channel failed with "The browser is already running".
The shell now sends SIGTERM, waits up to 5 seconds for the sidecar to exit,
then sends SIGKILL; Windows keeps its kill-on-close job. For crashes, where no
shutdown runs, the WhatsApp channel stops a browser left over from an earlier
run before starting its own. It only stops a process whose command line uses
this profile and whose parent is gone; a browser another running Waggle server
owns is left alone, and the channel says so instead of retrying.
- The packaged macOS app stayed on "Starting Waggle…": the shell looked
for node, service.js, native/ and node_modules/ next to the executable,
the Windows layout, while a macOS bundle keeps them in
Contents/Resources/resources. bundled_resources_dir() checks both.
- The startup screen used min-height 100vh on an unstyled body, which
showed scroll bars, and a fixed light text colour that is invisible in
the light theme. It is now styled from index.html, fixed to the window,
with a dark text colour for the light theme.
- tsconfig.build.json references the nine in-scope packages; each package
is composite and references the workspace packages it depends on.
build:packages is now `tsc -b tsconfig.build.json` instead of a chain
of cd commands.
- Every in-scope package exports its TypeScript entry under a `source`
condition next to the dist/ entries. Vitest, tsx (dev:server, the
Tauri dev launch, the e2e server), the sidecar and launcher bundles and
the web app resolve it, so none of them needs build:packages first or
can pick up a stale dist/. The vitest src aliases remain only for the
excluded packages that have no source export.
- Published packages with a files list (agent, cli, marketplace) pack
src/ too, so the source condition never points at a missing file.
- tsconfig.tests.json and `npm run typecheck:tests` type-check the test
suites of the in-scope packages. They report 426 existing errors, so
the CI step is advisory for now.
- The root test run leaves out the excluded and postponed packages
(hive-mind-*, memory-mcp, wiki-compiler, team-server, waggle-dance,
worker, weaver); they are not built either.
- CI runs the test job on Ubuntu, macOS and Windows with Node 22.23.2
(ADR-0008), and no longer builds the hook runtime and the memory MCP
server.
- Stop building and staging the hive-mind CLI, the coding-agent hook
packages and the memory MCP server: the hooks, Waggle Room and the
memory MCP server are hidden in v1 (ADR-0002) and all of them write to
the legacy .mind files.
- Drop sqlite-vec: nothing loads a SQLite extension since the legacy
memory engine left. bundle-native-deps no longer copies vec0, the
resource check no longer probes it, the Tauri shell no longer sets
WAGGLE_SQLITE_VEC_PATH and install.sh checks plain SQLite.
- Stage bundle roots that npm keeps inside a workspace. mem0ai is not
hoisted (it stays in packages/memory-mem0), so staging skipped it
silently and the packaged sidecar would fail on the first memory
access. Roots that are not installed are now listed in the output.
- js-yaml is a runtime dependency of Puppeteer's config loader since the
WhatsApp channel moved to whatsapp-web.js (ADR-0005); it leaves the
resource-check denylist. chromium-bidi stays unstaged: Puppeteer loads
it only for WebDriver BiDi sessions.