For Marketing

Is this something to market?

No — directly, this is internal engineering tooling (a GitHub comment command and a status issue for the team's own PR sandboxes). There's no customer-facing change, no new screen, no new product capability. Nothing here belongs in a changelog, release notes, or customer communication.

Where it's still useful to know about

If Marketing ever needs a live, disposable demo environment of an in-progress feature — e.g. to record a screen-capture of something not yet released, or to let a product manager preview a feature before it ships — the sandbox infrastructure this PR improves is the thing that produces that environment. Knowing it exists means:

• You can ask engineering for "a sandbox link for PR #___" instead of asking

for a special one-off deploy — it's the same mechanism used for every PR review, so it's cheap to request.

• Each sandbox comes with a seeded demo dataset (see the credentials in the

sandbox-info PR comment) — a believable clinic with appointments, invoices, and multiple staff roles already populated, useful for screenshots or recordings without manual data entry.

What NOT to say

Don't describe /sandbox or the registry issue as a "feature" in anything customer-facing — it's a developer-experience change to how the team reviews its own code, not a capability of the Dentolize product.