Trigger sync-to-zesty view auto-create for 4 pending pages

[ardeay]

Per ardeay (2026-09-09 Discord): the stage-merge sync-to-zesty runs since Aug 30 all failed with 401 invalid or expired developer token. Token was rotated today. A fresh stage push scoped to just these 4 files will let sync-to-zesty POST-create the view records and capture their ZUIDs.

Why this approach

• Full-sync dispatch also failed today (400 "filename already exists" on AEM — that view record exists in Zesty already but isn't in zesty.config.json)
• A scoped stage merge only processes files in the DIFF_BASE...HEAD diff, so this PR avoids the AEM conflict entirely
• The 4 target files don't have Zesty view records yet, so POST /web/views should succeed cleanly for each

What sync-to-zesty will do on merge

1. Detect 4 unmapped files in scope (culture-cares, nonprofit-rfp, duda-vs, webflow-vs)
2. POST /web/views for each → capture ZUIDs
3. Commit ZUIDs back to zesty.config.json via the workflow's ZUID-mapping step
4. Save file contents to dev version of each new record

Ardeay then publishes the 4 in the Zesty editor → live URLs.

Diff

Trivial single-line HTML comment on line 1 of each file to place them in DIFF_BASE scope. HTML5-valid (comments before DOCTYPE are explicitly permitted by the spec, standards mode preserved). Can strip after view records are created if we want.

Sanity checks

• Stage CI run succeeds
• zesty.config.json gains 4 new mappings (auto-committed by the workflow)
• After ardeay's manual publish, all 4 URLs return 200

[github-actions]

💾 Stage sync preview

New files to create (4):

• webengine/views/culture-cares.html
• webengine/views/duda-vs-content-one.html
• webengine/views/nonprofit-website-rfp-template.html
• webengine/views/webflow-vs-content-one.html

Will add/update — differ from dev (0):
none

Unchanged, skipped: 0

_{192 mapped resources · zesty-sync}