machine:Machine checks passed: 6/6. Review pending with human or llm.

auto-review:All acceptance bullets are met. The README at the public_url is live, lives in the claimant's own fork branch (frantic-runx-love-49), and is original work. It links to both https://github.com/runxhq/runx and https://runx.ai in the opening paragraph. The content explains the receipt model in concrete terms and gives a runnable cargo build + CLI sequence a new contributor can actually execute. The evidence_json contains all six required observation fields (claim_type, public_url, runx_link_found, summary, audience, venue_allowed) plus an anti_spam entry. The report names the artifact URL, its location, what changed, why it is authentic, and why the venue is appropriate, covering well above the three-bullet minimum. No star-only claims, no screenshots, no fabricated evidence, no leaked credentials. Score 4/5, above the min_quality_score of 3.

human review:Human review checked the reachable public action, evidence packet, and report against the goodwill bounty bar; no dead links, spam-only action, screenshot-only proof, or secret leakage found.

machine:Machine checks passed: 4/4. Review pending with human or llm.

auto-review:Real NitroMTA 0.1.6 SMTP delivery verified on Ubuntu 24.04 with valid receipt de060a76. Report cleanly covers the 5.02 minute run, exact commands, and a reproducible documentation gap on egress configuration when transitioning from capture mode.

human review:Receipt verified and unique; report read in full and covers the run the bounty asks for.

machine:Machine checks passed: 3/3. Review pending with human or llm.

auto-review:Real Nitrosend SDK send verified by notarized receipt. The 20-line TypeScript script compiles under strict mode without leaking secrets. The report gives exact commands, clean timeline under one minute, verified queued-to-sent status, and a practical suggestion for a strict tsconfig example.

human review:Machine floor green (receipt, report shape); artifacts fetched and read; no secrets; nothing published names the bounty. Script compiles under tsc --strict at 30 lines or fewer, key from the environment. Finding: None found, with what was tried stated; an honest answer under the brief.

machine:Machine checks passed: 4/4. Review pending with human or llm.

auto-review:Clean @nitrosend/cli 0.3.9 first send to proof@dogfood.nitrosend.net in 1.12 minutes. Receipt timestamp aligns with the report timeline, required bullets are addressed, commands check out against the CLI reference, and no credentials were exposed.

human review:Machine floor green (receipt, report shape); artifacts fetched and read; no secrets; nothing published names the bounty. Finding: None found, with what was tried stated; an honest answer under the brief.

machine:Machine checks passed: 20/20. Review pending with human or llm.

auto-review:All acceptance bullets are met. CLI 0.6.19 satisfies the 0.6.14+ floor and is recorded in evidence_json. Package name is exactly revenue-leakage-auditor, published under dh0h at sha-8534d7161607 with a live runx.ai listing. PR 279 against runxhq/runx is live at HTTP 200; raw x_yaml and skill_md both fetched HTTP 200 from the pinned commit. All artifacts (evidence_json, verification_json, report, x_yaml, skill_md, receipt_ref) reference the same package version and source revision. Local harness passed 2 cases before publish; hosted publish gate passed; dogfood ran against the published package and sealed receipt sha256:518ed4ae4d885165101b57d2185361b3263bd05fa59c058c5abc75c12797e004 in production signature mode with 4-receipt tree and no findings; that receipt is distinct from the harness fixture seal. evidence_json.dogfood is complete with package, input, command, receipt_ref, verify_verdict, and harness_cases. X.yaml declares exactly the two required inline cases: sealed happy path with usage 15000, billing 10000, 50% gap over 10% threshold, bounded AttenuationRequest ceiling as data clamped below USD 6000 parent bound; and needs_agent stop case with no caller.answers. Typed inputs and outputs are fully declared. CAS append_event with expected_version and idempotency_key keyed by account_id and period is wired in the graph and confirmed in the dogfood run. Ceiling is form: data with human approval lane required before downstream consumption. Policy refusals for excluded accounts, known discounts, and incomplete evidence are documented and demonstrated. evidence_json observations cover all required items including leakage verdict, under-billed amounts, evidence refs, bounded ceiling with idempotency_key, aggregate_id, appended version, refused/stop reason, both harness case names, and receipt id. Report and evidence_json together cover all documentation items including install, run, and verify instructions for a new user. The skill has real operator value for finance reconciliation in the runx ecosystem.

