You have Atelier 0.15.0. Version 0.16.0 exists somewhere out there. This page shows, step by step, how it would travel from the author's computer to yours — and what your terminal has to do with it.
Atelier never downloads anything on its own. New versions sit on a shelf, far away, doing nothing — until you ask for them.
The terminal is simply how you ask. Typing a command is like phoning a warehouse and saying “anything new for me? If yes, deliver it.” No phone call → no delivery → nothing on your computer changes. That's why you're still on 0.15.0 even though 0.16.0 came out today: nobody phoned.
Atelier on your computer is made of two kinds of things, and they arrive by completely separate routes. This is the part that's confusing — so let's split it clearly:
The main server program itself — the thing that runs everything. This is what went from 0.15.0 → 0.16.0.
Arrives via: the npm warehouse — Route A below
Flights, Finance, Meetings… the individual apps that run inside the engine.
Arrive via: collections — Route B below
npm is a giant public warehouse on the internet where programmers put software packages for others to download. Atelier's author put the engine there. Every version ever published stays on the shelf: 0.14.0, 0.15.0, … 0.16.0.
The “phone call” looks like this (this page is only showing it — it has not been run):
Apps don't come from the npm warehouse. Since version 0.15, they travel as collections. A collection is like a sealed box of apps with a diary attached:
An app version only goes into the box if it actually works — a broken version physically can't be packed. (Atelier calls one packed version a “cut”.)
The box carries the full history of every version ever packed — so your computer always knows exactly which version it has and what's newer.
The author puts the box somewhere reachable — usually GitHub (a public shelf on the internet). It just sits there until someone asks.
The two phone calls of Route B (again — shown, not run):
That _collections folder that appeared in your Atelier folder on July 7? That's your mailbox — the local copy of the “flights” box. That's exactly how your Flights app arrived.
So why hasn't 0.16.0 arrived? Because updates are deliveries you order, not letters that get pushed through your door. Until someone opens the terminal in the Atelier folder and makes the Route-A phone call, 0.16.0 stays on the warehouse shelf and your computer keeps running 0.15.0. Exactly as designed — nothing is wrong.
One command per route: updating the engine
(npm update @pa1nd/atelier) does not update your apps, and updating apps
(npx atelier update) does not touch the engine. Two shelves, two couriers.