.agents/skills/summarise-ecosystem-results/references/subagent-handoff.md
Use this reference whenever the summary skill delegates reproduction or minimization.
Freeze the exact report, Actions run, and attempt. Run scripts/collect_ty_ecosystem_run_metadata.py once for all projects with retained source-attributable diagnostics or new, fixed, or meaningfully changed reproducible failure outcomes, then build and copy both exact-revision profiling binaries before assigning any subagent work.
Publish the immutable TY_ECOSYSTEM_RUN_METADATA, TY_ECOSYSTEM_BASE_BINARY, and TY_ECOSYSTEM_PR_BINARY absolute paths. Install the copied PR ecosystem config once at $TY_ECOSYSTEM_CONFIG_HOME/ty/ty.toml and publish the absolute TY_ECOSYSTEM_CONFIG_HOME path. Treat the snapshot, optional structured JSON, binaries, metadata, copied config, and installed configuration as read-only shared inputs.
If a subagent requests an exact-revision debug binary, only the primary agent may build it. Pause every active worker and wait for acknowledgment, verify the shared checkout is clean, remember its original ref, then build and copy the requested binary. Always restore the original ref before resuming workers, even if the build fails; publish the binary's immutable path only after a successful build and restoration. The profiling binaries remain the behavioral oracle.
Subagents must not regenerate shared manifests, rebuild shared profiling binaries, switch shared Ruff refs, rewrite shared configuration, or overwrite another agent's working files.
Give each subagent:
TY_ECOSYSTEM_RUN_METADATA, TY_ECOSYSTEM_BASE_BINARY, TY_ECOSYSTEM_PR_BINARY, and TY_ECOSYSTEM_CONFIG_HOME absolute paths.gh invocation with GH_TELEMETRY=false.minimizing-ty-ecosystem-changes skill with the shared manifest, copied profiling binaries, installed configuration, and a unique temporary directory; never generate another manifest.git -C <ruff-checkout> show <exact-revision>:<repository-relative-path>, using the analyzed revisions from the immutable manifest rather than the restored working tree.Request:
If a later entry has exactly the same behavior change and cause as an already minimized entry, the subagent may classify it as a duplicate instead of repeating the full minimization, but it must explain the match.