Sibling Sync
Bilateral reconciliation of SYNERGY-*.md and UPSTREAM-*.md files between
this project and its sibling vp-* projects. Read-only by default — surfaces
drift, reciprocal gaps, stale-aligned rows, and status drift across sides
without mutating anything. The opt-in --auto-reciprocate flag writes
reciprocal entries to the sibling's SYNERGY file via per-entry confirmation.
Companion to /vendor-sync (which handles upstream → project drift); this
skill handles peer-to-peer drift between siblings registered in
.claude/synergy-registry.json.
Design Rationale
The bd v1.0.0 Integration Charter
(gastownhall/beads@5d524cf7:docs/INTEGRATION_CHARTER.md) explicitly punts
cross-tracker orchestration out of bd's scope: bd will never grow a feature
that routes a cross-project item from project A's tracker to project B's
tracker. /sibling-sync is exactly the workflow-automation layer the Charter
defers to external tools — file-based reconciliation between sibling vp-*
projects, mediated by registries and confirmation prompts rather than
synchronous tracker calls.
This mirrors the rationale already cited by /synergy-tracker for keeping
cross-project state in SYNERGY-*.md plus Basic Memory rather than in bd.
Cross-skill boundaries
/sibling-sync is a comparison and reconciliation layer that sits alongside
the per-side logging skills. It owns nothing in Basic Memory and nothing on
this project's side of the SYNERGY/UPSTREAM files.
- Does NOT write SYNERGY entries on this project's side.
/synergy-tracker
workflow 1 (Log a synergy entry) owns logging on this side.
- Does NOT pull upstream subtrees.
/vendor-sync owns subtree pulls and
the upstream → project drift workflow.
- Does NOT write Basic Memory notes.
/synergy-tracker workflow 5
(Promote to Basic Memory) owns ## Cross-Project Synergy writes
to sibling entity notes; /upstream-tracker workflow 6 (Promote to Basic
Memory) owns ## Upstream Friction writes. Basic Memory write tools are
intentionally absent from this skill's allowed-tools.
- Does NOT write
## Trend Reviews entries to SYNERGY files. Those belong
to /synergy-tracker workflow 4 (Trend review (quarterly)). Even under
--auto-reciprocate, /sibling-sync only mirrors content entries into
reciprocal sections — never trend-review summaries.
- Stale-row detection is INLINE here for the threshold values used during
comparison runs. The canonical staleness-threshold definition lives in
/synergy-tracker workflow 4 (Trend review (quarterly)) — workflow 2 (Sync
sibling SYNERGY) below cites it. Per RETRO-10 YAGNI guard: extract this to
a shared helper only when a third skill needs the same logic.
- Surfacing reciprocal-friction findings is in scope; acting on them is
not. Workflow 3 (Sync sibling UPSTREAM) Mode B (see below) reads the sibling's
UPSTREAM-<this-project>.md to surface friction the sibling tracks about
this project. Filing the resulting work as bugs/features/opportunities on
this side is /upstream-tracker workflow 1 (Log a new entry)'s job.
Annotating the sibling's entry as resolved is /upstream-tracker workflow
3 (Resolve an entry)'s job, performed on the sibling's side. /sibling-sync
reports only.
- Orchestrator role for follow-up actions (v0.14.0). Workflows 2 (Sync
sibling SYNERGY) and 3 (Sync sibling UPSTREAM) end with a per-sibling
action menu (see "Action-menu protocol" below) that delegates writes to
the owning skill (
/vp-beads:synergy-tracker,
/vp-beads:upstream-tracker) via the Skill tool, or runs bd create
directly for beads issues. /sibling-sync still owns nothing in Basic
Memory and nothing in this project's SYNERGY/UPSTREAM files —
ownership boundaries are unchanged.
Registry and path resolution
Sibling projects are declared in .claude/synergy-registry.json (array of
{name, file, remote, bm-entity, relationship, local-path?} entries). The
optional local-path field gives the on-disk path to the sibling checkout
(relative paths resolve from this project root). When absent, fall back to
../<name>/.
.claude/synergy-registry.local.json is a gitignored companion that overrides
fields in the committed registry — same per-entry merge by name pattern as
.claude/vendor-registry.local.json — and can add fully-private siblings
(see "Private sibling handling" below). Resolution order:
- Read
.claude/synergy-registry.json.
- If
.claude/synergy-registry.local.json exists, merge it on top by name
key, in two modes:
- Override mode (entry
name matches a base entry): fields in
.local.json win; absent fields keep the base value.
- Private-add mode (entry
name not in the base registry AND its file
is a PRIVATE-SYNERGY-<name>.md value): the entry is added to the
merged result as a private sibling. The PRIVATE- prefix on file is the
marker (there is no boolean); it governs the restrictions below.
- Entries in
.local.json whose name is not in the base registry and whose
file is NOT PRIVATE-SYNERGY-* are ignored (backward compatibility —
typos and accidental entries stay silent).
- For each merged entry, resolve
local-path (registry value or
../<name>/).
- If the resolved path does not exist on disk, report informatively and SKIP
that sibling. Do not error out — continue with siblings that are
accessible.
Workflow 3 (Sync sibling UPSTREAM) additionally consumes the merged
.claude/vendor-registry.json (+ .local.json) to identify shared vendor
dependencies across siblings. (The vendor registry has no private-add mode —
private siblings are synergy-registry only.)
Private sibling handling
A private sibling is one whose merged registry entry has a
file: PRIVATE-SYNERGY-<name>.md value (added via private-add mode above, or —
in principle — a base entry, which the validator forbids because it would commit
the name). Its name lives only in the gitignored .local.json and
PRIVATE-SYNERGY-<name>.md; it must never reach a committed file. This skill
therefore treats private siblings under a strict read-vs-write split, keyed on
the PRIVATE-SYNERGY-* file predicate:
- Read (allowed) — hybrid read-diff. Unlike a public sibling's
glob-discovered
PRIVATE-SYNERGY-*.md overlay (which this skill never reads),
a private sibling's PRIVATE-SYNERGY-<name>.md is its registry file, so
workflows 1 (Discover sibling(s)), 2 (Sync sibling SYNERGY), and 3 (Sync
sibling UPSTREAM, Mode A only) read it to produce read-only diff findings.
Findings appear in the ephemeral terminal report only — never written.
- Write (blocked) — every committed surface. For a
PRIVATE-SYNERGY-*-filed
sibling:
- Reciprocation: workflow 4 (Apply reciprocation batch) skips it entirely
(writing
SYNERGY-<this-project>.md on the sibling's side would expose the
relationship).
bd create: the action menu suppresses the UPSTREAM "file beads issues"
option (a committed .beads/*.jsonl entry would leak the name) — findings
stay report-only.
- Logging on this side: any "log unreciprocated entry" follow-up routes to
the gitignored
PRIVATE-SYNERGY-<name>.md, never a committed
SYNERGY-<name>.md (delegated to /synergy-tracker).
- BM promotion: never (this skill has no BM tools;
/synergy-tracker
workflow 5 (Promote to Basic Memory) skips PRIVATE-SYNERGY-* siblings).
- UPSTREAM Mode B: out of scope for private siblings — an
UPSTREAM-<name>.md filename would itself leak the name. Workflow 3 (Sync
sibling UPSTREAM) runs Mode A (shared dependencies — names no sibling) but
skips Mode B for PRIVATE-SYNERGY-* siblings.
The PRIVATE-SYNERGY-* file predicate is the single structural marker — the
same prefix that keeps content outside the SYNERGY-*.md glob also gates every
write path here.
Workflows
Determine which workflow the user needs based on their request. If ambiguous,
default to running workflow 1 (Discover sibling(s)) followed by workflow 2
(Sync sibling SYNERGY) and workflow 3 (Sync sibling UPSTREAM) as a single
report. Workflow 4 (Apply reciprocation batch) only fires under explicit
--auto-reciprocate.
1. Discover sibling(s)
Resolve which siblings will participate in this run.
Steps:
- Read
.claude/synergy-registry.json. If the file does not exist, redirect:
tell the user no sibling registry is configured and offer to invoke
/synergy-tracker workflow 1 (Log a synergy entry), which will run the
guided registry creation flow at step 1b for the first sibling. If the
user names a sibling now, follow the synergy-tracker step 1b prose from
this conversation (re-reading
skills/synergy-tracker/SKILL.md workflow 1 (Log a synergy entry) step 1b
and applying its logic in-session — Claude Code has no actual
inline-skill-invocation mechanism, so this means executing step 1b's
instructions verbatim from sibling-sync's context). After the registry
is created, resume from step 2 below. Otherwise stop, and instruct the
user to invoke /synergy-tracker directly with the sibling name and
then re-run /sibling-sync.
- If
.claude/synergy-registry.local.json exists, merge it on top per the
per-entry merge rules in the Registry section above. This includes
private siblings — .local.json-only entries whose file is
PRIVATE-SYNERGY-<name>.md, which are added to the participating set (they
read-diff like any sibling but are blocked from every committed-write path —
see "Private sibling handling").
- If the user named a specific sibling in their request or argument, filter
the merged list to that entry. Otherwise, all merged entries participate.
- For each entry, resolve
local-path → ../<name>/ fallback. Probe each
resolved path with a directory existence check.
- Build the participation lists:
- Accessible siblings (path exists) — proceed to workflow 2 (Sync
sibling SYNERGY) and workflow 3 (Sync sibling UPSTREAM) for each. Mark any
private sibling (registry
file is PRIVATE-SYNERGY-*) with a [private]
label so the user can see which relationships are private.
- Inaccessible siblings (path missing) — report them so the user
knows what was skipped, with the resolved path and a hint that
.claude/synergy-registry.local.json can override the path
- Report the participation list before continuing.
Output:
Siblings participating:
- vp-knowledge → /Users/.../vp-claude (registry local-path)
- acme-partner → /abs/path/to/acme-partner [private]
Siblings skipped (path not accessible):
- vp-other → ../vp-other (set local-path in synergy-registry.local.json)
If no siblings are accessible, stop and report. The user can either correct
the paths via .claude/synergy-registry.local.json or accept that this run
has no work to do.
2. Sync sibling SYNERGY
For each accessible sibling from workflow 1 (Discover sibling(s)), compare
the bidirectional SYNERGY files and surface drift findings. Report only —
no writes.
Steps:
Read this project's SYNERGY file for the sibling, by the registry file
value — SYNERGY-<sibling>.md for a public sibling, or
PRIVATE-SYNERGY-<sibling>.md for a private sibling (its registry file;
the hybrid read-diff exception). For a public sibling, never pull in a
glob-discovered PRIVATE-SYNERGY-*.md overlay — the PRIVATE- prefix keeps
those outside the SYNERGY-*.md namespace, so reading the committed file by
name never touches them (see /synergy-tracker ### Private overlay). For a
private sibling, all downstream findings are read-only and stay in the
ephemeral report (the write blocks in "Private sibling handling" apply). If
the file is absent, treat as zero entries and proceed (the gap will surface as
"Unreciprocated entries on sibling" if the sibling has any entries).
Read the sibling's SYNERGY-<this-project>.md at
<resolved-local-path>/SYNERGY-<this-project>.md. If absent, treat as
zero entries.
Parse each side's entries section-by-section (Shared Patterns,
Divergences, Extraction Candidates, They Have / We Don't). Build a
bidirectional entry map keyed by title, normalized per the rule in
Guidelines below (2-pass matching: deterministic lead-clause pass, then
judgment pass on residuals).
Section migration is its own signal — not silently merged. Matching
is within-section: an entry's title is paired only with same-section
titles on the sibling. If an entry has migrated sections on one side
(e.g., Shared Pattern here, Divergence on sibling — typical when one
side promoted after noticing drift), it surfaces as (a) on the
originating section and (b) on the destination section, NOT as a
finding (d) Status drift. The section migration is itself the drift
signal worth surfacing, and the (a)/(b) framing tells the user
precisely which side moved. Finding (d) applies within-section only.
Section asymmetry — excluded from findings (a)/(b): the
They Have / We Don't section is intrinsically asymmetric. Entries here
describe what the sibling has that we don't; reciprocally on the
sibling's side, the same-named section describes what we have that
they don't — a different semantic set. Bilateral title comparison is
meaningless for this section. Skip its entries when computing findings
(a) and (b). The user can read the section directly to act on adoption
candidates; logging an adoption decision is /synergy-tracker's job,
not /sibling-sync's.
Walk the merged map and classify each entry into one of four findings:
(a) Reciprocal gaps — entries on this side with no matching title
on the sibling. The sibling lacks the reciprocal entry. Candidates for
workflow 4 (Apply reciprocation batch) under --auto-reciprocate.
Excludes entries from They Have / We Don't (asymmetric — see step 3).
(b) Unreciprocated entries on sibling — entries on the sibling
with no matching title here. The user may want to invoke
/synergy-tracker workflow 1 (Log a synergy entry) to log these on
this side. /sibling-sync does NOT write to this side automatically.
Excludes entries from They Have / We Don't (asymmetric — see step 3).
(c) Stale alignment claims — entries with Status: aligned and
Last verified: more than 8 sprints old (≈ two trend-review cycles).
Inline threshold; canonical definition is /synergy-tracker workflow
4 (Trend review (quarterly)). Treat 1 sprint ≈ 2 weeks if no other
calibration is available; if the entry has no Last verified: field,
fall back to the entry's date stamp.
(d) Status drift — matched entries whose Status: field differs
across sides. Applies to two cases:
- Shared Patterns where one side records
aligned and the other
records drifting or diverging (or any disagreement on the
Status value). Often signals that one side has converged or
re-diverged without the reciprocal note being refreshed.
- Divergences with
Convergence path: adopt-theirs or
Convergence path: propose-shared where one side has moved to
adopted/converged while the other still says drifting or
similar.
Excludes Divergences with Convergence path: accept-difference —
those are intended-asymmetric and have no drift signal to flag.
Output a structured report grouped first by sibling, then by finding
category. Include each entry's title, both sides' values where they
differ, and a one-line action hint per category.
Output format (per sibling):
## SYNERGY drift — vp-knowledge
### (a) Reciprocal gaps (here, missing on sibling)
- "Hook event coverage" (Shared Patterns) — sibling has no matching entry
→ /sibling-sync --auto-reciprocate to file the reciprocal
### (b) Unreciprocated entries on sibling
- "validate-plugin tool-reference audit" (Shared Patterns) — we don't track this
→ /synergy-tracker to log on this side
### (c) Stale alignment claims (>8 sprints since Last verified)
- "PreCompact prompt command hook" — Last verified: 2026-01-15 (here),
2026-01-15 (sibling). Re-verify now.
### (d) Status drift
- "npm-run-all2 parallel check stages" (Shared Patterns) — Status here:
diverging. Status sibling: aligned. Sibling converged; refresh this row.
- "BM section ownership scheme" (Divergences, propose-shared) — Status
here: drifting. Status sibling: aligned.
- Offer follow-up actions. After workflow 3 (Sync sibling UPSTREAM)
has also finished printing for this sibling, prepare the SYNERGY tier of
the action menu (built from this workflow's findings) and let workflow 3
(Sync sibling UPSTREAM) step 6 pair it with the UPSTREAM tier into a
single
AskUserQuestion call. Do NOT issue the prompt from this step —
the prompt is dispatched from workflow 3 (Sync sibling UPSTREAM) step
6 once both reports are on screen. Full protocol — which findings map to which menu options,
the header values, the --auto-reciprocate precedence rule, and the
plugin-namespaced Skill invocations — lives in the "Action-menu
protocol" section below.
3. Sync sibling UPSTREAM
For each accessible sibling, build two kinds of UPSTREAM file pairs and
compare friction tracking on each. Same report-only contract as workflow 2
(Sync sibling SYNERGY).
Two pairing modes coexist; both can fire on a single sibling:
- Mode A — shared-dependency pairing. Both sides have
UPSTREAM-<dep>.md
with the same basename (e.g., both have UPSTREAM-basic-memory.md). The
files describe the same third-party dependency <dep>. Findings (a)–(d).
- Mode B — reciprocal sibling-friction pairing. This project has
UPSTREAM-<sibling-name>.md (friction we log about the sibling) AND/OR the
sibling has UPSTREAM-<this-name>.md (friction the sibling logs about us).
Different basenames; same bilateral relationship. Owner-side semantics
invert relative to Mode A: an entry in the sibling's UPSTREAM-<this-name>.md
with Ownership: upstream means THIS project is the upstream that must
act. Findings (e)–(h).
Steps:
Build Mode A pairs. Glob this project for UPSTREAM-*.md. Glob the
sibling's resolved local-path for UPSTREAM-*.md. Compute the
intersection by basename — each match is one Mode A pair. Record both
sides' full UPSTREAM basename lists for use in step 2.
Detect Mode B pair. Skip Mode B entirely for private siblings
(merged registry file is PRIVATE-SYNERGY-*): a Mode B file is named
UPSTREAM-<sibling-name>.md, whose filename would commit the private name.
Private siblings are SYNERGY-only; Mode A above (keyed on shared dependency
names, never the sibling) still runs. For a non-private sibling, derive this
project's canonical name per the four-tier algorithm in
skills/synergy-tracker/references/project-name-derivation.md to
compute <this-name>. Apply the same algorithm (tier 3 for the sibling
subject) to the registry name field for <sibling-name>.
Stale local-path guard: if the registry entry specifies a
local-path that does not resolve to an accessible directory, tier 1
(sibling-registry back-pointer) silently falls through to tier 2
(this project's plugin.json). Warn the user before falling through:
"Sibling local-path is not accessible — tier 1 derivation skipped;
<this-name> may diverge from how the sibling registered this project.
Update .claude/synergy-registry.local.json if the sibling moved."
Then check:
- Does the sibling have
<resolved-local-path>/UPSTREAM-<this-name>.md?
- Does this project have
UPSTREAM-<sibling-name>.md?
If either file exists, this sibling has a Mode B pair (one-sided or
two-sided). Both files absent is normal — no reciprocal friction tracked
on either side. Skip Mode B for this sibling and continue.
The Mode B file pair is <this-root>/UPSTREAM-<sibling-name>.md ↔
<sibling-root>/UPSTREAM-<this-name>.md. By construction these basenames
differ from any Mode A pair's basename (Mode A keys on shared
third-party dep names; Mode B keys on sibling project names that appear
in the synergy registry). No deduplication guard needed.
Process Mode A pairs. For each Mode A pair, read both copies and
parse entries (Bugs, Feature Requests, Upstream Opportunities,
Resolved). Build a bidirectional entry map by title using the same
2-pass matching rule as workflow 2 (deterministic lead-clause Pass 1 +
judgment Pass 2 on residuals — see Guidelines). UPSTREAM titles are
typically more structured than SYNERGY titles, so Pass 2 fires less
often, but the rule is identical for consistency. Classify each entry:
- (a) Duplicate friction — same title on both sides. Sanity check:
are the workarounds, dates, and status fields aligned? If not, it's a
candidate for category (b).
- (b) Complementary workarounds — same title both sides but the
Workaround: field (or equivalent) differs. The sibling may have
found a better mitigation. Flag for cross-pollination.
- (c) Stale entries — entries dated more than 3 months ago without a
Trend Review annotation since. Either side. Stale ≠ wrong, but worth
re-verifying.
- (d) Sibling-only entries — friction the sibling tracks for a
shared dependency that we don't. Potential adoption: invoke
/upstream-tracker workflow 7 (Sync from Basic Memory) or workflow 1
(Log a new entry) to bring matching entries over here. /sibling-sync
does NOT write here automatically.
Process Mode B pair. Read whichever side(s) of the pair exist.
Parse entries the same way as step 3. Match titles bidirectionally with
the same 2-pass rule. Classify each entry:
- (e) Sibling's unresolved friction against this project — entries
in
<sibling-root>/UPSTREAM-<this-name>.md that are NOT prefixed with
_(Resolved ...)_ and NOT in a ## Resolved section if one exists.
Ownership: upstream on these entries means THIS project owns the
fix (we are upstream from the sibling's perspective). Surface ALL
unresolved entries — every one is a request directed at us. Action
hint: file beads issues here or address inline; consider logging a
cross-reference in our UPSTREAM-<sibling-name>.md if a workaround
is built.
- (f) Our unresolved friction against the sibling — entries in
<this-root>/UPSTREAM-<sibling-name>.md that are unresolved on our
side and have no corresponding _(Resolved ...)_ annotation on
either side. Informational: documents work blocked on the sibling.
Action hint: check sibling release notes or changelog for shipped
fixes the sibling forgot to annotate.
- (g) Cross-side staleness — our entry, sibling may have shipped.
Entry in
<this-root>/UPSTREAM-<sibling-name>.md unresolved on our
side, but the sibling shows a "shipped" signal (see "What 'shipped'
means" below). Use 6 months as the look-back horizon for git-log
scanning. Action hint: re-verify against the sibling's current
release; annotate with _(Resolved ...)_ via /upstream-tracker
workflow 3 (Resolve an entry) if confirmed shipped.
- (h) Reverse cross-side staleness — sibling tracks us, we may have
shipped. Entry in
<sibling-root>/UPSTREAM-<this-name>.md unresolved
on the sibling's side, but this project shows a "shipped" signal
(recent CHANGELOG entry, _(Resolved ...)_ in our cross-reference,
or git tag/commit subject within 6 months matching the entry title).
Read-only finding: /sibling-sync cannot write the sibling's file.
Action hint: notify sibling maintainer, or raise on their side via
/upstream-tracker workflow 3 (Resolve an entry) so they can
annotate.
What "shipped" means (pinned definition for findings (g) and (h)):
a fix is shipped when (1) a CHANGELOG or _(Resolved ...)_ annotation
exists on the owner's side, OR (2) the feature/fix is referenced in a
git tag message or commit subject within the relevant release window
(use git -C <owner-path> log --oneline --since="6 months ago" as a
heuristic proxy — string-match the entry title or its lead clause; do
not parse). A Workaround: full on the filing side without a
corresponding shipped version on the owner's side is NOT sufficient;
that is the filing project's mitigation, not upstream resolution.
Output. Report Mode A findings first (grouped by sibling, then by
shared dependency, then by finding category), then Mode B findings
(grouped by sibling) under a separate header. This ordering keeps the
existing Mode A output shape intact and adds Mode B as an additive
block.
Note on UPSTREAM coverage gaps: /sibling-sync now handles two cases:
shared third-party dependencies (Mode A, basename intersection) and
reciprocal sibling-friction pairs (Mode B, inverse-name detection).
One-sided UPSTREAM files about non-sibling, non-shared dependencies are
still out of scope — those are the sibling's responsibility to discover
via /upstream-tracker workflow 7 (Sync from Basic Memory) on its own.
Output format additions for Mode B:
## UPSTREAM reciprocal-friction — vp-knowledge
(Mode B: this-side UPSTREAM-vp-knowledge.md ↔ sibling-side UPSTREAM-vp-beads.md)
### (e) Sibling's unresolved friction against this project (we should action)
- "vp-beads: new /sibling-sync skill" (Feature Requests, 2026-05-04) — sibling
marks Workaround: partial; we shipped in v0.12.0. See finding (h).
- "synergy-tracker: mandate bilateral reciprocation" (Feature Requests, 2026-05-04)
Ownership on their side: upstream (us) · Workaround on their side: full
→ file beads issue or address inline
### (f) Our unresolved friction against the sibling
- "Agent effort defaults not overridable from parent" (Feature Requests, 2026-04-05)
Ownership: upstream (them) · Workaround: none
### (g) Cross-side staleness: our entry the sibling may have shipped
- (none this run)
### (h) Reverse staleness: sibling tracks us but we may have shipped
- "vp-beads: new /sibling-sync skill" — v0.12.0 tag (2026-05-05) matches.
Sibling should annotate _(Resolved 2026-05-05, vp-beads v0.12.0)_.
→ notify sibling maintainer; cannot write their file from here
- Offer follow-up actions. This is the dispatch point. After this
workflow finishes printing (and workflow 2 (Sync sibling SYNERGY) has
already finished for the same sibling), build a single
AskUserQuestion
call combining workflow 2 (Sync sibling SYNERGY)'s SYNERGY tier with
this workflow's UPSTREAM tier. The "Action-menu protocol" section below
specifies the full UPSTREAM tier: findings (b) and (d) collapse into a
single "Update our UPSTREAM" option that delegates to
/vp-beads:upstream-tracker; finding (e) routes directly to bd create; finding (g) delegates to /vp-beads:upstream-tracker workflow
3 (Resolve an entry). Findings (a), (c), (f), and (h) are informational
and not present in the menu. If no UPSTREAM findings are actionable AND
no SYNERGY findings are actionable for this sibling, skip the prompt
for this sibling. If only one tier has actionable findings, issue a
single-question call.
4. Apply reciprocation batch
Opt-in mutation path. Only runs when the user supplies --auto-reciprocate
in their invocation, or explicitly confirms intent like "yes, apply all the
reciprocal gaps". Mirrors /upstream-tracker workflow 7 (Sync from Basic
Memory)'s per-entry confirmation pattern.
Steps:
- Exclude private siblings first. Drop any sibling whose merged registry
file is PRIVATE-SYNERGY-* before doing anything else — reciprocation would
write SYNERGY-<this-project>.md on the sibling's side and expose that the
private relationship exists. Announce each exclusion: "Skipping reciprocation
for <name> — private sibling (existence must not cross to the sibling's
side)." This guard runs at the top of the loop, before any read of the
sibling's SYNERGY file.
- Re-run workflow 2 (Sync sibling SYNERGY) finding (a) (reciprocal gaps)
for each remaining (non-private) accessible sibling, applying the stricter
matching rules from the Hard Limits section below: Pass 1 (deterministic)
matches only; any Pass 2 (judgment) matches from workflow 2 (Sync sibling
SYNERGY) are added back to the reciprocation queue with an extra
disambiguation prompt rather than suppressed silently. These are the entries
on this side that the sibling demonstrably lacks.
- For each reciprocal gap, in order:
- Read the source entry from this project's
SYNERGY-<sibling>.md
(full entry text including title, date, structured fields).
- Determine the destination file at the sibling:
<resolved-local-path>/SYNERGY-<this-project>.md (derive
<this-project> per
skills/synergy-tracker/references/project-name-derivation.md).
If it does not exist yet, plan to Write a new file using the
four-section template from
skills/synergy-tracker/references/synergy-entry-format.md.
- Determine the destination section from the source entry's section
(a Shared Pattern on this side becomes a Shared Pattern on the
sibling, etc.).
- Show the user: source entry text + destination file path +
destination section. Ask: "Write reciprocal entry to
<sibling-path>/SYNERGY-<this-project>.md under ### <Section>?
[y/n/skip-rest]".
- On
y: append the entry under the destination section using Edit
(or Write if the file is new). Replace any
_No entries yet._ placeholder in that section with the entry. Keep
the entry text as-is from this side — do not rewrite to the
sibling's voice; reciprocation IS the verification step (per
/synergy-tracker workflow 1 (Log a synergy entry) bilateral
mandate). The sibling will re-verify on their next reciprocation
pass.
- On
n or skip-rest: skip and continue (or stop the batch on
skip-rest).
- After the batch, report:
- Entries written, with destination file paths
- Entries skipped, with reason
- Verification reminder for the user: run
git status in the
sibling repo, review the appended entries, commit on that side. /sibling-sync
does not commit on the sibling's behalf. Also remind the user to file
a beads follow-up on the sibling for re-verification next sprint, per
/synergy-tracker workflow 1 (Log a synergy entry)'s reciprocation
mandate.
Hard limits on workflow 4 (Apply reciprocation batch):
- Only mirrors entries from workflow 2 (Sync sibling SYNERGY) finding (a).
Does NOT mirror UPSTREAM entries from workflow 3 (Sync sibling UPSTREAM)
—
/upstream-tracker workflow 7 (Sync from Basic Memory) is the right
channel for cross-project UPSTREAM adoption (BM is the cross-project
bridge for friction; SYNERGY is the cross-project bridge for patterns).
This applies equally to Mode A findings (a)–(d) AND Mode B findings
(e)–(h): finding (e) entries get filed natively on this side via
/upstream-tracker workflow 1 (Log a new entry), not mirrored;
finding (h) annotations get written by the sibling via their own
/upstream-tracker workflow 3 (Resolve an entry), not by us.
- Never sources a reciprocal entry from a
PRIVATE-SYNERGY-*.md private
overlay. Those entries are private to this checkout (the proprietary↔public
boundary); writing one to a sibling would leak it. This is enforced
structurally: reciprocation reads the committed SYNERGY-<project>.md (by
exact name, workflow 2 (Sync sibling SYNERGY) step 1), and the PRIVATE-
prefix keeps overlays outside the SYNERGY-*.md namespace so no glob here can
reach them. See
/synergy-tracker ### Private overlay.
- Never reciprocates for a private sibling (merged registry
file is
PRIVATE-SYNERGY-*). Step 1 of this workflow excludes them before the loop;
writing SYNERGY-<this-project>.md on the sibling's side would commit the
private relationship's existence to their repo. See "Private sibling
handling".
- Never mirrors entries from
## They Have / We Don't. The section is
intrinsically asymmetric (entries here describe sibling capabilities
WE lack; the sibling's same-named section describes the inverse
asymmetry). Workflow 2 (Sync sibling SYNERGY) already excludes this section from finding (a),
but this is restated here as a mutation-side guard: even if a future
edit relaxes the workflow 2 (Sync sibling SYNERGY) exclusion, workflow 4 (Apply reciprocation batch) must never write a
They Have / We Don't entry to the sibling.
- The reciprocal-gap list is computed using Pass 1 matches only.
Entries that paired via Pass 2 (judgment) in workflow 2 (Sync sibling SYNERGY) are added back
to the reciprocation queue and presented to the user with a flag:
"This entry may already exist on the sibling as
<pass-2-matched-title>
— does that match? [y=skip / n=write reciprocal anyway / skip-rest]".
Defaulting to caution at the mutation boundary inverts the read-only
cost asymmetry: under --auto-reciprocate, suppressing a write that
should happen (false-positive Pass 2 match) is more expensive than
proposing a duplicate the user can reject (false-negative).
- Never writes to
## Trend Reviews sections on either side.
- Never writes to this project's side. Reciprocal entries go to the
sibling only — logging on this side is
/synergy-tracker workflow 1
(Log a synergy entry)'s job.
- Never writes to Basic Memory (no BM edit tooling allowed in this skill).
BM writes are
/synergy-tracker workflow 5 (Promote to Basic Memory)
and /upstream-tracker workflow 6 (Promote to Basic Memory)'s
territory.
Action-menu protocol
This skill never writes SYNERGY/UPSTREAM/BM directly — even the menu options
dispatch to the owning skill via the Skill tool, or run bd create for
beads issues. The menu is a navigation aid, not a write path. The default
read-only contract from earlier versions still holds: a user who picks
"None" for both questions receives the report and exits without any
mutation.
After workflows 2 (Sync sibling SYNERGY) and 3 (Sync sibling UPSTREAM) have
printed their per-sibling reports, sibling-sync issues a single
AskUserQuestion call with up to two single-select questions per sibling.
The AskUserQuestion SDK contract caps options at 2-4 per question
(plus an auto "Other"); we therefore split SYNERGY and UPSTREAM into
separate questions rather than one flat menu. Skipping a question is just
selecting its "None" option; both tiers default to read-only on skip.
Two-tier menu shape
Q1 — SYNERGY follow-up (header: "Synergy", 7 chars). Options listed
only when their finding count is nonzero:
| Option |
Trigger |
Dispatch |
| 1. Apply reciprocal gaps (N) |
finding (a) > 0 |
re-enter workflow 4 (Apply reciprocation batch) in-skill — no Skill call |
| 2. Log unreciprocated sibling entries (N) |
finding (b) > 0 |
Skill(skill="/vp-beads:synergy-tracker", args=...) → workflow 1 (Log a synergy entry) |
| 0. None — synergy report only |
always |
exit SYNERGY tier without action |
Q2 — UPSTREAM follow-up (header: "Upstream", 8 chars). Options listed
only when their finding count is nonzero. Findings (b) and (d) collapse
into a single option to keep the question within the 4-option SDK cap:
| Option |
Trigger |
Dispatch |
| 1. Update our UPSTREAM (b/d, N total) |
finding (b) > 0 OR finding (d) > 0 |
Skill(skill="/vp-beads:upstream-tracker", args=...) — args route to workflow 1 (Log a new entry) and/or workflow 7 (Sync from Basic Memory) inside upstream-tracker |
| 2. File beads issues for sibling's friction (N) |
finding (e) > 0 |
Bash → bd create per entry |
| 3. Resolve cross-stale entries (N) |
finding (g) > 0 |
Skill(skill="/vp-beads:upstream-tracker", args=...) → workflow 3 (Resolve an entry) |
| 0. None — upstream report only |
always |
exit UPSTREAM tier without action |
If neither tier has actionable findings for a sibling, skip the
AskUserQuestion call entirely for that sibling. If only one tier has
actionable findings, issue a single-question call (the SDK supports 1-4
questions per call).
Private-sibling guard (no-commit-leak). When the sibling's merged registry
file is PRIVATE-SYNERGY-*, every committed-write menu option is removed
because it would commit the private name:
- Q2 option 2 (
bd create) is suppressed — a .beads/*.jsonl entry naming
the sibling would leak it. The finding stays in the report only. (Finding (e)
does not arise anyway: workflow 3 (Sync sibling UPSTREAM) skips Mode B for
private siblings.)
- Q1 option 2 (Log unreciprocated sibling entries) redirects — its
/synergy-tracker dispatch targets the gitignored PRIVATE-SYNERGY-<name>.md,
never a committed SYNERGY-<name>.md (pass the private destination in the
args prose).
- Q1 option 1 (Apply reciprocal gaps) is absent — workflow 4 (Apply
reciprocation batch) already excludes private siblings.
If that leaves no actionable options for a private sibling, skip the prompt and
present the read-only findings as report-only.
Per-action argument templates
Pass natural-language prose in the Skill tool's args field. The
delegated skill receives the prose as narrative context. Templates:
- SYNERGY 2 (Log unreciprocated sibling entries):
Log unreciprocated entries from sibling <sibling-name>: <bullet list of titles + sections>. Invoke workflow 1 (Log a synergy entry) for each.
- UPSTREAM 1 (Update our UPSTREAM, b/d collapse):
From sibling-sync findings against <sibling-name>: adopt complementary workarounds for <package, title> entries (sibling's workaround text: <quoted>); also scan sibling-only entries <package, titles>. Use workflow 1 (Log a new entry) and workflow 7 (Sync from Basic Memory) as appropriate.
- UPSTREAM 3 (Resolve cross-stale entries):
`Resolve entries in UPSTREAM-.md: . Verify against the sibling's recent changelog/tags first. Invoke workflow 3 (Resolve an ent
…(truncated)
1---2name: sibling-sync3description: "Bilateral SYNERGY/UPSTREAM reconciliation across sibling projects. Use when the user wants to sync sibling SYNERGY/UPSTREAM files, compare both sides to surface drift, find reciprocation gaps (entries here but not there, or vice versa), flag stale-aligned rows, detect status drift across sides, surface friction the sibling tracks ABOUT this project (their UPSTREAM-<this-project>.md), or apply a reciprocation batch with --auto-reciprocate. Workflow 3 covers two UPSTREAM pairing modes: shared third-party dependencies AND reciprocal sibling-friction pairs (UPSTREAM-<sibling>.md here ↔ UPSTREAM-<this-project>.md there). NOT for logging entries on this side (use /synergy-tracker workflow 1 (Log a synergy entry)) — sibling-sync compares both sides without writing by default. NOT for upstream → project drift (use /vendor-sync); sibling-sync handles peer-to-peer drift between sibling vp-* projects. Trigger phrases: 'sibling sync', 'compare siblings', 'sync sibling', 'reconcile siblings', 'reciprocation gap', 'sync drift', 'bilateral sync', 'sync SYNERGY', 'sync UPSTREAM both ways', 'auto-reciprocate', 'check sibling drift', 'peer-to-peer drift', 'cross-project drift', 'sibling reconciliation', 'sibling has friction about us', 'what does the sibling say about us', 'reconcile sibling-tracked friction', 'reciprocal upstream friction', 'friction filed against this project', 'sibling follow-up', 'act on sibling drift', 'after sibling-sync', 'follow-up actions', 'what to do about sibling findings'."4user-invocable: true5argument-hint: "[--auto-reciprocate] [sibling-name]"6paths:7 - "SYNERGY-*.md"8 - "PRIVATE-SYNERGY-*.md"9 - "UPSTREAM-*.md"10 - ".claude/synergy-registry.json"11 - ".claude/vendor-registry.json"12allowed-tools:13 - Bash14 - Read15 - Glob16 - Grep17 - Edit18 - Write19 - Skill20 - AskUserQuestion21 - mcp__basic-memory__search_notes22 - mcp__basic-memory__read_note23metadata:24 source: https://skillmd.com/skills/voxpelli/sibling-sync25---2627# Sibling Sync2829Bilateral reconciliation of `SYNERGY-*.md` and `UPSTREAM-*.md` files between30this project and its sibling vp-\* projects. Read-only by default — surfaces31drift, reciprocal gaps, stale-aligned rows, and status drift across sides32without mutating anything. The opt-in `--auto-reciprocate` flag writes33reciprocal entries to the sibling's SYNERGY file via per-entry confirmation.3435Companion to `/vendor-sync` (which handles upstream → project drift); this36skill handles peer-to-peer drift between siblings registered in37`.claude/synergy-registry.json`.3839## Design Rationale4041The bd v1.0.0 Integration Charter42(`gastownhall/beads@5d524cf7:docs/INTEGRATION_CHARTER.md`) explicitly punts43cross-tracker orchestration out of bd's scope: bd will never grow a feature44that routes a cross-project item from project A's tracker to project B's45tracker. `/sibling-sync` is exactly the workflow-automation layer the Charter46defers to external tools — file-based reconciliation between sibling vp-\*47projects, mediated by registries and confirmation prompts rather than48synchronous tracker calls.4950This mirrors the rationale already cited by `/synergy-tracker` for keeping51cross-project state in `SYNERGY-*.md` plus Basic Memory rather than in bd.5253## Cross-skill boundaries5455`/sibling-sync` is a *comparison and reconciliation* layer that sits alongside56the per-side logging skills. It owns nothing in Basic Memory and nothing on57this project's side of the SYNERGY/UPSTREAM files.5859- **Does NOT write SYNERGY entries on this project's side.** `/synergy-tracker`60 workflow 1 (Log a synergy entry) owns logging on this side.61- **Does NOT pull upstream subtrees.** `/vendor-sync` owns subtree pulls and62 the upstream → project drift workflow.63- **Does NOT write Basic Memory notes.** `/synergy-tracker` workflow 564 (Promote to Basic Memory) owns `## Cross-Project Synergy` writes65 to sibling entity notes; `/upstream-tracker` workflow 6 (Promote to Basic66 Memory) owns `## Upstream Friction` writes. Basic Memory write tools are67 intentionally absent from this skill's `allowed-tools`.68- **Does NOT write `## Trend Reviews` entries** to SYNERGY files. Those belong69 to `/synergy-tracker` workflow 4 (Trend review (quarterly)). Even under70 `--auto-reciprocate`, /sibling-sync only mirrors content entries into71 reciprocal sections — never trend-review summaries.72- **Stale-row detection is INLINE here** for the threshold values used during73 comparison runs. The canonical staleness-threshold definition lives in74 `/synergy-tracker` workflow 4 (Trend review (quarterly)) — workflow 2 (Sync75 sibling SYNERGY) below cites it. Per RETRO-10 YAGNI guard: extract this to76 a shared helper only when a third skill needs the same logic.77- **Surfacing reciprocal-friction findings is in scope; acting on them is78 not.** Workflow 3 (Sync sibling UPSTREAM) Mode B (see below) reads the sibling's79 `UPSTREAM-<this-project>.md` to surface friction the sibling tracks about80 this project. Filing the resulting work as bugs/features/opportunities on81 this side is `/upstream-tracker` workflow 1 (Log a new entry)'s job.82 Annotating the sibling's entry as resolved is `/upstream-tracker` workflow83 3 (Resolve an entry)'s job, performed on the sibling's side. /sibling-sync84 reports only.85- **Orchestrator role for follow-up actions (v0.14.0).** Workflows 2 (Sync86 sibling SYNERGY) and 3 (Sync sibling UPSTREAM) end with a per-sibling87 action menu (see "Action-menu protocol" below) that delegates writes to88 the owning skill (`/vp-beads:synergy-tracker`,89 `/vp-beads:upstream-tracker`) via the `Skill` tool, or runs `bd create`90 directly for beads issues. /sibling-sync still owns nothing in Basic91 Memory and nothing in this project's SYNERGY/UPSTREAM files —92 ownership boundaries are unchanged.9394## Registry and path resolution9596Sibling projects are declared in `.claude/synergy-registry.json` (array of97`{name, file, remote, bm-entity, relationship, local-path?}` entries). The98optional `local-path` field gives the on-disk path to the sibling checkout99(relative paths resolve from this project root). When absent, fall back to100`../<name>/`.101102`.claude/synergy-registry.local.json` is a gitignored companion that overrides103fields in the committed registry — same per-entry merge by `name` pattern as104`.claude/vendor-registry.local.json` — **and** can add fully-private siblings105(see "Private sibling handling" below). Resolution order:1061071. Read `.claude/synergy-registry.json`.1082. If `.claude/synergy-registry.local.json` exists, merge it on top by `name`109 key, in two modes:110 - **Override mode** (entry `name` matches a base entry): fields in111 `.local.json` win; absent fields keep the base value.112 - **Private-add mode** (entry `name` not in the base registry AND its `file`113 is a `PRIVATE-SYNERGY-<name>.md` value): the entry is **added** to the114 merged result as a private sibling. The `PRIVATE-` prefix on `file` is the115 marker (there is no boolean); it governs the restrictions below.116 - Entries in `.local.json` whose `name` is not in the base registry and whose117 `file` is NOT `PRIVATE-SYNERGY-*` are **ignored** (backward compatibility —118 typos and accidental entries stay silent).1193. For each merged entry, resolve `local-path` (registry value or120 `../<name>/`).1214. If the resolved path does not exist on disk, report informatively and SKIP122 that sibling. Do not error out — continue with siblings that are123 accessible.124125Workflow 3 (Sync sibling UPSTREAM) additionally consumes the merged126`.claude/vendor-registry.json` (+ `.local.json`) to identify shared vendor127dependencies across siblings. (The vendor registry has no private-add mode —128private siblings are synergy-registry only.)129130### Private sibling handling131132A **private sibling** is one whose merged registry entry has a133`file: PRIVATE-SYNERGY-<name>.md` value (added via private-add mode above, or —134in principle — a base entry, which the validator forbids because it would commit135the name). Its `name` lives only in the gitignored `.local.json` and136`PRIVATE-SYNERGY-<name>.md`; **it must never reach a committed file.** This skill137therefore treats private siblings under a strict read-vs-write split, keyed on138the `PRIVATE-SYNERGY-*` `file` predicate:139140- **Read (allowed) — hybrid read-diff.** Unlike a *public* sibling's141 glob-discovered `PRIVATE-SYNERGY-*.md` overlay (which this skill never reads),142 a private sibling's `PRIVATE-SYNERGY-<name>.md` **is** its registry `file`, so143 workflows 1 (Discover sibling(s)), 2 (Sync sibling SYNERGY), and 3 (Sync144 sibling UPSTREAM, Mode A only) read it to produce **read-only diff findings**.145 Findings appear in the **ephemeral terminal report only** — never written.146- **Write (blocked) — every committed surface.** For a `PRIVATE-SYNERGY-*`-filed147 sibling:148 - **Reciprocation:** workflow 4 (Apply reciprocation batch) skips it entirely149 (writing `SYNERGY-<this-project>.md` on the sibling's side would expose the150 relationship).151 - **`bd create`:** the action menu suppresses the UPSTREAM "file beads issues"152 option (a committed `.beads/*.jsonl` entry would leak the name) — findings153 stay report-only.154 - **Logging on this side:** any "log unreciprocated entry" follow-up routes to155 the gitignored `PRIVATE-SYNERGY-<name>.md`, never a committed156 `SYNERGY-<name>.md` (delegated to `/synergy-tracker`).157 - **BM promotion:** never (this skill has no BM tools; `/synergy-tracker`158 workflow 5 (Promote to Basic Memory) skips `PRIVATE-SYNERGY-*` siblings).159 - **UPSTREAM Mode B:** out of scope for private siblings — an160 `UPSTREAM-<name>.md` filename would itself leak the name. Workflow 3 (Sync161 sibling UPSTREAM) runs Mode A (shared dependencies — names no sibling) but162 skips Mode B for `PRIVATE-SYNERGY-*` siblings.163164The `PRIVATE-SYNERGY-*` `file` predicate is the single structural marker — the165same prefix that keeps content outside the `SYNERGY-*.md` glob also gates every166write path here.167168## Workflows169170Determine which workflow the user needs based on their request. If ambiguous,171default to running workflow 1 (Discover sibling(s)) followed by workflow 2172(Sync sibling SYNERGY) and workflow 3 (Sync sibling UPSTREAM) as a single173report. Workflow 4 (Apply reciprocation batch) only fires under explicit174`--auto-reciprocate`.175176### 1. Discover sibling(s)177178Resolve which siblings will participate in this run.179180**Steps:**1811821. Read `.claude/synergy-registry.json`. If the file does not exist, redirect:183 tell the user no sibling registry is configured and offer to invoke184 `/synergy-tracker` workflow 1 (Log a synergy entry), which will run the185 guided registry creation flow at step 1b for the first sibling. If the186 user names a sibling now, follow the synergy-tracker step 1b prose from187 this conversation (re-reading188 `skills/synergy-tracker/SKILL.md` workflow 1 (Log a synergy entry) step 1b189 and applying its logic in-session — Claude Code has no actual190 inline-skill-invocation mechanism, so this means executing step 1b's191 instructions verbatim from sibling-sync's context). After the registry192 is created, resume from step 2 below. Otherwise stop, and instruct the193 user to invoke `/synergy-tracker` directly with the sibling name and194 then re-run `/sibling-sync`.1952. If `.claude/synergy-registry.local.json` exists, merge it on top per the196 per-entry merge rules in the Registry section above. This includes197 **private siblings** — `.local.json`-only entries whose `file` is198 `PRIVATE-SYNERGY-<name>.md`, which are added to the participating set (they199 read-diff like any sibling but are blocked from every committed-write path —200 see "Private sibling handling").2013. If the user named a specific sibling in their request or argument, filter202 the merged list to that entry. Otherwise, all merged entries participate.2034. For each entry, resolve `local-path` → `../<name>/` fallback. Probe each204 resolved path with a directory existence check.2055. Build the participation lists:206 - **Accessible siblings** (path exists) — proceed to workflow 2 (Sync207 sibling SYNERGY) and workflow 3 (Sync sibling UPSTREAM) for each. Mark any208 private sibling (registry `file` is `PRIVATE-SYNERGY-*`) with a `[private]`209 label so the user can see which relationships are private.210 - **Inaccessible siblings** (path missing) — report them so the user211 knows what was skipped, with the resolved path and a hint that212 `.claude/synergy-registry.local.json` can override the path2136. Report the participation list before continuing.214215**Output:**216217```218Siblings participating:219- vp-knowledge → /Users/.../vp-claude (registry local-path)220- acme-partner → /abs/path/to/acme-partner [private]221222Siblings skipped (path not accessible):223- vp-other → ../vp-other (set local-path in synergy-registry.local.json)224```225226If no siblings are accessible, stop and report. The user can either correct227the paths via `.claude/synergy-registry.local.json` or accept that this run228has no work to do.229230### 2. Sync sibling SYNERGY231232For each accessible sibling from workflow 1 (Discover sibling(s)), compare233the bidirectional SYNERGY files and surface drift findings. Report only —234no writes.235236**Steps:**2372381. Read this project's SYNERGY file for the sibling, by the registry `file`239 value — `SYNERGY-<sibling>.md` for a public sibling, or240 `PRIVATE-SYNERGY-<sibling>.md` for a **private** sibling (its registry `file`;241 the hybrid read-diff exception). For a *public* sibling, never pull in a242 glob-discovered `PRIVATE-SYNERGY-*.md` overlay — the `PRIVATE-` prefix keeps243 those outside the `SYNERGY-*.md` namespace, so reading the committed file by244 name never touches them (see `/synergy-tracker` `### Private overlay`). For a245 private sibling, all downstream findings are read-only and stay in the246 ephemeral report (the write blocks in "Private sibling handling" apply). If247 the file is absent, treat as zero entries and proceed (the gap will surface as248 "Unreciprocated entries on sibling" if the sibling has any entries).2492502. Read the sibling's `SYNERGY-<this-project>.md` at251 `<resolved-local-path>/SYNERGY-<this-project>.md`. If absent, treat as252 zero entries.2532543. Parse each side's entries section-by-section (Shared Patterns,255 Divergences, Extraction Candidates, They Have / We Don't). Build a256 bidirectional entry map keyed by **title**, normalized per the rule in257 Guidelines below (2-pass matching: deterministic lead-clause pass, then258 judgment pass on residuals).259260 **Section migration is its own signal — not silently merged.** Matching261 is within-section: an entry's title is paired only with same-section262 titles on the sibling. If an entry has migrated sections on one side263 (e.g., Shared Pattern here, Divergence on sibling — typical when one264 side promoted after noticing drift), it surfaces as (a) on the265 originating section and (b) on the destination section, NOT as a266 finding (d) Status drift. The section migration is itself the drift267 signal worth surfacing, and the (a)/(b) framing tells the user268 precisely which side moved. Finding (d) applies within-section only.269270 **Section asymmetry — excluded from findings (a)/(b):** the271 `They Have / We Don't` section is intrinsically asymmetric. Entries here272 describe what the *sibling* has that we don't; reciprocally on the273 sibling's side, the same-named section describes what *we* have that274 they don't — a different semantic set. Bilateral title comparison is275 meaningless for this section. Skip its entries when computing findings276 (a) and (b). The user can read the section directly to act on adoption277 candidates; logging an adoption decision is `/synergy-tracker`'s job,278 not /sibling-sync's.2792804. Walk the merged map and classify each entry into one of four findings:281282 - **(a) Reciprocal gaps** — entries on this side with no matching title283 on the sibling. The sibling lacks the reciprocal entry. Candidates for284 workflow 4 (Apply reciprocation batch) under `--auto-reciprocate`.285 Excludes entries from `They Have / We Don't` (asymmetric — see step 3).286 - **(b) Unreciprocated entries on sibling** — entries on the sibling287 with no matching title here. The user may want to invoke288 `/synergy-tracker` workflow 1 (Log a synergy entry) to log these on289 this side. /sibling-sync does NOT write to this side automatically.290 Excludes entries from `They Have / We Don't` (asymmetric — see step 3).291 - **(c) Stale alignment claims** — entries with `Status: aligned` and292 `Last verified:` more than 8 sprints old (≈ two trend-review cycles).293 Inline threshold; canonical definition is `/synergy-tracker` workflow294 4 (Trend review (quarterly)). Treat 1 sprint ≈ 2 weeks if no other295 calibration is available; if the entry has no `Last verified:` field,296 fall back to the entry's date stamp.297 - **(d) Status drift** — matched entries whose `Status:` field differs298 across sides. Applies to two cases:299300 1. **Shared Patterns** where one side records `aligned` and the other301 records `drifting` or `diverging` (or any disagreement on the302 Status value). Often signals that one side has converged or303 re-diverged without the reciprocal note being refreshed.304 2. **Divergences** with `Convergence path: adopt-theirs` or305 `Convergence path: propose-shared` where one side has moved to306 `adopted`/`converged` while the other still says `drifting` or307 similar.308309 Excludes Divergences with `Convergence path: accept-difference` —310 those are intended-asymmetric and have no drift signal to flag.3113125. Output a structured report grouped first by sibling, then by finding313 category. Include each entry's title, both sides' values where they314 differ, and a one-line action hint per category.315316**Output format (per sibling):**317318```319## SYNERGY drift — vp-knowledge320321### (a) Reciprocal gaps (here, missing on sibling)322- "Hook event coverage" (Shared Patterns) — sibling has no matching entry323 → /sibling-sync --auto-reciprocate to file the reciprocal324325### (b) Unreciprocated entries on sibling326- "validate-plugin tool-reference audit" (Shared Patterns) — we don't track this327 → /synergy-tracker to log on this side328329### (c) Stale alignment claims (>8 sprints since Last verified)330- "PreCompact prompt command hook" — Last verified: 2026-01-15 (here),331 2026-01-15 (sibling). Re-verify now.332333### (d) Status drift334- "npm-run-all2 parallel check stages" (Shared Patterns) — Status here:335 diverging. Status sibling: aligned. Sibling converged; refresh this row.336- "BM section ownership scheme" (Divergences, propose-shared) — Status337 here: drifting. Status sibling: aligned.338```3393406. **Offer follow-up actions.** After workflow 3 (Sync sibling UPSTREAM)341 has also finished printing for this sibling, prepare the SYNERGY tier of342 the action menu (built from this workflow's findings) and let workflow 3343 (Sync sibling UPSTREAM) step 6 pair it with the UPSTREAM tier into a344 single `AskUserQuestion` call. Do NOT issue the prompt from this step —345 the prompt is dispatched from workflow 3 (Sync sibling UPSTREAM) step346 6 once both reports are on screen. Full protocol — which findings map to which menu options,347 the `header` values, the `--auto-reciprocate` precedence rule, and the348 plugin-namespaced `Skill` invocations — lives in the "Action-menu349 protocol" section below.350351### 3. Sync sibling UPSTREAM352353For each accessible sibling, build two kinds of UPSTREAM file pairs and354compare friction tracking on each. Same report-only contract as workflow 2355(Sync sibling SYNERGY).356357**Two pairing modes coexist; both can fire on a single sibling:**358359- **Mode A — shared-dependency pairing.** Both sides have `UPSTREAM-<dep>.md`360 with the same basename (e.g., both have `UPSTREAM-basic-memory.md`). The361 files describe the same third-party dependency `<dep>`. Findings (a)–(d).362- **Mode B — reciprocal sibling-friction pairing.** This project has363 `UPSTREAM-<sibling-name>.md` (friction we log about the sibling) AND/OR the364 sibling has `UPSTREAM-<this-name>.md` (friction the sibling logs about us).365 Different basenames; same bilateral relationship. Owner-side semantics366 invert relative to Mode A: an entry in the sibling's `UPSTREAM-<this-name>.md`367 with `Ownership: upstream` means THIS project is the upstream that must368 act. Findings (e)–(h).369370**Steps:**3713721. **Build Mode A pairs.** Glob this project for `UPSTREAM-*.md`. Glob the373 sibling's resolved `local-path` for `UPSTREAM-*.md`. Compute the374 intersection by basename — each match is one Mode A pair. Record both375 sides' full UPSTREAM basename lists for use in step 2.3762. **Detect Mode B pair.** **Skip Mode B entirely for private siblings**377 (merged registry `file` is `PRIVATE-SYNERGY-*`): a Mode B file is named378 `UPSTREAM-<sibling-name>.md`, whose filename would commit the private name.379 Private siblings are SYNERGY-only; Mode A above (keyed on shared *dependency*380 names, never the sibling) still runs. For a non-private sibling, derive this381 project's canonical name per the four-tier algorithm in382 `skills/synergy-tracker/references/project-name-derivation.md` to383 compute `<this-name>`. Apply the same algorithm (tier 3 for the sibling384 subject) to the registry `name` field for `<sibling-name>`.385 **Stale `local-path` guard:** if the registry entry specifies a386 `local-path` that does not resolve to an accessible directory, tier 1387 (sibling-registry back-pointer) silently falls through to tier 2388 (this project's `plugin.json`). Warn the user before falling through:389 "Sibling local-path is not accessible — tier 1 derivation skipped;390 `<this-name>` may diverge from how the sibling registered this project.391 Update `.claude/synergy-registry.local.json` if the sibling moved."392 Then check:393394 - Does the sibling have `<resolved-local-path>/UPSTREAM-<this-name>.md`?395 - Does this project have `UPSTREAM-<sibling-name>.md`?396397 If either file exists, this sibling has a Mode B pair (one-sided or398 two-sided). Both files absent is normal — no reciprocal friction tracked399 on either side. Skip Mode B for this sibling and continue.400401 The Mode B file pair is `<this-root>/UPSTREAM-<sibling-name>.md` ↔402 `<sibling-root>/UPSTREAM-<this-name>.md`. By construction these basenames403 differ from any Mode A pair's basename (Mode A keys on shared404 third-party dep names; Mode B keys on sibling project names that appear405 in the synergy registry). No deduplication guard needed.4063. **Process Mode A pairs.** For each Mode A pair, read both copies and407 parse entries (Bugs, Feature Requests, Upstream Opportunities,408 Resolved). Build a bidirectional entry map by **title** using the same409 2-pass matching rule as workflow 2 (deterministic lead-clause Pass 1 +410 judgment Pass 2 on residuals — see Guidelines). UPSTREAM titles are411 typically more structured than SYNERGY titles, so Pass 2 fires less412 often, but the rule is identical for consistency. Classify each entry:413414 - **(a) Duplicate friction** — same title on both sides. Sanity check:415 are the workarounds, dates, and status fields aligned? If not, it's a416 candidate for category (b).417 - **(b) Complementary workarounds** — same title both sides but the418 `Workaround:` field (or equivalent) differs. The sibling may have419 found a better mitigation. Flag for cross-pollination.420 - **(c) Stale entries** — entries dated more than 3 months ago without a421 Trend Review annotation since. Either side. Stale ≠ wrong, but worth422 re-verifying.423 - **(d) Sibling-only entries** — friction the sibling tracks for a424 shared dependency that we don't. Potential adoption: invoke425 `/upstream-tracker` workflow 7 (Sync from Basic Memory) or workflow 1426 (Log a new entry) to bring matching entries over here. /sibling-sync427 does NOT write here automatically.4284. **Process Mode B pair.** Read whichever side(s) of the pair exist.429 Parse entries the same way as step 3. Match titles bidirectionally with430 the same 2-pass rule. Classify each entry:431432 - **(e) Sibling's unresolved friction against this project** — entries433 in `<sibling-root>/UPSTREAM-<this-name>.md` that are NOT prefixed with434 `_(Resolved ...)_` and NOT in a `## Resolved` section if one exists.435 `Ownership: upstream` on these entries means THIS project owns the436 fix (we are upstream from the sibling's perspective). Surface ALL437 unresolved entries — every one is a request directed at us. Action438 hint: file beads issues here or address inline; consider logging a439 cross-reference in our `UPSTREAM-<sibling-name>.md` if a workaround440 is built.441 - **(f) Our unresolved friction against the sibling** — entries in442 `<this-root>/UPSTREAM-<sibling-name>.md` that are unresolved on our443 side and have no corresponding `_(Resolved ...)_` annotation on444 either side. Informational: documents work blocked on the sibling.445 Action hint: check sibling release notes or changelog for shipped446 fixes the sibling forgot to annotate.447 - **(g) Cross-side staleness — our entry, sibling may have shipped.**448 Entry in `<this-root>/UPSTREAM-<sibling-name>.md` unresolved on our449 side, but the sibling shows a "shipped" signal (see "What 'shipped'450 means" below). Use 6 months as the look-back horizon for git-log451 scanning. Action hint: re-verify against the sibling's current452 release; annotate with `_(Resolved ...)_` via `/upstream-tracker`453 workflow 3 (Resolve an entry) if confirmed shipped.454 - **(h) Reverse cross-side staleness — sibling tracks us, we may have455 shipped.** Entry in `<sibling-root>/UPSTREAM-<this-name>.md` unresolved456 on the sibling's side, but this project shows a "shipped" signal457 (recent CHANGELOG entry, `_(Resolved ...)_` in our cross-reference,458 or git tag/commit subject within 6 months matching the entry title).459 Read-only finding: /sibling-sync cannot write the sibling's file.460 Action hint: notify sibling maintainer, or raise on their side via461 `/upstream-tracker` workflow 3 (Resolve an entry) so they can462 annotate.463464 **What "shipped" means** (pinned definition for findings (g) and (h)):465 a fix is shipped when (1) a CHANGELOG or `_(Resolved ...)_` annotation466 exists on the owner's side, OR (2) the feature/fix is referenced in a467 git tag message or commit subject within the relevant release window468 (use `git -C <owner-path> log --oneline --since="6 months ago"` as a469 heuristic proxy — string-match the entry title or its lead clause; do470 not parse). A `Workaround: full` on the filing side without a471 corresponding shipped version on the owner's side is NOT sufficient;472 that is the filing project's mitigation, not upstream resolution.4735. **Output.** Report Mode A findings first (grouped by sibling, then by474 shared dependency, then by finding category), then Mode B findings475 (grouped by sibling) under a separate header. This ordering keeps the476 existing Mode A output shape intact and adds Mode B as an additive477 block.478479**Note on UPSTREAM coverage gaps:** /sibling-sync now handles two cases:480shared third-party dependencies (Mode A, basename intersection) and481reciprocal sibling-friction pairs (Mode B, inverse-name detection).482One-sided UPSTREAM files about non-sibling, non-shared dependencies are483still out of scope — those are the sibling's responsibility to discover484via `/upstream-tracker` workflow 7 (Sync from Basic Memory) on its own.485486**Output format additions for Mode B:**487488```489## UPSTREAM reciprocal-friction — vp-knowledge490491(Mode B: this-side UPSTREAM-vp-knowledge.md ↔ sibling-side UPSTREAM-vp-beads.md)492493### (e) Sibling's unresolved friction against this project (we should action)494- "vp-beads: new /sibling-sync skill" (Feature Requests, 2026-05-04) — sibling495 marks Workaround: partial; we shipped in v0.12.0. See finding (h).496- "synergy-tracker: mandate bilateral reciprocation" (Feature Requests, 2026-05-04)497 Ownership on their side: upstream (us) · Workaround on their side: full498 → file beads issue or address inline499500### (f) Our unresolved friction against the sibling501- "Agent effort defaults not overridable from parent" (Feature Requests, 2026-04-05)502 Ownership: upstream (them) · Workaround: none503504### (g) Cross-side staleness: our entry the sibling may have shipped505- (none this run)506507### (h) Reverse staleness: sibling tracks us but we may have shipped508- "vp-beads: new /sibling-sync skill" — v0.12.0 tag (2026-05-05) matches.509 Sibling should annotate _(Resolved 2026-05-05, vp-beads v0.12.0)_.510 → notify sibling maintainer; cannot write their file from here511```5125136. **Offer follow-up actions.** This is the dispatch point. After this514 workflow finishes printing (and workflow 2 (Sync sibling SYNERGY) has515 already finished for the same sibling), build a single `AskUserQuestion`516 call combining workflow 2 (Sync sibling SYNERGY)'s SYNERGY tier with517 this workflow's UPSTREAM tier. The "Action-menu protocol" section below518 specifies the full UPSTREAM tier: findings (b) and (d) collapse into a519 single "Update our UPSTREAM" option that delegates to520 `/vp-beads:upstream-tracker`; finding (e) routes directly to `bd521 create`; finding (g) delegates to `/vp-beads:upstream-tracker` workflow522 3 (Resolve an entry). Findings (a), (c), (f), and (h) are informational523 and not present in the menu. If no UPSTREAM findings are actionable AND524 no SYNERGY findings are actionable for this sibling, skip the prompt525 for this sibling. If only one tier has actionable findings, issue a526 single-question call.527528### 4. Apply reciprocation batch529530Opt-in mutation path. Only runs when the user supplies `--auto-reciprocate`531in their invocation, or explicitly confirms intent like "yes, apply all the532reciprocal gaps". Mirrors `/upstream-tracker` workflow 7 (Sync from Basic533Memory)'s per-entry confirmation pattern.534535**Steps:**5365371. **Exclude private siblings first.** Drop any sibling whose merged registry538 `file` is `PRIVATE-SYNERGY-*` before doing anything else — reciprocation would539 write `SYNERGY-<this-project>.md` on the sibling's side and expose that the540 private relationship exists. Announce each exclusion: "Skipping reciprocation541 for `<name>` — private sibling (existence must not cross to the sibling's542 side)." This guard runs at the top of the loop, before any read of the543 sibling's SYNERGY file.5442. Re-run workflow 2 (Sync sibling SYNERGY) finding (a) (reciprocal gaps)545 for each remaining (non-private) accessible sibling, applying the stricter546 matching rules from the Hard Limits section below: Pass 1 (deterministic)547 matches only; any Pass 2 (judgment) matches from workflow 2 (Sync sibling548 SYNERGY) are added back to the reciprocation queue with an extra549 disambiguation prompt rather than suppressed silently. These are the entries550 on this side that the sibling demonstrably lacks.5513. For each reciprocal gap, in order:552 1. Read the source entry from this project's `SYNERGY-<sibling>.md`553 (full entry text including title, date, structured fields).554 2. Determine the destination file at the sibling:555 `<resolved-local-path>/SYNERGY-<this-project>.md` (derive556 `<this-project>` per557 `skills/synergy-tracker/references/project-name-derivation.md`).558 If it does not exist yet, plan to `Write` a new file using the559 four-section template from560 `skills/synergy-tracker/references/synergy-entry-format.md`.561 3. Determine the destination section from the source entry's section562 (a Shared Pattern on this side becomes a Shared Pattern on the563 sibling, etc.).564 4. Show the user: source entry text + destination file path +565 destination section. Ask: "Write reciprocal entry to566 `<sibling-path>/SYNERGY-<this-project>.md` under `### <Section>`?567 \[y/n/skip-rest]".568 5. On `y`: append the entry under the destination section using `Edit`569 (or `Write` if the file is new). Replace any570 `_No entries yet._` placeholder in that section with the entry. Keep571 the entry text *as-is* from this side — do not rewrite to the572 sibling's voice; reciprocation IS the verification step (per573 `/synergy-tracker` workflow 1 (Log a synergy entry) bilateral574 mandate). The sibling will re-verify on their next reciprocation575 pass.576 6. On `n` or `skip-rest`: skip and continue (or stop the batch on577 `skip-rest`).5784. After the batch, report:579 - Entries written, with destination file paths580 - Entries skipped, with reason581 - **Verification reminder for the user**: run `git status` in the582 sibling repo, review the appended entries, commit on that side. /sibling-sync583 does not commit on the sibling's behalf. Also remind the user to file584 a beads follow-up on the sibling for re-verification next sprint, per585 `/synergy-tracker` workflow 1 (Log a synergy entry)'s reciprocation586 mandate.587588**Hard limits on workflow 4 (Apply reciprocation batch):**589590- Only mirrors entries from workflow 2 (Sync sibling SYNERGY) finding (a).591 Does NOT mirror UPSTREAM entries from workflow 3 (Sync sibling UPSTREAM)592 — `/upstream-tracker` workflow 7 (Sync from Basic Memory) is the right593 channel for cross-project UPSTREAM adoption (BM is the cross-project594 bridge for friction; SYNERGY is the cross-project bridge for patterns).595 This applies equally to Mode A findings (a)–(d) AND Mode B findings596 (e)–(h): finding (e) entries get filed natively on this side via597 `/upstream-tracker` workflow 1 (Log a new entry), not mirrored;598 finding (h) annotations get written by the sibling via their own599 `/upstream-tracker` workflow 3 (Resolve an entry), not by us.600- **Never sources a reciprocal entry from a `PRIVATE-SYNERGY-*.md` private601 overlay.** Those entries are private to this checkout (the proprietary↔public602 boundary); writing one to a sibling would leak it. This is enforced603 structurally: reciprocation reads the committed `SYNERGY-<project>.md` (by604 exact name, workflow 2 (Sync sibling SYNERGY) step 1), and the `PRIVATE-`605 prefix keeps overlays outside the `SYNERGY-*.md` namespace so no glob here can606 reach them. See607 `/synergy-tracker` `### Private overlay`.608- **Never reciprocates for a private sibling** (merged registry `file` is609 `PRIVATE-SYNERGY-*`). Step 1 of this workflow excludes them before the loop;610 writing `SYNERGY-<this-project>.md` on the sibling's side would commit the611 private relationship's existence to their repo. See "Private sibling612 handling".613- Never mirrors entries from `## They Have / We Don't`. The section is614 intrinsically asymmetric (entries here describe sibling capabilities615 WE lack; the sibling's same-named section describes the inverse616 asymmetry). Workflow 2 (Sync sibling SYNERGY) already excludes this section from finding (a),617 but this is restated here as a mutation-side guard: even if a future618 edit relaxes the workflow 2 (Sync sibling SYNERGY) exclusion, workflow 4 (Apply reciprocation batch) must never write a619 `They Have / We Don't` entry to the sibling.620- The reciprocal-gap list is computed using **Pass 1 matches only**.621 Entries that paired via Pass 2 (judgment) in workflow 2 (Sync sibling SYNERGY) are added back622 to the reciprocation queue and presented to the user with a flag:623 "This entry may already exist on the sibling as `<pass-2-matched-title>`624 — does that match? \[y=skip / n=write reciprocal anyway / skip-rest]".625 Defaulting to caution at the mutation boundary inverts the read-only626 cost asymmetry: under `--auto-reciprocate`, suppressing a write that627 should happen (false-positive Pass 2 match) is more expensive than628 proposing a duplicate the user can reject (false-negative).629- Never writes to `## Trend Reviews` sections on either side.630- Never writes to this project's side. Reciprocal entries go to the631 sibling only — logging on this side is `/synergy-tracker` workflow 1632 (Log a synergy entry)'s job.633- Never writes to Basic Memory (no BM edit tooling allowed in this skill).634 BM writes are `/synergy-tracker` workflow 5 (Promote to Basic Memory)635 and `/upstream-tracker` workflow 6 (Promote to Basic Memory)'s636 territory.637638## Action-menu protocol639640This skill never writes SYNERGY/UPSTREAM/BM directly — even the menu options641dispatch to the owning skill via the `Skill` tool, or run `bd create` for642beads issues. The menu is a navigation aid, not a write path. The default643read-only contract from earlier versions still holds: a user who picks644"None" for both questions receives the report and exits without any645mutation.646647After workflows 2 (Sync sibling SYNERGY) and 3 (Sync sibling UPSTREAM) have648printed their per-sibling reports, sibling-sync issues a single649`AskUserQuestion` call with up to two single-select questions per sibling.650The `AskUserQuestion` SDK contract caps options at 2-4 per question651(plus an auto "Other"); we therefore split SYNERGY and UPSTREAM into652separate questions rather than one flat menu. Skipping a question is just653selecting its "None" option; both tiers default to read-only on skip.654655### Two-tier menu shape656657**Q1 — SYNERGY follow-up** (`header: "Synergy"`, 7 chars). Options listed658only when their finding count is nonzero:659660| Option | Trigger | Dispatch |661| ----------------------------------------- | --------------- | --------------------------------------------------------------------------------------- |662| 1. Apply reciprocal gaps (N) | finding (a) > 0 | re-enter workflow 4 (Apply reciprocation batch) in-skill — no `Skill` call |663| 2. Log unreciprocated sibling entries (N) | finding (b) > 0 | `Skill(skill="/vp-beads:synergy-tracker", args=...)` → workflow 1 (Log a synergy entry) |664| 0. None — synergy report only | always | exit SYNERGY tier without action |665666**Q2 — UPSTREAM follow-up** (`header: "Upstream"`, 8 chars). Options listed667only when their finding count is nonzero. Findings (b) and (d) collapse668into a single option to keep the question within the 4-option SDK cap:669670| Option | Trigger | Dispatch |671| ----------------------------------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |672| 1. Update our UPSTREAM (b/d, N total) | finding (b) > 0 OR finding (d) > 0 | `Skill(skill="/vp-beads:upstream-tracker", args=...)` — args route to workflow 1 (Log a new entry) and/or workflow 7 (Sync from Basic Memory) inside upstream-tracker |673| 2. File beads issues for sibling's friction (N) | finding (e) > 0 | `Bash` → `bd create` per entry |674| 3. Resolve cross-stale entries (N) | finding (g) > 0 | `Skill(skill="/vp-beads:upstream-tracker", args=...)` → workflow 3 (Resolve an entry) |675| 0. None — upstream report only | always | exit UPSTREAM tier without action |676677If neither tier has actionable findings for a sibling, skip the678`AskUserQuestion` call entirely for that sibling. If only one tier has679actionable findings, issue a single-question call (the SDK supports 1-4680questions per call).681682**Private-sibling guard (no-commit-leak).** When the sibling's merged registry683`file` is `PRIVATE-SYNERGY-*`, every committed-write menu option is removed684because it would commit the private name:685686- **Q2 option 2 (`bd create`) is suppressed** — a `.beads/*.jsonl` entry naming687 the sibling would leak it. The finding stays in the report only. (Finding (e)688 does not arise anyway: workflow 3 (Sync sibling UPSTREAM) skips Mode B for689 private siblings.)690- **Q1 option 2 (Log unreciprocated sibling entries) redirects** — its691 `/synergy-tracker` dispatch targets the gitignored `PRIVATE-SYNERGY-<name>.md`,692 never a committed `SYNERGY-<name>.md` (pass the private destination in the693 `args` prose).694- **Q1 option 1 (Apply reciprocal gaps) is absent** — workflow 4 (Apply695 reciprocation batch) already excludes private siblings.696697If that leaves no actionable options for a private sibling, skip the prompt and698present the read-only findings as report-only.699700### Per-action argument templates701702Pass natural-language prose in the `Skill` tool's `args` field. The703delegated skill receives the prose as narrative context. Templates:704705- **SYNERGY 2 (Log unreciprocated sibling entries):**706 `Log unreciprocated entries from sibling <sibling-name>: <bullet list of titles + sections>. Invoke workflow 1 (Log a synergy entry) for each.`707- **UPSTREAM 1 (Update our UPSTREAM, b/d collapse):**708 `From sibling-sync findings against <sibling-name>: adopt complementary workarounds for <package, title> entries (sibling's workaround text: <quoted>); also scan sibling-only entries <package, titles>. Use workflow 1 (Log a new entry) and workflow 7 (Sync from Basic Memory) as appropriate.`709- **UPSTREAM 3 (Resolve cross-stale entries):**710 `Resolve entries in UPSTREAM-<sibling-name>.md: <titles>. Verify against the sibling's recent changelog/tags first. Invoke workflow 3 (Resolve an ent711712…(truncated)