Refill the agent backlog from FastFollow study packets #75

Outcome

Create a standing FastFollow job that studies admitted upstream projects and proposes deduplicated forge issues for verified product gaps.

Current behavior

Issue #42 can aim parallel agents at the backlog, but backlog creation remains manual. Episode 255 defined content-addressed study packets and gap receipts as a separate learning contract from product intent and proof intent.

Source: docs/episode-triage.md, episode 255.

Contract

• Maintain an explicit, reviewable list of upstream repositories, revisions, accepted lessons, and rejected defaults.
• Build a content-addressed study packet for each run.
• Compare the packet with current code, docs, issues, and project items.
• Emit gap receipts with evidence, affected surface, expected behavior, and confidence.
• Create or update a draft triage issue by stable gap ID; never file directly into active work without policy.
• Deduplicate against open and closed issues and record why a known gap was not refiled.
• Exclude private source and respect upstream licenses and repository authority.

Acceptance criteria

• A scheduled or authorized manual run produces a bounded report and zero or more draft triage issues.
• Re-running the same packet does not create duplicate issues.
• Each proposal links the exact upstream revision and local evidence.
• A reviewer can accept, reject, or defer a proposal without editing generated evidence.
• Rejected product patterns remain recorded so later runs do not resurrect them without new evidence.

Verification

Test packet identity, comparison, deduplication, private-source exclusion, issue creation, rejection memory, and schedule recovery. Run one pilot against an admitted upstream project.

Dependencies

Build on #42, the accepted-outcome contract, and the do-not-build register project.