Vercel Voice Agents PR

[CoderOMaster]

Voice agents with vercel ai sdk package.

[github-actions]

Codex review

The PR adds a Vercel voice-agent cookbook, but the new runtime route and CI/package metadata introduce regressions that can break the demo or future merges/releases.

Findings not on changed lines:

• .github/workflows/ci.yml:133 BLOCKING ```yaml
  node-version: '20'

This PR deletes `.github/workflows/python-test.yml`, whose deleted comment says the branch ruleset still requires a `python-test` status check, but no replacement `python-test` job is added here. After merge, protected branches can wait forever for a check no workflow emits. Restore that workflow or add a job named exactly `python-test` before removing the shim.
- `packages/vercel-sdk/package.json:35` **BLOCKING** ```json
"ai": "^6.0.0"

The PR adds an AI SDK 7 cookbook (examples/cookbook/vercel-voice-agent uses ai@^7 and @moss-tools/vercel-sdk@^0.1.1) while rolling this package metadata back to 0.1.0 and dropping the AI7 peer/test matrix. A release from this state either tries to publish/tag an older version or produces a local package that cannot satisfy the new AI7 consumer. Keep the version monotonic, for example 0.1.2, and restore "ai": "^6.0.0 || ^7.0.0" plus the Node22/AI7 CI case, or move the cookbook to AI6-compatible dependencies.

[github-actions]

BLOCKING ```ts
.catch((err: unknown) => { console.error('[MOSS] loadIndex failed:', err); throw err; });

`indexReady` is created at module load, so if `loadIndex()` rejects before any search request awaits it, this rethrow leaves the stored promise rejected without a handler and can terminate the Node/Next process instead of returning the intended 503. Keep the startup promise fulfilled with status, then branch in the handler:
```ts
const indexReady = client.loadIndex(indexName)
  .then(() => true)
  .catch((err) => { console.error('[MOSS] loadIndex failed:', err); return false; });

if (!(await indexReady)) return new Response('Search index unavailable', { status: 503 });

[github-actions]

CONSIDER ```ts
const text = await res.text();

`/api/token` deliberately returns non-2xx responses for auth and index-load failures, but this handler treats every response body as a successful tool result and returns it to the model. Check `res.ok` before counting hits or returning text so the UI surfaces failures instead of letting the assistant answer from `Unauthorized`, `Search index unavailable`, or an HTML error page:
```ts
if (!res.ok) {
  const message = await res.text();
  setError(message || `Search failed (${res.status})`);
  throw new Error(message || `Search failed (${res.status})`);
}
const text = await res.text();