From bb71aec52bd8eabdaf4f3afa65cfb9543643614d Mon Sep 17 00:00:00 2001 From: Ubuntu Date: Tue, 20 Oct 2026 11:17:20 +0800 Subject: [PATCH] docs: clarify integration workspace workflow Document explicit workspace selection for runtime validation, standalone GOWORK=off checks, and independent child commits and integration pin updates. Validation: documentation and script consistency review; git diff --check. No source, dependency, or integration pin changes. Co-authored-by: Codex --- AGENTS.md | 26 +++++++++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 9c42a55..12b2a9f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -169,6 +169,26 @@ and consume public node/runtime capabilities. ## Validation -Run `gofmt`, `git diff --check`, `go test ./...`, `go vet ./...`, and -`go build -buildvcs=false ./...` before committing. Also run a Windows -cross-build for changes to daemon lifecycle, locking, filesystem, or CLI code. +For Go changes, run `gofmt`, `git diff --check`, `GOWORK=off go test ./...`, +`GOWORK=off go vet ./...`, and `GOWORK=off go build -buildvcs=false ./...` +before committing. Also run a Windows cross-build with `GOWORK=off` for changes +to daemon lifecycle, locking, filesystem, or CLI code. Apply the shared host's +resource limits to full-module checks. Documentation-only changes require +relevant content checks and `git diff --check`, not a full Go suite. + +This repository may be a standalone checkout or a pinned submodule of +`malt-integration`. Follow the parent `AGENTS.md` when present and the +integration guide when working inside that checkout. Its ancestor `go.work` +can substitute local modules, so check `go env GOWORK` and actual module +directories before validation. + +Use the integration root's `scripts/verify-go.sh` for pinned Go combinations. +For development branches/worktrees, run the selected evaluator's boundary +checker with absolute `MALT_CORE_REPO`, `MALT_RUNTIME_REPO`, and `GATEWAY_REPO` +paths and `MALT_INTEGRATION_REQUIRED=1`; record HEADs and dirty states. +Standalone runtime checks and Gateway-owned product E2E remain separate +validation boundaries. + +Use a topic branch and PR for runtime changes. Create a branch before editing +a detached submodule, push child commits to this repository, and update +integration Git links only in a separate reviewed integration change.