Verifier revisions lose the capped severity guarantee

Open Beginner friendly
#73 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript

Research direction

Start with src/llm/verifier-revision.ts:119-124 and trace how a title-only revision copies schema fields; then read src/pipeline/verifier.ts:1287 and 505 to understand how severityBeforeCap is used. Reproduce the Stage 7 capped critical finding case described in the issue and check that a title-only revise preserves the critical guarantee while a plain keep still works.

Written by the indexing model from the issue text.

Description

bug

Problem: A title-only revise of a Stage 7 critical finding already capped to medium loses severityBeforeCap because the revision copies only submitted schema fields. A fresh medium finding then fails to preserve the critical guarantee.
File:line: src/llm/verifier-revision.ts:119-124; src/pipeline/verifier.ts:1287,505.
Evidence: @architect-2 confirmed with a Stage 7 capped critical finding; a plain keep preserves severityBeforeCap.
Suggested fix size: S.
Found during #44 (workstream U, confirmed by @architect-2).

Dominant language
TypeScript
Stars
8
Forks
1
Avg merge
5m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from 0xPolygon/codegenie

All issues in 0xPolygon/codegenie

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.