What shipped, and when

Overview, per-course and per-account spend, per-build costs, and a maintenance switch that holds builds through a deploy.

• The panel now opens on an overview that leads with anything wrong — failed builds, unread feedback, maintenance left on — and says so plainly when nothing is.
• Every course on the platform, with its owner, its versions and what it cost to build.
• Every build, with its duration, its model calls and its cost. An average over a month hides the one build that ran four repair loops; this does not.
• Maintenance mode holds new builds instead of refusing them. A build started during a deploy queues itself and starts on its own afterwards, so nobody has to remember to press Build again.

A new name, a new mark, and a library that uses the width of the page.

• The mark draws a course outline sealed inside a package, which is what SCORM is. The previous one was a play triangle in a box, and a box with a play triangle is a video file.
• The course library moved to three columns and shares a left edge with the header, so three courses fill a row instead of leaving one stranded beside an empty half-page.
• Course titles wrap to two lines. Truncated to one, a course and its duplicate rendered as two identical cards.

Completion, average score and time taken for courses shared by link, with no LMS involved.

• Results are recorded only from the standalone shared link. A package running inside your LMS reports to your LMS, and we never see it.
• Nothing identifies a learner. The id is random, made up by their browser, and no name, address or header is stored.

One course, several audiences — plus artwork on every card whether or not you uploaded any.

• A duplicate carries the brief, the options, the written content and the built package, so it opens ready to edit. Build history, chat and published versions stay with the original.
• A copy is always private, whatever the original was.

Suggested topics, suggested detail, and a quiet warning when the scope looks wrong for the module count.

• The help only ever adds. It cannot block a build, refuse a form, or overwrite something you typed.
• The scope check stays silent when it has nothing to say. A confirmation step that always appears is one people learn to click through.

Real accounts, replacing the shared developer password.