# Recheck

[![CI](https://github.com/InInNHD/dsh-recheck/actions/workflows/ci.yml/badge.svg)](https://github.com/InInNHD/dsh-recheck/actions/workflows/ci.yml)

[简体中文](README.md) · [Releases](https://github.com/InInNHD/dsh-recheck/releases) · [Installation](docs/12-installation.md) · [Issues](https://github.com/InInNHD/dsh-recheck/issues)

**Unofficial community project, independently developed and maintained.**

**Trial limitation: the planned three-user, one-week real-project trial is not complete.** On 2026-10-14 the maintainer chose to release 0.1.0 within the existing technical validation scope. The version number does not mean the trial goals were met. See [release acceptance and limitations](docs/20-stable-release-readiness.md) and [trial and backup/recovery guide](docs/21-trial-and-recovery.md) (Chinese, with an English status summary in the acceptance document).

Bind project conclusions to evidence files and revisit them when those files change. Recheck contributes one `recheck` tool and a native DSH right sidebar. Card operations require no additional model calls.

Current release: **0.1.0**, retaining beta.1 assessment filters, stable sorting, explicit selected-card checks, and check/read/choose/save review steps. Eight actions and schema 1 remain compatible. See [acceptance notes](docs/19-beta1-acceptance.md), the [compatibility manifest](compatibility.json), and the [versioned Release](https://github.com/InInNHD/dsh-recheck/releases/tag/v0.1.0). Pin the version or use the npm `latest` channel. This release adds packaged backup/recovery drills and fixes UI acceptance assertions to await rendered results. Publication is gated by Windows/Ubuntu × both exact hosts; Release notes link the matching commit and CI result. Web validation does not imply Desktop validation.

![Recheck beta.1 filters, sorting and selected checks](docs/assets/recheck-beta1-main.png)

![Recheck beta.1 reading confirmation and review](docs/assets/recheck-beta1-demo-3.png)

## Install

The commands below pin 0.1.0 with Harness 0.2.0-rc.2. See [installation notes](docs/12-installation.md) for verified combinations and rollback to beta.1/alpha.6. UI behavior is retained from beta.1; screenshots and the demo remain labeled as real beta.1 captures.

Install the pinned npm version with the matching Web host:

```sh
npx --yes --package=@deepseek-ai/dsh@0.2.0-rc.2 dsh plugin --profile web add dsh-recheck@0.1.0
npx --yes --package=@deepseek-ai/dsh@0.2.0-rc.2 dsh web
```

Download the tgz and SHA-256 checksum from Releases. For Web, run these commands from the download directory with the matching host:

```sh
npx --yes --package=@deepseek-ai/dsh@0.2.0-rc.2 dsh plugin --profile web add ./dsh-recheck-0.1.0.tgz
npx --yes --package=@deepseek-ai/dsh@0.2.0-rc.2 dsh web
```

Use `npx.cmd` in Windows PowerShell. Desktop users install into the `desktop` profile through the application's bundled CLI or plugin manager, then restart Desktop. Do not start the Electron desktop profile with a standalone Web CLI. [Full install, backup, removal and rollback instructions](docs/12-installation.md).

The release tgz includes built files. GitHub's automatically generated source ZIP requires a build. This version supports the npm `latest` channel as well as GitHub Release distribution.

## Demo

![beta.1 real UI: file change → check → read → review](docs/assets/recheck-beta1-demo.gif)

The disposable `evidence.txt` changes from `API_VERSION=v1` to `v2`. Check detects the byte change; after reading, explicitly refute the original conclusion and save a note. These are captured UI states, with no model judgment.

Create a conclusion card with 1–8 relative evidence paths. Check the files, change a disposable evidence file and check again. Read the evidence before explicitly choosing supported, refuted or uncertain and entering a review note. Inspect history and export Markdown.

**Unchanged files do not prove a conclusion is true.** Freshness and review assessments are independent. Reviews re-read evidence and reject stale revisions or checks.

Actions: `create/list/get/edit/check/review/archive/export`. Edits, reviews, archive operations and single-card checks use the latest `expectedRevision`. Reviews also reference the latest persisted `checkId`. The host supplies workspace identity, actor, fingerprints and timestamps.

## Data and limits

Data lives in the project's `.dsh/recheck/cards.json`; evidence contents are not stored. Business I/O uses host file-system policies and the sandbox. No business network requests, automatic tests, watchers or semantic judgments. Atomic version-guarded writes preserve existing files on corruption, future schemas and capacity errors. Uninstall preserves project data.

Limits: 100 active / 200 total cards, 20 versions per card, 2 MiB per evidence file, 8 MiB storage. A batch has a 200 unique-file, 64 MiB and 10-second budget; uncovered evidence is unknown. Read-only checks must explicitly use `persist:false` and cannot authorize a persisted review. Files are observed separately, not as a simultaneous project snapshot. Drafts are memory-only. Multiple hosts writing one store, shared network disks and remote file systems are unverified.

## Develop

```sh
git clone https://github.com/InInNHD/dsh-recheck.git
cd dsh-recheck
npm ci
npm run check
npm run test:package
npm pack
```

`check` runs Host/Client type checks, build and 47 real FS/Native/Node PTC, diagnostics and evidence-feedback tests. `test:package` installs the actual tgz, runs tests against that host's SDK, toggles the live plugin 20 times, and verifies uninstall/reinstall, rollback to both beta.1 and alpha.6, upgrade again, unchanged data/history and nine backup/recovery checks. Use `npm run test:package -- --host 0.2.1-alpha.1 --web` for the second host. Test data stays in ignored `.integration`. Desktop tests require `--app` or `RECHECK_DESKTOP_APP`.

The collapsed diagnostics panel reads status on demand. Its copyable summary excludes workspace paths, session identifiers and business content. A permissive session policy does not override filesystem permissions. Host-version support is distinct from platform validation; consult the compatibility manifest.

[Contributing](CONTRIBUTING.md) · [Changelog](CHANGELOG.md) · [Version management](docs/11-version-management.md) · [Historical acceptance](docs/09-implementation-and-acceptance.md)

MIT License. Learning documents are historical examples, not current project configuration.