# Testing dsh-loglens

The plugin is useful only when it can be installed by DeepSeek Harness, expose
the declared tools, and return bounded log results. Use the following checks in
order.

## Package checks

```bash
corepack pnpm install
corepack pnpm run test:plugin
corepack pnpm test
corepack pnpm run build
corepack pnpm run smoke
```

`test:plugin` checks the Host `apply()` entry, the four model-facing tools, and
the client card definition. The full test suite checks parsing, bounded sources,
cursor persistence, grouping, and configuration safety.

## Harness install check

With a local DeepSeek Harness checkout available:

```bash
export DSH_HOME="$PWD/runtime/dsh-loglens-home"
node "$PWD/vendor/deepseek-harness/apps/cli/lib/bin.js" \
  plugin --profile headless add "$PWD"
node "$PWD/vendor/deepseek-harness/apps/cli/lib/bin.js" \
  --profile headless --help
```

The install must complete without a loader error. The plugin contract is then
verified by `test:plugin`: `logs_list`, `logs_read`, `logs_raw`, and
`logs_reset_cursor` must register, and `logs_read` must append a compact
`loglens/snapshot` event without placing raw log lines in the card payload.

For a Web profile, install with `--profile web` and start the Harness Web UI;
the `loglens` Conversation card is the visual proof that the client entry was
loaded separately from the Host entry.