DrugClaw — Drug Discovery Research Agent

No reviewer summary was written for this build.

First TalentDelta packaging at pinned commit 960a6e0e5935 (2026-03-23). Upstream paths deliberately NOT shipped: screenshots — upstream README and demo imagery (about 5.8 MB), regenerable and unnecessary to run the agent. Every other file is byte-identical to the pinned commit, a provenance record is appended to README.md, and the packaging secret scan found only sample placeholder keys (replace-me, test-key, masked fixtures), no live credential.

Review: Decision: APPROVED — drugclaw-drug-discovery-agent v1.0.0 ([internal reference removed]), decided 2026-09-30 19:41:51Z Uploader / notice recipient: [internal reference removed] — the file's only credit (position 0, role 'scouted') and the version's uploader, so the two agree; the address is internal (@talentdelta.ai), which the notice path skips by design, so no external party is mailed. WHAT WAS CHECKED, AND HOW - Bytes: fetched from our own store (scripts/review-lane/blob-fetch.cjs) by the stored object hash, not through the customer download door. sha256 501e6fae6e526bbc0f16f36b872fe8b8339518552c2a56e4fb1b2f9a6e90413a · 5,556,001 B — matches FileVersion.blobId→Blob.contentHash and the uploaded size exactly. - Provenance, verified by fetching the commit rather than trusting the pack: the tree was compared path-by-path and byte-by-byte (git blob sha1, mode + content) against a clean clone of DrugClaw/DrugClaw sitting at the disclosed pin 960a6e0e5935. Result: 359 files identical, 1 differing (README.md), 0 added, 9 not shipped. The pinned clone's HEAD is 960a6e0e5935, matching the pin named in the change note and the README append; zero symlinks ship. - The one differing file is README.md, and the difference is purely additive: upstream's README text is a byte-prefix of the shipped file, whose extra bytes are the appended provenance record (upstream URL, licence, pin, runtime note, and the list of what was not shipped). - Removals are exactly the disclosed set: `screenshots/` — the README and demo imagery (9 files, about 5.8 MB). Every not-shipped path falls inside those categories; zero undisclosed removal. - Licence: Apache-2.0 — DrugClaw (2026). Licence text ships; the terms match the claim. - Taxonomy: 5 skill slugs, all storable leaves: science_specialized/life_sciences/{drug_discovery,genomics_analysis,bioinformatics_databases}, science_specialized/healthcare_clinical/biomedical_literature_search, research_knowledge_productivity/research/deep_research; domains life_science/pharmaceutical_research, life_science/genomics — each verified against the pinned snapshot apps/web/src/lib/taxonomy/oasf-1.1.0.json (tag v1.1.0, commit f510be0d4b58, 513 skills / 201 domains): node exists, category=false, no children. - Secrets: the lane's own packaging reader plus an independent secret-shaped scan over every text member. No live credential. Findings and adjudication: * Reader verdict BLOCKED: 36 blocking, adjudicated in three classes. Six are `/home/drugclaw` in the `Dockerfile` and `docker-compose.yaml` — the container's own user/home path that the Dockerfile creates, not a host leak. One is the README's `cp drugclaw.config.example.yaml drugclaw.config.yaml`: the target is meant to be created by the copy and the example *does* ship (the reader's template-name rule is narrower than the `.example` convention its own SKILL.md §2 requires it to accept). * The remaining 29 are `skills/**/SKILL.md` files pointing at `scripts/`, `references/`, `templates/` or `assets/` paths that do not ship — and none of them exists in the upstream tree at the pinned commit either (checked file by file in the clean clone). They are the vendored skills' own dangling references, not files this packaging removed; zero undisclosed removal was found. * Record-accuracy gap, recorded and not treated as a hold: the summary says 'the README and the full docs set are in English and Chinese'. Only `README_CN.md` (2,555 CJK characters) and `docs/test/blackbox-core-20-cases.md` carry Chinese; the rest of `docs/` is English-only. * Removed README imagery: the README's `<img src="screenshots/…">` references are now broken, and the append states the files were not shipped — matches the disclose-don't-erase rule. * Claims verified: `install.sh` branches on `uname` for macOS and Linux and `install.ps1` covers Windows (the 'macOS, Linux and Windows' claim). Rust sources, `Cargo.toml`, Docker image, MCP bridge examples, GUI and web console all ship. WHAT I COULD NOT CHECK - The live install-test (an unattended run through the download door on a test identity) was not run for this pack; the byte read proves packaging, not that the pack does its job on a stock host. - Delivery: the decision notice goes to an internal address, which the platform skips by design (skipped=internal_recipient) — there is no external recipient to confirm receipt. VERDICT: approved. The bytes are upstream's at the pin, the removals are the disclosed ones, the licence and taxonomy check out, and nothing private, client-owned or live is in it. (2026-09-30)