dsh-pixinsight-pipeline

A DeepSeek Harness (DSH) plugin that packages the pixinsight-pipeline skill 閳?automated deep-sky astrophotography processing driven from DSH through a file-based IPC bridge into a running PixInsight 1.9.4.

It bundles three things so it works as a normal DSH plugin:

1. the skill (skills/pixinsight-pipeline/SKILL.md + reference/ knowledge base),
2. the bridge CLI (lib/pixinsight-mcp/scripts/pi-tool.mjs) and its ops modules,
3. the PJSR watcher (lib/pixinsight-mcp/pjsr/pixinsight-mcp-watcher.js) plus the headless WBPP wrapper (lib/pixinsight-mcp/run-wbpp.ps1).

DSH agent 閳光偓閳光偓 pi-tool.mjs 閳光偓閳光偓> ~/.pixinsight-mcp/bridge/commands/{id}.json
                                   閳?
       PixInsight 閳光偓閳光偓 pixinsight-mcp-watcher.js (PJSR poll loop)
                                   閳? reads command, runs PJSR, writes result
                                   閳?
                           ~/.pixinsight-mcp/bridge/results/{id}.json

For AI agents (read me first)

This package is only the director side. Before calling pi-tool, PixInsight must be running with the bundled watcher script loaded, otherwise every call fails with PixInsight process not found. The exact launch / verify / drive / shutdown steps are in AGENTS.md 閳?start there, then read skills/pixinsight-pipeline/SKILL.md for the processing order.

Requirements

Install

A. As a DSH plugin (recommended)

powershell -ExecutionPolicy Bypass -File scripts\install-as-plugin.ps1 -Profile desktop

It backs up the profile package.json, copies the package into the profile node_modules, deploys the bridge toolkit to %DSH_HOME%\pixinsight-mcp, and appends the package to dsh.profile.bundles. Then fully restart DSH.

Uninstall: ... -Uninstall.

B. As a plain skill-root install

powershell -ExecutionPolicy Bypass -File scripts\install-into-dsh.ps1

Copies the skill to %DSH_HOME%\skills\pixinsight-pipeline and the toolkit to %DSH_HOME%\pixinsight-mcp. Use one of A / B, not both (otherwise the skill appears twice).

First run

The toolkit lives either at %DSH_HOME%\pixinsight-mcp (installed) or in the source tree at \tools\pixinsight-mcp. Resolve it once instead of guessing:

node "$env:DSH_HOME\pixinsight-mcp\scripts\resolve-toolkit.mjs" --check

If that path is missing, run \tools\pixinsight-mcp\scripts\resolve-toolkit.mjs instead. It prints the resolved toolkit root and per-file checks; every \... below means that root.