issues Search Results · language:Dune language:Python language:JavaScript language:JavaScript linked:pr linked:pr
Filter by
4.1M results
Create src/relay_demo/greet.py exporting greet(name: str) - str returning f Hello, {name}! . Acceptance: greet( World )
returns exactly Hello, World!. Stdlib only; no other behaviour yet.
Match date (YYYY-MM-DD)
2026-06-02
Players (player1, player2)
@Johnor12 , @parkerquarles
Sets (one line per set, player1 s games first)
6-3
new-singles-match
Update the completed T-2026-0017 plan so its status reflects merged #1545 and its no-claim wording names the current
real100_v2 private-eval boundary. Scope: docs-only; do not touch eval/run manifest code, ...
Update the completed T-2026-0008 plan so its status/PR reference reflect merged #1515 and its eval-boundary wording does
not imply a current real100_v2 performance claim. Scope: docs-only; do not touch ...
What went wrong
The autoresearch loop was started without completing the mandatory INIT config interview (skill step 5). Claude set
silent defaults for literature search, parallelization, dashboard server, ...
Update the completed T-2026-0005 plan so its status and eval-boundary wording reflect merged #1499 and the current
real100_v2 private-eval policy. Scope: docs-only; do not touch eval code, indexing code, ...
Update the completed T-2026-0004 plan so its status and eval-boundary wording reflect the merged #1490 implementation
and the current real100_v2 private-eval policy. Scope: docs-only; do not touch visual_ingestion.py, ...
Problem
Codex-backed planning on Radiance issue 667 exceeded the current default automation timeouts. The $advise call timed out
at 180 seconds even though it completed shortly after, and the R1 planner ...
state:needs-plan
작업 배경
최근 README가 최종 제출/프로젝트 소개 중심 구조로 정리되면서, 이전 README에 포함되어 있던 개발·협업 운영 규칙을 docs 부록으로 별도 보존할 필요가 있음.
작업 범위
- [ ] README 변경 이력 확인
- [ ] 이전 README의 작업 규칙/협업 규칙/브랜치·PR 운영 규칙 확인
- [ ] docs/development-workflow-rules.md ...
docs
Clarify T-2026-0002 Eval Artifact Surface Guard so private-eval surface wording names the current real100_v2
aggregate-only boundary instead of generic private real-eval wording.\n\nScope:
docs/plans/T-2026-0002-eval-artifact-surface-guard.md ...

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.