Skip to content

HANDOFF.md

Latest commit

 

History

History
104 lines (90 loc) · 7.29 KB

HANDOFF.md

File metadata and controls

104 lines (90 loc) · 7.29 KB
Raw

Handoff — 2026-09-12

State of play for the next session. Conventions, how-tos and release history live in README.md; the agent-facing subset is CLAUDE.md.

Where things stand

Two releases shipped and waved on 2026-09-10, both recorded in README, their only home: v1.15.0 (the issue path cannot end green without a PR; the DRIVER_AGENTS_REF bump; the wave carries stubs and the PR template whole-file) and v1.16.0 (every third-party action floats on its major tag; Dependabot proposes majors only). The audit after the second wave: 51 pins at ff3ff344, 88 files matching, and 2 drifted rows — the hand-installed lint.yml in driver-agents and driver-engineering-app, which the wave never reaches; a to-do is filed in each repo and the rows clear when they land. Floating past majors (@main) was raised and declined the same day: the major tag is the maintainers' only compatibility promise, and reconciling a major across the fleet is one wave, so the refs stay where they are. The Dependabot proof from the 2026-08-22 handoff closed that morning (vite-plugin-shopify-clean #95, opened unaided, merged, waved).

2026-09-12: Macroscope owns automatic PR review, org-wide (Maria). Claude is the pipeline and the on-demand second opinion, never an automatic reviewer of an opened PR; the implementer's own pre-review before it opens a PR is implementing and stays. #57 (merged) records the decision (macroscope-integration-scope.md) and changes no workflow: a fleet scan the same day found no Claude review on any pull_request event, so the kit already complied. dependabot-report is the one Claude-driven automatic verdict on a PR left, and Macroscope reviews Dependabot PRs too since 2026-09-10 — whether it stays is Maria's call. #58 repoints every live driver-bonsai-mcp reference at driver-agents (the repo was archived 2026-09-11) and drops the dead ngrok default from the retired ticketed rail — in flight. The to-do list was swept the same day against the decision and the 2026-09-11 state-of-play survey (Maria's claude.ai artifact, the cross-repo order of work; steps 6 and 8 are this repo's): eight items stand, and the one new gated item is the Check Run agents file set for fleet-wave.sh.

Otherwise nothing is in flight. The fleet's claude.yml fails an issue run that leaves no PR and keeps the full transcript in the job log — and no real ticket has run on it yet. That run is the acceptance test (step 7 of the 2026-09-10 state-of-play), and reading its transcript is how the Avara #195 diagnosis gets confirmed.

Open decisions

  • Fable billing. Unchanged since 2026-08-21: watch, don't gate; fallback --model opus (MODEL NOTE in templates/github/claude.yml). It needs an actual answer before the next claude.yml wave — claude-yml-wave-plan.md.
  • Reusable conversion of claude.yml — still TABLED, and the 2026-09-10 pin-model investigation strengthened the case: across the last eight releases, seven changed a whole-file kit file (claude.yml in six), so the per-repo commit per release is claude.yml's churn, not the SHA pin. Mutable refs, an npm package, and ruleset-required workflows were assessed and declined — the dated note in reusable-conversion-scope.md.
  • Identity unification — still DEFERRED; identity-unification-scope.md.
  • dependabot-report's future. It runs Claude automatically on every Dependabot PR (verdict over the inert artifact, never the diff). Macroscope reviews Dependabot PRs too since 2026-09-10, so it is the one place two bots still review automatically. Keep, or retire like the review rails.
  • Marcella-NYC-Main review coverage. Macroscope cannot reach a repo outside the org, so that active client work gets no bot review. Install Macroscope there, transfer the repo, or accept it (state-of-play survey, 2026-09-11).
  • The two retired review rails (pr-first-review.yml, ticketed-review.yml) are kept caller-less for re-activation, and re-activating an automatic Claude review now contradicts the 2026-09-12 decision. Delete them, or keep them as the fallback if Macroscope ever goes.

Watch-items

  • The first real ticket through v1.15.0. The guard step should stay quiet; if it fires, the failure note lands on the issue and the transcript is in the run log (show_full_output).
  • Major bumps of the kit's floated actions. actions/checkout@v7, actions/upload-artifact@v7 and anthropics/claude-code-action@v1 float in the kit; when a new major ships, a fleet repo's Dependabot moves ahead and the audit reads the kit as behind until the kit's major is bumped. Below a major boundary the foundrae-blackridge #174 drift-and-rollback cannot recur.
  • The cooldown exemption is unverified live until a tag lands and a repo carrying the kit block bumps the same day; vite-plugin-shopify-clean is the one to watch at the next tag.
  • WebSearch/WebFetch stay off until #690 ships a fix (still open at 2026-07-28); the action floats on v1, so the fix arrives on its own and the caveat comment in claude.yml is what gets removed.
  • A human @claude (tag mode) still gets the action's own co-author text; the nine-item quality standard is global to --append-system-prompt — both unchanged.

Recommended next steps

The 2026-09-10 state-of-play sets the order; the workflows-side pieces are:

  1. One real ticket end to end on the v1.15.0 rail, transcript read. Pairs with the dispatcher heartbeat in driver-agents.
  2. The next claude.yml wave — ride-alongs and gates in claude-yml-wave-plan.md; the Figma REST wrapper (driver-agents) gates two of them, a Macroscope answer on headless CLI auth gates the third.
  3. Check Run agents pilot (Avara first). When the prompts exist in driver-agents, tools/fleet-wave.sh gains .macroscope/check-run-agents/ as a second file set — the dest() helper is where a second root goes.
  4. Fleet dependabot.yml audit (to-do): the kit block, cooldown included, is the house-standard candidate; the five repos without a github-actions block are listed in fleet-operations.md.

Pointers

  • README.md — release + repin order, what's in the kit, dated release history.
  • fleet-operations.md — wave mechanics, the fleet counts, what the pin audit cannot see, branch protection.
  • claude-yml-wave-plan.md — the next implementer wave and its gates.
  • macroscope-integration-scope.md — the 2026-09-12 decision that Macroscope owns automatic review, the Macroscope → Bonsai build, and what replaced the retired bridge server. Observed 2026-09-10: it re-reviews every push, resolves its own threads once a push addresses them, and its verdict reads Approved at <sha> once nothing is left; a fleet-changing kit release gets "not approved" on risk with zero findings.
  • driver-agents — the dispatcher (since 2026-09-10), the box-retirement spec, and config/reviewers.json, the live reviewer map.