Repository navigation
feat: add Publication history across CLI, MCP and desktop - #356
Merged
Merged
Conversation
This was referenced Oct 7, 2026
nokhodian
added a commit
that referenced
this pull request
Oct 7, 2026
fix(publication): follow-ups from #356 review
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.
Summary
Agents and workflows could publish content without a unified local history. Add a profile-scoped Publication section that records successful posts, comments, replies, articles, videos and shared-channel publications, with their exact content, returned identities and workflow/agent source.
publication list|get|register|stats, offline reference, and apublication.registernode for custom publishers.Type of change
Validation
go build ./...andgo build -tags nosocial ./...go test -p 2 ./...(5,876 tests)nosocialtests: publication, registration node, node registry, MCP and org grantsnpm test -- --maxWorkers=2)Notes for reviewers
Records remain profile-scoped; metadata capture excludes credentials and private destinations. MCP registration retains the existing mutation gate and org grant mode is unchanged. Registration does not send content. Discord channel metadata is used to distinguish shared channels from private messages.
Prepared against current
masterin an isolated worktree. Existing workspace dependency/generated-file changes and the separate coder workflow-guidance commit are excluded. The coder publication prompt pins the turn's CLI, profile and custom database. Host-dependent test fixtures were corrected without changing runtime discovery behavior; broad checks use reduced concurrency after an initial timing failure in the existing cancellation test.