- The active `/books/design` route now delegates to the private `books/design/routes.tsx` module.
-`DesignView.jsx` owns the dedicated Chuangkit editor integration; no list abstraction or artificial query/Hook layer was introduced.
- The public URL and full-size `ckt-design-page` render target remain unchanged.
## Preserved integration behavior
- The existing Chuangkit app ID, app secret, device type, kind ID, version, authorization, taxpayer values, and render target are preserved exactly.
- Signature generation still sorts every `key=value` pair, joins with `&`, hashes with MD5, and uppercases the result.
- Version 2 signing continues to use `app_id`, the current millisecond `expire_time`, Redux `userInfo.id` as `user_flag`, and `app_secret`.
- The SDK opens after the view mounts and closes during cleanup; a user identity change safely recreates the editor with a matching signature.
-`window.chuangkitComplete` remains installed as the completion/save callback and preserves the original callback handling.
- The legacy page had no backend request wrapper, explicit application error UI, or separate stylesheet, so none were invented during migration.
## Legacy compatibility
- The old `pages/books/design/index.jsx` was not deleted because deprecated `src/routes/routes.jsx` still imports it and `src/config/component.js` still names it through the dynamic component path. Both references are outside this task's allowed scope.
-`pnpm exec tsc --noEmit`: no diagnostics under `src/modules/books/design` or `src/modules/books/routes.tsx`; the workspace still has unrelated existing diagnostics.
-`pnpm test`: passed, 11 tests.
-`pnpm build`: passed; only the existing formula-editor and large-chunk warnings were emitted.
## Concerns
- Per task direction, no API/query/Hook tests were added; this page has no local API/query/Hook layer.
- The client-side Chuangkit credentials and taxpayer metadata remain hardcoded because preserving the existing integration exactly was required.
- The legacy page remains until its deprecated route/config references can be migrated in an explicitly authorized scope.