lunheng-article-pipeline-dsh

Lunheng (lunheng-article-pipeline) — a DeepSeek Harness bundle for multi-agent long-form writing 🌐 English (this file) ｜ 中文 ｜ Español ｜ Português ｜ हिन्दी 版本：v19.27.16（DSH bundle：package.json + cordis.patch.yml + lib/index.js） A DeepSeek Harness (DSH) bundle that registers two on-demand agent skills: - lunheng-article-pipeline — the main 9-role pipeline (T1–T9, see below). - lunheng-commands — a thin wrapper exposing 13 /lunheng-* slash commands (draft / resume / cite / audit / journal / ppt / history / rollback / status / stats / gate / abort / help). No new role, no new M-gate item; see skills/lunheng-commands/SKILL.md. The main skill turns long-form production — academic papers, industry analysis, business commentary, and long-form articles — into a 9-role pipeline with a human in the loop. What this is

Lunheng is a writing pipeline, not a text generator. It splits a long-form deliverable into 9 independent roles (T1–T9) across 6 phases, orchestrated with DSH subagent calls, and produces output with an evidence base, counter-argument review, independent audit, and human checkpoints.

The nine roles are independent and interchangeable with nothing else: T1 literature scout, T2 data scout, T3 case scout, T4 analyst, T5 writer, T6 critical companion, T7 auditor, T8 finalizer (executed by the coordinator itself), T9 peer reviewer. When to use it You need a long-form piece (over 2000 characters) that has to hold up under scrutiny, and you can wait several hours (the pipeline deliberately gives no hour range — see skills/lunheng-article-pipeline/SKILL.md §边界). The topic involves facts, figures, or multiple viewpoints, so it needs an evidence base rather than opinion only. You want human checkpoints: confirm the outline before drafting, and review the final draft. When not to use it

Lunheng actively collects published evidence and integrates evidence you supply. It cannot produce the following on its own; supply the material first, or use another tool: First-hand data collection — experiments, surveys, interviews, field work. Statistical analysis — it can cite results but does not run SPSS/R/Python. Raw chart data collection — it renders data visualizations; scraping, OCR, and speech-to-text need dedicated tools. Original images or video — DSH has no built-in text-to-image. Covers fall back to local SVG or supplied files. Code execution — the pipeline runs only whitelisted scripts; anything else needs your explicit approval.

Rule of thumb: ask whether the evidence is already published. If yes, Lunheng collects it. If not, supply it first. What you get Pipeline overview

Triangular evidence base ([L] + [D] + [C]) — every claim must map to literature, data, and (for event claims) case evidence. Independent audit — the auditor never edits; it reports. Four human checkpoints — Phase 0, 2.5, 3.5, and 5. Repository layout

The plugin entry registers skills/lunheng-article-pipeline/SKILL.md as a skill whose resourceBase is that directory, so references/ and scripts/ resolve relative to it from any working directory.

The patch layer does two things: it inserts one row for this package (- id: lunheng-article-pipeline / name: lunheng-article-pipeline) — that row is what makes the loader import lib/index.js, which is what registers the skill — and it inserts the three model-tier subagent tools, which are not mounted by default (set any LUNHENG_{RETRIEVAL,STRONG,AUDIT}_{PROVIDER,MODEL} or LUNHENG_TIERING=on to mount them, off to force them off). That self row is load-bearing: without it the entry is never imported and no skill appears (the v18.0.0 defect fixed in 18.0.1; guarded by tests/bundle-contract.test.mjs). Documentation Publishing (maintainers)

Releases are tag-only; a local npm publish is forbidden (it would bypass the CI gates and OIDC provenance, and a published npm version can never be overwritten).

Install

As a bundle (recommended; the entry registers the skill + the C-g