Skip to content

skills(t27b-loop): pin hooksPath per worktree, pace the weekly budget (Closes #8544) - #8545

Merged
gHashTag merged 1 commit into
masterfrom
skill-t27b-loop-pace-8544
Oct 10, 2026
Merged

gHashTag merged 1 commit into
masterfrom
skill-t27b-loop-pace-8544

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #8544

Lessons from the loop's first night (see epic #8326):

  • Per-worktree hooks pin. The shared core.hooksPath flipped to an absolute path four times. Run git -C <wt> config --worktree core.hooksPath .githooks right after git worktree add. extensions.worktreeConfig is on, so the pin makes worktree commits immune to the flips.
  • Pace rule. Stay under about 0.6% of the weekly budget per hour; if usage runs ahead of that, start no new agent. Three agents burned about 4.5% per hour and the loop hit 98% in two hours. Prefer one agent at a time, on a model whose separate weekly bucket has room.
  • New trap: a spec rewrite is not a t27b regression. Other sessions' spec rewrites (c757043, c9d36f3) turned master's native ratchet red with UNEXPECTED FAILURE although t27b did not regress. Check git log on the spec first.

Markdown only.

🤖 Generated with Claude Code

…Closes #8544)

The shared core.hooksPath flipped to an absolute path four times between
2026-10-09 and 2026-10-10; a per-worktree pin (extensions.worktreeConfig
is on) makes worktree commits immune. Three agents burned about 4.5% of
the weekly budget per hour against a pace of about 0.6%, so the guard
gets a pace rule. Adds the trap of spec rewrites by other sessions
turning master's native ratchet red without a t27b regression.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-10 12:14:21 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 48
PRs with All Checks Green 2
READY 0
FAILING 48
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 48 + 0 + 0 = 48, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=bd3352ccb90e != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

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.

skills(t27b-loop): pin hooksPath per worktree, pace the weekly budget

2 participants