Mateus Cardoso 9e150cd3b2 fix(agent-context): apply default markers when config markers are blank (bash) (#3736) ...

When the extension config omits context_markers (or sets them blank),
relying on the built-in defaults, the Bash port aborted with "malformed
config parser output" and never updated the context file, while the
Python (`or DEFAULT_*`) and PowerShell (default-initialized) ports handled
it correctly.

The config parser prints three lines (context_files JSON, marker_start,
marker_end), captured via `_raw_opts="$(...)"`. Command substitution strips
trailing newlines, so blank marker lines collapse the output to fewer than
three, tripping the `(( ${#_opts_lines[@]} < 3 ))` guard and making the
DEFAULT_START/END substitution unreachable — the exact case it was written
for.

Require only the context_files line and default the marker lines to empty
(`${_opts_lines[1]:-}` / `${_opts_lines[2]:-}`) so the existing
DEFAULT_START/END fallback fills them in. Add a parity regression test with
blank markers (it fails on the old guard and passes with the fix).

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-27 10:33:56 -05:00

..

bash

fix(agent-context): apply default markers when config markers are blank (bash) (#3736)

2026-07-27 10:33:56 -05:00

powershell

fix(agent-context): discover nested plan.md in scoped layouts (#3024) (#3301)

2026-07-10 14:21:43 -05:00

python

fix(agent-context): discover nested plans in Python port mtime fallback (#3734)

2026-07-27 07:41:20 -05:00