Commit Graph

194 Commits

Author SHA1 Message Date
shumeiko.it
1d43d978f4 docs(oss): log UF-070, the Settings logs link that sends no session token 2026-11-04 19:26:15 +01:00
shumeiko.it
1cfe337053 Merge licensing: shipped notices, Apache-2.0 core files and LGPL terms
Every installer and the server archive carry LICENSE and the
third-party notices, and Settings > General links to both. The files
copied from hive-mind-core keep Apache-2.0 with SPDX headers. The LGPL
components name their versions and where their source is. ADR-0010
settles the marketplace catalog question. Logs UF-069 and marks UF-059
Fixed.
2026-11-04 19:25:44 +01:00
shumeiko.it
9cb53a5eaf Merge P1.3c: separate data directory and the Benchmarks page removal
The community edition defaults to ~/.waggle-community and copies nothing
from the commercial ~/.waggle (ADR-0011). The Benchmarks page, which
showed scores of a memory engine the community edition does not run, is
removed. Logs UF-068.
2026-11-04 19:23:45 +01:00
shumeiko.it
eb2aaa486d docs: note the Apache-2.0 files and the shipped notices in the changelog 2026-11-04 10:48:00 +01:00
shumeiko.it
d3a39fe3cf test: stage the legal files in the launcher archive fixture
build-server-archive.mjs now requires LICENSE and THIRD_PARTY_NOTICES.md,
so the installer fixture stages both and checks that they land next to
service.js. The sidecar half of the legal route test gets the 60 s hook
timeout the other full-server suites use.
2026-11-04 10:47:15 +01:00
shumeiko.it
1a496e1ec5 chore: tidy ignore rules and the PR template 2026-11-04 10:42:26 +01:00
shumeiko.it
b11bdb8029 docs: make CONTRIBUTING the single contributor guide 2026-11-04 10:41:40 +01:00
shumeiko.it
fc9ab861ee fix(web): mention the Apache-2.0 files in Settings > About
Waggle is MIT-licensed except the files of packages/core copied from
hive-mind-core; the About text and the License dialog say so.
2026-11-04 10:36:23 +01:00
shumeiko.it
c4580b95f8 docs(oss): settle the licensing items the owner left to us
ADR-0010 records that the marketplace catalog holds package metadata
only (names, authors, licenses, short descriptions, links, install
instructions), like any package index, and needs no licensing review.
The pending licensing row of the ADR index keeps only the copyright
holder in LICENSE; the settled items (Apache-2.0 files in core, the
notices and the LGPL terms, the catalog) are listed below the table.
The README names the Apache-2.0 files of packages/core.
2026-11-04 10:35:54 +01:00
shumeiko.it
de9adcb03d chore: stop tracking CLAUDE.md
CLAUDE.md held notes for one AI coding assistant; AGENTS.md is the
contract for every contributor. The file stays local and is ignored;
the PR template and .gitignore now point to AGENTS.md.
2026-11-04 10:35:00 +01:00
shumeiko.it
35bf8e26bd feat(licenses): meet the LGPL notice and source terms for libvips and node-webpmux
The notices now carry the LGPL-3.0 and GPL-3.0 texts from
scripts/license-texts (the LGPL text byte-identical to gnu.org's, the GPL
text as the Rust toolchain ships it), whatever the dependencies ship.
The LGPL section names each component with its exact version, says it
ships unmodified as a separate library, and gives the upstream source
release of that version: sharp-libvips v1.3.2 and libvips v8.18.3 for
the libvips packages, sharp v0.35.3 for @img/sharp-win32-x64, the npm
package of node-webpmux 3.2.1. The libraries built into libvips are
listed with their versions from versions.json. Versions and repository
URLs come from the lockfile and the installed packages.

The LGPL exceptions of the license gate are no longer pending: the
project owner left these items to us. A test checks the texts, the LGPL
rows and the Apache-2.0 files against the committed notices. UF-059 is
fixed.
2026-11-04 10:34:32 +01:00
shumeiko.it
e0836388f1 docs: record the separate data directory (ADR-0011)
Add ADR-0011: the community edition defaults to ~/.waggle-community, a
temporary name that follows the product-name decision (Q8), and copies
nothing from the commercial ~/.waggle. It supersedes point 4 of
ADR-0009 and closes the pending "separate data directory" decision.

