repo-scoping/docs/self-scoping/assessments/repo-scoping-post-wp0015-clean-2026-05-15.md

Self-Scoping Comparison: repo-scoping-challenger-run-1

• Status: regression
• Golden profile: repo-scoping-golden-profile-v1
• Target repo: repo-scoping
• Summary: Assessment repeats known or forbidden self-scoping patterns; prefer the golden profile until the engine is corrected.

Missing Expected Capabilities

• Explore Dependency And Impact Graphs
• Generate And Maintain SCOPE.md
• Generate Reviewable Candidate Characteristics
• Index Source Content With Provenance
• Provide Scope Context To Downstream Agents
• Register And Track Repositories
• Review And Approve Candidate Characteristics
• Scan Repositories Into Observed Facts
• Search Compare And Export Approved Profiles

Forbidden Native Capabilities Present

• Route LLM Requests Across Providers

Known Regression Patterns

• RREG-SELF-REG-001 LLM provider vocabulary promoted as native capability: Generated tree contains Route LLM Requests Across Providers as a repo-scoping capability.
• RREG-SELF-REG-002 Native API and CLI surfaces attached under false capability: API or CLI surface features are nested below provider routing.

Misplaced Features

• HTTP API surface: possible API surface, GET /health, @app.get(, +49 more under Route LLM Requests Across Providers (API): API/CLI surface is nested below provider-routing capability.
• CLI command surface: CLI command build_parser, CLI command make_service under Route LLM Requests Across Providers (CLI): API/CLI surface is nested below provider-routing capability.

Matched Expected Capabilities

• None

Review Hints

• Do not promote this assessment as a preferred baseline.
• Inspect forbidden capabilities and misplaced features first.
• Use the findings as signal for scanner, generator, or acceptance-policy changes.