MySQL messaging: add JavaScript Stored Routines (Tech Preview) awareness to drive trial and feedback

[thefactremains]

Objective

Raise awareness of Percona Server for MySQL's JavaScript stored routines feature to drive trial, adoption, and user feedback. The business purpose is to build the demand signal that supports graduating the feature from Tech Preview to GA. The messaging encourages teams to try it and share feedback while staying accurate that it is still a Tech Preview.

Change

Updates products/mysql/messaging.md with two small, tightly scoped additions:

• One bullet under Adaptability for Emerging Workloads introducing JavaScript stored routines: write stored procedures and functions in JavaScript using the LANGUAGE JS clause in CREATE FUNCTION and CREATE PROCEDURE, suited to algorithmic logic and JSON handling, with more readable and easier-to-debug code than SQL stored-program (PSM) syntax. The bullet invites teams to try the Tech Preview and share feedback through the Percona Forums. Cites the js-lang overview docs and the announcement blog inline.
• One matching sales-enablement conversation starter (phrased as a question, Tech Preview noted).

Accuracy (Tech Preview, no GA claim)

• Stated explicitly as a Tech Preview in Percona Server for MySQL 8.4.7-7. Verified against the js-lang docs (which carry the Tech Preview banner) and the 8.4.7-7 release notes (component_js_lang).
• Does not imply GA, production-readiness, or a GA date. The copy frames feedback and demand as informing the path toward general availability, with no promise or timeline.
• Syntax shown is LANGUAGE JS in CREATE FUNCTION / CREATE PROCEDURE, matching the docs.
• States factually that Oracle offers JavaScript stored programs only in MySQL Enterprise Edition, with no disparagement.

New-file decision gate (reference/content-governance.md)

1. Which existing files were reviewed first? products/mysql/messaging.md (the canonical MySQL product file).
2. What exact gap was found? No awareness bullet for JavaScript stored routines, the feature we want teams to trial and give feedback on.
3. Why can this not be an update to existing canonical files? It is an update to an existing canonical file. No new file is created.
4. Who owns long-term maintenance? MySQL Product (domain owner per GOVERNANCE.md and CODEOWNERS).
5. Decomposition and propagation plan? Keep this awareness copy in the canonical MySQL product file; any overlay or campaign assets should reference it rather than duplicate it.

Sequencing with open PRs on the same file

This touches the same file (products/mysql/messaging.md) as open PR #180 and as the already-merged PR #172. It should be rebased and sequenced accordingly to avoid conflicts; the additions are localized (one bullet plus one conversation starter) so rebase should be straightforward.

Reviews and checks

• Expect the blocking licensing or open-source-claims impact check to run, given the open source MySQL versus MySQL Enterprise Edition framing.
• Please loop in the required reviewers for terminology and naming (reference/canonical-naming.md, reference/banned-terms.md), plus framework files and offerings owners, per CODEOWNERS.

Verification

• npx -y markdownlint-cli2@0.22.1 "products/mysql/messaging.md" passes with 0 errors.
• Grep confirmed: no em dashes, no hyphenated "open-source", no standalone "Pro" or Pro-build/Pro-tier wording, no "flag" as a verb, "Tech Preview" present, and no GA claim or date for the feature.
• Vale CLI is not installed in this environment, so the Vale pass was not run locally; CI will run it.

[github-actions]

Messaging Impact Check

• Changed files: 1

licensing-or-open-source-claims (BLOCKING)

License and open source positioning changes are cross-cutting.

Required review files:

• reference/canonical-naming.md
• reference/banned-terms.md
• framework/core-positioning.md
• framework/why-percona.md
• offerings/expert-support.md
• offerings/expertops.md
• offerings/expert-consulting.md

Suggested additional scan:

• use-cases-value-pillars/*.md
• products/**/messaging.md

product-messaging-module-touch (WARN)

Product messaging modules often need checks against company framing and shared pillars or offerings.

Required review files:

• framework/core-positioning.md
• framework/why-percona.md

Suggested additional scan:

• use-cases-value-pillars/*.md
• offerings/*.md

Manual waiver commands (maintainers):

• /impact-ok all (optional same-line note after all is ignored)
• /impact-all (same as /impact-ok all)
• /impact-ok <exact missing path>
• /impact-reset all
• /impact-reset <exact missing path>

Waiver state is stored in <!-- messaging-impact-waiver-data:v1 -->.

---

_{Triggered by pull_request. Workflow impact-check.yml. Docs: AUTOMATION.md, automation/README.md.}

[github-actions]

Messaging Smart Suggestions

File	Why impacted	Claim	Confidence
reference/canonical-naming.md	License and open source positioning changes are cross-cutting.	reliability	0.95
reference/banned-terms.md	License and open source positioning changes are cross-cutting.	reliability	0.95
framework/core-positioning.md	License and open source positioning changes are cross-cutting.	reliability	0.95
framework/why-percona.md	License and open source positioning changes are cross-cutting.	reliability	0.95
offerings/expert-support.md	License and open source positioning changes are cross-cutting.	reliability	0.95
offerings/expertops.md	License and open source positioning changes are cross-cutting.	reliability	0.95
offerings/expert-consulting.md	License and open source positioning changes are cross-cutting.	reliability	0.95
framework/core-positioning.md	Product messaging modules often need checks against company framing and shared pillars or offerings.	reliability	0.95
framework/why-percona.md	Product messaging modules often need checks against company framing and shared pillars or offerings.	reliability	0.95

Only auto-apply suggestions at high confidence with reviewer approval.

---

_{Triggered by pull_request. Workflow smart-suggestions.yml. Docs: AUTOMATION.md, automation/README.md.}

[github-actions]

New File Governance Check

No added markdown files detected.

Doc Coverage Check

No new markdown docs detected.

Duplicate Detector

• Changed markdown docs: 1

No significant overlap detected.

Manual waiver commands (maintainers)

• /governance-ok all or /governance-all
• /governance-ok new-file, /governance-ok doc-coverage, /governance-ok duplicate
• /governance-reset all or /governance-reset with the same token

Waiver JSON is stored in a hidden PR comment (messaging-governance-waiver-data:v1), same pattern as Impact Check.

---

_{Triggered by pull_request. Workflow content-governance-checks.yml. Docs: AUTOMATION.md, automation/README.md.}