[debba]

Adds the operator-managed ai-assistant preset used by Tabularis #1337, with the declarative HTTP contract, Gemini authoring example and optional public catalogue page. It leaves generic registry defaults unchanged.

The existing eight providers are embedded in the application, including API Route. They do not need external replacement releases; ChatGPT account login also remains built in. Gemini is the first external example.

Validation against current main: all 66 manifest-package tests pass, including the Gemini example against the merged core-plus-kind schema and rejection of missing contracts/executable fields. The preset matches the application source, including explicit-model metadata. Focused Biome checking passes. GitNexus detects only the expected companion changes against current main; incoming-main Markdown changes were inspected separately.

This remains a companion draft. Source deployment alone does not apply the operator preset or publish a provider. The authenticated production rollout has now been completed for Gemini, as recorded below. See deploy/tabularis/README.md for the Gemini-only rollout procedure.

Published Gemini example

Google Gemini on Tabularium is now a concrete external ai-assistant example. Gemini 1.0.2 ships the standalone .tabularium manifest and gemini-1.0.2-universal.zip with:

{
  "id": "gemini",
  "name": "Google Gemini",
  "version": "1.0.2",
  "kind": "ai-assistant",
  "min_runtime_version": "0.32.1-4"
}

This is an excerpt; the complete manifest also declares the ai_assistant HTTP contract. 0.32.1-4 is the next nightly expected on November 13, 2026, following the currently published 0.32.1-3. The plugin is published now and requires that upcoming runtime or a newer compatible release; the nightly itself has not shipped yet.

The authenticated operator has applied the ai-assistant kind preset. Gemini 1.0.2 is approved and indexed, its universal ZIP resolves through the registry, and its version, runtime floor, SHA-256, size and signed integrity metadata are present. The release workflow passed and the repository webhook is installed for future releases. Gemini 1.0.0/1.0.1 remain historical development previews without this runtime floor.

To try it on a compatible runtime: Settings → AI → Available providers → Google Gemini → Install and use, then configure a Gemini API key or GEMINI_API_KEY. This publication check does not add a live Gemini generation test to the validation reported above.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
tabularium-docs	Ready	Preview	Nov 12, 2026 10:40pm UTC
tabularium-website	Ready	Preview	Nov 12, 2026 10:40pm UTC

[NewtTheWolf]

I checked 20264751b90ebaab3175802ecafc133f2f6ac847 alongside the current Tabularis #1337 revision (33df995a). The 66 manifest-package tests pass. The operator preset is structurally identical to the preset currently bundled in that application PR, and the actual Gemini 1.0.1 manifest validates against the merged core-plus-kind schema, including its HTTPS icon, native model-resource URL, key header and discovery filter. The standalone manifest and ZIP agree, with SHA-256 and sizes matching the GitHub release metadata.

The rollout documentation now needs the change Debba described in the application checklist: the seven existing providers stay embedded and require no external replacement packages. Please replace the seven-package publication requirements in this PR's description and deploy/tabularis/README.md with the Gemini-only rollout and its actual first supporting runtime version. Gemini 1.0.1 is still a development prerelease without min_runtime_version.

I checked the connected deployment read-only: GET of kind ai-assistant returns 404 and the AI-kind catalog is empty. The preset has not been applied there. Deploying this source alone still does not create the operator kind, publish the provider or establish native application compatibility.

Tabularis #1337 also has a reproduced failed-discovery cache bug and current-main conflicts, now recorded in my review there. I am leaving this companion draft open for the updated rollout text and coordinated application/runtime gates. I did not change production registry configuration or publish a release.

[NewtTheWolf]

Updated 98a3f540ba68f81dc359bad28e2c564c134e3850 alongside the fixed application revision. The source now matches the application's operator schema and Gemini example, keeps the existing providers embedded, and replaces the obsolete seven-replacement-package rollout with the actual Gemini/runtime gates. Current-main manifest tests pass (66), as does focused formatting/lint validation.

The connected deployment still returns 404 for kind ai-assistant and an empty AI listing. I left production unchanged and kept this companion draft: applying the authenticated operator preset, selecting the actual first shipping runtime version, and publishing/ingesting a gated Gemini successor are still release operations. The current 1.0.1 prerelease should not become a production listing without that runtime requirement.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
deploy/tabularis/README.md	46	Rollout steps 4-5 tell operators to publish seven external replacement providers. The PR description says the existing providers stay embedded and Gemini is the only external example.

Files Reviewed (4 files)

• deploy/tabularis/README.md - 1 issue
• deploy/tabularis/ai-assistant-kind.json
• packages/manifest/test/tabularis-ai-assistant.test.ts
• .github/workflows/ci.yml

Fix these issues in Kilo Cloud

---

_{Reviewed by claude-sonnet-5.5 · Input: 246 · Output: 2.3K · Cached: 167.7K}