Shape-4 handoff: eval expectations and link ignore that change with it
Mantenedores costumam responder em até 1 dia
Avaliação
- Dificuldade
- 3/5
- Tempo estimado
- Meio dia
- Facilidade para iniciantes
- 25/100
Direção de pesquisa
Start with plugins/session-flow/evals/re-oversized-brief/resume-eval.json (hop 4, after arm) and plugins/session-flow/evals/re-rule-after-size-fail/resume-eval.json (hop 6), then .lycheeignore. Widen only the named patterns: the slot_size and OVER-CAP alternatives for the first file, ^(size|OVER-CAP): for the second, and the four placeholder github.com/example repository names for the ignore list. Done when PR #17677 merges with these changes and no other expectation is widened. Coordinate with that open PR first, since this work depends on it.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Problem
PR #17677 (shape-4 handoff, Track B) makes HANDOFF_SHAPE = 4, so the resume eval's after arm now seeds shape-4 chains. Two test expectations and one link-check ignore change with it. This issue is their spec, so reviewers can check each against a stated reason.
Changes and why
plugins/session-flow/evals/re-oversized-brief/resume-eval.json,expected_failhop 4,afterarm only: the pattern acceptsslot_size: Resumption brief (slot 'brief') holdsandOVER-CAP: Resumption brief holds. The harness requires every FAIL line of the hop to match. For one oversized brief the shape-4 writer emits both lines: the slot-budget FAIL (AC3) and the binding-content OVER-CAP FAIL (AC5). Seeded output,afterarm at hop 4:FAIL: slot_size: Resumption brief (slot 'brief') holds 29513 bytes, 28534 bytes over its 979-byte budget; …FAIL: OVER-CAP: Resumption brief holds 29536 bytes, and the binding and carried sections alone are over the 24600-byte hot-file cap …
plugins/session-flow/evals/re-rule-after-size-fail/resume-eval.json,expected_failhop 6:^(size|OVER-CAP):. This hop sits at the 24,600-byte cap and the run's temp path length moves it across: after the shape-4 writer moves its movable sections, the hop FAILs eithersize:(over the cap with movable content left) orOVER-CAP:(binding content alone over the cap), both the same size failure the case states. Seeding the same case file twice gave different bytes; with the same writer one run printedFAIL: size: 24794 bytes is over the 24600-byte hot-file cap …and the harness test printedFAIL: OVER-CAP: Current rules holds 18350 bytes …. An exact single-arm pattern fails one of the two..lycheeignore:^https://github\.com/example/(exports|billing|scheduler|search)\.git$. The five parked reader evals (cb-dirty-tree-blocks-launch,fh-confirms-before-resume,or-routes-recovery-writes-nothing,ra-fetches-base-reports-drift,rt-reads-each-hop-from-hop-files) carry these four placeholder repository URLs in their fixture handoffs'repo:andHandoff origin:lines; they name no real repository, so the link checker skips exactly those four.
Done when
- #17677 merges with these two expectations and the four-name ignore, and no other widened expectation.
- Linguagem predominante
- Shell
- Estrelas
- 22
- Forks
- 2
- Merge médio
- 2h 17min
- PRs com merge (30d)
- 960
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de melodic-software/claude-code-plugins
-
source-control: ExitWorktree remove no longer deletes another running session's worktree (2.1.330)Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
melodic-software/claude-code-plugins#17829 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
melodic-software/claude-code-plugins#17827 · 3 comentários ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 65/100
melodic-software/claude-code-plugins#17779 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
docs(source-control): stop a HIGH or CRITICAL merge-risk merge for the owner only on token, account or billing riskTalvez já em andamento @kyle-sexton assumiu hoje. Aberta
Dificuldade 2/5 Menos de uma hora Facilidade para iniciantes 18/100
melodic-software/claude-code-plugins#17849 · 3 comentários ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 3/5 Meio dia Facilidade para iniciantes 15/100
melodic-software/claude-code-plugins#17843 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de melodic-software/claude-code-plugins
Issues semelhantes
-
security
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
btclib-org/portanode#985 ·
Mantenedores costumam responder em até 1 dia
-
omarchy-restart-shell fails with "notification service did not become ready" on slow CPUs (2s wait)Talvez já em andamento @stevederico assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
omacom/omarchy#19627 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 62/100
Mantenedores costumam responder em até 1 dia
-
bench/api.sh exec test fails with curl exit 52, and --ignore-failure still records the timingsAbertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
libracoder/kiri#669 ·
Mantenedores costumam responder em até 1 dia
-
documentation needs-triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
Sour-Dev-Home/metaphor-accessibility#621 ·
Mantenedores costumam responder em até 1 dia