[Model behavior] Fixes applied that likely duplicate a known upcoming change
Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 2, 2026
The model added handler-level fixes ('fixes on top') to several merged pull requests without reading the tracking issue, which announced a follow-up series implementing the same mechanism generically and asked for it to be merged last. The result is likely duplicate/conflicting code the maintainer now has to untangle.
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.