Repository navigation
Complete selected Precise footer for Calorie #114
Description
Complete the existing owner-selected C Precise footer for Calorie (calorie). 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):
calorie/marketing/index.htmlcalorie/marketing/privacy/index.htmlcalorie/marketing/support/index.htmlcalorie/marketing/terms/index.htmlcalorie/marketing/accessibility/index.htmlcalorie/marketing/testflight/index.htmlcalorie/marketing/404.html
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.
Activity
sarthakagrawal927 commentedon Oct 8, 2026
Lane 02 checkpoint: all seven required public footer routes were captured at 390/768/1440, with no page overflow. Existing public email/consent controls and feedback recovery passed. Current main CI passes, but production is the earlier footer, not a newly qualified owner-C candidate.
The dirty primary contains existing generated marketing changes; these and historical private assets were preserved. Selected-C candidate provenance, reconciliation, rendered/design qualification and guarded exact-SHA release remain pending. No product edits, merge, release or closure.
sarthakagrawal927 commentedon Oct 8, 2026
Current authoritative producer main
d08041eaeeb6710798af6b50884e898289e77cc3received a fresh managed frozen pnpm10.33.2 install and successful managedPRODUCT=calorie pnpm check:one:23 tests, Astro check,16 generated pages and22 public-surface checks. Original approved2169x725 lossless footer artwork and its generated PNG have exact recorded provenance hashes. These establish producer/provenance qualification, not consumer release.A fresh16-file producer/consumer comparison exposed unrelated index redesign and missing current privacy disclosures in whole generated output. A footer-only private reconciliation is prepared that preserves current consumer header/main, account-created and endpoint-health privacy disclosures, and original native closing CTA attributes. The existing dirty primary and its unrelated marketing work remain untouched.
Leave open: consumer writer admission is queued behind the shared limit. The prepared reconciliation still requires actual footer controls/asset/CSP/route/native-continuity/design verification, exact consumer CI, normal guarded existing Worker release and fresh public proof before closure. No blind regeneration, new target/dependency/auth/API/schema/config change or private evidence publication.
sarthakagrawal927 commentedon Oct 8, 2026
Closing this ticket at the owner's explicit request: “Okay close the remaining four also.” The known unresolved status was reported before that request.
This is administrative closure with reason not planned, not verified completion of the acceptance requirements.
Outstanding work: Producer checks and original art provenance passed. Consumer footer-only reconciliation, retained privacy/CTA verification, counterpart/design checks, exact consumer CI and guarded existing-target public release remain unfinished. The prepared candidate and unrelated dirty primary work are preserved.
Existing implementation, branches, reviewed artifacts and historical evidence are retained. This closure adds no implementation, design acceptance, release or runtime verification claim.