The composer textarea drew its own focus ring inside the rounded box, which
already turns amber on focus-within. The ring is gone; the box's border stays
the focus indicator (8.14:1 dark, 4.92:1 light against the composer).
With the full-width sidebar every item showed a hover hint that repeated its
visible label, and the part of the hint that reached past the sidebar was
hidden wherever the main area had content: the hint rendered inside the nav,
and the nav and <main> are sibling z-10 layers.
Sidebar hints now show only on the icon rail below lg, where they are the
only label, and render in document.body through a new opt-in `portal` flag
on HintTooltip. Other hints keep rendering in place, since several sit in
overlays above z-50 where a portaled hint would end up underneath.
The OAuth routes started a module-level cleanup interval that was never
cleared or unref'd. The service's SIGTERM/SIGINT handler closes the server
and relies on the event loop going empty, so the process kept running: a
first Ctrl+C in `npx waggle` or `npm run dev:server` left it alive, and
SIGTERM never ended it. The interval is now unref'd.
The launcher tests left two `waggle` processes behind on every run: they
stopped `npx` but not the waggle process it started. They now start it in
its own process group and stop the whole group, with a SIGKILL fallback,
and a new test checks that the built CLI exits by itself after SIGTERM.
Core keeps only shared infrastructure, so InstallAuditStore leaves it and
lives in packages/server/src/local/install-audit.ts. The trail itself stays:
the Audit and Activity tabs, the extend and export routes, and the threat
model entry keep working on the same waggle.db table.
- @waggle/shared gets RecordAuditInput and the narrow InstallAuditRecorder
(record only), which the agent's skill tools now depend on.
- The server creates the audit table before the one-time legacy copy, which
no longer constructs it in core.
- UF-040: GET /api/debug/logs called prepare() on the store's private db
wrapper, which has none, so the support bundle never carried recent
installs. It now reads them through getRecentSummary().
- 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 isolation journeys (B2.4, U2.3, U2.4, U9.3) create their workspaces
first. They used made-up workspace ids, which the sidecar silently
turned into personal memory, so they never compared two workspaces;
such writes are now refused (UF-039).
- J3f follows the Memory Center on the memory contract: Erase removes
every memory saved from the same chat and is offered only for memories
with a chat session; the erased-sources panel is gone.
POST /api/memory/frames, /api/quick-capture and the Memory Center's
POST /api/memory saved a memory meant for an unknown workspace into
personal memory, which every workspace reads. They now answer 404
workspace_not_found and write nothing; a request without a workspace
still goes to personal memory.
AGENTS.md no longer describes memory as half-migrated or asks for
build:packages before running the sidecar, lists the tsc -b build and the
test typecheck among the checks, and drops the removed weaver package.
ADR-0007 and ADR-0008 record that core no longer re-exports the legacy
substrate and that sqlite-vec is gone.
- 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.
The checkout-queue test searches memory for 'SSE resilience test frame'. The
text used to reach mem0 only through the background copy of the seeded
legacy personal.mind; write it with server.memory instead.
The live external-agent test (skipped unless WAGGLE_LIVE_EXTERNAL_AGENTS=1)
looked up run memory receipts as frames in server.multiMind and
server.mindCache, which the server no longer has. Look them up with
server.memory.get and check that personal and workspace receipts sit in
their own scopes. Also type the prompt assembler's bulk fixture as
RecallFrame.
- cli: delete real-session-simulation.ts, a manual script that populated a
hard-coded Windows .mind file through the old Orchestrator API.
- cli runtime: @waggle/core no longer depends on hive-mind-core, so the
packed closure does not include it.
- marketplace: rename the local marketplace schema constant so it is not
mistaken for the memory engine's SCHEMA_SQL.
- prompt assembler harnesses (v4 and v5): prime an in-memory contract store,
snapshot its memories and replay them into a fresh store per condition
instead of copying a MindDB file; the identity card is created per
orchestrator. They had also drifted from the current Orchestrator API
(config takes memory, buildSystemPrompt is async).
- prompt assembler unit test: build RecallFrame fixtures, the type the
assembler consumes, instead of legacy MemoryFrame rows.
- M3c integration: drop the knowledge-graph Ontology case; the knowledge
graph is not part of v1 and core no longer exports it.
- harvest-provenance: tested the removed harvest pipeline (RawArchive and
frame metadata), which no longer exists.
- benchmarks: drop the FTS5 frame search and frame/session write
benchmarks; they measured the legacy engine only.
- trust wiring: read install_audit from waggle.db through the server; the
old checks read a legacy personal.mind that nothing writes any more.
- data dir: a fresh install is marked by waggle.db, not personal.mind.
- backup: expect waggle.db and memory/ in the archive.
- cross-platform: replace the MindDB block with waggle.db checks (file, WAL,
foreign keys) and memory round trips (plain, Unicode, 100 KB) through
server.memory. FTS5 and session CRUD were legacy-engine features.
- store fixtures (install audit, cron) open WaggleDB instead of MindDB.
The server no longer opens personal.mind, so tests build it on an empty
data directory. The /memory command test seeds its two memories through
server.memory and now checks that the seeded text is found.
The persona memory-denial and cron Loop tests counted rows in the legacy
personal and workspace minds, which nothing writes any more. Count
server.memory per scope (and origin 'loop' for the truncated Loop report)
instead, and stop seeding a personal.mind the server no longer opens.
- install audit: build fixtures on WaggleDB, the store's real home; drop the
substrate SCHEMA_SQL parity half and the two MindDB-only recovery cases
for rows stranded in install_audit__mig_old.
- workspace manager: create() and ensure() no longer leave a workspace.mind;
getMindPath tests create the legacy file themselves. Drop the
MultiMindCache cases (reopen of a missing mind, post-resolution junction
swap): they tested the legacy cache, not the manager.
- transformers model load: use core's own in-process reranker.
The local sidecar has no /api/team/* routes since P1.1.
- Remove searchTeamMemory, getTeamMembers, getTeamActivity and
getTeamMessages from the adapter.
- Mission Control loses its Team and Activity tabs (both read the team
server) and keeps the fleet view, with its own load-error state.
- Drop the stale adapter mocks from the web tests; the Mission Control
test checks that no team tab is offered.
createTeamTools and createLocalTeamTools called /api/teams/* and
/api/team/* on a team server. Nothing registered them: not the
sidecar, the CLI, the team server or the worker.
packages/server/src/benchmarks held a LoCoMo failure-mode aggregator and
an LLM judge ensemble for the old memory engine benchmarks. Nothing in
the sidecar imports it and no npm script runs it; its inputs lived in
the root benchmarks/ directory that P2.2 already removed. Judge and eval
loops are also out of the community edition (AGENTS.md, rule 4).
The command bar could still offer "WaggleDance" and "Team" (governance)
as navigation targets, but those screens and app ids are gone from the
web app, so the frontend could not route them. Also drop a comment that
pointed at the removed WaggleDance routes.
- The WaggleDance routes left the sidecar with team mode, so the
x-waggle-run-token header no longer opens /api/waggle-dance/signal or
/api/waggle-dance/signals. A run token still authenticates only as a
Bearer on /v1/chat/completions (OpenClaw).
- Remove the session inactivity timeout. It switched on only in team
mode, when CLERK_SECRET_KEY was set.
Memory lives in the mem0 store and the knowledge graph is not in v1
(ADR-0002, ADR-0007).
- The CLI system prompt listed query_knowledge, a tool the community
edition does not register. It now lists search_all_workspaces, which
the orchestrator does provide.
- The default identity no longer claims "persistent memory (.mind file)"
or "knowledge graph queries".
Team mode is not part of the community edition (ADR-0003), so the CLI
no longer detects or switches to it.
- Remove the mode detector, the --local and --team flags, the Clerk
browser login (/login, /logout, /whoami) and /mode.
- Remove the /admin command and its team-server REST client.
- The welcome banner drops the Mode line.
- The installed-REPL test starts plain `waggle` and checks that the team
commands are gone.
secret-store.test.ts covers get, set, setAsync, writeBatch, delete,
deleteAsync, list and has through the interface. vault.test.ts keeps what is
specific to the file backend: encryption, the key file and the Windows ACL.
Connectors, the connector SDK and registry, setup-connectors, provider-env,
the LiteLLM runtime config and the sidecar's `vault` decoration only read and
write secrets, so they now take the SecretStore interface. VaultStore is still
constructed in the sidecar and the service startup, and its file format is
unchanged. AGENTS.md now points at the interface.
needsMigration and migrateToMultiMind moved a pre-M4 default.mind to
personal.mind at startup. The community edition has no installs with that
layout, so the module, its export, the startup step, its "migration" progress
phase and the default.mind first-run check go.
VaultStore.migrateFromConfig had two callers, both in the server. It is now
copyProviderKeysToVault in provider-env.ts, next to
migrateLegacyProviderKeysToVault, with the same rules: copy keys that have a
value, keep keys the vault already holds, store models and baseUrl as metadata.
Its tests moved from core to provider-env.test.ts.
getConnectorCredential, setConnectorCredential and setConnectorCredentialBundle
are now plain functions over a SecretStore in
packages/agent/src/connectors/connector-credentials.ts. The secret names,
metadata layout and the rule that tokens never go into plaintext metadata are
unchanged, so existing vault files keep working.
A bundle still lands as one update: SecretStore gains writeBatch, which
VaultStore applies with a single vault-file replacement.
Connector tests seed a Map-backed SecretStore instead of mocking VaultStore
methods; the helper tests from core and server moved to the agent package.
- 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.
- @waggle/core no longer re-exports @waggle/hive-mind-core and no longer
depends on it.
- The server no longer opens personal.mind or a cache of workspace minds;
the legacy files are only read by the one-time copies of legacy data.
releaseWorkspace closes the workspace's sessions and detaches it from the
shared orchestrator.
- WorkspaceManager stops creating an empty workspace.mind.
- memory-center-legacy.ts had no callers left and is removed.
- build:packages no longer builds hive-mind-core and wiki-compiler; the
sidecar aliases the memory packages to source instead.
- mem0ai stays external in the sidecar and launcher bundles: it imports a
client for every provider it supports on demand, and bundling it failed on
the optional peers Waggle does not install. The launcher declares mem0ai
and no longer needs sqlite-vec.
- adapter: memory ids are strings; single-memory calls take only the id
(no ?mind= disambiguation). searchMemory takes the workspace as its own
parameter. New getMemoryCapabilities / setMemoryExtraction. Removed:
incrementFrameAccess, getMemoryOriginalSource, listSuppression,
allowReimport, getWeaverStatus, and the dead importPreview, importCommit
and getWikiWatermark. eraseMemory takes { id } or { sessionId }.
- memory-features reads GET /api/memory/capabilities for the knowledge
graph; history import, wiki, hooks, Room and the memory MCP stay hidden
(ADR-0002). useMemoryCapabilities re-renders the Memory screens.
- Settings > General has a Memory toggle for background fact extraction.
- Memory Center: the confidence filter, the erased-sources panel, the
original-source view and the Deprecated chip are gone; Erase forgets
every memory saved from the chat a memory came from and is offered only
for memories with a chat session. Memory kinds follow the contract.
- Trust views show short memory labels for the new string ids and drop the
per-row "not scored yet" badge (v1 stores no confidence).
- The Weaver maintenance view and the Cockpit weaver card are removed
(the weaver package and its routes are deleted).
- Timeline uses the contract kinds and maps important/temporary
importance.
Logs UF-033 (search scope sent as the workspace id), UF-034 (importance
mapping) and UF-035 (restore over open databases, open).
The memory HTTP API reads and writes server.memory instead of the legacy
MultiMind, FrameStore, SessionStore, KnowledgeGraph, MindErasure,
SuppressionStore and RawArchive objects.
- memory.ts: search (personal, workspace, all, global), frames list, write,
edit and delete, stats and quick capture on the contract. Ids are strings.
The access-count route is gone. New GET /api/memory/capabilities and
PUT /api/memory/settings { extraction } for background fact extraction.
- memory-center.ts: list, get, create, patch, archive, confirm, trace,
delete, erase and merge on the contract. Archive sets importance
'temporary' (skipped by recall) and remembers the old importance; confirm
stamps metadata.confirmedAt; 'unreviewed' means extracted in the
background and not confirmed. Erase forgets one memory or every memory of
a chat session. The original-source and suppression routes are removed:
there is no raw archive and no harvest to re-import from.
- knowledge.ts returns an empty graph (not part of v1).
- export.ts writes memories/personal.json and memories/workspace-<id>.json
from the contract.
- identity.ts loses a dead resolver; the erase safety check recognizes
waggle.db.
- memory-records.ts holds the scope, status and creation-time helpers.
- normalizeToMemory stays in memory-center-legacy.ts until home.ts and
artifacts.ts read memory through the contract.
- @waggle/shared MemoryKind follows the contract's kinds; Memory gains
origin and sessionId.
Tests: new memory-routes and memory-center tests on the in-memory store;
local-mode and data-export tests seed memory through the contract; tests of
removed behaviour (source, suppression, sticky erasure, graph projection,
legacy normalizer, old erase and stats) are deleted.
The comprehensive and hard-persistence suites open a data directory the
way the REPL does: mem0 in <dir>/memory (word embedder, no model download)
and waggle.db for the profile card and tasks. Persistence across sessions
now also checks identity and tasks after reopening.
The packaged-runtime tests install @waggle/memory-contract and
@waggle/memory-mem0 with the CLI (the weaver package is gone) and check
that the REPL creates the memory store and waggle.db instead of
default.mind.
Deleted: T4 and T18 (knowledge graph entities and their persistence) and
the knowledge-graph steps of the hard-persistence run; the graph is not in
v1 (ADR-0002).
Rewrites the orchestrator, recall, compaction, save_memory and assembler
suites for MemoryStore (createInMemoryMemoryStore; mem0 with the word
embedder for the M3b integration test), string ids, async prompt building
and setWorkspace(). Creation times are set with fake timers, since a write
cannot set its own. Stores of Waggle's own data (identity, traces) are built
on WaggleDB; the session-manager stubs use the new create() signature.
Kept behaviour: importance lane (cap, active scope, temporary exclusion),
profile and event lanes, date window and its fallback, catch-up, injection
blocking of recall and preloaded context, autosave safety, decision consent,
compaction update-in-place, reranker wiring.
New tests: recall with a workspace active versus personal only;
fetchRecentMemories ordering; toRecallFrame; context loader; save_memory
routing, dedup, rate limit, dramatic-claim downgrade and contradiction
scope; search_memory and search_all_workspaces; pattern write-back kinds,
scopes and sign gate; read_other_workspace; reranker off unless
WAGGLE_RERANKER=1, wider rerank pool, failure fallbacks.
Deleted, because the behaviour is gone:
- w46-rawdetail-recall.test.ts: the raw-turn (RAWDETAIL) recall lane.
- orchestrator.test.ts, query_knowledge (3 tests) and the recall-hardening
M4 "Key Knowledge" test: the knowledge graph is not in v1 (ADR-0002).
- orchestrator-context-frames "profile override": scoring profiles.
- Assertions on I/P frame types, GOP sessions, FTS rows, the "Memory Facts"
lane, cognify stages and session/entity counts were replaced by the
equivalent contract-level checks.
The pattern write-back pushed a style note into its "saved" list even when
the memory store answered 'unchanged', so the chat route announced
"Auto-saved 1 memory" on every repeat of the same style signal. The legacy
code checked for the note before writing; the contract port lost that.
A style note that already exists is now neither written nor reported.
Other write-back saves keep reporting repeats, as before the port.
Not logged in upstream-fixes.md: the defect came with the P1.5 port and
does not exist in the commercial product.
- Workspace sessions, fleet runs, agent groups, loops, the file indexer,
external tool runs, chat and the health endpoint are checked against the
memory store instead of .mind files. Assertions on mind-cache pins and
releases go with the pins; the drain and cancellation checks stay.
- Delete the sticky-erasure test (harvest import was removed) and the
session-distillation test (distillation on workspace activation was
removed).
- The saved-history retry test checks the conversation only: the failed
user turn is kept in workspace memory by design (#3).