Skip to content

Re-roll the org Claude harness baseline - #62

Merged
bs-door-harness[bot] merged 2 commits into
mainfrom
claude/reroll-org-harness-d073ea37
Sep 10, 2026
Merged

bs-door-harness[bot] merged 2 commits into
mainfrom
claude/reroll-org-harness-d073ea37

Conversation

@bs-door-harness

Copy link
Copy Markdown
Contributor

Brings this repo's committed harness baseline back to canonical (payload fingerprint d073ea37): canonical env keys and permissions.allow entries are merged into .claude/settings.json as 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.sh is 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 into CLAUDE.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

@bs-door-harness
bs-door-harness Bot marked this pull request as ready for review September 10, 2026 00:55
@bs-door-harness
bs-door-harness Bot merged commit 482cf3f into main Sep 10, 2026
9 of 10 checks passed
@bs-door-harness
bs-door-harness Bot deleted the claude/reroll-org-harness-d073ea37 branch September 10, 2026 00:55
@bounded-systems-front-desk bounded-systems-front-desk Bot moved this from Todo to Done in Front Desk Sep 10, 2026
bdelanghe added a commit that referenced this pull request Oct 27, 2026
…itin)

content/strings.json becomes the verbal layer every surface reads: the brand's
own copy stays at the top level, and each surface's microcopy lives in its own
DTCG group. The first is `approve`, the 40 tokens of bdelanghe/chitin's passkey
approve page (chitin #62), folded from flat dotted keys into nested groups;
`clax` and `allie` are reserved in the README.

- strings.schema.json: tokens or groups, recursively; $value and $description
  both required and non-empty; $value placeholders must be {name}
  ([a-z][a-z0-9_]*), so stray braces and alias-shaped {a.b} fail; keys may
  carry `_`.
- tools/content.mjs: validate() walks groups, reports the dotted key, and
  enforces the same rules (patterns read from the schema).
- flake.nix: the build runs `tools/content.mjs --check` and ships content/.
- README: a Content section on groups, placeholders and how a compiled
  consumer pins the file.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117AAnztxdG2tNqQSCsQB7q
bdelanghe added a commit that referenced this pull request Oct 27, 2026
…itin) (#66)

content/strings.json becomes the verbal layer every surface reads: the brand's
own copy stays at the top level, and each surface's microcopy lives in its own
DTCG group. The first is `approve`, the 40 tokens of bdelanghe/chitin's passkey
approve page (chitin #62), folded from flat dotted keys into nested groups;
`clax` and `allie` are reserved in the README.

- strings.schema.json: tokens or groups, recursively; $value and $description
  both required and non-empty; $value placeholders must be {name}
  ([a-z][a-z0-9_]*), so stray braces and alias-shaped {a.b} fail; keys may
  carry `_`.
- tools/content.mjs: validate() walks groups, reports the dotted key, and
  enforces the same rules (patterns read from the schema).
- flake.nix: the build runs `tools/content.mjs --check` and ships content/.
- README: a Content section on groups, placeholders and how a compiled
  consumer pins the file.


Claude-Session: https://claude.ai/code/session_0117AAnztxdG2tNqQSCsQB7q

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

0 participants