Most first issues stall on tooling. The post lives in one app, the list lives in another, and the paywall lives somewhere else. By the time the stack is wired, the issue is stale.
Start with one site, one list, and one published post. Airlancer is built so those three pieces already talk to each other. The first issue should prove that path, not a future architecture.
The last pass is operational. Confirm the slug, the feature image, the send audience, and the public URL. A calm launch is usually the result of boring checks done early.
