chore(release): v0.1.1228

[kwakayama]

Cuts v0.1.1228, the release that unblocks veryfront build.

Merging this publishes: version-check (cicd.yml:469) compares deno.json against the previous commit, and a changed stable version gates the release job.

Why this release matters

veryfront build has been broken for every project since 0.1.1206 — 22 releases. An external report surfaced it on 0.1.1227 (veryfront-issue-inbox#456).

There is no earlier version to pin to. 0.1.1205 fails the same templates with the CSSProcessor error that #3417 was fixing. A release is the only fix path.

What ships

PR	Fix
#3538	Prime host contracts in the build extension path
#3541	Resolve server-side esm.sh modules with a server target
#3542	Keep optional Deno imports optional
#3540	Isolate cwd-mutating unit tests

Verification on merged main (48cd2d5c7)

All 7 scaffold templates, each veryfront init + veryfront build from scratch:

Template	Result	Pages
minimal	✓ 4.87s	2
ai-agent (default)	✓ 7.04s	1
docs-agent	✓ 6.83s	2
agentic-workflow	✓ 2.50s	1
multi-agent-system	✓ 3.26s	1
coding-agent	✓ 4.24s	1
saas-starter	✓ 4.72s	3

Before these fixes, 5 of the 7 failed. Page counts are included because veryfront build can exit 0 with zero pages, so "built" alone is not evidence.

Hydration checked in a real browser on the docs-agent build served via veryfront serve: 428 requests all 200, zero console messages, React fibers attached. That matters because #3541 makes SSR evaluate esm.sh's node build while the browser still gets es2022, and a parity break there would be invisible to CI.

Diff: three files, not two

The version is also embedded in src/html/hydration-script-builder/hydration-runtime.generated.ts, so a bump must be followed by deno task generate.

My first attempt (#3545) bumped only deno.json and src/utils/version-constant.ts and failed ci (typecheck) — not on a type error, but on the manifests check:

[prebundle-hydration-runtime] hydration-runtime.generated.ts is stale.
  The committed bundle does not match src/html/hydration-script-builder/runtime/.

src/utils/version.test.ts:25 keeps the first two in sync; nothing pins the generated bundle, so the manifests check is the only thing that catches it.

Verified locally: deno task typecheck exit 0, version.test.ts 1 passed, deno fmt --check clean.

Rebased onto 80fb3a022 (#3543). The earlier attempt was cut from 48cd2d5c7, where tests (bun) was already failing; #3543 fixed it.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 31 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db982537-9faa-4adc-99e3-12f5186fedf9

📥 Commits

Reviewing files that changed from the base of the PR and between 80fb3a0 and 0b29157.

⛔ Files ignored due to path filters (1)

• src/html/hydration-script-builder/hydration-runtime.generated.ts is excluded by !**/*.generated.*

📒 Files selected for processing (2)

• deno.json
• src/utils/version-constant.ts

---

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