Files
dealplustech-astroreal/docs/HANDOFF.md
2026-08-30 11:06:03 +07:00

2.4 KiB
Raw Blame History

title, updated
title updated
Deal Plus Tech Engineering Handoff 2026-08-30

Engineering Handoff

Current State

  • Repository: /Users/kunthawat/Gitea/dealplustech-astroreal
  • Branch: main
  • HEAD: pending verified commit at the time this handoff was written
  • Remote target: origin/main
  • Working tree: staged for the verified commit; no credentials or private logs included

Completed

  • CcooL product page: /ฉนวนหุ้มท่อ-ccool/
  • CcooL images and pricing PDF added under public/
  • Navigation, product listing, breadcrumb, metadata, FAQ, Product JSON-LD, and CTA tracking updated
  • Robots/sitemap references and stale internal links corrected
  • Duplicate legal-page H1 output removed
  • Unsupported market-superlative claim wording replaced
  • Duplicate CcooL anchor ID removed; new-tab PDF link hardened with rel="noopener"

Verification

  • npm run buildpass, 44 pages
  • npx tsc --noEmitpass
  • git diff --cached --checkpass
  • Independent reviewer → pass, no security concerns or logic errors
  • Static output → 44 HTML pages, JSON-LD parses, Umami attributes are well-formed, images have alt; baseline-only duplicate SVG ID and blank-target links remain
  • Assets → five 1024×768 images; five-page A4 PDF; no PDF JavaScript/encryption

Known Limitations / Blockers

  • npm test cannot run because the project has no test script.
  • astro check reports 55 pre-existing errors in both baseline and final trees; no regression was introduced.
  • Production soft-404 behavior, Cloudflare crawler rules, live Search Console, and live external HTTP status were not changed or verified in this local push gate.
  • Domain-dependent SEO/deploy work is blocked until the real production domain is explicitly confirmed. Never guess it from repository configuration.
  • CcooL claims still need accessible first-party evidence; image CLS and complete ProductGroup/AggregateOffer modeling remain deferred.

Resume Procedure

  1. Verify git rev-parse HEAD and git ls-remote origin refs/heads/main agree after push.
  2. Update this file and the dated engineering log with the exact pushed SHA.
  3. Before deployment or further SEO changes, confirm the production domain explicitly.
  4. Fix server-level 404 routing and verify an unknown URL returns HTTP 404.
  5. Recheck Cloudflare robots/AI crawler settings and publish claim evidence.

Evidence Index