Update byteseats.com.storefront: add Cloudflare ownership TXT record

[nader-bytesai]

Description

Updates the previously-merged byteseats.com.storefront template (#1168) to add the Cloudflare hostname-ownership verification TXT record alongside the existing CNAME.

Bytes serves customer storefronts through Cloudflare for SaaS custom hostnames, which require two DNS records to go live: the routing CNAME (already in the template) and the _cf-custom-hostname ownership TXT (a per-hostname token that keeps ownership pre-validation on — the mitigation against dangling-CNAME subdomain takeover). With only the CNAME in the template, the one-click apply left customers to add the ownership TXT by hand; this change lets a single apply write both records.

Type of change

• 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?

• 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

• syncPubKeyDomain is set — public key is published at _dcpubkeyv1.byteseats.com
• warnPhishing is not set alongside syncPubKeyDomain
• syncRedirectDomain is set
• no TXT record contains SPF content — the only TXT is the Cloudflare ownership token at _cf-custom-hostname.<host>
• txtConflictMatchingMode is set on the TXT record that must be unique — set to All so a re-apply / hostname rotation replaces the ownership token rather than stacking a duplicate
• no variable is used as a bare full record value — the CNAME's pointsTo and the TXT's data are full values (%target% / %ownership%); the request is RSA-signed (Cloudflare requires signing), preventing tampering
• no bare variable is used as the full host label — CNAME host is @; TXT host is the literal prefix _cf-custom-hostname combined with the apply host parameter
• no variable is used in the host field to create a subdomain — the host parameter is used (hostRequired: true)
• %host% does not appear explicitly in any host attribute
• essential — N/A; both records are core service records that must not be removed without breaking the storefront

Online Editor test results

Subdomain test (apex test not required since hostRequired: true). Applying with domain=bytesai.dev, host=order, target=qa.web.byteseats.com, ownership=<cf-token> produces:

• CNAME order → qa.web.byteseats.com
• TXT _cf-custom-hostname.order → <cf-token>

Editor test link:
Test byteseats.com/storefront on bytesai.dev/order

🤖 Generated with Claude Code

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

byteseats.com.storefront.json

Level	Code	Note
info	DCTL1021	missing from iana definitions

[github-actions]

PR Description Check Passed

All required sections are filled in correctly.

Details

  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 10/10 checkboxes ticked
  OK  Online Editor test results: 1 link(s) found
  OK  Template coverage: all 1 template(s) covered
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete, Test links missing

PR description check PASSED