v2.1.2 — Projects title fix

The projects page no longer adds the site brand before the shared SEO layer appends it. HTML, Open Graph and Twitter titles now have one brand suffix, including custom brands. Page headings/content, article titles and shared SEO rules are unchanged.

Validation: real Astro builds fail before the fix and pass after it for default and custom brands (including /blog/); normal page/article titles and page content are checked. The regression runs in the existing site CI suite. Local site tests: 31 passing; Astro check: 0 errors, 0 warnings, 4 existing hints; build/verify: 23 pages, 0 failures, 28 nonblocking editorial warnings. No dependency or Worker changes.

Downstream blogs must sync and deploy this template release separately.

Validated commit: 85e4444eb949524f94d01b6be683c173e3a2c844.

• CI: site and Worker checks passed
• GitHub Pages: build and deployment passed
• Live demo projects page: HTML, Open Graph and Twitter titles each verified as Projects｜Refined-X.

Refined-X v2.1.1

Refined-X 2.1.1 fixes known dependency vulnerabilities in both the site and optional Worker, and protects asset inputs during cleanup and native encoder upgrades.

Security and compatibility

• Site: Astro 7.3.3, Sharp 0.35.5 and patched compatible transitive dependencies. Pagefind 1.5.2 and Starlight 0.42.0 remain unchanged.
• Worker: MCP client/server 2.3.0 and Wrangler 4.153.0, with patched Sharp 0.35.5, Undici 7.30.1 and Zod. Existing Worker APIs and compatibility date remain unchanged.
• Both complete npm audits report zero known vulnerabilities, including development dependencies. CI now audits both packages at all severities.
• The fresh baseline was 52 GitHub alerts (33 site, 19 Worker), versus the earlier push summary's 22. Each baseline alert was mapped to safe resolved versions; no alerts were dismissed or suppressed.

Asset safety

• Reject overlapping asset source/output roots and dangerous directory/file aliases before cleanup. Preserve declared Markdown and history manifest/blob inputs, while allowing content roots that contain the public directory.
• Image cache v3 includes platform and Sharp/native-library versions. Current cold, upgraded-cache and warm outputs match; original and content-addressed public URLs remain supported.

Validation

• 134 site tests and 175 Worker tests passed, including 100 native Pagefind generations, actual build fault injection, request-isolation/authentication checks, and modern plus legacy MCP protocol calls under local workerd.
• Root and /blog/ builds and output verification passed; an independent clean installation also passed.
• Chromium verified Pagefind result fragments, static Ask search and article navigation, mobile theme rendering, RSS and self-hosted fonts.
• Typechecks and Worker dry-run packaging passed. Four pre-existing Astro hints and 28 demo editorial metadata warnings remain; they are not dependency vulnerabilities.

Install the site and Worker independently with npm ci and rerun npm audit. Instances must regenerate Worker types and run the protocol tests before deployment. This release does not deploy an existing Worker or downstream blog. Windows, real-model calls, fresh external product-client acceptance and downstream CDN behavior are outside this acceptance.

See CHANGELOG and security upgrade notes for exact versions, primary advisory sources and upgrade boundaries.

v2.1.0 — Verified search and publishing assets

Refined-X 2.1.0 improves reusable publishing assets and rejects incomplete search bundles before deployment.

Changes

• Responsive, content-addressed WebP variants with EXIF-aware dimensions, explicit original/history retention, self-hosted Spectral fonts, and active-theme hero loading.
• RSS discovery and subscription entry, optional SEO titles, authored feed/page dates, and internal-link/image/metadata audits with deployment-base support.
• Fix intermittent zero-byte Pagefind entry files after native write/close. Use Pagefind 1.5.2 memory export, awaited Node writes, complete SHA-256 readback, and build plus standalone verification gates. No retries, sleeps, or patched dependencies.

Validation

• 120 local site tests passed, including 100 real multilingual Pagefind generations and actual Astro fault injection for empty, malformed and missing index artifacts.
• Astro check: zero errors, zero warnings, four existing hints.
• Isolated default demo with its own npm ci passed build and verify; root and /blog/ first/repeated builds passed with identical repeated search manifests.
• Chromium loaded real Pagefind results and fragments, exercised static Ask search and article navigation, and checked theme loading, RSS and fonts.
• CI and demo deployment both passed for commit a9e7246.

Upgrade

Run npm ci, the site/search suites, build, and verify. Deploy the complete pagefind directory including refined-x-manifest.json. Keep the search artifact gate last when adding Astro integrations. The stricter audit may expose existing broken links or assets. Pagefind memory export temporarily holds the full search bundle; large corpora need memory measurement.

Ask still uses its own JSON corpus. Personal content, analytics, hosting policies and downstream instance updates remain instance-owned. Windows, real-model calls and downstream CDN behavior were not part of this acceptance. GitHub's push receipt reported 22 repository dependency alerts (11 high, 10 moderate, 1 low); dependency-security remediation is outside this release.

See CHANGELOG and search integrity notes.

v2.0.0

Refined-X 2.0.0 is the dual-era MCP / capability-model release.

Breaking

• Removes legacy draft discovery files /.well-known/mcp.json, /.well-known/mcp/catalog.json, and /.well-known/mcp/server-card.json, plus the mcp site-config keys that only served those shapes.
• Prefer ask.mcpUrl, /openapi.json, and /.well-known/about.json. Last tagged release that still emitted those paths: 1.1.0.

Highlights

• Dual-era Worker POST /mcp (modern 2026-07-28 + legacy) on one ask tool, with offline test:mcp-protocol in CI.
• Build-time public-capabilities / ask.protocolProfile (default undeclared; set dual-era only after instance acceptance).
• Optional AWP 0.2 discovery (discovery.awp, default off).
• Subpath-safe navigation and SEO canonical/og:url (no doubled base).
• Hardened product-client acceptance gates (protocol path, summarize mode, CLI exit/signal, no truncated-SSE keyword success).

Notes

• Extended client matrix rows remain not_run unless separately accepted.
• Upgrade Live Ask Worker with the site when Ask/MCP is enabled.
• Details: CHANGELOG.md.

v1.1.0

Refined-X v1.1.0 adds optional, configuration-driven giscus comments for article pages. Discussions use stable article IDs, lazy loading, locale-aware copy, and synchronized light/dark themes. Partial configuration now fails at build time, and CI verifies generated comment surfaces.

v1.0.0

Refined-X 1.0.0

First stable release of Refined-X as an agent-ready personal publishing starter.

Highlights

• Editorial static site from Markdown/YAML with articles, series, projects, answers, and profile surfaces
• Machine-readable outputs: Markdown mirrors, llms.txt, JSON APIs, OpenAPI, well-known discovery
• Optional Live Ask Worker (NLWeb /ask, MCP ask, health)
• Content independence via contentRoot / instance config overlays
• CI quality gates (check, tests, build, verify, worker test/typecheck)
• Trust assets: Changelog, Contributing, Security, Issue/PR templates, public roadmap
• Static deploy guides (GitHub Pages workflow template, Cloudflare Pages) and Live Ask troubleshooting

Known limitations

• MCP catalog under /.well-known/mcp/ remains draft
• Live Ask is optional and not required for the static site
• Live Ask does not provide long-term memory, arbitrary actions, or impersonation

See CHANGELOG.md for the full notes.