fix(cli): sync cli/assets with src/ui-ux-pro-max source of truth

[alfredo-petri]

Problem

cli/assets/ was divergent from src/ui-ux-pro-max/ (the documented source of truth per CLAUDE.md). Users installing via npm received outdated data:

• scripts/core.py: only 3 stacks instead of 16
• scripts/search.py: stale domain/stack documentation
• 12 stack CSVs out of date
• 18 platform JSON templates with wrong stack counts/descriptions
• Several data CSVs divergent (app-interface, colors, icons, landing, products)

Root cause: The sync step (cp -r src/ui-ux-pro-max/...) is documented in CLAUDE.md but was never automated, so it drifts with every commit to src/.

Solution

• Add cli/scripts/sync-assets.js — a zero-dependency Node.js script that copies src/ui-ux-pro-max/{data,scripts,templates} → cli/assets/
• Add sync-assets npm script for manual runs
• Wire prepack and prepublishOnly to run sync automatically before every npm pack / npm publish
• Run sync to fix current 33-file divergence

Verification

node cli/scripts/sync-assets.js
diff -rq src/ui-ux-pro-max/data cli/assets/data      # empty
diff -rq src/ui-ux-pro-max/scripts cli/assets/scripts  # empty
diff -rq src/ui-ux-pro-max/templates cli/assets/templates # empty

🤖 Generated with Claude Code

[mrgoonie]

Summary: I’m deferring this PR from the cron-safe maintainer lane because it is a broad asset-sync packaging change and overlaps several active packaging PRs.

Decision: deferred / needs reconciliation

Evidence:

• This PR changes 37 files with +770/-719 across cli/assets plus a new sync script.
• It overlaps materially with the current CLI/package asset queue: fix(cli): re-sync bundled cli/assets/ with src (restores 15 stacks, repairs landing.csv) #330, fix: ship skill assets as real copies for Windows compatibility #336, Fix stack discovery in packaged skill assets #340, fix CLI asset sync #355, and Replace symlinks with real files and add conversion script #368.
• The repo already has review findings on fix CLI asset sync #355 that the asset sync guard can fail on raw-byte line-ending drift, so the sync strategy needs to define whether hashes compare raw files or normalized content.

Next step: please reconcile this PR with the other asset-sync PRs and make the acceptance path explicit: one chosen source-of-truth sync script, expected line-ending behavior, exact validation commands, and whether this supersedes #330/#336/#340/#355/#368. After that, a focused maintainer review can compare one packaging approach instead of reviewing parallel implementations.

[ia-abatista]

Recommend closing, @mrgoonie. A manual cli/assets re-sync, superseded by merged #355 which makes the src to cli/assets sync deterministic and enforced.