Refine artifact detail and separate customer template libraries

[scheemunai]

Scope — exactly the user's two accepted updates

• Artifact detail: wider document + adjacent desktop sharing, stacking below 760px; native section anchors. Existing red charts, stats widgets, panel components, forms, shell and security unchanged.
• Customer template library: image/title/tags-only cards; native My templates / Built-in templates query navigation. Existing linked-title/stretched-card preview still works; descriptions remain in storage/API/preview. Built-in remains the old first/default group; successful promotion opens My templates; preview/close preserve selection.
• Separate public catalog renderer and all 20 canonical template/source/thumb options unchanged. No broad admin redesign.
• Targeted style-guide pattern documentation and existing test extensions only. No dependency/schema/client-script/security/provider/launch-flag changes.

Verification

• pnpm check: zero errors, same 41 baseline diagnostics (10 important-styles, 30 descending-specificity, 1 unused-variable warning), no new suppressions.
• Build passes; full unit/integration 1,137 passed / 12 skipped.
• Full local Chromium E2E 310 passed / 12 skipped; final style-guide-only layout correction rechecked separately. Final head CI will cover the full tree.
• Three new integration assertions fail against archived clean baseline and pass here.
• Fresh local before/after 1440/768/390/320 plus 12 real breakpoint-neighbor widths; source-backed fixtures only. Native password/remove/revoke/re-share/restore/diff/promotion/preview/delete workflow, role boundaries and long-content frame scrolling checked. No production fixtures or provider actions.
• Existing detail panel functions are byte-identical; preview width 315→683px at desktop, 310→406px at768. Overview/artifact-list/settings/public-catalog paired desktop/phone pixels unchanged. Random synthetic bot key suffix/order and sticky-header crop effects are disclosed, not falsely called exact pixel matches.

Rollout / launch

STOP for internal parent review. No merge/deploy yet. After reviewed UI deployment and live verification, the user authorizes the existing homepage switch AA_COMING_SOON=true → false with the existing scoped PM2 reload. Do not redesign homepage, change provider/billing/tax settings or bypass the guarded deployment/private consistent backup/customer-invariant checks. Code rollback is an audited scoped revert; homepage rollback is only the prior flag value and reload, never routine database restore.