fix(session-flow): stop handoffs from dropping in-force rules to fit the hot-file size cap
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 34/100
Direzione di ricerca
Start by reading save_point.py validate and the session-flow plugin’s structure.md Shape 3 rules; the issue does not give their paths or identify the relevant tests. Add coverage for a dropped rule and a retired rule, separate core from non-core size in validation, and report when carried Prior sessions content causes the cap to be exceeded. The amendment carry-forward policy is an owner design decision, so completion also needs an agreed policy and a test for it.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
A shape-3 handoff's hot file has a 24,600-byte cap, but its core (Original goal, Direction changes, Resumption brief, Current rules, Standing preferences) grows every hop and is the part validate says never moves. When the core nears the cap, the only lever left to a writer is the rule list, so in-force rules get dropped from the hot file to pass validate, and the next session never sees them. Nothing in save_point.py validate catches a dropped rule: it reads only size, order and slots.
Evidence (lane 3 chain 20261101T025745Z-handoff-lane3-plan-b, hop 28, 2026-11-06):
- The hot file's core was 24,437 bytes with the cap at 24,600, leaving 163 bytes for every non-core section; the predecessor hop was already over the cap (26,460 bytes, core 21,782).
- The Original goal alone was 13,269 bytes: it carries every dated owner amendment verbatim, and the chain has 28 hops.
- To pass, the writer moved 20 in-force rules into the hop file (among them R77, wait for the hub's OUTAGE-END before GitHub writes; R58, limits on hand re-runs; R68 and R69, safe idle claiming). A side agent caught it; the rules were put back and the file emitted UNVALIDATED at 29,053 bytes (core 23,796).
structure.md"Shape 3" allows deleting a rule only when it is retired, not to fit the cap, but the skill gives no check that enforces it.
Done when
-
save_point.py validatefails when a rule id in the predecessor's Current rules is missing from the hot file and is not listed with a reason under a retired-rules heading in this hop's file (test: drop one rule, see FAIL; list it as retired, see PASS). - The core over the cap is never resolved by moving core content: the skill and
validate's FAIL text say to emit UNVALIDATED (as it already does for a core over the cap) rather than shorten the core, andvalidatenames the core size separately from the non-core size. - The Original goal stops growing without bound: a decided rule for how dated amendments past a threshold are carried (for example, the newest N verbatim in the hot file and the rest verbatim in the hop file with a pointer), with a test.
- A handoff over the cap because of carried deterministic content (the Prior sessions table) is reported as such, so the writer is not pushed to cut written sections.
Notes
The amendment rule touches what "verbatim Original goal" means, so its shape is a design choice for the session-flow plugin's owner; the rule-drop check and the FAIL text are not.
- Lingua principale
- Shell
- Stelle
- 22
- Fork
- 2
- Merge medio
- 1h 13m
- PR unite (30g)
- 954
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di melodic-software/claude-code-plugins
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
melodic-software/claude-code-plugins#9179 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Worktree-isolated sessions refuse claude plugin eval (guard reads 'eval' as shell eval)Forse già presa @kyle-sexton l’ha presa 6 giorni fa. Apertahost-run priority: low status: ready work-class: mechanical
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
melodic-software/claude-code-plugins#5696 · 16 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
chore(source-control): finish the public-data credential sweep left from #8282Forse già presa @kyle-sexton l’ha presa oggi. Apertahost-run priority: medium status: confirmed work-class: read-only
melodic-software/claude-code-plugins#13819 · 3 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
perf(pr-verify): set the capture key proxy's token-cap from a full measured captureForse già presa @kyle-sexton l’ha presa oggi. Apertahost-run priority: medium status: confirmed work-class: scoped
melodic-software/claude-code-plugins#13724 · 6 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
pr-pipeline: run Refine before review, triggered by events and file extensionsForse già presa @kyle-sexton l’ha presa oggi. Apertahost-run priority: medium status: needs-decision work-class: structural
melodic-software/claude-code-plugins#13717 · 13 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di melodic-software/claude-code-plugins
Issue simili
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
Frogging-Family/linux-tkg#1265 ·
-
False AMD GPU DetectionApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
community-scripts/core#217 ·
I maintainer di solito rispondono entro 1 giorno
-
known-red S3: friction & debt
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
MedakaLang/medaka#4969 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement needs:sonnet ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno