Skip to content

refactor(create-expert): clarify context passing mechanism between delegates#392

Merged
FL4TLiN3 merged 2 commits intomainfrom
refactor/382-context-passing
Jan 3, 2026
Merged

refactor(create-expert): clarify context passing mechanism between delegates#392
FL4TLiN3 merged 2 commits intomainfrom
refactor/382-context-passing

Conversation

@FL4TLiN3
Copy link
Contributor

@FL4TLiN3 FL4TLiN3 commented Jan 3, 2026

Summary

Makes explicit that context is passed via query (not shared state) since Perstack delegates only receive the query - no message history or parent context.

Changes

CREATE_EXPERT_INSTRUCTION:

Added "Context Passing" section:

## Context Passing

Delegates only receive the query - no shared state. Include all needed context inline:

**To property-extractor:**
Include the original user requirements in the query.

**To ecosystem-builder:**
Include extracted properties and original requirements in the query.

**To integration-manager:**
Include ecosystem info (expert names) and properties in the query.

**To report-generator:**
Include all accumulated context: requirements, properties, ecosystem info, and test results.

REPORT_GENERATOR_INSTRUCTION:

Clarified input source:

## Input (provided in your query)

The coordinator passes all context in the query:
- Original requirements: What the user asked for
- Extracted properties: From property-extractor output
- Ecosystem info: Expert names and structure
- Test results: From integration-manager output

This aligns with Perstack's context isolation design documented in docs/understanding-perstack/experts.md.

Closes #382

Test plan

  • CI passes
  • No behavior changes expected

Note

Clarifies context passing across delegates

  • In CREATE_EXPERT_INSTRUCTION, adds a "Context Passing" section stating delegates receive only the query (no shared state) and specifying what context to include for property-extractor, ecosystem-builder, integration-manager, and report-generator.
  • In REPORT_GENERATOR_INSTRUCTION, updates "Input" to explicitly note all context is provided in the query (requirements, extracted properties, ecosystem info, test results).
  • Adds .changeset/refactor-382-context-passing.md to release a patch.

Written by Cursor Bugbot for commit 7281c4d. This will update automatically on new commits. Configure here.

@codecov
Copy link

codecov bot commented Jan 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

FL4TLiN3 and others added 2 commits January 3, 2026 07:50
…legates

Make explicit that context is passed via query (not shared state) since
Perstack delegates only receive the query - no message history or parent context.

Changes to CREATE_EXPERT_INSTRUCTION:
- Add "Context Passing" section explaining the mechanism
- Specify what context to include for each delegate
- Replace procedural workflow with declarative delegates list

Changes to REPORT_GENERATOR_INSTRUCTION:
- Clarify that input comes from the query
- Explain what the coordinator provides

This aligns with Perstack's context isolation design documented in
docs/understanding-perstack/experts.md.

Closes #382

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@FL4TLiN3 FL4TLiN3 force-pushed the refactor/382-context-passing branch from a5726fa to 7281c4d Compare January 3, 2026 07:50
@FL4TLiN3 FL4TLiN3 merged commit d9a6370 into main Jan 3, 2026
7 checks passed
@FL4TLiN3 FL4TLiN3 deleted the refactor/382-context-passing branch January 3, 2026 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Refactor: clarify context passing mechanism between create-expert delegates

1 participant