* refactor: multi-channel infrastructure with explicit channel/is_group tracking - Add channels[] array and findChannel() routing in index.ts, replacing hardcoded whatsapp.* calls with channel-agnostic callbacks - Add channel TEXT and is_group INTEGER columns to chats table with COALESCE upsert to protect existing values from null overwrites - is_group defaults to 0 (safe: unknown chats excluded from groups) - WhatsApp passes explicit channel='whatsapp' and isGroup to onChatMetadata - getAvailableGroups filters on is_group instead of JID pattern matching - findChannel logs warnings instead of silently dropping unroutable JIDs - Migration backfills channel/is_group from JID patterns for existing DBs Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: skills engine v0.1 — deterministic skill packages with rerere resolution Three-way merge engine for applying skill packages on top of a core codebase. Skills declare which files they add/modify, and the engine uses git merge-file for conflict detection with git rerere for automatic resolution of previously-seen conflicts. Key components: - apply: three-way merge with backup/rollback safety net - replay: clean-slate replay for uninstall and rebase - update: core version updates with deletion detection - rebase: bake applied skills into base (one-way) - manifest: validation with path traversal protection - resolution-cache: pre-computed rerere resolutions - structured: npm deps, env vars, docker-compose merging - CI: per-skill test matrix with conflict detection 151 unit tests covering merge, rerere, backup, replay, uninstall, update, rebase, structured ops, and edge cases. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat: add Discord and Telegram skill packages Skill packages for adding Discord and Telegram channels to NanoClaw. Each package includes: - Channel implementation (add/src/channels/) - Three-way merge targets for index.ts, config.ts, routing.test.ts - Intent docs explaining merge invariants - Standalone integration tests - manifest.yaml with dependency/conflict declarations Applied via: npx tsx scripts/apply-skill.ts .claude/skills/add-discord These are inert until applied — no runtime impact. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * remove unused docs (skills-system-status, implementation-guide) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
Intent: src/index.ts modifications
What changed
Refactored from single WhatsApp channel to multi-channel architecture using the Channel interface.
Key sections
Imports (top of file)
- Added:
TelegramChannelfrom./channels/telegram.js - Added:
TELEGRAM_BOT_TOKEN,TELEGRAM_ONLYfrom./config.js - Added:
findChannelfrom./router.js - Added:
Channeltype from./types.js
Module-level state
- Added:
const channels: Channel[] = []— array of all active channels - Kept:
let whatsapp: WhatsAppChannel— still needed forsyncGroupMetadatareference
processGroupMessages()
- Added:
findChannel(channels, chatJid)lookup at the start - Changed:
whatsapp.setTyping()→channel.setTyping?.()(optional chaining) - Changed:
whatsapp.sendMessage()→channel.sendMessage()in output callback
getAvailableGroups()
- Unchanged: uses
c.is_groupfilter from base (Telegram channels passisGroup=trueviaonChatMetadata)
startMessageLoop()
- Added:
findChannel(channels, chatJid)lookup per group in message processing - Changed:
whatsapp.setTyping()→channel.setTyping?.()for typing indicators
main()
- Changed: shutdown disconnects all channels via
for (const ch of channels) - Added: shared
channelOptsobject for channel callbacks - Added: conditional WhatsApp creation (
if (!TELEGRAM_ONLY)) - Added: conditional Telegram creation (
if (TELEGRAM_BOT_TOKEN)) - Changed: scheduler
sendMessageusesfindChannel()→channel.sendMessage() - Changed: IPC
sendMessageusesfindChannel()→channel.sendMessage()
Invariants
- All existing message processing logic (triggers, cursors, idle timers) is preserved
- The
runAgentfunction is completely unchanged - State management (loadState/saveState) is unchanged
- Recovery logic is unchanged
- Apple Container check is unchanged (ensureContainerSystemRunning)
Must-keep
- The
escapeXmlandformatMessagesre-exports - The
_setRegisteredGroupstest helper - The
isDirectRunguard at bottom - All error handling and cursor rollback logic in processGroupMessages
- The outgoing queue flush and reconnection logic (in WhatsAppChannel, not here)