fix(ci): restore runtime host validation

[liuxiaocs7]

Summary

Restore the failing main CI path by replacing the remaining removed Runtime Host operation aliases with typed request(...) calls.

Repair a session-metadata migration version collision introduced by consecutive merges that both claimed version 30. Migration 31 now converges both released v30 database variants by ensuring the durable message-admission tables and WorkHub coordination uniqueness index all exist.

Keep the managed-dependency cross-process fixture from treating Node 24's expected SQLite experimental warning as a child-process failure.

Verification

• npm run lint
• npm run format:check
• npm run build
• npm run typecheck
• Storage workspace: 946 passed, 14 platform skips, 0 failed
• Runtime Host workspace: 1174 passed, 0 failed
• Regression test verified red before the migration fix and green after it

Root cause

Two consecutive changes independently added SQLite session-metadata migration 30. Because migrations are held in a Map, the later entry silently replaced the durable message-admission migration while the database was still recorded at version 30. Runtime Host startup then queried tables that had never been created.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex diagnosed the CI failures, implemented the fixes and regression coverage, and ran local verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[Astro-Han]

I reviewed this head and found no blocking issues. The v30→v31 repeatable migration correctly converges both v30 DB shapes and adds the required admission/WorkHub unique indexes. No concurrency gaps.

Checks on 1517d18 are test: success.

简体中文

该头未发现阻断。

[liuxiaocs7]

resolved by #3796

[liuxiaocs7]

Summary

Restore the failing main CI path by replacing the remaining removed Runtime Host operation aliases with typed request(...) calls.

Repair a session-metadata migration version collision introduced by consecutive merges that both claimed version 30. Migration 31 now converges both released v30 database variants by ensuring the durable message-admission tables and WorkHub coordination uniqueness index all exist.

Keep the managed-dependency cross-process fixture from treating Node 24's expected SQLite experimental warning as a child-process failure.

Verification

• npm run lint
• npm run format:check
• npm run build
• npm run typecheck
• Storage workspace: 946 passed, 14 platform skips, 0 failed
• Runtime Host workspace: 1174 passed, 0 failed
• Regression test verified red before the migration fix and green after it

Root cause

Two consecutive changes independently added SQLite session-metadata migration 30. Because migrations are held in a Map, the later entry silently replaced the durable message-admission migration while the database was still recorded at version 30. Runtime Host startup then queried tables that had never been created.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex diagnosed the CI failures, implemented the fixes and regression coverage, and ran local verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[Astro-Han]

I reviewed this head and found no blocking issues. The v30→v31 repeatable migration correctly converges both v30 DB shapes and adds the required admission/WorkHub unique indexes. No concurrency gaps.

Checks on 1517d18 are test: success.

简体中文

该头未发现阻断。

[liuxiaocs7]

resolved by #3796

[liuxiaocs7]

Summary

Restore the failing main CI path by replacing the remaining removed Runtime Host operation aliases with typed request(...) calls.

Repair a session-metadata migration version collision introduced by consecutive merges that both claimed version 30. Migration 31 now converges both released v30 database variants by ensuring the durable message-admission tables and WorkHub coordination uniqueness index all exist.

Keep the managed-dependency cross-process fixture from treating Node 24's expected SQLite experimental warning as a child-process failure.

Verification

• npm run lint
• npm run format:check
• npm run build
• npm run typecheck
• Storage workspace: 946 passed, 14 platform skips, 0 failed
• Runtime Host workspace: 1174 passed, 0 failed
• Regression test verified red before the migration fix and green after it

Root cause

Two consecutive changes independently added SQLite session-metadata migration 30. Because migrations are held in a Map, the later entry silently replaced the durable message-admission migration while the database was still recorded at version 30. Runtime Host startup then queried tables that had never been created.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex diagnosed the CI failures, implemented the fixes and regression coverage, and ran local verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[Astro-Han]

I reviewed this head and found no blocking issues. The v30→v31 repeatable migration correctly converges both v30 DB shapes and adds the required admission/WorkHub unique indexes. No concurrency gaps.

Checks on 1517d18 are test: success.

简体中文

该头未发现阻断。

[liuxiaocs7]

resolved by #3796

[liuxiaocs7]

Summary

Restore the failing main CI path by replacing the remaining removed Runtime Host operation aliases with typed request(...) calls.

Repair a session-metadata migration version collision introduced by consecutive merges that both claimed version 30. Migration 31 now converges both released v30 database variants by ensuring the durable message-admission tables and WorkHub coordination uniqueness index all exist.

Keep the managed-dependency cross-process fixture from treating Node 24's expected SQLite experimental warning as a child-process failure.

Verification

• npm run lint
• npm run format:check
• npm run build
• npm run typecheck
• Storage workspace: 946 passed, 14 platform skips, 0 failed
• Runtime Host workspace: 1174 passed, 0 failed
• Regression test verified red before the migration fix and green after it

Root cause

Two consecutive changes independently added SQLite session-metadata migration 30. Because migrations are held in a Map, the later entry silently replaced the durable message-admission migration while the database was still recorded at version 30. Runtime Host startup then queried tables that had never been created.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex diagnosed the CI failures, implemented the fixes and regression coverage, and ran local verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[Astro-Han]

I reviewed this head and found no blocking issues. The v30→v31 repeatable migration correctly converges both v30 DB shapes and adds the required admission/WorkHub unique indexes. No concurrency gaps.

Checks on 1517d18 are test: success.

简体中文

该头未发现阻断。

[liuxiaocs7]

