[river0825]

Why

The landing page kept serving the old build even after v1 was released.

Root cause: a literal v1 git tag makes jsDelivr treat @v1 as an immutable pin (Cache-Control: immutable, cached ~1 year). Promoting a release by force-moving the v1 tag therefore silently froze the CDN on stale content — purging @v1 couldn't fix it because jsDelivr kept re-serving the immutable object.

What

• Switch every production loader and install snippet to the floating @latest tag (README.md, docs/index.html, docs/rc.html, CLAUDE.md). jsDelivr revalidates @latest (~12h) and floats it to the newest stable tag automatically — no purge, no waiting.
• Landing page version switcher now defaults to latest instead of v1.
• Keep the explicit @v1.1.0-rc.1 pins on the RC page (intended).
• Document the pitfall + new release process in CLAUDE.md: cut a new, higher version number each release; never force-move a version tag and never maintain a literal v1 tag.

Context

The literal v1 git tag has been deleted and v1.2.0 (→ b043ab5, includes the issue-4 modal fix) tagged, so @latest already serves the current build.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request transitions the project's CDN distribution from a moving @v1 tag to jsDelivr's floating @latest tag to avoid immutable caching issues. It updates documentation across CLAUDE.md and README.md, and adjusts the version selection logic in the demo pages. Feedback suggests mapping legacy ?ver=v1 query parameters to latest in docs/index.html to maintain backward compatibility for existing bookmarks.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Since the literal v1 git tag has been deleted from the repository, any existing bookmarks or links that still contain ?ver=v1 will fail to load the script from jsDelivr. To ensure backward compatibility and a smooth transition, we should explicitly map v1 to latest (the default) when parsing the query parameter.

Suggested change

	var DEFAULT = "latest";
	var ver = new URLSearchParams(location.search).get("ver") || DEFAULT;
	var DEFAULT = "latest";
	var ver = new URLSearchParams(location.search).get("ver") || DEFAULT;
	if (ver === "v1") ver = DEFAULT;