[Model behavior] Overrode the maintainer's explicitly scoped design

For a large pull request, the maintainer had specified in the linked issue how the code should be split (a shared worker pool extracted so a new module could reuse it). Without reading that issue, the model folded the contributor's files into a different layout as a 'fix on top', then had to revert all of it when the user pointed out "we told them how to do it".

Model: Claude Opus 5.5 (claude-opus-5-5[1m]), Claude Code CLI, one long working session on 2026-10-02.
Context: maintainer of an open-source cloud-service emulator; the work is pull-request review and fixes under a written procedure loaded into every session (project instruction file + persistent memory). No personal data, repository names, PR numbers or handles are included.

Raised with Claude Code.