memory backpass: analysis calls run pi with tools off #280
No reviewers
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/tools!280
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/backpass-analysis-no-tools"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The built-in
piseat now runs the bulk and fallback analysis calls withpi -p --no-tools; the synthesis call and its fix call keep tools on because they edit the worktree. Nothing else changes. What proves it: the first realallod memory backpass --report-onlyrun on a dev VM showed the analysis call opening with "Let me read the memory files first as instructed", becausepi -ploads the machine's harness instruction file and, with tools on, follows its read-memory-at-start step instead of answering; the built-in seat test now records the stub pi's argv and asserts--no-toolson every analysis call and its absence on the synthesis call. If it is wrong: revert the one commit; an explicit--bulk-seatwrapper is unaffected either way.Refs allod/strategy#55
Risk
R1. One flag on one built-in invocation, with a test on the argv.
Validation
gofmt -l cmd/allodempty;go vet ./cmd/allod/...cleango test ./cmd/allodok;go test -tags site,secret ./cmd/allodok, rerun by the integratornix build .#checks.x86_64-linux.go-checkspasses (worker's run)