This change starts from the accepted readability commit e84a62e17e2f4cbd985968d716361e3bbd6d0f87. The original remote handoff branch was fetched read-only and remains at 9cae31f7ac0c1ef41790436e0454757d79b7783d. Work is isolated on feat/blog-targeted-multilingual-copy.
All 21 guides use the approved targeted edits, not the rejected broad rewrite:
The Chinese records exactly match the frozen approved file (SHA-256 c56347030ed63df372a8621d345cce6549a57e1d6b87909531aaae925f3f1766). All 21 records passed independent factual/semantic review; the 18 non-Chinese records also received the additional idiom/journey review. This is not a claim of human native-speaker proofreading.
All fields except body and the permitted appended Denmark source are unchanged: titles, descriptions, slugs, dates, official booking destinations, related IDs and publication flags. All seven H2 sections and original link occurrences remain. No navigation, green service panel, SEO implementation, source-date claim, financial-policy page or business logic is modified. The existing production indexing=true setup remains intact, including its 84-URL sitemap scope.
The existing refund policy has not been synchronized with the new guide promise. That policy/business consistency issue still requires a separate authorized update. This copy commit does not change refund calculations or payment behavior.
check-blog-targeted-copy.mjs enforces the current preservation contract against e84a62e. The earlier readability checker now explicitly verifies its accepted e84a62e snapshot against 9cae31f7; it does not silently reject the later authorized Denmark source addition.
Passed: targeted contract; historical readability milestone; content/release inventory; nav/style; seven-language dictionaries; nonincremental TypeScript; 260 protected-business checks with zero differences; focused ESLint for changed scripts; diff whitespace checks. Build/HTTP receipts follow below.
Full npm run lint still exits 1 because the existing next/core-web-vitals configuration cannot be loaded. The build skips lint by existing configuration; focused lint is not a full-project lint pass.
Browser QA is not rerun: the earlier readiness attempt in this environment failed before page load because Chromium socket creation was not permitted. No new screenshot, rendered mobile, hydration or interactive-browser result is claimed. HTTP checks do not validate real login, appointment availability, orders, payments, refunds or email delivery.
Environment files are neither read nor changed, and no environment files are included in the new bundle objects. Local builds use an explicit indexing flag and an isolated dummy API URL; those test artifacts must not be deployed. There is no remote push, master merge, deployment or Search Console action.
Both explicit BLOG_INDEXING_ENABLED=false and true production builds passed with exit 0. Their matching scripts/check-blog-http.mjs runs also passed: 28 blog pages, 56 public app pages and 42 private localized pages, plus admin/error/query checks. Preview sitemap: zero URLs. Indexed sitemap: exactly 84 URLs. Canonicals, reciprocal alternates, source/schema output and private noindex headers remain correct.
Both bounded servers were stopped. The final local test build is indexing=true with the isolated dummy API; it is not a deployment artifact. The cumulative handoff bundle requires 9cae31f7 and includes the accepted readability commit plus this targeted correction commit, supporting users starting from either 9cae31f7 or e84a62e.