Skip to content

Flag ruled-out approaches as possibly stale when their named file changed - #24

Merged
Coder8124 merged 2 commits into
mainfrom
code-anchored-staleness
Oct 4, 2026
Merged

Coder8124 merged 2 commits into
mainfrom
code-anchored-staleness

Conversation

@Coder8124

Copy link
Copy Markdown
Owner

Summary

  • A ruled-out approach recorded against a commit is flagged as possibly stale at resume and before_you_try when the files its text names have changed since
  • Moves the continuity eval suite out into the sibling logos-bench repo, leaving only the LongMemEval recall/QA self-check and bench pipeline here

Test plan

  • go build ./... && go test ./... && go vet ./... && gofmt -l .

@Coder8124

Copy link
Copy Markdown
Owner Author

looks good for most part, had to divest the bench into another repo because it was conflicting with the product itself.

@Coder8124
Coder8124 merged commit 50316bf into main Oct 4, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant