chore(release): bump version to 0.1.1189

[kwakayama]

Summary

• bump the framework and package version to 0.1.1189
• update the shared version constant
• regenerate the hydration runtime with the new version
• reconcile the release branch with current main

Version 0.1.1188 cannot be reused because @veryfront/ext-dev-ui-react was bootstrapped at that version after the partial release failure. The next unused patch is 0.1.1189, following the maintainer-confirmed patch release policy.

Release readiness

Completed:

• The authoritative Model Call Context canary passed.
• The durable child-run writer-token fix landed in fix(agent): scope durable child run event writers #3282 and is present on this branch through current main.
• @veryfront/ext-dev-ui-react@0.1.1188 was bootstrapped as a public npm package.
• The package trusted publisher is configured for GitHub Actions OIDC using .github/workflows/cicd.yml and the production environment.
• The failed 0.1.1188 release job will not be rerun because its immutable artifact identity cannot match the maintainer bootstrap publish.

Still blocked:

• Keep this PR draft and unmerged until the veryfront-proxy staging rollout is stable. The newest staging replica remains in CrashLoopBackOff after OOM termination while two prior replicas serve traffic.

Verification

• hydration runtime generation check passed with Deno 2.7.7
• formatting passed for all 4,877 checked files
• lint passed for all 4,800 checked files
• typecheck passed
• unit suite passed: 3,718 tests, 26,693 steps, 0 failed
• deno.json and the shared VERSION constant both contain 0.1.1189
• the branch diff against current main contains only the three release artifacts
• git diff validation passed

No tags, GitHub releases, or 0.1.1189 packages have been created.

[Copilot]

Pull request overview

This PR performs a routine Veryfront framework/package release bump to 0.1.1187, keeping the canonical version sources aligned and regenerating the prebundled hydration runtime that embeds the version.

Changes:

• Bump deno.json package version to 0.1.1187.
• Update the shared VERSION constant to 0.1.1187.
• Regenerate the prebundled hydration runtime so the embedded VERSION matches.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
deno.json	Updates the package version to 0.1.1187.
src/utils/version-constant.ts	Updates the shared VERSION constant to 0.1.1187 (kept in sync with deno.json).
src/html/hydration-script-builder/hydration-runtime.generated.ts	Regenerated hydration runtime bundle with the new embedded framework version.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kwakayama]

Authoritative Model Call Context canary is now PASS against the reviewed Code/API heads and their exact landed mappings.

• 25 warmups + 500 measured calls over 900.147s
• 2,359,296-byte contexts; 10 parts/context; 5 append requests/context
• p95 203.231ms; p99 259.617ms
• 0 timeouts, aborts, incomplete/corrupt contexts, sentinel leaks, locks, or deadlocks
• Cleanup completed

Evidence: .omx/evidence/model-call-context/final-authoritative-canary-5e7068a5-066da53f-20260802T1550Z/FINAL-SUMMARY.md in the shared implementation workspace.

The remaining operational merge gate is the pre-existing veryfront-proxy staging rollout: the new pod is still OOM-looping while two prior replicas serve traffic. Keep this PR draft/unmerged until that rollout is stable.

[kwakayama]

Additional release-blocking finding from the exact landed MCC architecture review:

• same-process durable child forks currently bootstrap only child identifiers/status;
• they reuse the ordinary request auth token for the child durable mirror;
• unlike detached/default-chat child invocation, they do not receive an exact-child-run runEventAppendToken;
• the deployed API correctly rejects private AGENT_RUN_MODEL_CALL_CONTEXT rows unless the exact run writer credential is used.

This violates the hosted child-run acceptance gate and will be fixed API-first with a private child-scoped writer-token handoff plus cross-repo auth/leakage tests. This draft must also be refreshed onto that Code fix before release.

Independent of that correctness issue, the staging proxy binary-size/OOM gate also remains open.

[kojiwakayama]

Release hold: do not publish this 0.1.1187 draft with PR #3282 included. #3282 intentionally changes public hosted-agent capability inputs, and the current CONTRIBUTING SemVer policy requires a major release for breaking changes. Keep this draft closed from merge/release until #3282 is either excluded or the project explicitly selects and documents the correct breaking-release version and policy.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db390dc3-8b0d-4c5d-970e-edc07651c850

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

[kojiwakayama]

Release-hold update at exact head 2ae859b:

• The maintainer confirmed this repository should continue with patch releases, so the branch now uses the next unused patch, 0.1.1189.
• The child-run writer capability blocker is addressed by merged PR fix(agent): scope durable child run event writers #3282 and is included through current main.
• The missing npm package was bootstrapped once at 0.1.1188, and its GitHub Actions trusted publisher is configured for tokenless OIDC publication. The old failed 0.1.1188 job will not be rerun.
• Full local pre-push verification passed: format, lint, typecheck, and 3,718 unit tests with 26,693 steps.

The operational proxy gate is still open. The newest staging replica remains CrashLoopBackOff after OOM termination while two older replicas serve, so this PR remains draft and must not merge yet.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

deno.json:3

• The PR metadata references #3282 as a breaking change and notes the release policy would require publishing that contract change as a major version (1.0.0). This PR bumps only the patch version to 0.1.1189, which appears inconsistent with that stated policy. Please confirm the current versioning policy for breaking changes and adjust the version accordingly before publishing.

  "name": "veryfront",
  "version": "0.1.1189",

[kojiwakayama]

Closing as superseded. The same patch release version (0.1.1189) landed on main in d63ea1b, and the recovered tokenless release job published veryfront@0.1.1189 plus the new @veryfront/ext-react-ssr@0.1.1189. Keeping this draft open would no longer produce a distinct release.