Refine Threadsmith orchestration hygiene - #60
Merged
Conversation
Teddy-creator
force-pushed
the
hygiene/performance-redundancy-v1
branch
from
May 29, 2026 06:39
d703096 to
773f11d
Compare
Teddy-creator
force-pushed
the
hygiene/performance-redundancy-v1
branch
from
May 29, 2026 06:51
773f11d to
8f7147c
Compare
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.
Summary\n- add role runtime timing fields for packet build, launch wait, result apply/read, and observed bridge overhead\n- split role packet construction into clearer orchestration defaults, build context, packet specs, and prompt contracts\n- reuse shared packet context reads and guard nested git evidence from parent repo noise\n\n## Verification\n- npm run test --workspace @threadsmith/domain\n- npm run test --workspace @threadsmith/orchestrator\n- npm run test --workspace @threadsmith/fs-bridge\n- npm run verify:project-truth\n- git diff --check\n- npm run build --workspaces --if-present\n\nFrontend remains frozen. No release or global skill sync.