sync upstream 07-22 refactor + substrate bump to 76bac5d0 (squashed patch) - #12
Merged
Merged
Conversation
…arting the Python sidecar
…ommand naming consistency
…SON and --config-file for paths
…nvironment support
…essesConfig to RegistryConfig
… flags to the root command
… from Kubernetes dependencies
Squashed agentfleet patch (imagecache Phase 1 + post-Phase-1 fixes through #510). Kept as a single commit on top of upstream sync merges so future upstream follows can cherry-pick it cleanly. - go.mod: substrate v0.0.0-20260706222328-3cb7433bd8a8 -> v0.0.0-20260724043042-76bac5d05142 - internal/ate/client.go, internal/harness/substrate/substrate.go, internal/harness/harnesstest/harnesstest.go: ActorRef/ActorId -> name-based addressing per upstream wire change Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017TK34TZokEcfPq5JdbUVWo
Absorbs the 07-24 batch: google#237 inter-component mTLS strict verify, #405 per-actor external volumes, #496 ateom de-privileged, #491 router health concurrency, #516 kubectl ate top workers, #523 ateapi graceful shutdown, #532 volume validation, and the three ateom-microvm durable-dir commits. No client-API changes; zero code adaptation. Cert-rotation risk from google#237 (upstream #531 still open) stays masked by the 12h ate-cert-restart CronJob. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017TK34TZokEcfPq5JdbUVWo
feifeigood
marked this pull request as ready for review
July 26, 2026 01:59
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.
Reworks #11 per new fork policy: follow all upstream first, then stack our patches.
Structure (3 commits)
google/axmain (cbd2c56, the 07-22 24-commit refactor storm — upstream has been quiet since). Conflict resolution keeps upstream's renames and our patches:seq→stepproto rename absorbed; ourharness_metadatafield (fix(controller): carry terminal harness metadata on the FAILED path #7 FAILED-metadata patch) retained onExecResponse/ConversationEvent;internal/k8s/ate→internal/atepackage move absorbed;proto/ax.pb.go+python/proto/ax_pb2.pyregenerated viamake proto.29f029f): pin3cb7433b→76bac5d0(imagecache Phase 1 + fixes through upstream substrate #510) + name-based actor API adaptation in 3 files.1234e31):76bac5d0→aa1d14a7(per maintainer instruction) — absorbs the 07-24 batch (Rename ControllerService to ExecutionService google/ax#237 mTLS strict verify, #405 external volumes, #496/#491/#516/#523/#532, microvm durable-dir). Zero code adaptation. Rename ControllerService to ExecutionService google/ax#237's cert-rotation exposure (upstream #531 open) stays masked by the 12h ate-cert-restart CronJob.Squash the two deps commits at merge (or treat
29f029f..1234e31as one unit when cherry-picking) to keep the single-patch maintenance model: future upstream follows = merge upstream → cherry-pick the patch.Verification
go build ./...+go vet ./...+go test -race ./...at each step — 13 packages ok, 0 failures.seq→stepbreaks af's turn stream +last-seqresume (2 non-test files) and renames ax'sconversation_log.seqDB column; existing protojson payloads carry"seq"keys that the new stub silently drops (DiscardUnknown) → cutover needs a one-shot SQL migration (column rename + payload key rewrite) with ax+af scaled to 0.ax.yamltop-level keyharnesses:→registry:(old key silently ignored → empty registry).Supersedes #11.
🤖 Generated with Claude Code
https://claude.ai/code/session_017TK34TZokEcfPq5JdbUVWo