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"