[Maintenance] Migrate private workspaces and UI dependency to @bytefolk

[PeterGuy326]

Parent: bytefolk/.github#22
Blocked by: bytefolk/design-system#19

Outcome

Use ByteFolk package identities throughout the private Doc workspace and consume the verified ByteFolk Design System artifact without publishing internal services.

Exact plan

• Rename private root and CLI identities to @bytefolk/doc and @bytefolk/doc-cli.
• Rename collaboration service to @bytefolk/doc-collaboration and set private: true to prevent accidental publication.
• Replace @fullstack-ai-infra/ui imports/dependency with @bytefolk/ui@0.2.1.
• Replace the vendored old-scope tarball with the exact verified tarball produced by the Design System release; update filename, integrity, lockfile, diagnostics, Docker/config paths, tests, docs, and changelog.
• Do not hand-edit or text-rewrite the tarball.

Acceptance

• Internal packages are private/nonpublishable.
• Vendored tarball checksum and package metadata match the verified Design System artifact.
• No active old-scope import, dependency, node_modules path, command, or lockfile entry remains.
• Repository checks and user-visible Doc flows pass.

[waterbro-8]

Still blocked by bytefolk/design-system#19 and parent bytefolk/.github#22. I cannot complete @fullstack-ai-infra/ui → @bytefolk/ui or the private package rename until that artifact is the published coordinate. No PR while the blocker is open.

[waterbro-8]

2026-09-22 重新核对外部依赖：bytefolk/design-system#19 仍 OPEN，bytefolk/.github#22 仍 OPEN。已发布且可验证的 @bytefolk/ui@0.2.1 坐标/制品仍未由这两项依赖解除；继续保持 blocked，不提交手改 tarball 或提前迁移消费者坐标的 PR。