Drop changelog.earth: it migrated off Jev before we listed it - #53
Merged
Merged
Conversation
Listed on the 25th on a code marker that turned out to be archive data. The live path calls Groq (lib/groq.mjs, lib/patch-titles.mjs); the only Jev references left are archived review metadata on 23 of 293 editions and a validator that preserves those fields when a Groq-only revision lands -- there is a script literally named check-groq-only.mjs. No Jev call exists in the repository. Ignored with that reason, so discovery does not re-offer it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013MQewmnosW2tdUbmHCnryG
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A correction to my own triage from the 25th, found while picking today's review batch.
byalex33/changelog.earthpassed the screen because the code containstypesafe-ai/jev. Reading it properly, that string lives in archived data, not on a live path:lib/groq.mjsandlib/patch-titles.mjsare the live editorial path, callingapi.groq.com.data/editions.jsonhas 293 editions; 23 carry ajev: {model: 'typesafe-ai/jev', eligibleProbability, faithfulProbability}block from when Jev did the screening.lib/edition-archive.mjspreserves those historical fields when a newer revision arrives, and the test that pins it is calledcheck-groq-only.mjs— "Groq-only revisions retain historical review metadata".api.typesafe.ai, no/v1/systemone, noTYPESAFE_API_KEYand no SDK anywhere in the tree, and the README no longer mentions Jev.So the project used Jev and moved on. Under our own bar — "the project should actually call Jev, not just mention it" — the entry does not qualify, so it comes out, and
byalex33/changelog.earthgoes intodiscovery-ignore.txtwith that reason so tomorrow's run does not offer it again.No review existed yet, so nothing is orphaned. Entry count 367 → 366.
The screener lesson, which I will add to the workflow doc separately: a marker in code is not the same as a marker on a live path. Archived JSON, fixtures and a validator that guards historical fields all read as "CODE-CALL" to the grep. The cheap discriminator is to check whether the marker appears in a module that anything calls, and to look at what the current README claims — this one had already stopped mentioning Jev.
🤖 Generated with Claude Code
https://claude.ai/code/session_013MQewmnosW2tdUbmHCnryG