docs: move build optimizations out of the agent guide - #449
Merged
Conversation
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
1 participant
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.
Description
The root agent guide mixes build-optimization details into the normal workflow, even when they do not change the agent's next action. Fixes #448.
Solution
Keep cache warm-up, ABI selection, fingerprint fallback, and build-sharing mechanics in
guide lifecycle buildsandguide lifecycle concurrency. The root keeps the required workflow, ownership/cleanup safety, short retry instruction, and links to those sections.Narrow the original authoring rule, which put every operational detail in the root, so optimization internals stay in the detailed, version-matched guides.
Independent of #447, which removes its PCH-specific root-guide note.
Test plan
guide agent,guide lifecycle builds, andguide lifecycle concurrency; verified the moved details remain accessible and the root retains worktree, device, and verification rules.