2 Commits

Include renames

Author	SHA1	Message	Date
ZacharyZhang-NY	813276de71	Kimi and Kimi CN join the provider catalog: OpenAI-compatible endpoints, verified live ... - kimi -> https://api.moonshot.ai/v1 (platform.kimi.ai keys), kimi-cn -> https://api.moonshot.cn/v1 (platform.kimi.com keys) - Adapters via openAiCompatibleAdapter; agent loop via makeChatCompletionsTurn; live model listing - Curated fallback models per current docs: kimi-k2.7-code, kimi-k2.7-code-highspeed, kimi-k2.6 - Migration 056 seeds both providers (disabled) into existing organizations - Both endpoints probed live: OpenAI-style 401 error envelope confirmed	2026-07-10 17:12:16 -04:00
ZacharyZhang-NY	07d0b4587d	Promote AgentCompany-New to the repository root and retire the old app ... The legacy application - its src, tests, landing site, promo assets, docs, release tooling, CI workflows, and root configs - leaves the tree; it stays reachable in history. Everything under AgentCompany-New moves up unchanged: same package name, so the production userData/database path is untouched, and e2e/build scripts already resolved paths relative to the project. The developer cred.txt stays gitignored at its new location. Full verify:ci passes from the new root.	2026-07-07 00:04:13 -04:00