Codex
2396bd2d3e
Remove Kingdee sync, business CLI/MCP tools, and internal order-query routing now owned by the separate kingdee-orders-mcp project. Keep Wiki retrieval, file assets and ingest available in code while its deployed service is off. Retain legacy response fields with business access disabled, and document migration ownership and rollback without exposing credentials or data. Validation: 174 Wiki tests pass. Independent order service verified with 36 template parity checks, authenticated HTTP queries, and a real sync.
1.2 KiB
Order service extraction
Order MCP and Kingdee synchronization now live in the independent project at /home/nac/repo/kingdee-orders-mcp. Its README documents CLI operations, MCP configuration, and systemd services. Neither project imports the other.
The new project owns .runtime/data/business-facts.sqlite, private API credentials, token cache, and its daily incremental sync. MCP clients retain the existing URL and bearer token. The order tool names are unchanged. Wiki query, file lookup, and ingest are not exposed by the order server.
The former obsidian-wiki-mcp.service and obsidian-wiki-business-sync.timer are disabled. The old vault _meta/business-facts.sqlite and private runtime configuration are retained as rollback backups, not active data sources. Do not run the old sync against this backup.
For rollback, stop the new MCP and sync timer first. Restore Wiki code from commit 6c451c3 (prefer an isolated checkout), restore its private service environment from the migration backup, and point the legacy service at a consistent backup of the latest new database before enabling it. Do not resume the stale original database silently. Ensure only one sync owns the live database. New credentials and databases must never be committed to Git.