chore(claude): settings-estate repair — plansDirectory alignment + install lever - #1896
chore(claude): settings-estate repair — plansDirectory alignment + install lever#18964444J99 wants to merge 3 commits into
Conversation
…stall lever Two limen-side slices of the 2026-08-06 settings-estate review/repair: - .claude/settings.json: plansDirectory "docs/plans" — built-in plan mode now writes plans where the charter declares they live (the home check-session-phase.py and check-session-streams.py actually read), closing the ~/.claude/plans divergence. - his-hand-levers.json: file L-CLAUDE-SETTINGS-ESTATE-INSTALL (19-line targeted append). The review proved all 19 inline PreToolUse guards in the user-level settings dead (CLAUDE_TOOL_ARG_* env vars were never the hook interface; stdin JSON is). The repair layer — stdin-JSON dispatcher, 26-fixture liveness predicate, cadence-tracker fix, validated candidate template with adoptions — is built, fixture-green, and staged; the final swap+apply is classifier-gated (settings self-modification boundary), so it is filed as the operator's one-paste lever per the compliant-gate-reroute rule. Verified: scripts/verify-scoped.sh green (syntax-changed, diff-hygiene, check-root-manifest, check-note-links, pytest-cli — 5204 passed). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F5GMLx6mh5y8giwBgdbzis
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 59 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Multi-agent review roll call (CodeRabbit and Claude review automatically. Reviewers: post substantive findings only. Authors/agents: address every thread, push fixes to this branch, reply and resolve, then re-request review.) |
|
To use Codex here, create a Codex account and connect to github. |
There was a problem hiding this comment.
Pull request overview
Warning
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
Aligns Claude “plan mode” output with the repository’s declared plans location and adds an operator lever to apply a validated settings-estate repair that can’t be performed by agent sessions due to the self-modification gate.
Changes:
- Configure Claude to write plans to
docs/plansvia.claude/settings.json. - Add a new lever entry documenting a one-paste, human-run install procedure for the staged settings/hook repair.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| his-hand-levers.json | Adds a new lever (L-CLAUDE-SETTINGS-ESTATE-INSTALL) with a prescribed install/apply workflow for the repaired Claude settings/hook layer. |
| .claude/settings.json | Sets plansDirectory to docs/plans to eliminate divergence from ~/.claude/plans. |
| "cd /Users/4jp/Workspace/domus-genoma", | ||
| "cp /tmp/settings.json.tmpl.candidate-611a4757 private_dot_claude/settings.json.tmpl", | ||
| "mkdir -p ~/.claude/archive-20260806-settings-estate && mv ~/.claude/settings.proposed.json ~/.claude/settings.json.bak ~/.claude/settings.json.bak-20260625-160116 ~/.claude/settings.json.bak-20260625-164006 ~/.claude/hooks/allow-trusted-cd-git.sh.bak ~/.claude/hooks/allow-trusted-cd-git.sh.bak-20260701 ~/.claude/hooks/allow-trusted-cd-git.sh.bak-20260709-resume ~/.claude/archive-20260806-settings-estate/ 2>/dev/null; mv private_dot_claude/settings.json.tmpl.bak ~/.claude/archive-20260806-settings-estate/source-settings.json.tmpl.bak", | ||
| "git add private_dot_claude/settings.json.tmpl private_dot_claude/hooks/executable_pretooluse-guard-dispatch.sh private_dot_claude/hooks/executable_guard-liveness-check.sh private_dot_claude/hooks/executable_comment-cadence-tracker.sh private_dot_claude/CLAUDE.md.tmpl && git commit -m 'feat(claude): stdin-JSON guard dispatcher, settings adoptions, estate hygiene (2026-08-06 review)'", | ||
| "chezmoi add ~/.claude/hooks/allow-trusted-cd-git.sh", | ||
| "chezmoi diff; chezmoi apply && ~/.claude/hooks/guard-liveness-check.sh && git push origin master" |
| "steps": [ | ||
| "cd /Users/4jp/Workspace/domus-genoma", | ||
| "cp /tmp/settings.json.tmpl.candidate-611a4757 private_dot_claude/settings.json.tmpl", | ||
| "mkdir -p ~/.claude/archive-20260806-settings-estate && mv ~/.claude/settings.proposed.json ~/.claude/settings.json.bak ~/.claude/settings.json.bak-20260625-160116 ~/.claude/settings.json.bak-20260625-164006 ~/.claude/hooks/allow-trusted-cd-git.sh.bak ~/.claude/hooks/allow-trusted-cd-git.sh.bak-20260701 ~/.claude/hooks/allow-trusted-cd-git.sh.bak-20260709-resume ~/.claude/archive-20260806-settings-estate/ 2>/dev/null; mv private_dot_claude/settings.json.tmpl.bak ~/.claude/archive-20260806-settings-estate/source-settings.json.tmpl.bak", |
…STALL (no-tasks-on-me graph parity) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01F5GMLx6mh5y8giwBgdbzis
Merge commits are not allowed on this repository
4444J99
added
the
lifecycle:active-human
Summary
Limen-side slices of the 2026-08-06 Claude settings-estate review/repair.
.claude/settings.json:plansDirectory: "docs/plans"— built-in plan mode now writes plans to the charter's declared plan home (whatcheck-session-phase.pyandcheck-session-streams.pyread), closing the~/.claude/plansdivergence.his-hand-levers.json: leverL-CLAUDE-SETTINGS-ESTATE-INSTALL(19-line targeted append). The review proved all 19 inline PreToolUse guards in the user-level settings dead (CLAUDE_TOOL_ARG_*env vars were never the hook interface — stdin JSON is; verified by three live probes on 2.1.223). The repair layer (stdin-JSON dispatcher + 26-fixture liveness predicate + tracker fix + validated candidate template) is built and fixture-green in domus-genoma; the final swap+apply is classifier-gated (settings self-modification boundary), so it is filed as the operator's one-paste lever per the compliant-gate-reroute rule.Verification
scripts/verify-scoped.shgreen on the diff: syntax-changed, diff-hygiene, check-root-manifest, check-note-links, pytest-cli (5204 passed, 2 skipped).🤖 Generated with Claude Code
https://claude.ai/code/session_01F5GMLx6mh5y8giwBgdbzis