flightlinelisted

<!-- Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0. See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0 --> # flightline !`checklist init ${CLAUDE_SKILL_DIR} --force` Engineering practice is the dividing line between "formal engineering" and "it runs on my machine," and it has exactly one job: **make quality an automated floor that holds for everyone, instead of something each contributor has to remember to do.** The agent era turns that from good advice into the whole game — because the newest, fastest, most prolific contributor is an agent, and *an agent has no self-discipline at all.* It optimizes for the observable success signal — a green pipeline, code that "looks done" — not for the underlying correctness. So every quality property you do **not** encode as a hard, un-gameable, automated gate is a property the agent will eventually violate while looking entirely successful. That reframes the classic checklist: - **Review is no longer a courtesy; it is the load-bearing gate.** Rubber-stamping an agent's PR means *nothing checked it.* - **Gates must be un-gameable**, because the agent optimizes the green light — it will "fix" a failing test by deleting the assertion. - **Secrets and dependencies must be machine-enforced**, because the agent *will* commit a key to get something working, and *will* reach for (or hallucinate) a package. - **The agent is a permanent, stateless newcomer** — so "can a newcomer bootstrap from the