HAL9000
39fa613890
CI / push-validation (pull_request) Successful in 28s
CI / helm (pull_request) Successful in 35s
CI / build (pull_request) Successful in 54s
CI / lint (pull_request) Failing after 1m9s
CI / quality (pull_request) Successful in 1m27s
CI / typecheck (pull_request) Successful in 1m34s
CI / security (pull_request) Successful in 1m52s
CI / coverage (pull_request) Has been skipped
CI / e2e_tests (pull_request) Successful in 4m17s
CI / integration_tests (pull_request) Successful in 4m50s
CI / unit_tests (pull_request) Failing after 6m6s
CI / docker (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 3s
- Fix AmbiguousStep conflict: rename documentation_steps.py step patterns from generic 'it should contain {text}' to 'the documentation should contain {text}' to avoid collision with k8s_helm_chart_steps.py and other step files
- Fix execution_environment.feature: update remaining 'it should contain' steps to 'the container types should contain' for consistency with line 132
- Add features/align_documentation.feature: Behave tests for the documentation changes using the new documentation-scoped step patterns
- Update docs/reference/skeleton_compressor.md: add DepthReductionCompressor references, correct module path (acms_skeleton_compressor), add v3.5.0 milestone
- Update docs/reference/di.md: add Skeleton Compressor Resolution section with resolve_configured_skeleton_compressor() and DepthReductionCompressor docs
- Update docs/reference/devcontainer_resources.md: add v3.6.0 named configuration scanning section, document config_name attribute, update discovery module docs
51 lines
2.7 KiB
Gherkin
51 lines
2.7 KiB
Gherkin
Feature: Documentation alignment for DepthReductionCompressor and devcontainer discovery
|
|
As a developer reading the CleverAgents documentation
|
|
I need the reference docs to accurately reflect the current implementation
|
|
So that I can understand and use the system correctly
|
|
|
|
# ── skeleton_compressor.md ──────────────────────────────────────────
|
|
|
|
Scenario: skeleton_compressor.md references DepthReductionCompressor
|
|
Given the skeleton_compressor.md documentation file exists
|
|
When I read the skeleton_compressor.md documentation file
|
|
Then the documentation should contain "DepthReductionCompressor"
|
|
|
|
Scenario: skeleton_compressor.md references the correct module path
|
|
Given the skeleton_compressor.md documentation file exists
|
|
When I read the skeleton_compressor.md documentation file
|
|
Then the documentation should contain "acms_skeleton_compressor"
|
|
|
|
Scenario: skeleton_compressor.md references v3.5.0 milestone
|
|
Given the skeleton_compressor.md documentation file exists
|
|
When I read the skeleton_compressor.md documentation file
|
|
Then the documentation should contain "v3.5.0"
|
|
|
|
# ── di.md ───────────────────────────────────────────────────────────
|
|
|
|
Scenario: di.md documents the DI resolution path
|
|
Given the di.md documentation file exists
|
|
When I read the di.md documentation file
|
|
Then the documentation should contain "resolve_configured_skeleton_compressor"
|
|
|
|
Scenario: di.md usage example matches tuple return type
|
|
Given the di.md documentation file exists
|
|
When I read the di.md documentation file
|
|
Then the documentation should contain "DepthReductionCompressor"
|
|
|
|
# ── devcontainer_resources.md ───────────────────────────────────────
|
|
|
|
Scenario: devcontainer_resources.md covers named configuration scanning
|
|
Given the devcontainer_resources.md documentation file exists
|
|
When I read the devcontainer_resources.md documentation file
|
|
Then the documentation should contain "named configuration"
|
|
|
|
Scenario: devcontainer_resources.md references v3.6.0
|
|
Given the devcontainer_resources.md documentation file exists
|
|
When I read the devcontainer_resources.md documentation file
|
|
Then the documentation should contain "v3.6.0"
|
|
|
|
Scenario: devcontainer_resources.md documents config_name attribute
|
|
Given the devcontainer_resources.md documentation file exists
|
|
When I read the devcontainer_resources.md documentation file
|
|
Then the documentation should contain "config_name"
|