Skip to content

fix(v1.5.1.1): remove stray merge conflict markers in /context-save#1115

Open
SmithLMichael wants to merge 2 commits intogarrytan:mainfrom
SmithLMichael:SmithLMichael/fix-ctx-conflict
Open

fix(v1.5.1.1): remove stray merge conflict markers in /context-save#1115
SmithLMichael wants to merge 2 commits intogarrytan:mainfrom
SmithLMichael:SmithLMichael/fix-ctx-conflict

Conversation

@SmithLMichael
Copy link
Copy Markdown

Summary

  • Deletes unresolved Git merge-conflict markers (<<<<<<< / ======= / >>>>>>>) and a stale duplicate "Resume flow" block from context-save/SKILL.md.tmpl that landed in fix(checkpoint): rename /checkpoint → /context-save + /context-restore (v1.0.1.0) #1064 on 2026-04-19 and have been sitting in main for two days.
  • The duplicated block already lives correctly as "Restore flow" in context-restore/SKILL.md.tmpl:59, so no behavior is lost — this is pure prompt cleanup.
  • bun run gen:skill-docs regenerated the published context-save/SKILL.md to match the template. Diff is 100% deletion: 200 lines removed, 0 added across the two files.

Scope

 CHANGELOG.md               |  36 +++
 VERSION                    |   2 +-
 context-save/SKILL.md      | 100 ---------
 context-save/SKILL.md.tmpl | 100 ---------
 package.json               |   2 +-
 5 files changed, 38 insertions(+), 202 deletions(-)

Two logical commits:

  1. fix(context-save): remove stray merge conflict markers — the actual fix.
  2. chore(v1.5.1.1): bump version + CHANGELOG — release metadata.

Test Coverage

  • bun testall pass (skill validation, gen-skill-docs quality, browse integration). bun run gen:skill-docs regenerates clean after the template edit.
  • bun run test:evals (diff-based selection, 15 E2E tests) — 22 pass, 211 skip, 1 fail. See below for triage.

Eval Results — v1.5.1.1 @ SmithLMichael/fix-ctx-conflict

Run on Claude Max subscription auth (no API key cost, just rate-limit time). Total ~220s across 218 seconds of E2E.

✅ Passed (22/23)

  • All 10 journey-* routing tests
  • context-save-list-all-branches
  • context-save-then-restore-roundtrip
  • context-save-routing
  • context-restore-legacy-compat and friends
  • All skill validation + gen-skill-docs tests

❌ Failed (1/23) — pre-existing, unrelated to this diff

  • context-save-list-current-branch — fails 3/3 retries on assertion expect(hidesAlpha).toBe(true) (test/skill-e2e-context-skills.test.ts:462). The agent's find output in a Bash tool_result surfaces the alpha-branch save filename even though the List flow is supposed to filter by current branch.

Blame analysis (per CLAUDE.md "E2E eval failure blame protocol"):

Check Result
Does this branch modify test/skill-e2e-context-skills.test.ts? No
Does this branch modify the List flow section of context-save/SKILL.md.tmpl? No — the deletion is above the List flow at former lines 201-300
vs-previous comparison in the eval run FAIL → FAIL across all 3 attempts
Logical relationship to diff The 200-line deletion is 100% merge-conflict markers + dead duplicate content. None of it is in the List flow code path.

Verification status: Unverified on main directly (would require another eval run). The diff on this branch cannot have caused this failure because it touches no code in the failing test's execution path. Flagging as "unverified pre-existing" per protocol.

Recommended follow-up (not in this PR): The List flow prompt tells the agent to find all .md files in $CHECKPOINT_DIR then filter by frontmatter. The filenames from find leak into the tool_result surface before the filter happens. Fix: either grep frontmatter first before surfacing filenames, or instruct the agent to suppress the initial find output. Worth a P3 TODO.

Pre-Landing Review

Adversarial review (Step 11) skipped with rationale: the diff is pure deletion of merge-conflict markers and dead content. There is no new code path, no new CLI flag, no new runtime behavior. Nothing to adversarially challenge.

Specialist dispatch (Step 9.1) skipped for the same reason — the >50 line threshold was triggered by the 200-line deletion count, but all 200 lines are the same single fix.

TODOS

None introduced. One follow-up suggestion captured in the failure triage above for the maintainer to triage.

Test plan

  • bun test passes
  • bun run test:evals runs — 1 pre-existing failure documented above
  • bun run gen:skill-docs leaves template + generated file in sync
  • git grep "<<<<<<<\|^=======$\|>>>>>>>" context-save/ returns no matches
  • Maintainer confirms the context-save-list-current-branch failure is pre-existing by running it on main (or accepts the logical argument)

First PR to gstack from a new community contributor. Happy to adjust the CHANGELOG tone or scope if the voice doesn't land.

🤖 Generated with Claude Code

SmithLMichael and others added 2 commits April 20, 2026 22:20
The rename of /checkpoint into /context-save + /context-restore left live
<<<<<<< / ======= / >>>>>>> markers in context-save/SKILL.md.tmpl lines
201-300. The stale block was the old "Resume flow" section, which already
lives correctly in context-restore/SKILL.md.tmpl.

Accept the origin/main side: delete the stale block and the three marker
lines. Regenerate SKILL.md for all hosts.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Release metadata for the /context-save merge-conflict fix in 4002c86.
Pure version/docs commit — no behavior change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant