Re-roll the org Claude harness baseline - #62
Draft
bs-door-harness[bot] wants to merge 3 commits into
Draft
Conversation
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.
Brings this repo's committed harness baseline back to canonical (payload fingerprint
d073ea37): canonical env keys andpermissions.allowentries are merged into.claude/settings.jsonas a floor — repo-specific env, hooks and the repo's own permissions are preserved, though the diff may include a jq reformat since the parsed object is the unit of truth —.claude/inject-org-context.shis refreshed verbatim where the settings reference it,.claude/org-repair.sh(the org bootstrap check/repair,.github-private#491) is refreshed verbatim, and the managed org stanza is merged intoCLAUDE.md(one marker-delimited block; everything else in the file is untouched). Opened by the re-roll lane, the adopters' counterpart to the initial rollout: adopt skips any repo that already carries settings, so canonical changes propagate through this path and the weekday census (harness-drift.yml) stays green for the right reason. See.github-private/docs/handoffs/claude-harness-reroll.md.Claim-issue: bounded-systems/.github#278