Update the install guide, troubleshooting, capabilities, memory,
architecture, the Windows build notes, THREAT_MODEL, README,
.env.example and the changelog. Log UF-068 (Open): marketplace skills
and plugins ignore a custom data directory.
2026-11-04 10:32:08 +01:00
shumeiko.it
ad222e8bf3 feat(web): name ~/.waggle-community as the data directory (P1.3c)
Settings > Advanced and the Vault notice showed ~/.waggle. Take the path
from DEFAULT_DATA_DIR_LABEL in @waggle/shared (ADR-0011) and update the
comments that describe the first-launch flag and skill locations.
2026-11-04 10:31:38 +01:00
shumeiko.it
4fabed70c0 feat(desktop,launcher): default to ~/.waggle-community (P1.3c)
The Tauri shell's bundled npm environment and its first-launch flag, the
server installer's --data-dir default and the NSIS installer config
fell back to ~/.waggle. Use ~/.waggle-community (ADR-0011).

The Rust shell keeps the name in DEFAULT_DATA_DIR_NAME in lib.rs and the
launcher, which uses only Node built-ins, in DATA_DIR_NAME.
packages/shared/tests/data-dir.test.ts fails when either copy, or the
marketplace's, differs from @waggle/shared.
2026-11-04 10:31:32 +01:00
shumeiko.it
b275f0bf89 feat: default the data directory to ~/.waggle-community (P1.3c)
The community edition defaulted to ~/.waggle, the data directory of the
commercial Waggle, so both editions would open the same config, vault,
waggle.db, marketplace catalog and skills. Default to
~/.waggle-community instead (ADR-0011). WAGGLE_DATA_DIR still overrides
it wherever it did; nothing is migrated from ~/.waggle.

The name is defined once as DEFAULT_DATA_DIR_NAME and
DEFAULT_DATA_DIR_LABEL in @waggle/shared, with defaultDataDir() in
@waggle/core for the sidecar, the CLI, the agent and the model caches.
The marketplace installs on its own without workspace packages, so it
keeps a copy in its data-dir.ts; the CLI help, which loads no
dependency, spells the path out and its runtime test checks it.

The marketplace security scan also flags skills that reference the new
skills folder. Tests that asserted the old default now use the
constant, and comments name the new directory.
2026-11-04 10:31:20 +01:00
shumeiko.it
58535a580f feat(server,web): open the license and third-party notices from Settings
The sidecar serves LICENSE and THIRD_PARTY_NOTICES.md read-only at
GET /api/legal/license and GET /api/legal/third-party-notices, from the
copies next to service.js in the desktop app and the server archive, or
from the repository root when run from source. Like every API route it
needs the session token.

