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

auto-review:All 12 acceptance bullets are met. CLI 0.9.1 reported and used throughout. Package name exact: postmortem-maker. Publish flow correct. public_url live on runx.ai, source_url at the delivered commit, no tokens in any artifact. PR runxhq/runx#531 contains X.yaml, SKILL.md, postmortem-maker.mjs, three fixtures, and harness-evidence.json; machine check confirmed head at 99d81a4d. All artifacts reference the same package version and source revision. Local harness 3/3 passed, hosted harness green, clean install confirmed with send-as and web-fetch staged. Dogfood used a real live incident URL (github.com/pgmac-net/incidents/issues/85), web-fetched at run time producing 19 fragments; evidence_json.dogfood block present and correct. Receipt passes runx verify: valid=true, digest valid, content address valid. When publishable, the skill composed send-as and executed message.send with independent message.read readback; delivered comment publicly readable at pull/531#issuecomment-6021345130; stampPublished throws on non-sent status so a fake send cannot pass. Harness covers publishable-executes-publish (sealed, publish executed), unknowns-block-publish (sealed, nothing published), and invented-citation-refuses (sealed, refused, nothing published); citation enforcement is deterministic in finalizePostmortem, not asserted. Typed inputs and output schema correct per X.yaml. All 14 evidence observations present. Report and evidence both cover the full documentation checklist including new-user install/run/verify guide without private context. Code-first audit: buildFragments reads from web-fetch output, not a hand-fed fixture; send-as is the real upstream skill referenced by relative path, not a local lookalike; canonical skill resolution confirmed; no-op paths block publish via conditional graph steps with schema-enforced publish_performed: false and publish_result: null; Boa lookbehind workaround is genuine implementation knowledge confirmed in source. Real value: a real incident URL in, a fragment-cited postmortem published as an actual GitHub comment with provider readback out, in one governed run.

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

auto-review:Real, well-formed GameAnalytics entity with one startup-specific offer. The YAML fields cross-check precisely against the live first-party source at gameanalytics.com/pricing/startup: 3 months free PipelineIQ Pro, then 50% off base price plus $1/1,000 MAU above 2M for 12 months, and 50% off an annual MarketIQ Pro subscription with 10 seats, all matching the source word for word. Eligibility (VC-backed, pre-Series B, SDK integrated), access (form at the first-party URL), lifecycle (active), and source refs are complete and correct with no invented facts. The offer is startup-specific and materially useful, not a generic free tier or coupon. Machine checks 3/3 passed. Path is correctly structured at entities/ga/gameanalytics.yaml. The work clears the bounty floor and the real-world value bar: an established analytics platform used by 100,000+ studios, a genuine VC partner program with named partners, a useful findable entry for the Sourcey directory.

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

auto-review:Prior auto-review rounds scored 2/5 for missing website_url and logo_url, but those artifacts were added to the bounty after this claim was made. The claim-time contract required only pr_url. Under the correct contract, the delivery holds: pr_url resolves at HTTP 200, machine checks passed 4/4 (PR opened by @nicolasesanchez50 on auscaster/stompstart-startup-list, 3 files changed under startups/, repo starred), and the PR is on the correct repo. The review gate (stompstart.com/api/startups/<slug> live with contributor attribution) is explicitly a post-delivery publication event that the human gate verifies at acceptance — not a basis for auto-review rejection. I cannot read the PR diff from the reference page, so startup launch-date eligibility, description originality, and logo dimensions go to the human reviewer. Work is real, contract is met, and the prior rejections applied the wrong standard. Pass to human review.

human review:https://stompstart.com/api/startups/eustella credits auscaster/stompstart-startup-list#2 by @nicolasesanchez50; Stompstart's review checked eligibility and captured the sources.

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

auto-review:PR #1286 adds entities/pl/planetscale.yaml to sourcey/startup-credits. PlanetScale is a real, well-known database platform; planetscale.com/startups is a live, first-party English-language source. The offer is startup-specific (migration assistance and credits, case-by-case basis), not a generic free tier or coupon. All three required artifacts resolve cleanly. Evidence is internally consistent: entity file path matches the shard/slug schema, source_live confirmed, claimant stars the repo. Machine floor is green with no deterministic blockers. Report is honest about offer terms without inventing fixed amounts. Delivery meets the github_contribution_v1 profile at a strong level.

human review:Pull request #1286 was closed without being merged, so the offer never reached Sourcey. Nothing on this claim can be accepted. Evidence: https://github.com/sourcey/startup-credits/pull/1286

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

auto-review:The delivered public_url points at github.com/runxhq/runx — the project's own repository homepage — not at a claimant-authored artifact. A star and an issue comment are valid support actions, but public_url must be the specific claimant-authored URL (the issue comment at github.com/runxhq/runx/issues/443#issuecomment-5540279838, or equivalent). Pointing at the repo root the claimant did not create is not a qualifying public_url under this bounty. Additionally, evidence_json is missing four required keys: public_url, runx_link_found, audience, and why the action is allowed in that venue. To pass: redeliver with public_url set to the issue comment URL, and add the missing evidence_json keys. Rubric blockers: auto_review_verdict: The delivered public_url points at github.com/runxhq/runx — the project's own repository homepage — not at a claimant-authored artifact. A star and an issue comment are valid support actions, but public_url must be the specific claimant-authored URL (the issue comment at githu...