Repository navigation
feat(registry): record repository purpose with Jev - #581
Conversation
|
Agent verification, performed through the authenticated Workers AI binding: Jev 1.13.0 passed all eight cases. Five public repositories used pinned GitHub commits. Three synthetic cases covered mirrors, missing evidence, and injected instructions.
The injected directory remained a directory. Missing evidence returned uncertain without calling Jev. This small sample establishes these cases only. |
🤖 MERGED
GitHub merged this pull request.
2cd3ec50-abcd-49ce-acf5-028fafdd87f5 Selected findings run after merge and open separate pull requests. |
There was a problem hiding this comment.
Harlan Agent Kit posted this automated review. AI open source policy.
Automated Review: READY.
|
Agent delivery evidence, read-only production D1 checks on 8 October 2026, around 16:07 to 16:11 UTC:
The audit SELECTs reported zero rows written. These observations cover the scheduled classification and large-tree source recovery paths. |
🔗 Linked issue
Follow-up to #575.
❓ Type of change
📚 Description
File counts confuse original Skill packs, software, directories, and mirrors. Record Jev repository purpose from bounded README and Skill excerpts at a pinned commit. Store the evidence, model, prompt version, probability, answer, and evaluation time in D1.
An hourly job queues 25 due repositories, prioritizing truncated trees and large Skill inventories. New submissions and discovery hold directories, mirrors, and uncertain findings for review. Existing Skills, human eligibility, named positive trust overrides, and verified-owner decisions retain source recovery.
Held discovery stops retrying until a human clears it. The runbook includes pending-finding and approval procedures for organizations and new submissions.