Add Univer CLI builder integration skill

[hexf00]

Why

The public univer-cli Skill is the discovery entry for operating .univer content. Builders also need a separate entry for understanding and integrating Univer CLI, Runtime Skills, daemon/Gateway, Univerfile Links, and Cowork. This Skill explains what the components provide, where to obtain them, how to connect them, who owns each responsibility, and how to complete a real delivery without prescribing an application type.

Correctness

• Adds the public integrate-univer-cli Skill while preserving the existing univer-cli content-operation entry as a separate responsibility.
• Synchronizes the complete capability, ownership, acquisition, connection, customization, delivery, and acceptance semantics from the validated Chinese source at dream-num/harness-skills@3c8156b58da7df0bba23db434ac733e35c8d5013.
• Places Univer CLI at the center and explains Univer, Univerfile, Unit, target, worktree, Runtime Skills, daemon/Gateway, Univerfile Links, and Cowork.
• Defines exact CLI and Cowork version pinning, the complete Univer SDK peer cohort, lockfile ownership, and a compatibility manifest.
• Uses Cowork for embedded Univer content and Unit/worktree/review state. univer open remains an external-open handoff and is not embedded through an iframe as a UI substitute.
• Routes browser HTTP and WebSocket traffic through a same-origin host proxy to the actual Gateway origin reported by the daemon. Browser code never receives a loopback address owned by a container or remote machine.
• Covers public controller, content-surface, Viewer, and lifecycle integration for both React and non-React hosts, with real browser acceptance.
• Registers both Skills in the READMEs and extends the existing validator to check the Builder Skill, its references, and public visibility. Repo-local drift validation remains scoped to the CLI-mirrored discovery Skill.

Long-term correctness

• The Chinese repository remains the internal incubation and adversarial-validation source. This repository publishes a complete English semantic snapshot from an explicit validated Chinese commit, rather than creating two independent sources of truth.
• Commands and Facade workflows use the installed CLI help and Runtime Skills as authority. Cowork integration uses the installed package exports, .d.ts declarations, and peer dependencies as authority.
• The Skill selects components from explicit capability requirements and does not enumerate or imply application types. The host continues to own domain workflows, application shell, routing, persistence, and product experience.
• When a public contract cannot complete a connection, the Skill reports the missing adapter or type instead of using a private parser, forced type cast, or iframe to claim success.
• Known product gaps are tracked independently in univer-cli#875, #876, #888, and #889.

Try the Builder Skill

The temporary builder preview branch is kept aligned with this PR. From the application repository where the agent should work, install the Skill with:

npx skills add https://github.com/dream-num/skills/tree/builder/skills/integrate-univer-cli

For a non-interactive project-local Codex installation:

npx skills add https://github.com/dream-num/skills/tree/builder/skills/integrate-univer-cli --agent codex --yes

Start a fresh agent session in the same repository and provide the actual user outcome in place of the placeholder:

Use $integrate-univer-cli to inspect this repository and help me integrate Univer for this goal: <describe the user outcome>. Explain what Univer provides; select only the needed Univer CLI, Runtime Skills, daemon/Gateway, Univerfile Links, and Cowork pieces; identify where each selected component comes from and how responsibilities and connections fit together; then implement and validate the integration. Do not assume an application type.

During review, check that the agent:

• grounds component selection in the repository and requested outcome, and explains both selected and excluded pieces;
• provides concrete acquisition, version, ownership, connection, customization, delivery, and acceptance guidance;
• uses Cowork for an embedded Univer UI when that capability is required, while treating univer open as an external-open handoff; and
• reports a missing public adapter or contract as a gap instead of claiming success through a private workaround, forced type cast, or iframe substitute.

Validation

• npm run validate: passed. The single repository gate now checks 2 official Skills, README links, and 14 contract Markdown files.
• Skill Creator quick_validate.py: passed.
• git diff --check: passed.
• Relative Markdown links: all 21 relative links and 6 heading anchors across 11 Markdown files resolve.
• Chinese-English parity review: all 12 files passed. The 31 fenced code blocks align; 23 command, configuration, and code blocks are byte-equivalent, while the remaining 8 only translate labels in text diagrams. URLs, package entrypoints, versions, and pinned commits are unchanged.
• Context-free English routing smoke: an agent correctly selected CLI, Runtime Skills, Gateway, Cowork, a same-origin proxy, and a single backend merge owner from an ordinary React/Node review request while preserving the Link/container failure boundary.
• Local skills installer smoke: discovered and installed both univer-cli and integrate-univer-cli; the temporary installation copy and lockfile were removed afterward.
• Branch-preview installer smoke: skills@1.5.19 discovered exactly one Skill from tree/builder/skills/integrate-univer-cli, installed it project-locally for Codex, and produced files identical to this PR.
• The Chinese source completed a real empty-repository application acceptance, published unchanged at https://github.com/dream-num/univer-cli-app-cowork-test/tree/b0d71c0b53c36753cb82d25fb33bd4e4f908840f.

This PR remains a draft for public English content review.