coldpass

Per-setup public labels: Linux / Haiku: Didn’t work

Static status badge · SVG · read-only JSON. Embed with ![Coldpass status](https://coldpass.dev/badge/T-Auto--dsh-ops.svg).

dshdsh-plugindsh-plugins

Didn’t work

Only older checks are saved; no current product test.

Answers apply to each recorded setup, revision and operation. Earlier observations remain in Run details.

Tested on Linux
PlatformHaikuLuna
Linuxno

Linux / Haiku 5.5: no · Oct 18, 2026 · 4b51b6333213 · claude-code / 2.1.300 (Claude Code)
Recorded operation: Not exercised: plugin install/enable inside a DSH host. Prerequisite missing: an initialized DSH host application/profile (<host-path>) and the official DSH CLI, neither available in this guest.…

Issue
yes, not fixed yet
Our test was blocked; no repo verdict.

Safety: no observations were recorded for the selected revision. Functional results do not establish a safety result.

Repair history and test corrections
Current diagnosis: unknown · prerequisite

No initialized DSH host profile and no DSH CLI in the guest; the plugin is a DSH plugin, not a standalone MCP server, so there is no stdio/HTTP endpoint to start and list tools.

Recorded action: Wait for the documented external prerequisite; keep partial grades.

Repair record fix-fd36c6d16a840be302c8 · current status JSON. Original run outcomes remain unchanged.

Failed run: T-Auto/dsh-ops · Oct 18, 2026 · Recorded operation failed.

Repair development: T-Auto/dsh-ops · Oct 18, 2026 · Repair work (development) · not an initial-trial result.

Run details

Haiku 5.5

Native agent · Recorded operation failed

Operation / attempted scope Not exercised: plugin install/enable inside a DSH host. Prerequisite missing: an initialized DSH host application/profile (<host-path>) and the official DSH CLI, neither available in this guest. limited success: Node 22.23.3 and npm dependencies installed; 'dsh-ops ladder' ran (exit 0), but it only renders a static prompt view and spawns nothing.

Agent-reported scope: Attempted README install (npx --yes dsh-ops@latest install --profile web) and local CLI install; the product's useful operation (installing the plugin into a DSH profile) could not run.

Run details
run
T-Auto--dsh-ops-claude-haiku-5-5-1792338302368586917
date
Oct 18, 2026
time to working
not recorded
product hosting / execution
Not recorded
recorded operation scope
Not exercised: plugin install/enable inside a DSH host. Prerequisite missing: an initialized DSH host application/profile (<host-path>) and the official DSH CLI, neither available in this guest. limited success: Node 22.23.3 and npm dependencies installed; 'dsh-ops ladder' ran (exit 0), but it only renders a static prompt view and spawns nothing.
model
claude-haiku-5-5
agent / version
claude-code / 2.1.300 (Claude Code)
platform
linux
reported cost
$0.011394
Recorded source
https://github.com/T-Auto/dsh-ops
Tool transport
mcp-assigned-vm
Test version
readme-03aea4c41d53955e3723c330e9927d2a9df627f6642624cc0078a97c73a53c8a
revision
4b51b6333213c376c8b7c173c12f35b408fdec2d
Current diagnosis: unknown · prerequisite

No initialized DSH host profile and no DSH CLI in the guest; the plugin is a DSH plugin, not a standalone MCP server, so there is no stdio/HTTP endpoint to start and list tools.

Recorded action: Wait for the documented external prerequisite; keep partial grades.

Repair record fix-fd36c6d16a840be302c8 · current status JSON. Original run outcomes remain unchanged.

Failed run: T-Auto/dsh-ops · Oct 18, 2026 · Recorded operation failed.

Repair development: T-Auto/dsh-ops · Oct 18, 2026 · Repair work (development) · not an initial-trial result.

Fix: fix-fd36c6d16a840be302c8.

Recorded blocker / warning

Step: node bin/dsh-ops.mjs install --profile web (docs/usage.md 'One-command npm installation')

No initialized DSH host profile and no DSH CLI in the guest; the plugin is a DSH plugin, not a standalone MCP server, so there is no stdio/HTTP endpoint to start and list tools.

Suggested next step (agent-reported): Provide a DSH host (desktop/web/dsh-tui) CLI in the guest and initialize the target profile (e.g. <host-path>), then re-run 'node bin/dsh-ops.mjs install --profile web' and probe with 'node bin/dsh-ops.mjs status --profile web'. Alternatively a host-run test that initializes the profile is needed before any product operation can be exercised.

What the agent did

Attempted README install (npx --yes dsh-ops@latest install --profile web) and local CLI install; the product's useful operation (installing the plugin into a DSH profile) could not run.

cd <host-path> && git log -1 --format=%H 2>/dev/null; ls -la; cat README* 2>/dev/null | head -300
cd <host-path> && ls -la .github/workflows 2>/dev/null; echo "CDP=$CDP_URL $<env-var>"; which python3 node npm uv pip3 2>&1
cd <host-path> && sed -n 1,200p docs/usage.md | head -150; echo ---; which dsh node npm npx 2>&1; echo ---; grep -n "run:" .github/workflows/ci.yml | head -40; echo ---; python3 -c "import json;d=json.load(open('package.json'));print(d.get('scripts'));print(d.get('engines'))"
export DEBIAN_FRONTEND=noninteractive; (sudo apt-get update -qq && sudo apt-get install -y -qq nodejs npm) >/tmp/apt.log 2>&1; echo rc=$?; node -v 2>&1; npm -v 2>&1; apt-cache policy nodejs | head -3; env | grep -i proxy | sed 's/=.*@/=***@/'
export NODE_USE_ENV_PROXY=1; mkdir -p <host-path> && cd <host-path> && npm install --prefix <host-path> node@22 >/tmp/node22.log 2>&1; echo rc=$?; tail -3 /tmp/node22.log; N=<host-path>; $N -v 2>&1; echo ---; (npm view dsh-ops version; npm view dsh version; npm view @deepseek/dsh version) 2>&1 | head; which dsh 2>&1
export PATH=<host-path> NODE_USE_ENV_PROXY=1; cd <host-path> && node -v && npm -v && npm ci --ignore-scripts --registry=https://registry.npmjs.org >/tmp/npmci.log 2>&1; echo ci_rc=$?; tail -3 /tmp/npmci.log; echo ---; timeout 120 npx --yes dsh-ops@latest install --profile web 2>&1 | tail -15; echo rc=$?; echo ---; which dsh; ls <host-path> 2>&1
cd <host-path> && python3 -c "import json;d=json.load(open('package.json'));print(d.get('os'),d.get('cpu'),d.get('bin'),d.get('version'))"; export PATH=<host-path>; node bin/dsh-ops.mjs --help 2>&1 | head -30; echo ---; wc -l <host-path>; grep -n "kind\|validate" <host-path> | head -60
export PATH=<host-path> NODE_USE_ENV_PROXY=1; cd <host-path> && timeout 120 node bin/dsh-ops.mjs install --profile web 2>&1 | tail -12; echo "install_rc=${PIPESTATUS[0]}"; echo ---; timeout 60 node bin/dsh-ops.mjs ladder 2>&1 | tail -20; echo "ladder_rc=${PIPESTATUS[0]}"; echo ---; timeout 60 node bin/dsh-ops.mjs status --profile web 2>&1 | tail -5; echo "status_rc=${PIPESTATUS[0]}"
cd <host-path> && mkdir -p .coldpass && cat > .coldpass/probe.json <<'EOF'
{"checks":[]}
EOF
cat > .coldpass/report.json <<'EOF'
{"outcome":"blocked","operation":"Attempted README install (npx --yes dsh-ops@latest install --profile web) and local CLI install; the product's useful operation (installing the plugin into a DSH profile) could not run.","operation_scope":"Not exercised: plugin install/enable inside a DSH host. Prerequisite missing: an initialized DSH host application/profile (<host-path>) and the official DSH CLI, neither available in this guest. Partial success: Node 22.23.3 and npm dependencies installed; 'dsh-ops ladder' ran (exit 0), but it only renders a static prompt view and spawns nothing.","steps":["apt-get install nodejs npm (Ubuntu gave Node 18.19.1, below required ^22.19)","npm install --prefix <host-path> node@22 (Node v22.23.3)","npm ci --ignore-scripts --registry=https://registry.npmjs.org in <host-path> (ok, 0 vulnerabilities)","node bin/dsh-ops.mjs ladder (exit 0, renders prompt ladder, nothing spawned)"],"deviations":["README 'npx --yes dsh-ops@latest install --profile web' failed: published [email protected] declares os win32 only (EBADPLATFORM on linux x64). Local checkout package.json (0.3.1) allows linux, so ran 'node bin/dsh-ops.mjs install --profile web' instead.","Local 'node bin/dsh-ops.mjs install --profile web' failed: 'Initialize the target DSH application/profile first: <host-path>' (exit 1). The DSH host CLI is not present in the VM (no 'dsh' on PATH).","Local 'node bin/dsh-ops.mjs status --profile web' failed with the same profile-initialization error (exit 1).","Ubuntu apt Node 18 is below the required ^22.19; installed Node 22 via npm package 'node@22' instead of apt."],"stuck_step":"node bin/dsh-ops.mjs install --profile web (docs/usage.md 'One-command npm installation')","main_blocker":"No initialized DSH host profile and no DSH CLI in the guest; the plugin is a DSH plugin, not a standalone MCP server, so there is no stdio/HTTP endpoint to start and list tools.","suggested_fix":"Provide a DSH host (desktop/web/dsh-tui) CLI in the guest and initialize the target profile (e.g. <host-path>), then re-run 'node bin/dsh-ops.mjs install --profile web' and probe with 'node bin/dsh-ops.mjs status --profile web'. Alternatively a host-run test that initializes the profile is needed before any product operation can be exercised."}
EOF
<env-var>=<host-path> python3 -I <host-path> --validate; echo rc=$?
Repair work and diagnoses (1)

Haiku 5.5

Native agent · Repair work (development) · not an initial-trial result

Operation / attempted scope <host-path> scripts/tools-trial.mjs

Agent-reported scope: Documented tools trial (docs/verify-locally.md, 'The tools trial'): `DSH_HOME=<tmp> node scripts/tools-trial.mjs` boots the plugin host harness, mounts the plugin and calls published tools against real files. Result: 4 attempted, 4 ok, 0 failed, 8 skipped (no trial scenario yet); writes tools-trial-report.md.

Run details
run
T-Auto--dsh-ops-claude-haiku-5-5-1792338970307397342
date
Oct 18, 2026
time to working
not recorded
product hosting / execution
Local command in the guest
recorded operation scope
product operation
model
claude-haiku-5-5
agent / version
claude-code / 2.1.300 (Claude Code)
platform
linux
reported cost
$0.018604
Recorded source
https://github.com/T-Auto/dsh-ops
Tool transport
mcp-assigned-vm
Test version
readme-3d9de7556813830a65ee8bd519648a62612b029e3dc0b1a8aa69383b1d8a77e3
revision
4b51b6333213c376c8b7c173c12f35b408fdec2d
Current diagnosis: unknown · prerequisite

No initialized DSH host profile and no DSH CLI in the guest; the plugin is a DSH plugin, not a standalone MCP server, so there is no stdio/HTTP endpoint to start and list tools.

Recorded action: Wait for the documented external prerequisite; keep partial grades.

Repair record fix-fd36c6d16a840be302c8 · current status JSON. Original run outcomes remain unchanged.

Failed run: T-Auto/dsh-ops · Oct 18, 2026 · Recorded operation failed.

Repair development: T-Auto/dsh-ops · Oct 18, 2026 · Repair work (development) · not an initial-trial result.

Double-checks failed run: T-Auto/dsh-ops · Oct 18, 2026.

Fix: fix-fd36c6d16a840be302c8.

What the agent did

Documented tools trial (docs/verify-locally.md, 'The tools trial'): `DSH_HOME=<tmp> node scripts/tools-trial.mjs` boots the plugin host harness, mounts the plugin and calls published tools against real files. Result: 4 attempted, 4 ok, 0 failed, 8 skipped (no trial scenario yet); writes tools-trial-report.md.

cd <host-path> && git log --oneline -1 2>/dev/null; ls -la; cat README.md 2>/dev/null | head -200; ls -la .coldpass 2>/dev/null; cat .coldpass/report.json 2>/dev/null | head -50
cd <host-path> && ls docs 2>/dev/null; sed -n 1,200p docs/usage.md 2>/dev/null; ls .github/workflows 2>/dev/null; which node npm python3; node -v 2>/dev/null
cd <host-path> && sed -n 1,80p README.en.md | cut -c1-600; echo ----; ls bin; echo ----; node -e 'const p=require("./package.json");console.log(JSON.stringify({scripts:p.scripts,engines:p.engines,bin:p.bin},null,1))' 2>&1 | head -60; echo ----; cat docs/verify-locally.md | head -80
cd <host-path> && sed -n 1,200p bin/dsh-ops.mjs 2>/dev/null | head -120; echo; which dsh; ls <host-path> 2>/dev/null; cat <host-path> 2>/dev/null | head -60
cd <host-path> && cat <host-path> | head -150; echo ----; grep -n "run:" .github/workflows/ci.yml | head -40; echo; cat docs/troubleshooting.md | head -60 | cut -c1-300
sed -n 150,400p <host-path> | grep -n "def \|validate" | head -40; (apt-cache policy nodejs | head -3); (command -v cargo rustc || echo no-cargo); echo $CDP_URL; echo $NODE_USE_ENV_PROXY
(sudo apt-get update -qq && sudo apt-get install -y -qq nodejs npm >/tmp/apt.log 2>&1); echo rc=$?; node -v; npm -v; apt-cache policy nodejs | head -3
cd /tmp && curl -fsSL -m 120 -o node22.tar.xz https://nodejs.org/dist/v22.20.0/node-v22.20.0-linux-x64.tar.xz; echo rc=$?; ls -la node22.tar.xz 2>/dev/null
mkdir -p <host-path> && tar -xJf /tmp/node22.tar.xz -C <host-path> --strip-components=1 && export PATH=<host-path> && node -v && npm -v && cd <host-path> && export NODE_USE_ENV_PROXY=1 && npm ci --ignore-scripts --registry=https://registry.npmjs.org > /tmp/npmci.log 2>&1; echo rc=$?; tail -5 /tmp/npmci.log
cd <host-path> && export PATH=<host-path> && node bin/dsh-ops.mjs install --profile web; echo rc=$?; node bin/dsh-ops.mjs status --profile web; echo rc=$?; node bin/dsh-ops.mjs ladder; echo rc=$?
cd /tmp && curl -fsSL -m 120 https://sh.rustup.rs -o rustup.sh && sh rustup.sh -y --profile minimal --default-toolchain 1.97.1 > /tmp/rustup.log 2>&1; echo rc=$?; tail -3 /tmp/rustup.log; source $HOME/.cargo/env && cargo --version
cd <host-path> && export PATH=<host-path> NODE_USE_ENV_PROXY=1 && timeout 1500 npm run build:ptc > /tmp/buildptc.log 2>&1; echo rc=$?; tail -15 /tmp/buildptc.log
cd <host-path> && export PATH=<host-path> NODE_USE_ENV_PROXY=1 && T=$(mktemp -d) && DSH_HOME=$T timeout 300 node scripts/tools-trial.mjs > /tmp/trial.log 2>&1; echo rc=$?; tail -20 /tmp/trial.log | cut -c1-400; node bin/dsh-ops.mjs ladder --json 2>/dev/null | head -c 800
cd <host-path> && export PATH=<host-path> NODE_USE_ENV_PROXY=1 && rm -rf /tmp/dsh-ops-probe-home && ls -la tools-trial-report.md 2>/dev/null; DSH_HOME=/tmp/dsh-ops-probe-home <host-path> <host-path> > /tmp/probe-run.log 2>&1; echo rc=$?; tail -2 /tmp/probe-run.log; ls -la /tmp/dsh-ops-probe-home 2>/dev/null | head -3; git -C <host-path> status 2>/dev/null | head -2; ls <host-path> 2>/dev/null
cd <host-path> && mkdir -p .coldpass && rm -f tools-trial-report.md && cat > .coldpass/probe.json <<'EOF'
{
  "kind": "cli",
  "argv": ["<host-path>", "scripts/tools-trial.mjs"],
  "cwd": "<host-path>",
  "env": {"DSH_HOME": "/tmp/dsh-ops-probe-home"}
}
EOF
cat > .coldpass/report.json <<'EOF'
{
  "outcome": "working",
  "operation": "Documented tools trial (docs/verify-locally.md, 'The tools trial'): `DSH_HOME=<tmp> node scripts/tools-trial.mjs` boots the plugin host harness, mounts the plugin and calls published tools against real files. Result: 4 attempted, 4 ok, 0 failed, 8 skipped (no trial scenario yet); writes tools-trial-report.md.",
  "operation_scope": "Exercises the native Rust file worker and the file tools (ops_inspect_local_file, ops_grep, ops_glob, ops_replace) through the in-repo host harness. NOT exercised: installation into a real DSH profile (`dsh-ops install --profile web|desktop|tui`), which needs an initialized DSH application profile at <host-path> and the official DSH CLI, neither present in the guest. ops_bash is not published on a bare host, so the bash shell path is not exercised here. The MCP start/list_tools path does not apply: the product is a DSH plugin, not a standalone MCP server.",
  "steps": [
    "Read README.md / README.en.md, docs/usage.md, docs/verify-locally.md",
    "Installed Node.js 22.20.0 (official linux-x64 tarball into <host-path>) because apt nodejs 18.19.1 does not satisfy engines ^22.19 || >=24",
    "NODE_USE_ENV_PROXY=1 npm ci --ignore-scripts --registry=https://registry.npmjs.org",
    "Installed Rust 1.97.1 minimal via rustup (cargo was absent; CI pins 1.97.1)",
    "npm run build:ptc (cargo build --release of native worker, staged to runtime/linux-x64/, closure validated)",
    "DSH_HOME=/tmp/dsh-ops-probe-home node scripts/tools-trial.mjs (probe): 4 ok, 0 failed, 8 skipped"
  ],
  "deviations": [
    "`node bin/dsh-ops.mjs install --profile web` (docs/usage.md 'One-command npm installation') fails with: 'Initialize the target DSH application/profile first: <host-path>' and no DSH CLI is available in the guest. Prerequisite missing (DSH host application), not a repo defect; no source change made. Not retried further because the DSH host cannot be supplied from inside the guest.",
    "Default `node` (apt, v18.19.1) was too old for package.json engines; installed Node 22.20.0 tarball instead.",
    "`cargo` was absent; installed Rust 1.97.1 via rustup (sh.rustup.rs) to run build:ptc.",
    "Running `npx`-based install was replaced by the local `node bin/dsh-ops.mjs` entry point; both reach the same profile-delegation step that fails."
  ],
  "stuck_step": null,
  "main_blocker": null,
  "suggested_fix": "To exercise profile installation, initialize a DSH host profile (web) and provide the official DSH CLI in the guest, then rerun `node bin/dsh-ops.mjs install --profile web --dsh-cli <path>`. Not required for the working tools-trial probe.",
  "fault_owner": "prerequisite"
}
EOF
export PATH=<host-path>; python3 -m json.tool .coldpass/probe.json >/dev/null && python3 -m json.tool .coldpass/report.json >/dev/null && echo json-ok; <env-var>=<host-path> python3 -I <host-path> --validate; echo rc=$?
ls -ld /tmp/dsh-ops-probe-home 2>/dev/null && rm -rf /tmp/dsh-ops-probe-home; ls <host-path> 2>/dev/null; pgrep -fa "dsh-ops-worker|tools-trial" || echo no-leftover-processes