doc-cross-repo-dependency-flow

Packet · {{ group }} · cross-repo/dependency-flow.md

Group mode only. This packet runs when the skill orchestrator is invoked with --group {{ group }}. In single-repo mode it is never seeded.

1. Objective

Produce {{ group_docs_root }}/cross-repo/dependency-flow.md: a single Mermaid flowchart TB showing inter-repo data flow across the {{ group }} group — nodes are repos (plus events/streams as needed), edges are contract groups labeled by HTTP verb + path or event type.

2. Scope

• Create: {{ group_docs_root }}/cross-repo/dependency-flow.md
• Do not touch: any other file under {{ group_docs_root }}/, any file under a member repo (including {{ member_repos }}/), {{ group_context_path }}, {{ group_prefetch_path }}, or any .packets/*.md other than this one.

3. Input specification

Source	Read how	Cache state
Group shared context	Read {{ group_context_path }}	always first
Group prefetch ledger	Read {{ group_prefetch_path }}	always first
Member list + freshness	{{ group_context_path }} § Members / {{ group_prefetch_path }} § group_list,group_status	cached
Group contracts	{{ group_prefetch_path }} § group_contracts	cached
Per-member route inventory	{{ group_prefetch_path }} § route_map(<repo>) per {{ member_repos }}	cached
Async / event topics	mcp__codehub__group_query({group: "{{ group }}", text: "message consumer"}) or "publishes"	mid-run, only if stream edges are suspected

4. Process

1. Read {{ group_context_path }} and Read {{ group_prefetch_path }}. Confirm the member list and re-verify every member is tagged fresh in the cached group_status digest. Abort to Work log if any member is stale.
2. Pull the contract inventory from {{ group_prefetch_path }} § group_contracts. For each (producer_repo, consumer_repo) pair, group the contracts by method + path-prefix to form a single edge labeled with the representative HTTP verb + path (e.g., POST /invoices).
3. Scan the contract list for event/stream shapes (kind = topic / queue / stream in the cached digest). For each stream, add a parenthesized node name[(stream.name)] and draw dashed edges (-.->) from consumers and solid edges (-->) from publishers.
4. Compose the node set: one node per member repo (repo["repo"] plain rectangle) plus one parenthesized node per event/stream. Cap at 20 nodes — if the group plus streams exceed 20, keep the top-20 by edge count and move overflow into a ## Legend (overflow) table.
5. Compose the edge set: solid arrows for synchronous HTTP calls, dashed arrows for async/pub-sub. Each edge label carries the HTTP verb + path (routes) or the event type (streams); ≤ 15 chars.
6. Draft the Mermaid flowchart TB. Every repo node's string identifier and every path/event on every edge must trace back to group_contracts or a route_map digest — no invented flows.
7. Write {{ group_docs_root }}/cross-repo/dependency-flow.md with H1 = {{ group }} · Dependency flow.