Add Meteorack hosting Domain Connect templates

[niknot]

Description

Add two new Meteorack hosting templates for Google-hosted tenant domains:

• meteorack.app.hosting-apex-v1.json
• meteorack.app.hosting-subdomain-v1.json

These templates are used by Meteorack to connect apex/root domains and subdomains to tenant sites hosted on the Meteorack Google tenant edge.

Notes:

• syncPubKeyDomain is set and live at _dcpubkeyv1.meteorack.app
• syncRedirectDomain is set to app.meteorack.com
• no SPF/TXT records are created by these templates
• bare variable values are intentionally used in A, AAAA, and CNAME targets because the target values are runtime infrastructure values provided by Meteorack during the sync flow
• %VERIFY_HOST% is intentionally used in host only for the Google-managed verification record; it is not used to emulate the Domain Connect host parameter for the customer-facing domain label

Type of change

Please mark options that are relevant.

• New template
• Bug fix (non-breaking change which fixes an issue in the template)
• New feature (non-breaking change which adds functionality to the template)
• Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

Please mark the following checks done

• Template functionality checked using Online Editor
• Template file name follows the pattern <providerId>.<serviceId>.json
• resource URL provided with logoUrl is actually served by a webserver

Checklist of common problems

Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.

• syncPubKeyDomain is set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejected
• warnPhishing is not set alongside syncPubKeyDomain — the two must not appear together
• syncRedirectDomain is set whenever the template uses redirect_uri in the synchronous flow
• no TXT record contains SPF content ("v=spf1 ...") — use the SPFM record type instead
• txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix (e.g. DMARC)
• no variable is used as a bare full record value (e.g. @ TXT "%foo%") unless necessary — prefer @ TXT "service-foo=%foo%"; if bare, justify in the PR description
• no variable is used in the host field to create a subdomain — use the host parameter or multiInstance instead
• %host% does not appear explicitly in any host attribute
• essential is set to OnApply on records the end user may need to modify or remove without breaking the template (e.g. DMARC)

Online Editor test results

Editor test link(s):

• Test meteorack.app/hosting-apex-v1 example.com/@
• Test meteorack.app/hosting-subdomain-v1 example.com/www

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

PR Description Check Failed

The PR description is missing required elements. Please update it according to the PR template.

Details

  WARNING: could not decode token: Invalid base64-encoded string: number of data characters (785) cannot be 1 more than a multiple of 4
  OK  Type of change: 1/4 checkboxes ticked
  OK  Checklist of common problems: 9/9 checkboxes ticked
  OK  Online Editor test results: 1 link(s) found

Labels to add: PR description incomplete, Test links missing
Labels to remove: Checklist of common problems not complete

PR description check FAILED:
  FAIL  'How Has This Been Tested?': 1/3 checkboxes are not ticked
  FAIL  Template coverage: meteorack.app.hosting-apex-v1.json: missing a test WITH host
  FAIL  Template coverage: meteorack.app.hosting-subdomain-v1.json: no editor test link found (expected template id 'meteorack.app.hosting-subdomain-v1')

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

meteorack.app.hosting-apex-v1.json

Level	Code	Note

meteorack.app.hosting-subdomain-v1.json

Level	Code	Note