content-factory-plugin

Content Factory

Plugin marketplaces

This plugin belongs to AIGC content creation.

Category · Marketplace · Purpose Full-stack development · Full Stack Plugins · Architecture and UI design, code understanding, quality checks, code review, workflow governance, and server operations AIGC content creation · Full AIGC Plugins · Image, video, audio, music, 3D, and multimodal content creation

A content production, review, and delivery plugin that turns real source material into publishable content.

English | 简体中文

Current implementation status

Content Factory has a working offline runtime and a fail-closed release gate. It is not yet a production release.

Current package: 1.0.0-rc.3 — release candidate, not a production release.

Task · Status · Evidence CF-001–002, 005–024, 037–038, 040, 043–052, 054–055, 058 · COMPLETE · Supply chain, Runtime Kernel, harness, import/edit/render/export, routing, recovery, security, and fail-closed release gate CF-003–004 · PARTIAL_OFFLINE · One sanitized AI content detector website observation is recorded; the authenticated API contract and content-platform account probe remain NOT_RUN CF-025–036, 039, 041, 053, 056–057 · PARTIAL_OFFLINE · Offline contracts pass; real services, accounts, host sessions, or human review remain NOT_RUN v1.0.0 release · BLOCKED · Release requires an immutable candidate plus complete live evidence; current details are maintained outside the package in docs/verification/

The current baseline has a cross-platform automated regression suite, 16 channel profiles, 39 explicit channel-format recipes, three host manifests, immutable vendor skills, and one plugin-local content-harness. The exact test count is reported by the current CI run rather than frozen in documentation. Offline verification is not live verification.

Verify the current baseline

Node.js 24+ is required:

npm install --ignore-scripts
npm run lint
npm run typecheck
npm test
npm run skills:check
npm run build
npm run doctor
npm run release:gate

npm run skills:check performs offline integrity validation. npm run skills:check:upstream additionally resolves pinned upstream tags. npm run release:gate currently exits non-zero by design and lists the missing live evidence.

Local Zhuque key setup

Run npm run zhuque:setup in the source checkout to open Content Factory's bundled local setup page. When this version's MCP server is loaded by a host, the agent can open the same page with content_factory_zhuque_setup. Enter the key in the page, never in chat. The page binds only to 127.0.0.1 and closes after ten minutes. The key is stored in the current user's config directory (macOS/Linux default: ~/.config/content-factory/credentials.json) with owner-only Unix permissions. An explicit process ZHUQUE_API_KEY takes precedence over the stored value.

npm run zhuque:status or content_factory_zhuque_status reports only whether a key is configured. Saving a key does not verify the API or detect an article. The page never sends article text or contacts Zhuque; actual detection remains subject to outbound-content consent, a real provider response, and exact-revision checks. This setup entry does not clear CF-025/CF-030 or production-release gates.

Architecture

HostContext + SourceContext + ChannelIntent
                    |
                    v
             content-harness
                    |
          ChannelProfile/Recipe
                    |
         admitted Vendor Skills
                    |
                    v
              Runtime Kernel
       revision / fact / approval
       detection / delivery / recovery
                    |
          +---------+---------+
          v                   v
    Image Factory        channel adapters

Key invariants:

• content-harness is the only plugin-local Skill.
• Research, writing, translation, editing, and formatting prefer reviewed immutable vendor skills.
• Generated images are delegated to Image Factory.
• Host, source platform, and target content channel are independent contexts.
• Remote delivery requires explicit account/action approval and read-back verification.

Documentation

• Complete architecture
• OpenSpec entry point
• CF-001–CF-058 implementation tasks
• Implementation plan
• Traceability
• Task evidence
• Verification status guide
• Blocked release candidate
• Integrated release result

Current vendor baseline

skills.lock.json currently pins:

• full-aigc-skills/baoyu-skills@v1.63.0
• commit c1e1526c84fd07d71d9d12e9845dceeb366d1b42
• baoyu-format-markdown
• baoyu-markdown-to-html
• MIT license provenance

Visual-generation Baoyu skills remain outside Content Factory and belong to Image Factory.

Release boundary

No v1.0.0 tag, release, package publication, or marketplace update has been created. The remaining gates require authorized external accounts, actual Codex/ZCode/Kimi sessions, three-sample authenticated AI content detection API evidence, content-platform draft save/readback, and the 30-document dual-human review. Until those checks bind to one exact commit and package digest, the release remains BLOCKED.