feat(ppt): add independent Kimi-only mode

[SuperstructureJH]

Summary

• add a second, independent Kimi-only PPT route to DSH Desktop
• mount only experimental-kimi-ppt-standard-adapter in the Desktop web profile
• name the bundled core package dsh-kimi-ppt so its ownership matches the Kimi-only route
• bundle the local PPTD renderer, editable PPTX delivery, the Kimi Skill, and 22 Kimi template packs: three visually distinct upstream choices in each of seven categories plus the user-supplied 58-page Vitality Blue logic-chart template
• remove the Vitality Blue top-right logo once from shared slide layout 7, preserving all 58 pages, charts, text, geometry, and page order
• expose all 58 sanitized page previews and the rich PPTX-derived semantic index; send eight representative pages initially and keep every source page available by number
• preserve explicitly admitted user templates across upstream catalog refreshes while retaining the 3-per-category upstream selection contract
• calculate a geometry-derived textCapacity for every template text region and include it in detailed PPTD references
• direct the Kimi Skill to keep titles and body copy within each region's capacity while retaining the single-pass authoring path
• place the PPT action directly beside Standard mode above the Composer, keep the catalog below the input, and render a selected-template preview before editable prompt text
• exclude Tencent editor_sdk, SlideP runtime, and the Tencent ppt_* tool surface from this route
• strengthen the Desktop plugin-closure check so every profile-mounted package must be both reachable from @deepseek-ai/dsh and declared as a local production dependency
• verify every JavaScript chunk imported by the Kimi Host entry is present in the packed artifact
• pin both bundled tarballs to their actual SHA-512 values in package-lock.json and verify that lock-to-artifact relationship in the integration gate
• package windows-hidden-console.mjs beside harness-node-entry.mjs and bind the runtime import to the extraResources entry in the release regression gate

This PR is the Kimi route. PR #278 remains independently reviewable for the Tencent/Slides route.

Verification

• pnpm --filter dsh-workbuddy-ppt bundle
• focused capacity checks in the Kimi source: 3 files, 3 selected tests passed
• scoped bilingual README pairing check: 1 pair consistent
• npm run typecheck
• npm test -- test/kimi-ppt-integration.test.ts: 1 file, 8 tests passed
• npm test -- test/release.test.ts test/windows-hidden-console.test.ts test/kimi-ppt-integration.test.ts: 3 files, 37 tests passed
• both core and adapter tarball SHA-256 values pass, and their computed SHA-512 values match package-lock.json
• packed-artifact inspection confirms 22 template packs, exactly 58 Vitality Blue page images, the sanitized source fingerprint, the Kimi Host split chunk, textCapacity in protocol/runtime/Skill, and zero Tencent/SlideP/editor SDK paths
• the 58-page sanitized source previously passed OOXML package integrity, Artifact Tool import, LibreOffice rendering, and full contact-sheet visual review
• prior isolated native DSH Desktop acceptance confirms the PPT action beside Standard mode, the 21-template catalog layout, and the selected-template preview inside the input before the prompt

Windows run 33858394947 passed npm ci, the full npm test suite, npm run typecheck, and the isolated development-package build. Its packaged Harness smoke then exposed the missing windows-hidden-console.mjs resource. The current branch includes that resource, its importer-to-resource regression checks, and a follow-up source-presence assertion; the refreshed Windows run remains the final CI gate.

Acceptance boundary

Source capacity calculation, package closure, and focused Desktop verification pass. Capacity is authoring-time guidance carried by the template reference, preserving the current single-pass generation workflow. Reproduction with the colleague's original failing deck and PowerPoint/WPS edit-save-reopen remain separate acceptance gates.