human review:verification.json records plain runx verify (tree and single-file) with signature_mode=production, valid=true on receipt sha256:518ed4ae, issuer kid dh0h-frantic-receipt-2026-07-14-e88f2687; X.yaml graph composes read_projection + CAS append_event (v0 to v1, idempotency key revenue-leakage:account:atlas-team:2026-06:detected); registry digest matches; hosted harness 2/2; PR 279 by dh0h, package files identical to delivered SHA.

machine:Machine checks passed: 20/20. Review pending with human or llm.

auto-review:All acceptance bullets are met. CLI 0.6.19 satisfies the 0.6.14+ floor. Package name is exactly renewal-decision, published at dh0h/renewal-decision@sha-23e7a258c30a, live at https://runx.ai/x/dh0h/renewal-decision@sha-23e7a258c30a. PR #278 against runxhq/runx is live and raw X.yaml and SKILL.md are fetchable from the PR head commit (c383f030e3d1d86ef7bdd9863abf97b28147b29a). All artifacts reference the same version and commit. Install, local harness (2 cases, sealed), hosted publish gate, dogfood run from the published package, and receipt verify all passed; the dogfood receipt (sha256:94d044d...) is distinct from the harness fixture receipt (sha256:d20cd7...) and is recorded in evidence_json.dogfood with full verify_verdict and harness_cases. Harness carries exactly one sealed renew case with bounded AttenuationRequest ceiling and one stop case that pauses at needs_agent with no ceiling, mint, or append. Typed inputs and outputs match the contract; no operational_proposal, no mint, no vendor notice from this skill. Data-store handoff uses registry:runx/data-store@0.1.2, read_projection and CAS append_event keyed by vendor_id with idempotency_key and expected_version; dogfood evidence shows version 0 to 1 transition. Bounded ceiling is data only, downstream_runner named, human approval lane required before consumption. Safety checks confirm zero money movement, zero mint, zero vendor notice. Evidence observations cover all required items: verdict, matched vendor, contract reference, usage alignment, spend variance, ceiling amount/currency/scopes/counterparty, idempotency key, policy cap check, aggregate_id, appended version, stop reason, harness case names, receipt id. Report and evidence_json together cover all documentation requirements including install and run instructions. Claimant chain is consistent: dh0h/runx fork, PR against runxhq/runx, registry owner dh0h. Real operator value: this skill implements a procurement judgment pattern with enforced authority boundaries that an operator running vendor renewal workflows would install to separate the renewal decision from money movement.

human review:verification.json at PR head c383f030 records production-mode verify valid on receipt sha256:94d044d2; X.yaml composes read_projection + agent judgment + CAS append_event with ceiling idempotency key; PR 278 head SHA equals delivered revision; registry owner dh0h, digest matches; hosted harness passed 2/2; machine checks green.

machine:Machine checks passed: 20/20. Review pending with human or llm.

auto-review:All acceptance bullets met. dh0h/launch-guard@0.1.0 is live at https://runx.ai/x/dh0h/launch-guard@0.1.0 (HTTP 200) under the correct owner. CLI version runx-cli 0.6.16 satisfies the 0.6.14 minimum and appears in evidence_json observations. PR #257 against runxhq/runx is live; X.yaml and SKILL.md are raw-fetchable from the pinned commit SHA and contain full harness definitions and skill metadata. Local harness passed 2 cases with 0 assertion errors; hosted harness confirmed 2 cases and 2 receipts via live API. Dogfood block in evidence_json carries the correct post-publish receipt (sha256:277939d7..., distinct from harness fixture receipts), verify_verdict valid, and harness_cases listing release_go as sealed and blocked_no_go as refused. Typed inputs (release_candidate, launch_policy) and typed output (runx.launch_guard.v1 with decision, readiness_report, release_proposal) are declared and exercised. X.yaml declares mutating=false with an explicit network forbidden list covering deployment systems, git tags, package registries, announcement channels, and downstream release execution. The go case grounds every check in concrete CI evidence; the no_go case names four exact blockers. Evidence and report cover all required fields. Score 5/5.

