feat(context): implement example custom scope resolver and scope chain documentation #5535

Open
opened 2026-04-09 07:14:57 +00:00 by HAL9000 · 1 comment
Owner

Background

Part of Epic #5507 (Pluggable Scope Chain Resolution). Provides an example custom scope resolver implementation and comprehensive documentation for the scope chain extension system.

Expected Behavior

  • GitBranchScopeResolver example that adds git branch name as a scope dimension
  • TeamScopeResolver example that adds team membership as a scope dimension
  • Documentation in docs/scope-chain-extensions.md explaining how to write custom resolvers
  • Example YAML configuration showing how to enable custom resolvers
  • Integration tests verifying custom resolvers work end-to-end

Subtasks

  • Implement GitBranchScopeResolver example resolver
  • Implement TeamScopeResolver example resolver
  • Write docs/scope-chain-extensions.md documentation
  • Add example YAML configuration for custom resolvers
  • Write Robot Framework integration tests for custom scope resolvers

Definition of Done

  • Example resolvers functional and documented
  • Documentation explains how to write custom resolvers
  • Integration tests pass
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch: feat/v3.6.0/pluggable-scope-chain
  • Commit Message: feat(context): implement example custom scope resolver and scope chain documentation
  • Milestone: v3.6.0
  • Parent Epic: #5507
  • Depends on: #5531 (ScopeChainResolver protocol must exist first)

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Background Part of Epic #5507 (Pluggable Scope Chain Resolution). Provides an example custom scope resolver implementation and comprehensive documentation for the scope chain extension system. ## Expected Behavior - `GitBranchScopeResolver` example that adds git branch name as a scope dimension - `TeamScopeResolver` example that adds team membership as a scope dimension - Documentation in `docs/scope-chain-extensions.md` explaining how to write custom resolvers - Example YAML configuration showing how to enable custom resolvers - Integration tests verifying custom resolvers work end-to-end ## Subtasks - [ ] Implement `GitBranchScopeResolver` example resolver - [ ] Implement `TeamScopeResolver` example resolver - [ ] Write `docs/scope-chain-extensions.md` documentation - [ ] Add example YAML configuration for custom resolvers - [ ] Write Robot Framework integration tests for custom scope resolvers ## Definition of Done - [ ] Example resolvers functional and documented - [ ] Documentation explains how to write custom resolvers - [ ] Integration tests pass - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch**: `feat/v3.6.0/pluggable-scope-chain` - **Commit Message**: `feat(context): implement example custom scope resolver and scope chain documentation` - **Milestone**: v3.6.0 - **Parent Epic**: #5507 - **Depends on**: #5531 (ScopeChainResolver protocol must exist first) --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.6.0 milestone 2026-04-09 07:16:13 +00:00
Author
Owner

Label compliance fix applied:

  • Added missing labels: Type/Feature, Priority/High, State/Verified
  • Reason: Feature issue had no labels. Type inferred from feat(context) prefix. Priority/High and State/Verified inferred from context.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels: `Type/Feature`, `Priority/High`, `State/Verified` - Reason: Feature issue had no labels. Type inferred from `feat(context)` prefix. Priority/High and State/Verified inferred from context. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#5535
No description provided.