Shape-4 handoff: eval expectations and link ignore that change with it

Aperta
#17,838 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@kyle-sexton ci sta già lavorando.

Dal 20/11/2026.

  • #17677 di @kyle-sexton — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
shell
Ambito
testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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_fail hop 4, after arm only: the pattern accepts slot_size: Resumption brief (slot 'brief') holds and OVER-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, after arm 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_fail hop 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 either size: (over the cap with movable content left) or OVER-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 printed FAIL: size: 24794 bytes is over the 24600-byte hot-file cap … and the harness test printed FAIL: 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: and Handoff 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.
Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
2h 17m
PR unite (30g)
960

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.