PHP Deployment Pipeline

Closest to 'silent in production until users hit it' (d9). The detection_hints note 'automated: no' and the code_pattern describes manual processes — no automated tool from the list (github-actions, gitlab-ci, deployer, envoyer, capistrano) will flag the absence of a pipeline. The absence of a proper pipeline only becomes visible when a bad deploy causes downtime, stale OPcache serves old code, or dropped requests occur during FPM restarts — all of which are silent until users experience errors.

Closest to 'cross-cutting refactor across the codebase' (e7). The quick_fix outlines a multi-stage pipeline: composer install → phpcs → phpstan → test → build docker image → push to registry → deploy to staging → smoke test → deploy to production. Moving from FTP/manual deploys to a fully automated atomic pipeline with zero-downtime deploys, OPcache clearing, and smoke tests requires coordinating CI/CD configuration files, server setup, Docker infrastructure, and potentially DNS/load balancer changes — spanning the entire delivery infrastructure.

Closest to 'strong gravitational pull' (b7). The deployment strategy shapes every aspect of the development workflow — how branches are structured, how environments are managed, how hotfixes are handled, and how the team responds to incidents. A poor or absent pipeline creates ongoing drag on every release cycle, affects both web and cli contexts per applies_to, and the lack of rollback mechanisms means every future deploy carries elevated risk until the pipeline is properly established.

Closest to 'serious trap — contradicts how a similar concept works elsewhere' (t7). The misconception field directly states the canonical wrong belief: 'FTP uploading files to a server is a valid PHP deployment strategy.' This is a well-established mental model carried over from earlier PHP development practices where FTP was the norm. Developers familiar with this approach don't realize it leaves the server in a mixed state mid-deploy, skips tests, and prevents atomic rollback — behaviors that contradict how modern deployment tools from the detection_hints list operate.