Verifier revisions discard finding provenance

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

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
backend

调研方向

Read the listed locations in src/pipeline/verifier.ts, src/llm/verifier-revision.ts, and src/pipeline/composer.ts to trace how revisions affect provenance and representative selection. The issue suggests forwarding trusted metadata or removing the dormant branch; clarify which behavior is intended before changing code. Done means revised promoted findings retain the intended provenance, or the unused branch is removed consistently.

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

描述

bug

Problem: Revised findings do not copy provenance. Since every surviving promoted candidate is revised, isPromotedFinding becomes false for all verified promoted findings and the promoted branch of representative selection only runs when verification is disabled.
File:line: src/pipeline/verifier.ts:1284-1301,504-513; src/llm/verifier-revision.ts:32-37; src/pipeline/composer.ts:2059-2074.
Evidence: Code reading by @architect; @lead-dev confirmed revision loses provenance.
Suggested fix size: S (forward trusted metadata) or delete the dormant branch.
Found during #44 (workstream A, challenged by @lead-dev).

主要语言
TypeScript
星标
8
派生
1
平均合并
5 分钟
30 天内合并 PR
2

环境准备

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

从这里开始

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

0xPolygon/codegenie 的其他 Issue

查看 0xPolygon/codegenie 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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