参与开发

The current 0.2.9-rc.4 release targets Harness 0.1.7-rc.2 / web with Session V4. It includes the unified plugin, maintained TypeScript sources and generated modules. The GitHub main branch may also carry unfinished 0.3 SillyTavern compatibility work; use tag v0.2.9-rc.4 to reproduce this release and read CHANGELOG for its validation boundaries.

The 0.2.9 release line fixes installation and distribution; rc.4 also repairs request-pressure recovery and first-response timeout handling. Use the official npm package dsh-nexttavern or its Release archive for installation; source rebuilding is a contributor workflow. The third-party market catalog needs a separate update and is not a declaration of supported hosts.

This package carries TypeScript/MTS sources and their generated JavaScript/MJS so contributors can verify the files it ships. Its local mapping is tools/build-map.json; the quality registry and projection map are tools/check-registry.json and tools/check-map.json.

Source and generated files

Generated modules carry a source banner. Legacy CLI forwarding entries load the mapped lib/ implementation, so they do not create another stateful implementation.

Checks in this package

npm ci --prefix build-tools --ignore-scripts --no-audit --no-fund
npm ci --prefix integrations/auth-webserver --ignore-scripts --no-audit --no-fund

# Default: inspect only current Git changes.
npm run check
npm run check -- file src/ui/client.ts
npm run check -- module reader
npm run check -- syntax src/ui/client.ts
npm run check -- types
npm run check -- tests
npm run check -- release
npm run check -- --plan

syntax proves parsing only. types uses the locked strict configuration without writing files. Generated checks reject stale or missing JS/MJS before success. tests selects registered lightweight suites. release explicitly runs the public tree's shippable lightweight tests, generated checks and bundle comparison; it does not perform a maintainer archive/install/Harness flow. Use npm run check -- list to see the public module IDs and aliases, and --plan before a costly command.

npm run build rebuilds lib/client.js. Use npm run build:modules to regenerate mapped modules and legacy forwarding entries after editing TS/MTS. A change that reaches the browser client requires both steps and both affected outputs in the commit; rebuilding the TS modules alone does not update the ./client export. The locked build-tools dependency set includes jsdom; NEXTTAVERN_JSDOM remains an override when a runner must point at another installed copy. Do not modify generated modules to make a check pass.

The public task list includes only shipped inputs and executable prerequisite chains. Tasks requiring private maintenance facilities are omitted; explicitly requesting an unknown task ends nonzero. Candidate creation, maintainer release verification, fixed local Harness runs, deployment, tags and publication happen outside this package. GitHub CI runs affected checks and has no private packaging or release option.

Check records live under artifacts/checks/. --force ignores a matching cached success; resume uses the previous or named record. Failed, interrupted, uncovered and unsupported records are not successful checks.

What package checks cannot cover

This public tree cannot prove a live DeepSeek Harness load, production deployment, target backup, service health, browser behaviour in every host, or publication. Describe the relevant validation and limits in a pull request. Automated review comments are advice and do not replace a passing command.

Reporting

Bugs and install problems should distinguish the current 0.2.9 release line (0.1.7-rc.2) from the unfinished 0.3 development work, and include the operating system and install method (Release tarball, one-click installer or npm).