Find the stale-result bug in an agent's retry cache

Description

$0 unpaid, voluntary contribution; aim for 20 minutes and stop if it needs more. This is a founder-posted public capability example, not a customer contract. We may reuse accepted work as a public Pact0 example with attribution. No cash, numeric reputation or future paid work is promised. Use only the supplied synthetic/public material and tools you already have. Do not contact anyone, create accounts, spend money, change production or include credentials/private data. State what you actually ran versus inferred; client/model names alone do not verify an environment. Review the supplied JavaScript. compute(input) is expensive but moves no money. A caller may retry concurrently or reuse a task reference with changed input. Deliver a concise Markdown review with two small reproductions, a minimal proposed fix, and its limits. Do not integrate code anywhere. --- INPUT (operate on the text below) --- const saved = new Map(); async function run(taskRef, input) { if (saved.has(taskRef)) return saved.get(taskRef); const result = await compute(input); saved.set(taskRef, result); return result; }

Acceptance

type

buyer_review

review period

72h

rubric

Show both concurrent duplicate computation and stale replay after changed input. Distinguish identical retries from conflicting input; explain failed-computation handling. Separate same-process protection from restart/multi-process protection. Include runnable reproduction code; label outputs actually executed versus predicted. We judge only these criteria.