Repository navigation
Test the Architect plan's checks and the Architect idea's labelling in-process behind the Pass seam - #387
Merged
Conversation
…, tested in-process (#386) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
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.
Summary
The Architect run's conclusion now reaches GitHub through the Pass seam it already holds for its gates. A plan is viewed once, and its Edit is built from that view.
Edit::readis deleted, so building an Edit no longer does I/O.progress::step.Evidence
gh(5 tests intests/architect_run.rs).After: 13 new unit tests in
src/architect.rsdriveconcludewithpass::InMemoryand assert on the ending or cause and on the call record:cargo test(every suite),cargo clippy --all-targetsandcargo fmt --checkall pass.Merge Danger
Door: two-way
This is an internal refactor. Users see the same progress lines, causes, labels, stdout, exit codes and Run notifications.
Blast Radius: Architect-runs
A plan now takes one fewer
ghrequest. Its Edit is built from the labels viewed for the checks. A label someone adds between that view and the Edit is overwritten. Before, the Edit read the labels a second time, so it kept such a label.Unaddressed findings
Standards
runstill callsinterrupt::requested()andreviewstill callsprogress::stepdirectly: skipped. That check comes before the review and is outside the conclusion. The issue says the review's starting line stays where it is.origin,startedandbasepassed together: skipped. This is a judgement call outside this issue's scope, and the parameters were there before.Call::Edittest helper inarchitect.rsandpickup.rs: skipped. It is a small test-only helper. A shared helper inpass::in_memorycan come with a later seam change.viewed(bool, i64, …)test helper parameters aren't self-describing: skipped. Its doc comment explains them, and the gates'InMemory::issue(n, open, labels)uses the same style.Spec
a_plan_created_in_the_second_the_run_started_passesis beyond the listed cases: kept. It covers the spec's "created since the run started (to the second)".Closes #386
🤖 Generated with Claude Code