Settings > General gets an About section at every detail level with
License and Third-party licenses buttons; each opens the document in a
dialog, loaded once through the adapter, so it works the same in the
Tauri webview and in a browser.
2026-11-04 10:30:33 +01:00
shumeiko.it
9ac6b9f0d4 feat(licenses): ship LICENSE and the third-party notices with every installer
build-sidecar.mjs copies LICENSE and THIRD_PARTY_NOTICES.md from the
repository root next to service.js in app/src-tauri/resources, and fails
when either is missing. The resources/* glob of tauri.conf.json bundles
them into every desktop installer, and build-server-archive.mjs refuses a
payload without them, so the server archive carries them too. The copies
are ignored by git. Tests cover the copy, the archive and the ignore rule.
2026-11-04 10:24:35 +01:00
shumeiko.it
0acaa1cf29 feat(licenses): list the Apache-2.0 files of @waggle/core in the notices
The generator finds the copies from hive-mind-core by their SPDX header
and lists each with the file it came from, whether it changed, the
copyright line and the Apache-2.0 text from packages/core/LICENSE-APACHE.
The text stays in the notices even if no dependency carries it.
2026-11-04 10:20:11 +01:00
shumeiko.it
0fef37ac53 chore(core): mark the files copied from hive-mind-core as Apache-2.0
The logger, injection scanner, ingress guard, WorkspaceManager, embedders,
recall helpers and execution traces came from @waggle/hive-mind-core
(Apache-2.0); awareness, identity and parts of WaggleDB were adapted from
it. They keep Apache-2.0: an SPDX header with the original copyright line
and the source file, packages/core/LICENSE.md listing them,
LICENSE-APACHE with the full text, and "MIT AND Apache-2.0" in
package.json. A test keeps the list and the headers in step. No code
changes.

Logs UF-069: the hive-mind-core LICENSE is an abridged Apache text.
2026-11-04 10:19:05 +01:00
shumeiko.it
120640780c refactor(web): remove the Benchmarks page
The page showed LoCoMo scores of the old hive-mind memory engine, which
the community edition does not run, so its numbers misled. Remove the
page and its test, the /benchmarks route, the command palette entry, the
route announcement label and the color-guard baseline entry. The e2e
route check now expects /benchmarks to show the not-found page.
2026-11-04 10:04:02 +01:00
shumeiko.it
d920325268 chore(licenses): accept the OFL fonts without a pending review
Hanken Grotesk and JetBrains Mono are unmodified OFL-1.1 fonts shipped
with their license, which OFL allows; they need no owner decision.
2026-11-04 09:56:36 +01:00
shumeiko.it
cc9bdda257 fix(deps): move exceljs to unzipper 0.12.3 to drop the unlicensed buffers (UF-060)
exceljs 4.4.0 pulled unzipper 0.10, which depends on binary and through
it on buffers 0.1.1, a package with no license grant. An npm override
moves exceljs to unzipper 0.12.3, the version whatsapp-web.js already
uses, so binary, buffers, chainsaw and traverse leave the installers.
Waggle only writes workbooks and loads them through JSZip; both still
work. The license gate drops the two exceptions it no longer needs.
2026-11-04 01:48:37 +01:00
shumeiko.it
eb3b54b1c6 docs(oss): record the confirmed WhatsApp browser source and v1 platforms
ADR-0005's open item is closed: the installed Chrome or Edge first, a
downloaded Chrome for Testing only when none is found. The v1 platform
list is confirmed and leaves the pending table. ADR-0005 no longer
mentions install.sh or an npm install on the user's machine.
2026-11-04 01:33:11 +01:00
shumeiko.it
187364dedf docs(oss): keep the marketplace catalog in the repository (ADR-0010)
Records the decision not to generate marketplace.db at build time or ship
it as a release artifact (P1.6), and adds the catalog's third-party
descriptions to the pending licensing review.
2026-11-04 01:15:20 +01:00
shumeiko.it
a92136cd69 fix(scripts): do not fail the desktop smoke test on temp cleanup
A writer of the stopped app can still be finishing in the data directory
when the smoke test removes its temp root, so rmdir failed with
ENOTEMPTY after the test had passed. The temp root is disposable: a
failed cleanup now logs a warning.
2026-11-02 17:13:17 +01:00
shumeiko.it
c9ad90c40e Merge: remove Waggle Room captured tasks for external agents (Q2) 2026-11-01 17:04:24 +01:00
shumeiko.it
7758060246 docs(oss): record the week 3 acceptance on macOS (P2.7) 2026-11-01 11:17:12 +01:00
shumeiko.it
a70bc14c63 fix(cli): talk to local Ollama models without a proxy
The CLI sent every request to a LiteLLM proxy on :4000, which the
community edition no longer starts (it needs Python), so the CLI could
not answer with any model out of the box. ollama/<tag> models now go to
Ollama's OpenAI-compatible API directly; other models still use the
configured proxy.
2026-11-01 11:15:37 +01:00
shumeiko.it
bf74f02420 fix: ship capability packs and starter skills, report the usable model (UF-066, UF-067)
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).
2026-11-01 11:15:37 +01:00
shumeiko.it
d7ef76ac90 docs: record the removal of Waggle Room tasks
- CHANGELOG "Removed" and the README's list of what is not in this
  edition name Waggle Room tasks for coding agents and say what the Tool
  Launcher still does.
- AGENTS.md lists the removal under "Already removed".
- The Room canvas no longer invites users to "launch a captured external
  task"; it shows Waggle agents, groups and launched tools.
2026-11-01 11:14:20 +01:00
shumeiko.it
6d187c8da7 test: remove the Windows external-agent lane
The lane drove real Claude Code, Codex, Hermes and OpenClaw installs
through Waggle Room runs, the coding-agent hooks and the hive-mind CLI,
none of which is in the community edition.

- scripts/test-windows-external-agents.ps1 and
  scripts/test-windows-official-auth-canaries.ps1 (the runners and their
  receipt sealing), scripts/verify-codex-tool-denial.mjs
- tests/e2e/launcher-real-hook-lifecycle.spec.ts and
  tests/e2e/launcher-real-tool-lifecycle.spec.ts (Windows-only, skipped
  unless the runner set them up)
- tests/integration/external-agent-collaboration.live.test.ts
- the tauri-config tests that pinned those scripts
2026-11-01 11:13:35 +01:00
shumeiko.it
25f95c584b refactor: launch external tools without Room credentials or hook settings
A Launcher launch still opens the tool in the active workspace's folder,
tracks its process, streams observed output and stops it. What it no
longer does:

- set WAGGLE_SIGNAL_EMIT, WAGGLE_SIDECAR_URL, HIVE_MIND_DATA_DIR or the
  Room identity variables (WAGGLE_RUN_ID, WAGGLE_ROOM_ID,
  WAGGLE_DANCE_TEAM_ID, WAGGLE_SENDER_ID, WAGGLE_RUN_TOKEN). Only the
  removed coding-agent hooks and the WaggleDance CLI read them. The
  external-process allowlist now admits WAGGLE_WORKSPACE_ID alone;
- issue a run credential. Run tokens existed for Room workers (the dance
  CLI and OpenClaw's model calls), so the registry's credential store,
  the middleware's run-token bearer on /v1/chat/completions and the
  proxy's per-run model scope go. While an agent run with a model is
  active, the proxy still serves only the session bearer.

The run record that a launch creates in the agent-run registry stays: it
backs cancel from the Room canvas, which this change does not remove.
2026-11-01 11:12:31 +01:00
shumeiko.it
80db300485 refactor(shared): drop the headless task contract from tool manifests
The `task` spec (argv templates, access modes, output dialects) and the
capability flags headlessTask, structuredProgress, resumable and
liveWaggleDance described how a Waggle Room run drove a coding agent
without its UI. Nothing runs tools headless any more, so built-in
manifests, the third-party adapter loader and detection results no
longer carry them. An adapter file that still declares `task` is
rejected like any other unknown key.
2026-11-01 11:08:26 +01:00
shumeiko.it
727c756651 refactor: route Best fit proposals to personas only
The executor router could propose Claude Code, Codex or Hermes and
dispatch the task as a Waggle Room run through POST /api/tools/run, which
is gone with the collaboration runtime. Confirming such a proposal could
only fail.

- ExecutorRegistry offers the five v1 personas; it no longer detects
  external tools.
- Route proposals dispatch persona chat turns only. The memory brief and
  its egress disclosure existed only for external executors, so
  executor-brief.ts, the egress fields and removeFrameIds go too.
- RouteProposalCard drops the memory disclosure, "Run without memory" and
  the link to an external run in the Room.
2026-11-01 11:06:43 +01:00
shumeiko.it
94ad4446fb refactor: remove Waggle Room captured tasks for external coding agents
Waggle Room is not part of the community edition (decision Q2, ADR-0002).
Its headless runs of Claude Code, Codex, Hermes and OpenClaw needed the
packaged collaboration CLI from the removed @waggle/hive-mind-cli, so
POST /api/tools/run answered 503 collaboration_runtime_missing.

- Remove POST /api/tools/run (routes/external-tool-runs.ts) with its
  Room fan-out, WaggleDance publishing, OpenClaw provisioning and the
  memory write-back of run results.
- Remove runExternalTool (agent/external-tool-runner.ts) and
  resolveWaggleRuntime; the taskkill path helper moves into the process
  tracker, its only remaining user.
- Launcher: drop the hidden "Run task" composer, the Room hand-off and
  adapter.runExternalToolTask. Detect, launch, watch and stop stay.
- Drop the `room` flag from the memory feature map: it only gated the
  Launcher task button.
- The viewer policy no longer reads participants[].workspaceIds, a body
  shape only /api/tools/run accepted.
2026-11-01 11:02:46 +01:00
shumeiko.it
8e528b3467 test(e2e): wait for the visible shell and use the phone path to new workspaces
Since phones get a bottom bar instead of the sidebar (UF-057), the shell
wait matched the hidden sidebar first and timed out at 390 px, and the
mobile journey clicked the sidebar's workspace button. The wait now takes
the first visible shell element, and the journey opens New workspace from
All workspaces, as a phone user does.
2026-11-01 10:56:12 +01:00
shumeiko.it
4d54612374 chore: version the desktop app 1.0.0 to match the installer
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.
2026-11-01 10:15:21 +01:00
shumeiko.it
0e2f3197eb docs: describe the release workflow now that it is merged
The architecture guide, AGENTS.md and the threat model said releases were
built by hand or Windows-first; ADR-0009 still listed the release
workflow as future work. The Windows build guide named the missing
Settings > API Keys tab.
2026-11-01 02:21:20 +01:00
shumeiko.it
608c804482 Merge P2.4: README and documentation for the community edition 2026-11-01 02:20:13 +01:00
shumeiko.it
10c013efcd Merge P1.3d: unsigned release workflow for three systems 2026-11-01 02:20:13 +01:00
shumeiko.it
b156072285 chore: drop billing and team variables from .env.example, add the installer README
.env.example described Stripe, Clerk, MinIO and the team server, none of
which the community edition runs, and sent users to a Settings tab that
does not exist. The web UI no longer names a person as author, and the
installer package gets the README its files list promised.
2026-11-01 02:10:01 +01:00
shumeiko.it
74200d46e8 fix: five defects found while rewriting the docs (UF-061 to UF-065)
- 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).
2026-11-01 02:08:57 +01:00
shumeiko.it
e34f95ec3c docs(oss): describe the release workflow in the Windows build guide (P1.3d)
The guide now says the release workflow builds Windows on windows-latest
with NSIS and MSI, and shows how to pack the server archive and run the
installer and desktop smoke tests locally.
2026-11-01 02:08:36 +01:00
shumeiko.it
687e3b86c7 ci(release): replace the commercial pipeline with an unsigned build for three systems (P1.3d)
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.
2026-11-01 02:08:31 +01:00
shumeiko.it
a73abd4d54 feat(scripts): add release smoke tests for the installer and the desktop app (P1.3d)
scripts/release-smoke.mjs runs on every release target:

- installer: installs the server archive with packages/launcher into a
  temporary directory, requires a clean doctor report (only the PATH
  warning is allowed), starts run on a free port with a temporary data
  directory, waits for /health, stops it and uninstalls;
- desktop: starts the packaged app (an executable or a macOS .app) with
  a temporary data directory, waits until its sidecar answers /health on
  127.0.0.1:3333, then stops the app and the sidecar and checks that the
  port is released.

The process tree is stopped through the process group on macOS and
Linux and with taskkill /T on Windows. The tests run both modes against
stand-in payloads.
2026-11-01 02:08:15 +01:00
shumeiko.it
ea837895e8 refactor(tauri): drop the certifier-only WebView debug port (P1.3d)
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.
2026-11-01 02:08:08 +01:00
shumeiko.it
87c1d398f9 docs: add desktop app update and uninstall steps to the install guide (P2.4) 2026-11-01 02:02:50 +01:00
shumeiko.it
dd6564451a docs: bring the command and local API references up to date (P2.4)
commands.md lists all 23 registered slash commands with their working
aliases and drops the FTS5 and two-mind wording. api.md explains the
bearer session token and that the API is internal, fixes the session
route parameters, lists the memory routes served through the memory
contract, the current chat stream events and the permissions body, and
removes the team, import and KVARK enterprise-pack routes.
2026-11-01 02:01:57 +01:00
shumeiko.it
94d54c4188 docs: rewrite the troubleshooting guide for this edition (P2.4)
Cover the unsigned installers, the server installer's error messages,
the desktop startup log, ports, models, memory on mem0 (including the
embedder mismatch) and the data directory. Drop team mode, the .mind
files, FTS5, docker compose for LiteLLM, the Node-on-PATH requirement
of the old desktop app and the invented cost per conversation.
2026-11-01 01:59:25 +01:00
shumeiko.it
834096146e docs: update the capabilities and connectors guides for this edition (P2.4)
Remove KVARK enterprise connectors, the 120+ package count and the
curl examples, which no longer work without the session token. Describe
Skills Hub, the marketplace scan as the code applies it, MCP Hub, the
30 native connectors, the approval modes, and the messaging channels
with the whatsapp-web.js warnings and browser download.
2026-11-01 01:58:42 +01:00