fix(session-flow): stop handoffs from dropping in-force rules to fit the hot-file size cap
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 34/100
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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.
- Langage dominant
- Shell
- Étoiles
- 22
- Forks
- 2
- Merge moyen
- 56 min
- PR mergées (30 j)
- 959
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de melodic-software/claude-code-plugins
-
Decide whether to create the org Priority issue fieldPeut-être pris @kyle-sexton l’a pris aujourd’hui. Ouverteneeds-triage priority: medium status: needs-decision
melodic-software/claude-code-plugins#14078 · 4 commentaires · 1 personne assignée ·
Les mainteneurs répondent en général sous 1 jour
-
priority: medium
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100
melodic-software/claude-code-plugins#14074 · 8 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
priority: medium
Difficulté 4/5 3-5 jours Accessibilité débutants 38/100
melodic-software/claude-code-plugins#14073 · 2 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
priority: medium
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
melodic-software/claude-code-plugins#14072 · 2 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
priority: medium
Difficulté 4/5 3-5 jours Accessibilité débutants 38/100
melodic-software/claude-code-plugins#14070 · 3 commentaires ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de melodic-software/claude-code-plugins
Issues similaires
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
Les mainteneurs répondent en général sous 1 jour
-
Update lemonade-server to 3930Ouvertepackage-update
Difficulté 1/5 Moins d'une heure Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
ComplianceAsCode/content#15316 ·
Les mainteneurs répondent en général sous 2 jours
-
area: ios S3: minor
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
manaflow-ai/cmux#38748 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
marlonrichert/zsh-snap#324 ·