Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> # Conflicts: # src/store/schema.ts
…in integration Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tion Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The owner's fleet runs on surfaces that cannot be pushed to (Freebuff tabs, AGY, the Codex app, Claude Code). The Brain becomes their check-in desk: - worker profiles bind each agent to its surface, a non-secret account label and optionally an exclusive resource key, so one BYOK key carries exactly one active worker while a subscription can carry many tabs; - the turn protocol records start/end (working, needs-task, awaiting-commit, blocked, paused) and answers with the ping: unread messages, the next or claimed queue task and whether the host has room for test/build/worktree; - the integrator approves a pending commit through the worker's inbox; - the board shows every worker once, with account, turn state, unread messages, task, leases, worktree branch and uncommitted files, overlaps and attention flags (awaiting-commit, needs-task, blocked, quota, stale); - host resources (disk, RAM, CPU) and reported account quotas drive admission: no build/install/worktree under 20 GB free, no tests under 5 GB. Reachable as `plugbrain swarm …` (store-direct, no Core key needed), as HTTP routes (/api/agent/profile|turn|approve-commit, /api/agents/board, /api/resources[/quota]) and as MCP tools (swarm_turn, swarm_board, swarm_resources). Labels, notes and summaries refuse credential-shaped text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A retired worker keeps identity and history, frees its resource key and leaves the fleet count. Used for legacy agents from earlier missions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CLI workers (Freebuff, AGY, Codex) can now declare the paths they write. A second writer on the same path is refused with the holder named, and the board shows every lease under its worker. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The live planet held 260 000 files, 4.7 million symbols and 16.4 million edges from 66 checkouts, a handful of them current. Narrowing the selection hides those rows but the indexer cannot remove them: every file delete cascades through edges.src_file and edges.dst_file, which are indexed only behind workspace_id, so each one paid two scans of the edge table (700 ms each on the live store), about four days for the backlog. `plugbrain planet prune` deletes set-wise in bounded batches with the WAL truncated in between. The foreign-key actions are read from the schema and replayed explicitly, each child is reached through an index proven by the query plan before the first batch, ownership is mirrored onto path_owner, nothing is tombstoned, and PRAGMA foreign_key_check closes the run. `plugbrain compact` merges the FTS indexes and vacuums, refusing when the disk cannot hold the copy. A write through the access layer now names its checkout. Without it the row was outside every live projection until the next full pass, and a prune took it for a pre-planet leftover. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep the seven Windows process-ownership journeys on Windows and verify the explicit no-launch refusal on Linux and macOS. Profile, argument, and prompt tests remain cross-platform.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem und Ergebnis
Dieser Draft führt die zuvor lokal entwickelte Brain-Flottensteuerung und die administrativen Queue-Operationen zur Prüfung auf Linux, macOS und Windows zusammen. Er umfasst Supervisor/Runner, Modellfamilienprüfung beim Review-Routing, Zustellung, Koordinationsereignisse, Dokumentation und die Turn-Ansicht.
Der erste CI-Lauf deckte plattformspezifische Testfehler und einen echten Fehler bei der Abgabe von Belegen über Windows-Kurzpfade auf. Vier Folgecommits beheben diese Befunde:
Aktuelle Kandidatenrevision:
2a580931686dcb760ed8609c68dff8f18e3b30f0.Validierung
Auf der vorherigen Revision 2dbabd3 unter Windows/Node 24:
CI-Lauf 36370711537 bestand unter Windows. Linux und macOS fanden genau einen Fehler im neuen Testaufbau: Bei der Registrierung fehlte das Pflichtfeld account. Folgecommit 2a58093 ergänzt dieses Feld, verwendet den vorhandenen Fixturemodus ok und zeigt Registrierungsfehler im Assertion-Text. Unabhängiger Google-Review PASS, lokale Runner-Tests 11 PASS / 1 SKIP / Exit 0, Typecheck Exit 0. Die Nicht-Windows-Prüfung muss die nächste exakte CI bestätigen. Die früheren Paketbau- und UI-Typecheck-Ergebnisse bezogen sich auf den vorherigen Integrationsstand und ersetzen diese Prüfung nicht.
Git-Historie
Commit
467e5bbverbindet die zuvor unabhängigen Historien mit öffentlichem main9b1b52b. Sein Quellbaum ist exakt identisch mit dem lokal geprüften Integrationsstand9dd3e10. Die vier CI-Korrekturen folgen als gewöhnliche Commits. Vor der ersten Veröffentlichung wurden zusätzlich 1383 neue Git-Blobs auf Geheimnisse geprüft; die elf Treffer waren belegte synthetische Erkennungs- und Canary-Fixtures.Freigabegrenzen
Draft zur CI und Quellprüfung. Kein automatischer Merge und kein Release. Der Owner verlangt signierte Installer vor einer lokalen Installation. Es werden hier keine Installationspakete veröffentlicht. Installiert bleibt 0.3.0; die Paketversion im Quellstand lautet 0.3.1.
Update 29.09.2026
Aktueller PR-HEAD:
ea2260a5f59d84c5daccf1835b1e4e82b6f68bc4. Der Plattformfix lehnt den Supervisor auf Nicht-Windows vor Datenbankzugriff ab und prueft Standardlauf sowie--once. Der exakte CI-Lauf ist auf Linux, macOS und Windows gruen; der enge Fix erhielt ein unabhaengiges Cross-Family-Review mit PASS. Der PR umfasst weiterhin 123 Dateien und bleibt fuer eine vollstaendige Integrationspruefung Draft. Der oeffentliche v0.3.1-Quellstand wurde separat ueber PR #1 in main gemergt; ohne signierten Installer erfolgt kein Release oder lokales Update.