Converge, deploy, and verify trytilde/our-openbot

[danielblignaut]

What to build

Converge trytilde/our-openbot onto the released canonical OpenBot and Tilde API stack, migrate its fork-owned materialized agents and templates, deploy it, and verify the complete workspace as one product. The fork must consume upstream packages and generated contracts rather than copying SDK logic into configuration.

This issue is tracked in canonical OpenBot because GitHub Issues are disabled in trytilde/our-openbot.

Acceptance criteria

• Rebase or update the fork from the merged canonical OpenBot release without dropping fork-owned configuration, encrypted environment references, current agents, subagents, prompts, skills, or templates.
• Replace legacy SDK/direct-key inference paths with current Tilde SDKs and managed Vercel project OIDC; no organization Gateway key is stored in the agent repository or runtime environment.
• Materialized agents and future-agent templates include durable goals/tasks/jobs/runs, compaction, routines, exact capability approval, automatic memory, Memory Catcher, personal-tool federation, and hosted AI-credit handling.
• Signup creates personal MCP, Skills, Wiki, and Memory resources; a configured Memory Catcher processes the 1,000-token bank queue and persists mutation receipts.
• End-to-end tests cover synchronous memory mutation, background synthesis, hybrid recall/reranking/provenance, protected owner facts, compaction/cache ordering, restart recovery without duplicate effects, background job steering/artifacts/wakes, provider setup continuation, personal-tool audience isolation, and insufficient-credit recovery.
• Linux x64 and macOS arm64 release paths pass for the converged fork.
• The convergence PR receives a complete self-review, Greptile score of at least 4/5, and green CI before merge.
• The deployed workspace passes smoke tests against the production API contract and leaves no retired provider configuration, plaintext secrets, or prohibited competitor wording.
• Exact deployment commits, endpoints, test evidence, and any intentionally deferred multiplayer UI work are recorded in the release handoff.

Blocked by

• https://github.com/trytilde/api/issues/233
• feat(memory): add automatic recall and background synthesis #120
• feat(inference): meter hosted Gateway calls #123
• docs: cover durable agent product stack docs#32