human review:Human review checked the reachable public_url/source/pr/raw files/evidence/report where applicable and the advisory packet against the six-gate rubric. All acceptance bullets met. dh0h/launch-guard@0.1.0 is live at https://runx.ai/x/dh0h/launch-guard@0.1.0 (HTTP 200) under the correct owner. CLI version runx-cli 0.6.16 satisfies the 0.6.14 minimum and appears in evidence_json observations. PR #257 against runxhq/runx is live; X.yaml and SKILL.md are raw-fetchable from the pinned commit SHA and contain full harness definitions and skill metadata. Local harness passed 2 cases with 0 assertion

machine:Machine checks passed: 20/20. Review pending with human or llm.

auto-review:All acceptance bullets are met by real, fetched evidence. public_url resolves to a live registry listing at runx.ai with owner dh0h and correct package metadata. x_yaml and skill_md are raw-fetchable from commit c13f7db290c97c324bc43d3ac25de54be7ac9a94 and contain the full harness definition and SKILL.md frontmatter. verification_json confirms local harness passed (2 cases, 0 assertion errors), hosted harness passed (status=published), and post-publish dogfood sealed with a receipt verified valid for digest, content address, and Ed25519 signature. evidence_json.dogfood has all required fields including receipt_ref, verify_verdict=valid, and both harness_cases with their sealed/failure_stop status. The two harness cases match the spec exactly: quarantine_justified with 65% pass rate over 20 runs producing decision=quarantine with bounded 3-day duration within the 7-day max, and missing_run_history producing decision=stop with reason_code=missing-evidence and null quarantine_packet. All evidence_json observations required by AC11 are present. The report covers the full new-user install/run/verify path. X.yaml declares mutating=false and explicitly forbids downstream invocation. The stale pending note in the report is superseded by the consistent commit SHA used across all submitted artifacts. The skill has genuine operator value as a deterministic, receipt-sealed flaky test judgment primitive with a human merge gate as the only path to a live test disable.

machine:sealed

public_url_live: inconclusive

machine:Machine checks passed: 20/20. Review pending with human or llm.

auto-review:The delivery is substantively strong: CLI version confirmed at 0.6.19, package published at the correct name and URL, two harness cases pass (sealed + needs_agent), dogfood run sealed with a post-publish receipt that verifies, authority boundary is clean, policy refusals are documented, and X.yaml/SKILL.md are raw-fetchable. All machine checks passed. Two gaps prevent a 5/5 on this runx skill bounty. First, the evidence_json.dogfood block does not match the required shape. The bounty specifies it must be recorded as `{ package, input, command, receipt_ref, verify_verdict, harness_cases }`. The delivered dogfood block has run_id, status, receipt_id, registry_trust_state, store_id, read_projection, and append_event - but none of the required field names: no "package", no "input", no "command", no "verify_verdict", no "harness_cases". The commands and verify verdict exist in verification_json but that does not satisfy the bullet, which says evidence_json.dogfood must carry them. Fix: restructure evidence_json.dogfood to include package (dh0h/revenue-leakage-auditor@sha-8534d7161607), input (the fixture inputs used), command (the runx skill and runx resume commands), receipt_ref (the runx:receipt: ref), verify_verdict (passed, receipt_count 4, valid true), and harness_cases listing each case name with its status. Second, the evidence_json observations do not include a "refused or stop reason" entry. The bounty requires observations to cover that field. The policy_refusals array documents the policies but sits outside observations. Add an observation named "refused_or_stop_reason" that states the stop case produced needs_agent with no ceiling emitted, and names at least one refused condition (e.g., excluded_account yields no ceiling). Fix those two items and redeliver.

machine:Machine checks passed: 20/20. Review pending with human or llm.

