Skip to content

Qualify the selected Precise C public closing footer #64

Description

@sarthakagrawal927

The owner selected Precise C for every Fleet public closing footer. Integrate Kinetic's original public CTA, routes, legal/disclosure text and existing updates capture with the shared product-native closing frame. Preserve operating app UI and original public hrefs.

Track source, owning checks, actual responsive/control review, dependency readiness and public release separately. Shared rollout: sass-maker/saas-maker#180.

Activity

  1. sarthakagrawal927 commented on Oct 4, 2026

    @sarthakagrawal927
    MemberAuthor

    The owner selected Precise C for all public closing footers. Kinetic source candidate is on agent/precise-footer-20261004 (2ae79bf,7652220,90a7e6a); commits remain local, with no PR/merge or production release yet.

    Completed: original native public routes/forms and palette preserved; both host-only loaders explicitly light; compact/integrated native updates; stable ?v=precise-b0adaa67 module URLs. The existing public CSP permits own-origin fonts but excludes the SaaS font origin. The approved fix mirrors8 licensed font/provenance files under landing-astro/public/fonts/fleet-footer-precise-v1 and switches4 host attrs to /fonts/fleet-footer-precise-v1/. All3 WOFF2 files, README and provenance match approved source bytes. Only trailing whitespace changed in3 OFL texts; original wording and before/after hashes are retained. CSP and private inbox UI are unchanged.

    Fresh design preflight,9 source contracts,7 Astro static transforms and diff checks passed. The maintained landing overlay publishes the fonts path. Actual loaded fonts and owning full build are still unverified.

    Remaining release steps:

    • Run maintained lint, typecheck, full Vitest and pnpm build through Fleet Workspace; verify all8 mirrored files in both Astro output and final dist.
    • Review actual built home/FAQ/changelog and public reading continuation at390/768/1440, including loaded Geist/Mono, decoded art, editable5-provider handoff and visible unchecked required consent. Keep private Gmail actions out of the footer task.
    • Push via normal hooks, create scoped PR, obtain exact-head/main CI and existing deploy guard, then release the existing Worker only.
    • Verify anonymous routes/assets and actual effective CSP after release; no CSP change or form submission is authorized by this font-origin fix.

    The owner’s latest scope is to finish near-complete releases and keep this owning task for the remaining qualification. No dependency migration or final visual/production acceptance is claimed.

  2. sarthakagrawal927 commented on Oct 4, 2026

    @sarthakagrawal927
    MemberAuthor

    Kinetic's selected Precise C footer is now merged and deployed from exact source.

    • Reviewed PR source SHA: 90a7e6a15fa83d6f2bffb89a14e894416a1072f2 (PR Mount Precise public closing footer with hosted, versioned modules #65), squashed to main 5e8a042be2012a0b5e363409ce7e50528d796829.
    • Exact-main CI passed: run #37229576164.
    • Maintained Fleet deploy guard passed 6/6 against clean main and exact origin/main.
    • Existing production workflow run #37230315437 succeeded on headSha=5e8a042be2012a0b5e363409ce7e50528d796829; it built and ran wrangler deploy --tag "$GITHUB_SHA", reported version 37564361-fa90-45cf-969e-f7ab597cc1f2 on both mail.significanthobbies.com and mail.sassmaker.com, and passed the changelog smoke check.
    • Public /, /faq, and /changelog return 200 and their HTML bytes match the exact local static build. All eight same-origin mirrored font/provenance files match local build bytes exactly. The production CSP allows same-origin fonts and HTTPS images. The original art matches the SaaS Maker source file byte-for-byte (1,067,188 bytes; SHA-256 608d95ab7e52b1aa43650828a4f2032bdc5bef686a715ea573931595594aeaa9).
    • Candidate CUA review passed at home 390/768/1440, FAQ 390/768, and changelog 390/1440; evidence is .fleet-local/precise-footer-release/resume-render-20261005/. Existing signed-in /app shell continuity was checked using a 256×360 navigation-only crop with no mailbox content saved. Fresh OAuth and semantic search remain untested.

    A final CUA review of the deployed production routes has not been completed, so this issue remains open for that gate. Candidate review and exact public-byte parity do not replace a production rendered acceptance. Scanner score remains unknown; no headless score was fabricated.

  3. sarthakagrawal927 commented on Oct 5, 2026

    @sarthakagrawal927
    MemberAuthor

    Kinetic closing CTA spacing correction is merged in PR #66 (153b9f4e8e0443ddccc97ff7e0368e14a2468d3d), with merge/current-main SHA 722d2559c35b37cbe7b82f0a15d8974e0f5135ff. The change adds visible space after the explicit heading line break so the public title no longer renders “emailyou”.

    Exact PR-head CI run 37270391202 passed; exact-main CI run 37270574362 passed quality, mailbox verification, build and docs checks. The existing manual production workflow 37270674077 completed successfully against the merge SHA, including the build, Wrangler deployment and changelog smoke check.

    Cloudflare’s read-only deployment/version list shows Worker email-manager, deployment 407aaec0-754f-4668-80d3-f827485e06e6, version #185 (23a9f60f-467f-4421-a2fb-52625946d252) tagged with the merge SHA at 100% traffic. Anonymous GET / on mail.significanthobbies.com returned 200 HTML with <h2>Find the email<br> you can almost describe.</h2>; response SHA-256: 35f155870ed4642720ad79a93eb0eba9b53c02d34a47af7b7f2753fd9778cbf0.

    Issue #64 remains open pending root’s post-release native browser review and selected-C design-workflow check. Full timestamped source/provider evidence is retained privately in the project’s .fleet-local/precise-footer-release/native-live-review-20261005/provider-version-review.json.

  4. sarthakagrawal927 commented on Oct 5, 2026

    @sarthakagrawal927
    MemberAuthor

    Precise shared-footer rollout is released and verified. PR66 corrects the one observed closing-heading whitespace defect; exact main 722d2559c35b37cbe7b82f0a15d8974e0f5135ff passed full CI 37270574362 and existing manual publisher 37270674077. Worker version185 23a9f60f-467f-4421-a2fb-52625946d252 serves100%, tagged that main SHA.

    Root’s live Chrome390/768 review verifies the corrected heading, retained original artwork and full-width studio strip, editable AI control, open updates input and unchecked consent; earlier complete390/768/1440 home/FAQ/changelog and native-control evidence remains retained for unchanged components. Current selected-C receipt completion check passed. No form submissions or fresh Gmail-auth/mailbox acceptance is claimed; pinned headless advisory scanner remains unscored.

    Private evidence: .fleet-local/precise-footer-release/native-live-review-20261005/released-correction-review.md, released-heading-390.png, provider-version-review.json; existing paired continuity and full-footer captures preserved. No redesign or additional production dependency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions