Resolve decorated class through the container in initDecorated()

[trm42]

What

CacheDecorator::initDecorated() now resolves the decorated class through Laravel's service container (resolve($class)) instead of new $class when no instance is passed to the constructor.

Why

The package is already Laravel-coupled (it uses the Cache, Config, and Log facades), and direct instantiation only worked for classes with a zero-argument constructor — it ignored the container entirely. Resolving through the container is a strictly-more-capable, low-risk upgrade:

• Decorated classes may now declare auto-wired constructor dependencies.
• decoratedClass() may return an interface bound in the container.
• Existing no-dependency stubs resolve identically, so the no-arg path is behaviorally unchanged.

Changes

• src/CacheDecorator.php — $decorated = new $class; → $decorated = resolve($class);. The LogicException null-class guard is unchanged (it fires before the container is touched). Updated the decoratedClass() PHPDoc.
• README.md / CLAUDE.md — documented container-based resolution per the README-sync convention.
• Tests — added StubCollaborator, StubServiceWithDependency (requires the collaborator in its constructor), and CachedStubServiceWithDependency, plus test_decorated_class_is_resolved_through_container_with_dependencies. The service has a required constructor argument, so the old new $class path would have thrown ArgumentCountError — the test only passes because resolution auto-wires the dependency.

Verification

composer test — 29 tests, 43 assertions, all green.

🤖 Generated with Claude Code