docs: tidy lead-effort note and report nits after batch 403 - #422
Merged
Merged
Conversation
The team-guide note now names /effort and the persistent per-model override it writes, and covers "file only" as well as "dispatch". The report carries the Opus re-review nits from PR #408. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Owner
Author
Reviewer report, lean track, fix round 1/3 (batch #417)VERDICT: CHANGES_REQUESTED
|
4 of 19 tasks
Batch #403 left the note silent on "file only" and on the persistent /effort override, which kept later Opus lead sessions at high; the first pass also dropped the switch-back instruction. This restores the instruction, states the override's persistence and scope, aligns the report's section 1 with the note, and reflows the edited paragraphs with each /effort code span on one line. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Owner
Author
Reviewer report, lean track, re-review after fix round 1/3 (batch #417)VERDICT: APPROVE
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #415. Part of batch #417. Lean track (docs only; no .claude/agents, skills, workflows, or code).
Changes
.claude/team-guide.md: the refinement-only note now says to type/effort xhighbefore replying "dispatch" or "file only", and that/effort highwrites a persistent per-model override intosettings.json(owner-confirmed 2026-10-01) which/effort xhighundoes.docs/reviews/2026-09-28-lead-effort-comparison.md:/effort highand/effort xhighwording (was--effort high); original no-writes window start 10:56:00Z; "this fix round" replaced by "on 2026-09-30, during the PR A/B: lead effort, Opus 5.5 at high vs xhigh, on the advisor refine task #408 review"; "cache-cold" dropped; H6 artifact effect restated (without it the gap would be 0, not 0.33, so condition 1 holds with more room than reported); judge-layout mismatch attributed to the pre-registered judge layout.docs/reviews/2026-09-28-lead-effort-comparison-data.json:no_writes_check_h4_h6.checked_utcis now the date only (2026-09-30), not the00:00:00Zplaceholder.Not touched: the frozen protocol file,
tiers.lead, agent frontmatter,effort-policy.test.mjs,~/.claude-work/settings.json. No score or result changed.perTurnEffort check (read-only)
Session logs under
~/.claude-work/projectswhose first record is after 2026-10-01 07:29Z: two exist, both show onlyperTurnEffort: xhigh(one session: 122 turns; the other: 18). Nohighvalue in either. Nothing copied into the repo.Checks
npm test-> 383/383 pass, exit 0.🤖 Generated with Claude Code