Complete selected Precise footer for Mashup

[sarthakagrawal927]

Complete the existing owner-selected C Precise footer for Mashup (mashup). Fleet rollout: sass-maker/saas-maker#180. This is remaining work, not an implementation, design-acceptance or production-release claim.

Existing candidate source, dirty primary changes and private footer receipts/art evidence must be preserved. Reconcile from fresh origin/main in a normal owned Fleet workspace; inspect current AGENTS/product purpose/dossier, actual routes and counterpart landing/app before writing. Do not blindly commit the historical release-matrix dirty paths or publish private catalog/evidence.

Current canonical required-source inspection pointers (verify before activation):

• mashup/web/src/pages/index.astro

Acceptance and next actions:

• Retain native product identity, truthful copy, theme/state/handlers and actual grouped navigation links on the left. Use the shared selected-C composition and footer-scoped Geist UI/Geist Mono fonts while preserving native product typography and signature identity.
• On the right, use the actual editable question and icon-only assistant handoffs with accessible names and URLs containing the edited question. Keep the real compact email field always open where newsletter/waitlist capture applies; consent remains explicit and unchecked, with existing validation, privacy, config failure and unsubscribe behavior. Honor existing capture opt-outs; add no collection, mock handler or duplicate native feedback service.
• Use product-specific original artwork with verified provenance and licensed font mirrors/metadata; unknown historical art stays private. Keep the personalized signature/art fade and fullwidth final one-line studio strip, correct current-project exclusion and keyboard scroll/focus. Preserve actual security policy; use same-origin approved mirrors when needed rather than changing CSP.
• Review exact footer-only allowlist and generated closing-region changes. Use native frozen managed install and smallest relevant tests first, then owning full checks/build and current exact-SHA CI. Preserve unrelated dirty work, original artifacts and private historical receipts.
• Qualify the actual HTTP/public surface at390/768/1440: route/CTA and landing-app continuity, hierarchy/type/art crop, readable controls, edited question links, email validation/unchecked consent, focus and feedback recovery, studio keyboard scroll, no page overflow and actual asset loading. Record concrete evidence and final design-workflow check; no self-awarded pass or local/CI-only release claim.
• Only after those gates pass, merge/release the exact clean current SHA using the existing owner target and guard. No new target, auth/API/schema migration, dependency/config change or private data publication is authorized by this task. Verify deployed SHA/current CI, anonymous applicable routes and exact art/font/runtime bytes; update #180 and close only after public proof.

[sarthakagrawal927]

Released the already-selected C Precise shared footer at main 2615b7cee725ae863979603790c6e16f6d47cd90, after exact CI 37328597282 passed. Production/main Pages deployment 001287d4-f257-4b06-8ffd-5d8e5ca12c4f serves the complete public proof bundle; the initial plain-build publication was superseded after detecting missing media.

Root actual Chrome DevTools reviews at390/768/1440 confirm one shared host/footer, loaded original2170×725 artwork and local Geist/Mono, no document overflow, native resource/local-use links and fullwidth final studio strip. Edited questions update all5 assistant URLs; native email validity/unchecked consent, feedback focus/Escape return and keyboard strip were exercised without submissions. The local offline editor counterpart remains excluded from public footer/public deployment.

Canonical media/caption MIME, bytes and all4 approved hashes match. Both real players advance with decoded frames and readyState4 at desktop/mobile; durations47.15/13.16seconds, no media errors, native captions disabled by default. The final maintained design-workflow completion check passes; rendered evidence, concrete craft tradeoffs, independent93/100 comprehension and explicit unknown numeric scan are retained privately.

Publisher guard PR21 separately enforces clean published-main source, fresh static bytes, approved complete media and exclusion of operator/private files, with seven passing focused regressions. This is a source reliability follow-up; the footer and playable live release are already qualified. Operator pilot #11 remains outside this bounded footer task.