fix(distill): unify Honcho distill author peer to family-assistant#327
Merged
Merged
Conversation
Distill messages were scattered across 4 author peers (hermes/dungae/ soonwook/nosuk) because the seed template supplies peerName=<NODE_NAME> while the distill hooks read aiPeer, falling through to a hardcoded "dungae" default. Verified live: 144 distill msgs, only 50 under hermes. - honcho-push.sh / queue-drain.sh: fallback "dungae" -> "family-assistant" - honcho.template.json: add "aiPeer":"family-assistant" so freshly seeded nodes converge on one shared AI author peer. Design A (single shared AI peer, harness-neutral name); forward-only cutover (Honcho has no peer rename/merge). distill-only scope; recall peerName unchanged. Operator-approved 2026-07-08. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
seoseo-ai
approved these changes
Jul 8, 2026
seoseo-ai
left a comment
Collaborator
There was a problem hiding this comment.
CI all green (7/7: codeql, harness-ci validate/lint/secret-scan, bridge-tests 3.11/3.12); mergeable. Distill-only scope, tests pass (honcho-push 17/0, queue-drain 16/0), operator-approved design per PR body. Auto-approved per PR-first policy (jinon86 author needs seoseo-ai reviewer).
seoseo-ai
pushed a commit
that referenced
this pull request
Jul 8, 2026
…er guard (#328) Fleet rollout tooling for unifying the distill author peer to family-assistant (follow-up to #327). - scripts/converge-distill-peer.sh: idempotent node-local helper. --check reports the resolved aiPeer, --apply rewrites an explicit override (flat .aiPeer or nested .hosts.hermes.aiPeer) to family-assistant with a backup, --verify posts a labelled canary and confirms the author peer. Nodes with no explicit override converge via the #327 fallback alone. - honcho-push.sh / queue-drain.sh: treat an unfilled seed placeholder baseUrl (e.g. "<HONCHO_BASE_URL>") as unconfigured so a freshly seeded honcho.json cleanly no-ops instead of failing /health and queuing junk. Tests: honcho-push 17/0, queue-drain 16/0. Convergence helper validated across flat/nested schema, idempotent re-run, and placeholder cases. Co-authored-by: jinon86 <247078695+jinon86@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Unify the Honcho distill author peer to a single, harness-neutral identity:
family-assistant.Why (root cause — verified live 2026-07-08)
Scanned 326 sessions / 4,137 messages in the
seoyoon-familyworkspace. Distill messages (source=claude-code-distill) were scattered across 4 author peers:Only 35% landed on
hermes. Root cause is a config-schema drift: the seed template suppliespeerName=<NODE_NAME>(used for recall), but the distill hooks read a separateaiPeerfield and fall through to a hardcoded"dungae"default when it's absent. Nodes seeded at different times diverged.Change (distill-only scope)
honcho-push.sh/queue-drain.sh: fallback"dungae"→"family-assistant"(drift safety net).honcho.template.json: add"aiPeer": "family-assistant"so freshly seeded nodes converge on one shared AI author peer.peerName(recall axis) unchanged.Design decision
Design A — single shared AI peer, harness-neutral name. Forward-only cutover (Honcho SDK has no peer rename/merge/message-move; existing history stays under old peers by design — "분절 수용"). Operator-approved.
Evidence
honcho-push.test.shPASS=17/0,queue-drain.test.shPASS=16/0.jqtemplate validation OK;bash -nOK on both hooks.Follow-up (not in this PR)
Per-node
~/.hermes/honcho.jsongets explicitaiPeer=family-assistantvia A2A fan-out (11 nodes), plus canary validation on gwakga.🤖 Generated with Claude Code