fix(build): correct module-name type in pyproject.toml files

[60ke]

Summary

The module-name field in [tool.uv.build-backend] should use string syntax for these single-module packages.

Regression History

This is a regression for the root package configuration:

• Commit b75c9973 (2025-11-17) fixed the root pyproject.toml by changing module-name = ["kimi_cli"] to module-name = "kimi_cli".
• Commit d2dfc94c (chore(dep): move kaos package to separate repo) later changed the root configuration back to module-name = ["kimi_cli"] while removing kaos from the same list.

The workspace package files have the same invalid single-module list syntax, so this PR corrects all affected uv_build package configs together.

Problem

The incorrect list syntax causes uv run to fail with:

TOML parse error at line 57, column 15
   |
57 | module-name = ["kimi_cli"]
   |               ^^^^^^^^^^^^
invalid type: sequence, expected a string

Root Cause

According to the uv build backend settings documentation:

• Single module packages should use string syntax, for example module-name = "sklearn".
• List syntax, for example module-name = ["foo", "bar"], is for namespace packages with multiple modules.

These packages each expose a single root module, so they should use string format.

Changes

File	Before	After
pyproject.toml	module-name = ["kimi_cli"]	module-name = "kimi_cli"
packages/kaos/pyproject.toml	module-name = ["kaos"]	module-name = "kaos"
packages/kimi-code/pyproject.toml	module-name = ["kimi_code"]	module-name = "kimi_code"
packages/kosong/pyproject.toml	module-name = ["kosong"]	module-name = "kosong"
sdks/kimi-sdk/pyproject.toml	module-name = ["kimi_sdk"]	module-name = "kimi_sdk"

Test Plan

• uv run python -c "print('works')"
• uv sync
• uv build

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.