authorize-releaselisted

# /foundry:authorize-release A **display + routing** surface over a release's atoms — not a bulk-authorization loop. An adopter's measured history (462 atoms authorized, 24 built — 438 authorized-never-built from bulk pre-authorization of a backlog) is why the bulk-sign loop that used to live in this skill's prose is **retired**: authorization is now **just-in-time**, one atom at a time, at the moment that atom is next. ## When to trigger - "authorize release `<slug>`", "/foundry:authorize-release `<slug>`" — after the release is DRAFT-shaped (atoms enumerated) and BEFORE implementation dispatch (steel-man-1 ordering). ## Procedure 1. **Resolve** the release → its ordered atom list. Across the list, resolve each atom's routed lane (charter lane by default; factory lane for the security set — see `skills/intake/SKILL.md` "Lane routing") and readiness (`depends_on` satisfied? spec or charter committed? contract drafted, for a factory-lane atom?). 2. **Display the dashboard.** Show the release's atoms with: name, lane (charter/factory), readiness, and current state. This is a read-only status view — it authorizes nothing by itself. 3. **Identify the next atom** — the first atom (in dependency order) whose `depends_on` are all satisfied and that is not yet authorized/built. There is exactly one "next" atom at a time; the rest of the release stays displayed but untouched. 4. **Route the next atom just-in-time.** - **Charter lane** — no `/foundry:au