Skip to content

chore: integrate the bugs-2026-09-28 coordinator branch (claude harness 1.1.18, promoted potentials, consolidated agent memory) - #983

Merged
drmoisan merged 39 commits into
mainfrom
chore/bug-triage-2026-09-28
Oct 7, 2026
Merged

drmoisan merged 39 commits into
mainfrom
chore/bug-triage-2026-09-28

Conversation

@drmoisan

@drmoisan drmoisan commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Suggested title

chore: integrate the bugs-2026-09-28 coordinator branch (claude harness 1.1.18, promoted potential entries, consolidated agent memory)

Summary

  • Brings the maintainer's claude harness 1.1.18 push-down (commit 83fb045dd) into main. Main currently carries harness 1.1.12. This is the bulk of the diff: hooks, agents, skills, rules, .claude/lib/**, and config/blast-radius.json / config/orchestration-routing.json.
  • Adds the potential-entry records promoted during the bugs-2026-09-28 bug triage and parallel run (docs/features/potential/**).
  • Consolidates agent memory written during the run onto one branch before the run's worktrees and branches are deleted:
    • memory from this coordinator branch;
    • memory from eight item branches whose code had already merged but that carried one trailing memory-only commit each (cherry-picked with -x provenance);
    • memory from two preparation backup branches (cherry-picked with -x provenance).
  • This branch is used for consolidation in place of a dedicated documentationandmemories branch. The pre-implementation gate admits commits only in a worktree whose checkpoint names an active feature folder, and this coordinator branch already held most of the content.
  • No product code (C#, tests, project files) changes.

Why

The bugs-2026-09-28 parallel run is closed and its run records are already on main. The coordinator branch and the item branches still hold the run's lasting outputs: the harness update the run executed under, the promoted potential entries, and the agent-memory lessons. Merging them preserves that content, and the worktree cleanup can then delete the remaining branches without losing anything.

What Changed

  • Harness (.claude/**, config/**): the 1.1.18 push-down, unchanged from the maintainer's commit. It adds:
    • worktree-resolution, merge-gate and removal-gate resolution hooks;
    • the cleanup-merged-worktrees scripts;
    • the blast-radius scheduling and parallel-drift libraries;
    • the CI-gate parser;
    • agent and skill updates.
  • Potential entries (docs/features/potential/**): promoted records from the triage.
  • Agent memory (.claude/agent-memory/**): new lesson files plus updated MEMORY.md indexes for the atomic-executor, atomic-planner, orchestrator, parallel-orchestrator, feature-review, prd-feature and task-researcher agents.

Architecture / How It Fits Together

  • Harness files: consumed by Claude Code sessions in this repository; nothing in the product build references them.
  • Agent memory: loaded by the respective agents at session start.
  • Potential entries: inputs to the promotion lifecycle.

Verification

Completed:

  • origin/main was merged into the branch, so the branch is current with main (merge base a52f3c692).
  • Memory index conflicts were resolved by keeping this branch's reorganized index and appending every main-only entry whose target file is not already indexed. No conflict markers remain under .claude/agent-memory.
  • A conflicting numbered lesson file was deduplicated and renumbered.

Not verified in this PR: no local build or test run. The repository CI checks on this pull request are the verification for the harness changes.

Recommended:

  • git diff --stat origin/main...HEAD -- .claude/hooks .claude/lib config

Backward Compatibility / Migration Notes

The harness update changes hook behavior for every agent session in this repository once merged, including new resolution logic in the merge and worktree-removal gates. config/blast-radius.json and config/orchestration-routing.json change with it.

Risks and Mitigations

  • Risk: a harness hook regression affects agent sessions.
    • Mitigation: the content is the maintainer's own push-down, unchanged.
    • Rollback: revert the merge commit.
  • Risk: large MEMORY.md indexes. The orchestrator index already exceeds the agent memory read limit and carries duplicate entries inherited from this branch.
    • Mitigation: none in this PR; recorded as a follow-up.

Review Guide

  1. .claude/hooks/** and .claude/lib/**: behavioral harness changes.
  2. config/blast-radius.json and config/orchestration-routing.json.
  3. docs/features/potential/**.
  4. .claude/agent-memory/**: mechanical, high volume; skim.

Follow-ups

  • Trim and deduplicate .claude/agent-memory/orchestrator/MEMORY.md.
  • After merge, rerun the worktree cleanup to delete the eight item branches, the backup branches and their worktrees.

GitHub Auto-close

  • None

🤖 Generated with Claude Code

https://claude.ai/code/session_01XYKFZYM6SyG8iN7ChTM6dd

drmoisan and others added 30 commits September 28, 2026 19:39
…issues 927 to 933. Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
…parallel run

Lessons and index updates from the atomic-planner, feature-review,
orchestrator, parallel-orchestrator, parallel-planner and atomic-executor
agents during preparation and execution of items 927 and 928.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KjdFkwww4yKK7NduUg6vNf
…allel run

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…un (929, 940, 941, 944, 945)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N3r7uhChZ6XRKuQntGLpsG
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ota pause

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…andoff

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resolve agent-memory conflicts by taking the union of both sides: atomic-planner and orchestrator index entries, and the prd-feature AC-gate notes (main's item renumbered to 10).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… token recurrence on 973

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
…ution passes

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
…-09-28

# Conflicts:
#	.claude/agent-memory/atomic-executor/MEMORY.md
#	.claude/agent-memory/atomic-planner/MEMORY.md
#	.claude/agent-memory/atomic-planner/index_legacy_preflight_seams_pre_900.md
#	.claude/agent-memory/feature-review/MEMORY.md
#	.claude/agent-memory/orchestrator/MEMORY.md
#	.claude/agent-memory/prd-feature/feedback_ac_gates_verify_satisfiability.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit edb01a0)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 6043369)
drmoisan and others added 9 commits October 7, 2026 06:55
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 3344b7c)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit b2c3a41)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 2eec70e)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 27dc9b4)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 16457c4)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit ed8f55b)
… worktree

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 7f05b3e)
… worktree

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit a64a1cf)
…olidation

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
@drmoisan
drmoisan merged commit 9911fe1 into main Oct 7, 2026
7 checks passed
@drmoisan
drmoisan deleted the chore/bug-triage-2026-09-28 branch October 7, 2026 12:45
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