For Marketing

Straight answer: there's nothing to market externally

This PR changes a CI workflow file. It ships no clinic-facing feature, no UI, no API. A dentist, a receptionist, or a patient using Dentolize will never encounter it, directly or indirectly. If asked "what's new this release," this item doesn't belong in a customer-facing changelog.

Where it is worth a line: the internal engineering channel

If your organization keeps an internal engineering update (a Slack channel, a weekly eng newsletter), this is a reasonable one-liner for it:

PR sandboxes now inherit team-wide defaults (WhatsApp/queue/cron toggles, shared test secrets) from a shared GitHub Environment, instead of every PR having to configure everything from scratch in its own description.

Keep the framing honest and narrow:

• Do say it reduces repetitive PR-description boilerplate for engineers

who open sandbox-backed PRs regularly.

• Do say shared test secrets no longer need to be pasted into a PR

description as a secret:<NAME> reference for common cases — the team default handles it.

• Don't say it "adds new security" or "encrypts secrets" — the

secret:<NAME> resolution and the github_token guardrail already existed before this PR; see Secrets and safety guardrails. This PR extends where defaults can come from, not what protects them.

• Don't call the new sandbox deployment marker a gate or an approval

step — it explicitly isn't one (see The sandbox GitHub Environment).