Guild Stack
Run / Verify a host-adapter migration run

R06 / Run

Verify a host-adapter migration run

The migration-specific evidence packet, reviewer requirements, and followup policy used to verify work against the host-adapter migration spec.
First move
Verify one host-adapter migration
Expected receipt
G-implementation:<host-id> packet
Last verified
Jul 17, 2026

Page evidence and guidance

Read as StartThe migration goal, exact tests, required review packet, docs sync, and support evidence. SteerG-implementation review packets, cross-host independence, followup classification, and support-matrix proof. ExtendPer-host review gates, liveness, degraded-local evidence, documentation reconciliation, and receipt-derived support state.

This page summarizes the execution gate for the host-adapter migration in docs/v2/host-adapter-migration-spec.md. It is not the generic completion contract for every Guild Stack task. A migration run is complete only when its packet proves the assigned migration goals, the required host reviews have no unresolved issues, tests cover the host claims, docs/v2 and support evidence are current, and every followup is resolved or assigned to a named later migration run.

Evidence bar

What a verified migration packet contains

Gate Required evidence Owner Path
Code diff Exact files changed, traceable to the lane scope that was approved. Author lane .guild/runs/<run-id>/evidence.md
Tests / build Exact test commands and outputs proving the claimed behavior, not just that a suite ran green. Author lane .guild/runs/<run-id>/evidence.md
Review posture Claude reviews every migration run. A Claude-family author also requires Codex cross-host review, or the explicit degraded-local skip-streak evidence when Codex is unavailable. Reviewer host .guild/runs/<run-id>/review/G-implementation:<host-id>/
Docs sync Canonical docs stay current and website-ready; a documentation followup blocks the run if user-facing docs are affected. Author lane docs/v2/** or src/content/docs/**
Followups None open, or explicitly reclassified into a named later run. Followups never disappear into prose. Lead .guild/runs/<run-id>/followups.md
Migration closeout The affected host claim and generated support-matrix row match executable evidence; tests passing alone does not promote support. Lead .guild/runs/<run-id>/run.yaml
These fields belong to a host-adapter implementation run under .guild/runs/<run-id>/. Other run classes use their own phase and verification contracts.

Followup policy

Followups are classified, not left as loose prose:

  • Blocking followup: the run cannot close until it is fixed and re-reviewed.
  • Non-blocking local followup: may move to a named later run only if that run already exists and the current run still proves its own goals without the fix.
  • Plugin-level followup: becomes a sanitized analysis artifact and requires user approval before it is filed as an issue.
  • Documentation followup: blocks the run if the changed behavior affects user-facing docs, website source docs, or support-matrix claims.

Migration review gate

After local tests pass, every host-adapter migration run requires Claude review at review/G-implementation:<host-id>/. If Claude-family authored the change, Codex must also provide the independence-satisfying cross-host review. When Codex is unavailable, the packet records the degraded-local path, independence: weak, and the .guild/codex-skip-streak.json sentinel. A reviewer that produces no output, stops heartbeating, or gives a broad ungrounded response leaves the migration review inconclusive.

See Also