cleveragents/cleveragents-core

Fork 3

UAT: ComponentResolver docstring claims "27 extension points" but extension_catalog.py defines 30 — TOTAL_EXTENSION_POINTS constant inconsistency #3169

New issue

Open

opened 2026-04-05 07:11:04 +00:00 by freemo · 1 comment

freemo commented

2026-04-05 07:11:04 +00:00

Owner

Metadata

Branch: fix/component-resolver-extension-points-docstring
Commit Message: docs(component_resolver): correct stale "27 extension points" docstring to 30
Milestone: None (backlog)
Parent Epic: #397

Description

There is a documentation inconsistency between src/cleveragents/application/services/component_resolver.py and src/cleveragents/infrastructure/plugins/extension_catalog.py regarding the number of spec-defined extension points.

What was tested

Code analysis of src/cleveragents/application/services/component_resolver.py — module docstring
Code analysis of src/cleveragents/infrastructure/plugins/extension_catalog.py — TOTAL_EXTENSION_POINTS constant and _EXTENSION_POINT_DEFS tuple

Expected behavior

All references to the number of extension points should be consistent. The authoritative count should match the actual number of entries in _EXTENSION_POINT_DEFS.

Actual behavior

component_resolver.py module docstring (line ~12): "The specification defines 27 extension points across ACMS pipeline components, context strategies, sandbox strategies, UKO vocabulary/analyzers, and validation implementations"
extension_catalog.py line 257: TOTAL_EXTENSION_POINTS: int = 30
Actual count of entries in _EXTENSION_POINT_DEFS tuple: 30 (12 context + 3 output + 2 validation + 2 tools + 2 skills + 2 resources + 2 A2A + 2 events + 2 config + 1 safety = 30)

The component_resolver.py docstring is stale — it references "27 extension points" from an earlier version of the spec, but the catalog has since grown to 30.

Code location

src/cleveragents/application/services/component_resolver.py — module docstring, line ~12
src/cleveragents/infrastructure/plugins/extension_catalog.py — TOTAL_EXTENSION_POINTS = 30 (line 257) and _EXTENSION_POINT_DEFS tuple (30 entries)

Steps to reproduce

Read component_resolver.py module docstring — says "27 extension points"
Read extension_catalog.py — TOTAL_EXTENSION_POINTS = 30, 30 entries in _EXTENSION_POINT_DEFS

Impact

Documentation inconsistency. Developers reading component_resolver.py will have incorrect expectations about the number of extension points. Low severity but should be corrected for accuracy.

Subtasks

Update component_resolver.py module docstring: replace "27 extension points" with "30 extension points"
Audit the rest of component_resolver.py for any other stale numeric references to extension point counts
Audit all other files in src/cleveragents/ for any stale "27 extension points" references
Verify TOTAL_EXTENSION_POINTS = 30 in extension_catalog.py matches the actual count of entries in _EXTENSION_POINT_DEFS
Run nox (all default sessions), fix any errors
Verify coverage >= 97% via nox -s coverage_report

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
All nox stages pass.
Coverage >= 97%.

Backlog note: This issue was discovered during autonomous operation
on milestone None. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-uat-tester

## Metadata - **Branch**: `fix/component-resolver-extension-points-docstring` - **Commit Message**: `docs(component_resolver): correct stale "27 extension points" docstring to 30` - **Milestone**: None (backlog) - **Parent Epic**: #397 ## Description There is a documentation inconsistency between `src/cleveragents/application/services/component_resolver.py` and `src/cleveragents/infrastructure/plugins/extension_catalog.py` regarding the number of spec-defined extension points. ### What was tested - Code analysis of `src/cleveragents/application/services/component_resolver.py` — module docstring - Code analysis of `src/cleveragents/infrastructure/plugins/extension_catalog.py` — `TOTAL_EXTENSION_POINTS` constant and `_EXTENSION_POINT_DEFS` tuple ### Expected behavior All references to the number of extension points should be consistent. The authoritative count should match the actual number of entries in `_EXTENSION_POINT_DEFS`. ### Actual behavior - `component_resolver.py` module docstring (line ~12): "The specification defines **27 extension points** across ACMS pipeline components, context strategies, sandbox strategies, UKO vocabulary/analyzers, and validation implementations" - `extension_catalog.py` line 257: `TOTAL_EXTENSION_POINTS: int = 30` - Actual count of entries in `_EXTENSION_POINT_DEFS` tuple: **30** (12 context + 3 output + 2 validation + 2 tools + 2 skills + 2 resources + 2 A2A + 2 events + 2 config + 1 safety = 30) The `component_resolver.py` docstring is stale — it references "27 extension points" from an earlier version of the spec, but the catalog has since grown to 30. ### Code location - `src/cleveragents/application/services/component_resolver.py` — module docstring, line ~12 - `src/cleveragents/infrastructure/plugins/extension_catalog.py` — `TOTAL_EXTENSION_POINTS = 30` (line 257) and `_EXTENSION_POINT_DEFS` tuple (30 entries) ### Steps to reproduce 1. Read `component_resolver.py` module docstring — says "27 extension points" 2. Read `extension_catalog.py` — `TOTAL_EXTENSION_POINTS = 30`, 30 entries in `_EXTENSION_POINT_DEFS` ### Impact Documentation inconsistency. Developers reading `component_resolver.py` will have incorrect expectations about the number of extension points. Low severity but should be corrected for accuracy. ## Subtasks - [ ] Update `component_resolver.py` module docstring: replace "27 extension points" with "30 extension points" - [ ] Audit the rest of `component_resolver.py` for any other stale numeric references to extension point counts - [ ] Audit all other files in `src/cleveragents/` for any stale "27 extension points" references - [ ] Verify `TOTAL_EXTENSION_POINTS = 30` in `extension_catalog.py` matches the actual count of entries in `_EXTENSION_POINT_DEFS` - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - All nox stages pass. - Coverage >= 97%. > **Backlog note:** This issue was discovered during autonomous operation > on milestone None. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-uat-tester

freemo added a new dependency

2026-04-05 07:14:22 +00:00

#397 Epic: Server & Autonomy Infrastructure

freemo added the

MoSCoW

Could have

label

2026-04-05 07:22:43 +00:00

freemo added this to the v3.6.0 milestone

2026-04-05 07:22:44 +00:00

freemo modified the milestone from v3.6.0 to v3.8.0

2026-04-05 07:24:00 +00:00

freemo commented

2026-04-05 07:25:52 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Backlog — documentation inconsistency only; no functional impact
Milestone: v3.8.0
MoSCoW: Could Have — this is a stale docstring ("27 extension points" vs actual 30). Low severity, no functional impact. Can be fixed opportunistically.
Parent Epic: #397

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog — documentation inconsistency only; no functional impact - **Milestone**: v3.8.0 - **MoSCoW**: Could Have — this is a stale docstring ("27 extension points" vs actual 30). Low severity, no functional impact. Can be fixed opportunistically. - **Parent Epic**: #397 --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo referenced this issue

2026-04-05 07:27:04 +00:00

Task: Autonomous build progress report — 2026-04-05 #3075

freemo referenced this issue

2026-04-05 07:37:42 +00:00

[CA-AUTO] UAT Pool Supervisor — v3.2.0–v3.7.0 — Session Tracker #3094

freemo referenced this issue

2026-04-05 07:47:07 +00:00

[CA-AUTO] UAT Pool Supervisor — v3.2.0–v3.7.0 — Session Tracker #3124