Automate footer update dates

[mtap-research]

What changed

• replace the fixed Updated July 2026 text in all 13 public footers with a semantic time marker
• add a dependency-free Netlify build step that stamps the deployed Git commit date in Asia/Seoul
• validate marker count and visible/ISO date consistency in the static-site checks
• add KST midnight-boundary and marker-failure regression tests

Why

The footer date was manually duplicated across every public page, so it became stale after later site updates. Build-time stamping keeps the displayed date tied to the deployed source revision rather than the visitor's current date.

Impact

This changes footer metadata only. The existing abstract submission, revision, Google Sheets sync, exchange-rate automation, and Netlify Functions are unchanged. The separate travel-information verification date remains untouched.

Validation

• node --check scripts/update_footer_date.mjs
• node scripts/test_footer_date.mjs
• node scripts/update_footer_date.mjs
• python scripts/check_site.py
• node --check js/exchange-rate.js
• node scripts/test_exchange_rate.mjs
• node scripts/test_sheets_sync.mjs
• git diff --check

[netlify]

✅ Deploy Preview for pbast10-pacific-basin-conference-on-adso-cd-cb27cc3e73 ready!

Name	Link
🔨 Latest commit	8e152f1
🔍 Latest deploy log	https://app.netlify.com/projects/pbast10-pacific-basin-conference-on-adso-cd-cb27cc3e73/deploys/6a762659fe299000087b8c2e
😎 Deploy Preview	https://deploy-preview-48--pbast10-pacific-basin-conference-on-adso-cd-cb27cc3e73.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Warning

Review limit reached

@mtap-research, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d0948a1d-c7f7-4493-8967-3246246b3c59

📥 Commits

Reviewing files that changed from the base of the PR and between 6d7bb4b and 8e152f1.

📒 Files selected for processing (19)

• .github/workflows/site-checks.yml
• 404.html
• README.md
• abstract-submission.html
• getting-to-yonsei.html
• index.html
• netlify.toml
• program.html
• registration.html
• revise-abstract.html
• scripts/check_site.py
• scripts/test_footer_date.mjs
• scripts/update_footer_date.mjs
• speakers.html
• special-issue.html
• sponsorship.html
• thank-you.html
• venue.html
• visa.html

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}