Extract agent_chat message bus to NOVA-Openclaw/agent-chat (#579) - #586
Merged
Conversation
added 5 commits
August 11, 2026 16:28
…etection (#579) - Remove agent_chat schema/migrations, plugin source, migration scripts, and legacy installer tests from nova-mind. - Add lib/agent-chat-peer-detection.sh for read-only detection of an optional agent_chat bus via postgres.json section or psql probe. - Delegate registration/plugin install to AGENT_CHAT_REPO checkout when a bus is present; warn (but continue) on missing checkout or unreachable bus. - Add schema-version handshake warning (KNOWN_COMPATIBLE_AGENT_CHAT_SCHEMA_VERSION=1). - Update agent-install.sh to source peer-detection lib and invoke _agent_chat_integrate_peer at the appropriate point. - Replace tests/install/test_agent_chat_installer.bats with focused peer-detection coverage in tests/install/test_agent_chat_peer_detection.bats.
- Point all agent_chat runtime/provisioning documentation at the dedicated NOVA-Openclaw/agent-chat repository. - Remove references to installer-managed agentChatDatabase key and the production-mutation guard now owned by the peer repo. - Update schema-reference and database-config guides to reflect that agent_chat schema/migrations/plugin no longer live in nova-mind.
- Add tests/TEST-CASES-ISSUE-579.md mapping acceptance criteria to concrete test cases for the agent_chat extraction. - Add reports/SE643-step2-agent-chat-extraction-validation.md capturing consumer/credential analysis and gaps discovered during assumption validation.
…version (#579, QA F-1)
Audit and correct documentation across nova-mind against the final tested code on feat/579-extract-agent-chat, per SE run #643 step 9. - ARCHITECTURE.md: fold #579 into the #320 agent_chat exception note (5 spots) — the bus's schema/plugin now live in NOVA-Openclaw/agent-chat, not just a separate database within this repo. - CHANGELOG.md: add missing agent-chat-extraction-579 batch entry (Removed/Added/Fixed/Documentation/Known follow-ups/Issues Closed), cross-referencing agent-chat#1, agent-chat#2, nova-mind#582/#584/#585 and the TC-04 adoption-rehearsal precondition from the step-8 QA report. - cognition/CHANGELOG.md: add Removed section documenting the cognition/focus/agent_chat/, database/agent-chat/, and scripts/agent-chat-migration/ deletions (the implementer's diff had no cognition/CHANGELOG.md entry for the removal itself). - memory/CHANGELOG.md: add Removed section noting the agent_chat table documentation de-scoped from memory/README.md and memory/docs/database-schema-guide.md. - psyche/ARCHITECTURE-agent-chat.md: add top-of-file pointer to the dedicated repo as the canonical source for schema/plugin/security-model, clarifying this file's remaining scope (psyche-level design). - cognition/ISSUE-147/148/149-test-cases/151: update stale cognition/focus/agent_chat/ path references and pre-#579 architecture claims in historical issue records with accurate status notes; issue content left otherwise intact as historical record. Verified via full audit of implementer-touched docs (ARCHITECTURE.md, README.md, memory/*, cognition/*, database/schema-reference.md, psyche/ARCHITECTURE-agent-chat.md, lib/agent-chat-peer-detection.sh) against the actual shipped code, plus SE643 step2/6/7/8 reports. No code, test, or report files modified. Refs nova-mind#579
This was referenced Aug 12, 2026
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
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.
Closes #579
Removals
The
agent_chatmessage bus has been extracted to NOVA-Openclaw/agent-chat. This PR removes the now-redundant in-tree copies:database/agent-chat/— schema and migrationscognition/focus/agent_chat/— legacy test suite and tsconfigscripts/agent-chat-migration/— migration/decommission/audit toolingagent_chatfunctions, including the CRITICAL: installer agent_chat provisioning targets shared cluster — staging install mutated PRODUCTION agent_chat (broke send_agent_message ecosystem-wide) #569 refusal guard — staging isolation now holds by construction (the bus lives in its own repo/DB context, so the guard that prevented accidental cross-environment installs is no longer needed here)Addition
lib/agent-chat-peer-detection.sh— detects a sibling checkout of theagent-chatrepo (${AGENT_CHAT_REPO:-$HOME/agent-chat}), DB-probes for presence of the bus, and performs a schema-version handshake with directional warnings (ahead/behind) when versions don't match.tests/install/test_agent_chat_peer_detection.bats— coverage for the above.Related but not closed by this PR
Addresses #395, #409 — related cleanup that this extraction advances but does not fully resolve. Not using "closes" for these; they remain open pending further verification.
Test evidence
agent_chat_staging_643Full evidence:
reports/SE643-step7-staging-test-execution.md,reports/SE643-step8-qa-validation.md.Follow-ups filed
Docs audit (step 9)
psyche/ARCHITECTURE-agent-chat.mdhas been re-scoped to reflect that the bus now lives in the externalagent-chatrepo; this repo's docs describe integration/consumption, not ownership of the bus internals.Production deploy (step 11 of this SE run) is gated on a data-bearing TC-04 adoption rehearsal, per QA (
reports/SE643-step8-qa-validation.md§3). Do not deploy to production until that rehearsal is complete and signed off.