Fix ConfigurationManager API mismatch: register_config_type vs register_config

[jeremymanning]

Problem

The test suite for ConfigurationManager expects methods and attributes that don't match the actual implementation:

Tests expect:

• register_config_type(name, config_class) method
• _config_types attribute
• Config type registration and creation workflow

Implementation provides:

• register_config(name, config_instance) method
• configurations attribute
• Config instance storage workflow

Impact

• Tests in TestConfigurationManager class fail/timeout due to missing methods
• API inconsistency between test expectations and implementation

Files Affected

• tests/core/test_wrapper_framework.py (lines 301-340)
• src/orchestrator/core/wrapper_config.py (ConfigurationManager class)

Solution Options

1. Update ConfigurationManager to match test expectations
2. Update tests to match current implementation
3. Design new unified API that serves both needs

Priority

Medium - affects test coverage but doesn't block core functionality

[jeremymanning]

No longer relevant after Claude Skills refactor (issue #426)

[jeremymanning]

Re-verified: the API mismatch is unchanged.

Tests expect register_config_type(name, config_class) and a _config_types attribute; the implementation provides register_config(name, config_instance) and configurations. This is a live contributor-blocking failure, not a superseded one.

---

Reopened during a repository-wide issue audit. This issue was closed on 2025-10-18 with "No longer relevant after Claude Skills refactor (issue #426)", but that refactor never shipped a working replacement — its compilers are orphaned and unreachable from orchestrator run (see the audit comment on #426). The gap described here is in the canonical YAMLCompiler path, which that refactor never touched. Evidence above was re-verified against main today.