resolved by #3796

[liuxiaocs7]

Summary

Restore the failing main CI path by replacing the remaining removed Runtime Host operation aliases with typed request(...) calls.

Repair a session-metadata migration version collision introduced by consecutive merges that both claimed version 30. Migration 31 now converges both released v30 database variants by ensuring the durable message-admission tables and WorkHub coordination uniqueness index all exist.

Keep the managed-dependency cross-process fixture from treating Node 24's expected SQLite experimental warning as a child-process failure.

Verification

• npm run lint
• npm run format:check
• npm run build
• npm run typecheck
• Storage workspace: 946 passed, 14 platform skips, 0 failed
• Runtime Host workspace: 1174 passed, 0 failed
• Regression test verified red before the migration fix and green after it

Root cause

Two consecutive changes independently added SQLite session-metadata migration 30. Because migrations are held in a Map, the later entry silently replaced the durable message-admission migration while the database was still recorded at version 30. Runtime Host startup then queried tables that had never been created.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex diagnosed the CI failures, implemented the fixes and regression coverage, and ran local verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[Astro-Han]

I reviewed this head and found no blocking issues. The v30→v31 repeatable migration correctly converges both v30 DB shapes and adds the required admission/WorkHub unique indexes. No concurrency gaps.

Checks on 1517d18 are test: success.

简体中文

该头未发现阻断。

[liuxiaocs7]

resolved by #3796

[liuxiaocs7]

Summary

Restore the failing main CI path by replacing the remaining removed Runtime Host operation aliases with typed request(...) calls.

Repair a session-metadata migration version collision introduced by consecutive merges that both claimed version 30. Migration 31 now converges both released v30 database variants by ensuring the durable message-admission tables and WorkHub coordination uniqueness index all exist.

Keep the managed-dependency cross-process fixture from treating Node 24's expected SQLite experimental warning as a child-process failure.

Verification

• npm run lint
• npm run format:check
• npm run build
• npm run typecheck
• Storage workspace: 946 passed, 14 platform skips, 0 failed
• Runtime Host workspace: 1174 passed, 0 failed
• Regression test verified red before the migration fix and green after it

Root cause

Two consecutive changes independently added SQLite session-metadata migration 30. Because migrations are held in a Map, the later entry silently replaced the durable message-admission migration while the database was still recorded at version 30. Runtime Host startup then queried tables that had never been created.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex diagnosed the CI failures, implemented the fixes and regression coverage, and ran local verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[Astro-Han]

I reviewed this head and found no blocking issues. The v30→v31 repeatable migration correctly converges both v30 DB shapes and adds the required admission/WorkHub unique indexes. No concurrency gaps.

Checks on 1517d18 are test: success.

简体中文

该头未发现阻断。

[liuxiaocs7]

resolved by #3796

[liuxiaocs7]

Summary

Restore the failing main CI path by replacing the remaining removed Runtime Host operation aliases with typed request(...) calls.

Repair a session-metadata migration version collision introduced by consecutive merges that both claimed version 30. Migration 31 now converges both released v30 database variants by ensuring the durable message-admission tables and WorkHub coordination uniqueness index all exist.

Keep the managed-dependency cross-process fixture from treating Node 24's expected SQLite experimental warning as a child-process failure.

Verification

• npm run lint
• npm run format:check
• npm run build
• npm run typecheck
• Storage workspace: 946 passed, 14 platform skips, 0 failed
• Runtime Host workspace: 1174 passed, 0 failed
• Regression test verified red before the migration fix and green after it

Root cause

Two consecutive changes independently added SQLite session-metadata migration 30. Because migrations are held in a Map, the later entry silently replaced the durable message-admission migration while the database was still recorded at version 30. Runtime Host startup then queried tables that had never been created.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex diagnosed the CI failures, implemented the fixes and regression coverage, and ran local verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[Astro-Han]

I reviewed this head and found no blocking issues. The v30→v31 repeatable migration correctly converges both v30 DB shapes and adds the required admission/WorkHub unique indexes. No concurrency gaps.

Checks on 1517d18 are test: success.

简体中文

该头未发现阻断。

[liuxiaocs7]

resolved by #3796

[liuxiaocs7]

Summary

Restore the failing main CI path by replacing the remaining removed Runtime Host operation aliases with typed request(...) calls.

Repair a session-metadata migration version collision introduced by consecutive merges that both claimed version 30. Migration 31 now converges both released v30 database variants by ensuring the durable message-admission tables and WorkHub coordination uniqueness index all exist.

Keep the managed-dependency cross-process fixture from treating Node 24's expected SQLite experimental warning as a child-process failure.

Verification

• npm run lint
• npm run format:check
• npm run build
• npm run typecheck
• Storage workspace: 946 passed, 14 platform skips, 0 failed
• Runtime Host workspace: 1174 passed, 0 failed
• Regression test verified red before the migration fix and green after it

Root cause

Two consecutive changes independently added SQLite session-metadata migration 30. Because migrations are held in a Map, the later entry silently replaced the durable message-admission migration while the database was still recorded at version 30. Runtime Host startup then queried tables that had never been created.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex diagnosed the CI failures, implemented the fixes and regression coverage, and ran local verification.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[Astro-Han]

I reviewed this head and found no blocking issues. The v30→v31 repeatable migration correctly converges both v30 DB shapes and adds the required admission/WorkHub unique indexes. No concurrency gaps.

Checks on 1517d18 are test: success.

简体中文

该头未发现阻断。

[liuxiaocs7]

resolved by #3796