fix: filedrop reply routing + debug logging + workspace deploy (#151) #153
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Competitor
Kind/Documentation
Kind/Enhancement
Kind/Epic
Kind/Feature
Kind/Security
Kind/Story
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Scope/Core
Scope/Cross-Plugin
Scope/Plugin-System
Scope/Single-Plugin
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ultanio/cobot!153
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/filedrop-reply-logging"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
1. Filedrop reply mechanism
Filedrop plugin now implements
communication.sendviahandle_send(). When the loop plugin processes a filedrop message and generates a response,comm.send()routes it back through filedrop to the original sender. The recipient is extracted from the inbox path inchannel_id.2. Debug logging
filedrop: log_debug on poll, read, move-to-processed, sendloop: log_debug on message handling (sender + channel_type)3. Workspace context deployment
deploy.shnow copiesworkspace/*.mdto~/.cobot/workspace/(SOUL.md, TOOLS.md, HEARTBEAT.md)workspace/HEARTBEAT.mdwith filedrop check instructionsNote
This PR also includes deploy.sh fixes from #139/#149 since they haven't merged yet and all touch the same file. PR #150 can be closed if this merges first.
Closes #151