dsh-bid-qual-check
Manifest valid?????????(????????????????,?????,???????)
dsh-bid-qual-check
Boundary: this plugin checks a 投标人资格条件核对表 for the closed loop a checklist can be held to — that every condition records its requirement and the bidder's actual position, that evidence is attached, that verdicts come from your vocabulary, that a pass/fail item records all three, that the table names its project and bidder, that numbers are unique, and that no placeholder survives. It does not decide whether a bidder is qualified, whether qualification fails, or whether a bid should be rejected. That is the qualification committee's call, made against the evidence originals and the tender document's conditions.
⚠️ Read this before trusting a citation in the report
Every
excerptin this plugin's rule pack says, in so many words, that the clause text was not obtained. The regime lives in 《中华人民共和国招标投标法》(notably its articles on qualification conditions and on bidders' qualifications), 《招标投标法实施条例》, and each tender document's own qualification conditions. The verification pass could not retrieve verbatim clause text, so rather than paraphrase a quotation the pack states the gap in theexcerptfield itself and puts the honest reasoning innote. Every rule is thereforewarnorinfo, and a test asserts that no rule claims a quotation it does not have. When the texts are in hand, two things must be done: replace eachexcerptwith the real clause, and raisekindtodirect.Two judgements are yours, not the plugin's. Which conditions count as pass/fail items depends entirely on the tender document, so
BQ-005reads the checklist's own 是否否决项 column rather than any built-in list, and the values that mark an item as pass/fail are configurable. And the verdict vocabulary ships empty — with nothing configured,BQ-004reports itself inskipped. A finding never says a bid is invalid; it says a cell is empty or a value is not in your vocabulary.
Compatibility
| Surface | Status |
|---|---|
| Harness | Peer range >=0.1.2-rc.1 <0.2.0 || >=0.2.0-0 <0.3.0 — verified to accept both 0.2.0-rc.2 and 0.2.1-alpha.1. engines.dsh is deliberately not declared: it has no reader and cannot reject a host |
| Node | `^22.19.0 |
| Platforms | All (plain ESM; no native code, no network, no model call) |
| Tool mode | Works in native, ptc and both; for several bidders use ptc |
What it does
Registers the bid_qual_check tool. It reads one qualification register — the package header plus one row per
condition — applies a versioned rule pack, and returns a report.
| Rule | Check | Severity | Basis kind |
|---|---|---|---|
BQ-001 | every condition records its requirement | warn | principle |
BQ-002 | every condition records the bidder's actual position | warn | principle |
BQ-003 | every condition attaches evidence | warn | principle |
BQ-004 | the verdict comes from your vocabulary (off by default) | info | local |
BQ-005 | a pass/fail item records position, evidence and verdict | warn | principle |
BQ-006 | the table names its project and bidder | warn | principle |
BQ-007 | condition numbers are unique | warn | principle |
BQ-008 | the requirement column holds no unreplaced placeholder | warn | principle |
Install
pnpm pack
dsh plugin --profile <name> add ./dsh-bid-qual-check-0.1.0.tgz
dsh --profile <name> --dump-config | grep 'dsh-bid-qual-check'
Configuration
| Key | Type | Default | Description |
|---|---|---|---|
rulesFile | string | rules/bid-qual-check.yaml | Rule-pack path, relative to the package root |
disabledRules | string[] | [] | Rule ids to stop running; each appears in skipped |
onlyRules | string[] | [] | Run only these rule ids; empty runs every rule |
skipNotes | string | "" | Note appended to every skipped reason |
timeoutMs | number | 120000 | Cooperative tool timeout budget |
Rule-level parameters worth knowing:
BQ-004values— your verdict vocabulary, e.g.[符合, 不符合, 需澄清]. Empty means no check.BQ-005conditionValues— the values in your 是否否决项 column that mark an item as pass/fail, by default[是, Y, yes, true, 否决项, √].BQ-008terms— the placeholders to look for.
Material format
The tool accepts JSON or YAML:
project: 某某工程施工招标
tenderNo: ZB-2026-018
bidder: 某某建设有限公司
rows:
- { 序号: '1', 资格条件: 施工资质等级, 要求内容: 建筑工程施工总承包二级及以上,
投标人情况: 持有建筑工程施工总承包二级资质,证书在有效期内,
证明材料: 资质证书复印件,资格文件第 12 页, 核对结论: 符合, 是否否决项: 是, 核对人: 李工 }
Column names are matched case-insensitively and ignoring spaces, underscores and hyphens; the register's own column names are kept, so a finding names the column it read.
Rule sources
Rule data lives in rules/bid-qual-check.yaml. The pack's header states the citation gap in full, and each
rule's note repeats the part that matters for that rule. The load-time guard that normally enforces "an
excerpt must be a real quotation of at least eight characters" cannot tell a quotation from a description —
so this pack leans on the header, the per-rule notes and a test that asserts every excerpt admits the gap.
Troubleshooting
BQ-004orBQ-005reports itself as skipped. The verdict vocabulary is empty, or no row is marked as a pass/fail item. Both depend on your project, and the plugin will not guess them.BQ-002fires on a condition I consider self-evident. A blank actual-position cell means "not checked", which is the one thing a qualification register must never be. Record the position, even if it is obvious.BQ-005fires on a pass/fail item missing evidence. That is the check: a pass/fail item without all three records cannot be defended after the fact.BQ-008fires on a requirement I copied verbatim. The wordXXXor待填really is in the cell. Narrowterms, or fix the register.- The plugin installs but the tool never appears. Check that
mainresolves tolib/index.mjsand thatpnpm run buildproduced it; a wrongmainmakes the loader skip the entry silently. dsh plugin addrefuses the package as incompatible. The peer range covers0.1.xand0.2.x; if your runtime sits outside it, grant an explicit exemption:dsh plugin --profile <name> allow-version dsh-bid-qual-check@0.1.0 --dsh-version <runtime> --accept-riskcheckreportsmanifest-peersas failed. The static checker compares against a hard-coded peer range that predates the 0.2 line. The runtime enforces peer compatibility at install time, so the declared range is the correct one; this is a known upstream issue indsh-plugin-dev.
Development
pnpm install
pnpm run typecheck # tsc --noEmit
pnpm test # vitest, the shared table-plugin suite plus paired fixtures
pnpm run build # tsdown -> lib/index.mjs + lib/index.d.mts
node ../scripts/sync-shared.mjs dsh-bid-qual-check # refresh src/shared from ../_shared
The plugin is data-only: src/model.ts declares the table shape, the shared kit supplies the reader and
the check engine, and the rule pack declares every check.
License
Apache License 2.0 © 2026 dsh-bid-qual-check contributors.
Comments
Loading…
Similar plugins
by PerryLink
??????????????(????????????,?????,???????)
★ 0
NOASSERTION
TypeScript
Oct 9, 2026
dsh plugin --profile web add dsh-archive-checkby PerryLink
????????(?????????????????????,?????,???????)
★ 0
NOASSERTION
TypeScript
Oct 9, 2026
dsh plugin --profile web add dsh-permit-report-checkby PerryLink
???????????(??????????????????????,?????,???????)
★ 0
TypeScript
Oct 8, 2026
dsh plugin --profile web add dsh-lawcite-adapterby PerryLink
PPAP ?????????(???? PPAP ??????????????????,?????,???????)
★ 0
NOASSERTION
TypeScript
Oct 8, 2026
dsh plugin --profile web add dsh-ppap-checkby HERO476
DSH ????(??????):????/????????,???????????????????Selection follow-up for DeepSeek Harness with an independent side-card answerer.
★ 1
MIT
JavaScript
Oct 8, 2026
dsh plugin --profile web add dsh-sidecard-askby ESxyzbil
DSH ??????:?????? + ??????? + ????
★ 1
MIT
JavaScript
Aug 22, 2026
dsh plugin --profile web add dsh-official-document-mode