Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

jev-v3 shadow week: review the disagreement report and decide the flip

未关闭
#116 7 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
bun, typescript

调研方向

Review the shadow week logs by running bun eval/live-report.ts --hours 168. Check for regressions where the live system denied but v3 would allow. Examine the 'headless blocks v3 would allow' list and outage bucket. Decide whether to flip the policy to 'jev-v3' based on the report, then update configuration accordingly.

由索引模型根据 Issue 内容生成。

描述

enhancement ready-for-human

Phase 2 of docs/plans/2026-09-19-intent-aware-judgment.md is merged (#100 #104 #101 #102 #110, with fixes #105 #108 #112 #114 #115). The jev-v3 judgment now runs in shadow on every fresh classification and logs v3 beside the live verdict. This issue is the plan's "Flip" step.

merged 2026-09-22 ─▶ OMP reloads the plugin ─▶ shadow week ─▶ review report ─▶ flip or not
                                                (7 days)       bun eval/live-report.ts --hours 168

Before starting the clock

  • OMP has reloaded the plugin from main (a decision line carries v3).
  • shadowV3 is on (the default).

At the end of the week

  • Run bun eval/live-report.ts --hours 168. It must not print INCOMPLETE.
  • REGRESSIONS (denied live, v3 would allow) is empty. That is the plan's flip criterion.
  • Read the "headless blocks v3 would allow" list and the outage bucket.
  • Decide the flip: set policy: "jev-v3", then after a further week without regression, remove the jev-v2 path.

Known limits going in

  • Branch 5 (the reviewer) is UNSURE until Phase 3 builds it.
  • A task stated mid-session still ages out of evidence (#106).
  • The live evidence collectors read past /clear (#103); the jev-v3 builder doesn't.
  • The shadow costs two more Jev requests per fresh classification.
主要语言
TypeScript
星标
0
派生
1
平均合并
2 小时 10 分钟
30 天内合并 PR
64

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

STRML/omp-classifier 的其他 Issue

查看 STRML/omp-classifier 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。