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.
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.
- The workspace isolation scenarios store memories through the memory
store and check that one workspace's search never returns another's.
- The Ollama manifest test covers the Linux x64 and arm64 artifacts added
for P1.3b; an unsupported platform still resolves to nothing.
- The root run leaves out the tests that only exercise excluded packages
(the hook packages and the memory MCP server); they go with those
packages in P2.2.
- 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.
The commercial repository carries the product's internal history: audits,
screenshots, briefs, decisions, pricing, publication drafts, personal data
and research runs. None of it belongs in the community edition.
- delete judging/, "UAT 3/", benchmarks/ (including LoCoMo data under
CC BY-NC), preflight-results/, gepa-phase-5/, notes/, decisions/,
.understand-anything/, .agents/, .lovable/, the legacy sidecar/ package
and waggle-cowork/ (an analysis of Claude Code sources)
- delete docs/ except docs/oss, the user guides (without the team-mode
guide), the reference, methodology, architecture, getting-started and
contributing pages, which P2.4 rewrites
- delete render.yaml, .parity-allowlist, the retired mind-parity and
sync-mind workflows and 29 one-off scripts nothing references
- delete tests that only checked removed files (sidecar package, Render
blueprint, UAT capture, benchmark harness isolation, internal audit and
signing docs); drop sidecar/ and benchmarks/ from the hive-mind subtree
split guard; prune ignore, attribute, lint and test globs
- replace the commercial README with an interim one for this edition
Source comments still point at some deleted docs; P2.2 part 2 cleans them
together with names and paths.