{"repo":"NousResearch/hermes-agent","public_id":"139724","display_label":"Configurable retired-WAL capture cap and header-only degradation warning","summary":"One issue reports that retired-WAL capture falls back to a header-only artefact above a hard-coded 512 MiB cap, with no configuration option or warning. Two pull requests propose making the cap configurable and surfacing or avoiding the silent header-only degradation; their outcome isn't established by the titles alone.","subsystem":"agent","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":1,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":139724,"title":"Retired-WAL capture silently degrades to a header-only artefact above a hard-coded 512 MiB cap (no config, no warning)","url":null,"state":"open"},{"kind":"pr","number":139733,"title":"fix(state): make the retired-WAL capture cap configurable and warn on the header-only degradation","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false},{"kind":"pr","number":139735,"title":"fix(state): make the retired-WAL main-image cap configurable and never silently header-only","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#140893","number":140893},{"kind":"pr","value":"#140849","number":140849},{"kind":"pr","value":"#140808","number":140808},{"kind":"pr","value":"#140236","number":140236},{"kind":"pr","value":"#139530","number":139530}],"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}