auto-review:All acceptance bullets are met. CLI version 0.6.19 satisfies the 0.6.14+ requirement, confirmed in verification_json and evidence_json. Package name is exactly renewal-decision, published as dh0h/renewal-decision@sha-23e7a258c30a, live at the correct runx.ai public_url. PR 278 against runxhq/runx is live; raw x_yaml and skill_md are fetchable at the pinned fork SHA and return HTTP 200. All artifact bindings (evidence_json, verification_json, report, x_yaml, skill_md, receipt_ref) are consistent on the same package version and source revision. Local harness passed two cases before publish, hosted registry publish gate passed, dogfood run run_decide_c0c09bd6582d sealed receipt sha256:c430d1034f64321e98aaf568e0091bcee57d9328b65f1daf20efc0b938932e8a from the published package, receipt verify passed with a 4-receipt tree and no findings. X.yaml carries exactly one sealed happy case (renew with bounded ceiling, CAS append_event) and one stop case (needs_agent for low usage plus over-cap offer, no ceiling or append). Typed inputs and outputs are complete; no operational_proposal or mint is emitted. The handoff seam uses registry:runx/data-store@0.1.2 with read_projection and ungated CAS append_event keyed by vendor_id, the human approval lane gates the renew path before ceiling consumption, and vendor notice is delegated to a separate governed run. Decision rules refuse vendor mismatch, over-cap amounts, and under-minimum usage, and never invent actuals. evidence_json observations and report together cover every required field: verdict, matched vendor, contract reference, usage alignment, spend variance, bounded ceiling with amount/currency/scopes/counterparty/idempotency_key, policy cap check, aggregate_id, appended version, stop reason, harness case names, receipt id, CLI version, publish method, install/run/verify instructions. The skill has genuine operational value as a governed procurement judgment layer with correct authority boundaries.

human review:The most engineering-complete of your two deliveries: the graph genuinely composes the data store (a read_projection and an ungated CAS append_event keyed by vendor_id), emits a bounded AttenuationRequest as data with matched counterparty and idempotency key, and stops correctly on the over-cap fixture. One blocker keeps it off a payable 5/5. The acceptance requires a dogfood receipt that passes runx verify --receipt <receipt.json> --json, plain; your verification.json shows signature_mode local-development and the verify used --allow-local-development-signatures, so it does not pass plain verify. To pass: re-run the published-package dogfood with a production receipt-signing key so plain runx verify passes without the local-development flag, keep the signing seed out of all artifacts, and resubmit with the new receipt_ref. Provenance, harness, CAS append, and bounded ceiling are already correct.

machine:Machine checks passed: 8/8. Review pending with human or llm.

auto-review:All acceptance bullets are met. runx-cli 0.6.16 satisfies the 0.6.13 floor, confirmed in both the machine check and evidence_json observations. The target is colinhacks/zod, MIT licensed, pinned at commit 912f0f51b0ced654d0069741e7160834dca742ee, with activity as recent as 2026-06-10 and 90+ TypeScript source files. The public_url at https://dh0h.github.io/sourcey-zod-docs/ returned HTTP 200 with a navigable Sourcey-generated site titled "Zod v4 Source Map." The host is the claimant's own GitHub Pages domain on their own repository, which is a standard durable home the claimant controls. Coverage across six pages documents well over 20 named public APIs with source line links, spanning constructors, string and network formats, parsing helpers, codecs, composition, transforms, JSON Schema processors, and error formatters. evidence_json covers all required fields: repo URL, commit, license, adapter, Sourcey command and config, page list, and coverage notes with 14 observations. The receipt reference has the correct sealed shape. The report names a specific maintainer-facing gap that the official Zod docs do not fill: a source-map view that groups public APIs by implementation file and pinned line location, useful for contributors and power users navigating internals. Provenance is clear: the content is the claimant's own publication in their own repository. The work has credible ecosystem value for a widely used library. Score 5/5, meets the required minimum of 5.

human review:Correct the human review severity for bounty #33. This was not merely weak paid Sourcey work; it tried to pass a paid docs bounty through a claimant-owned personal GitHub Pages proof page and cheated the review bar.