feat(profile): publish Atrinik organization identity

[zoeyrose]

Closes #60.

Coordinates with #57 by extending the existing config/organization.json and authoritative community-health/ publisher design; it does not introduce a competing writer or edit the generated atrinik/.github repository.

Coordinates

• Base: main at 77b83cf30a9f74712f98d9bd39c1e7a66532b0ca
• Head: feat/organization-profile at 014d1e6cb832d34ebd0dfc67d168948189261b2c
• Worktree: /workspaces/atrinik/workspace/worktrees/github-settings/issue-60-organization-profile
• Commits:
  • 5fceddf4877777178ab6727773bc17dcdf008372 (feat(profile): govern organization identity and pins)
  • 014d1e6cb832d34ebd0dfc67d168948189261b2c (fix(profile): document public pin workflow)

Scope

• govern the exact game-first organization description while preserving https://atrinik.org and unrelated owned organization defaults;
• report field-level live/desired drift and skip organization PATCH requests when desired state is already converged;
• generate .github/profile/README.md from community-health/profile/README.md, with explicit Classic GPL, replacement MIT, and separate content/media licensing boundaries;
• record the exact six public pins and stable repository IDs as manual state, then verify their count, identity, visibility, active state, and order read-only through GraphQL;
• document the post-merge, separately authorized publisher and organization-owner UI steps.

Validation

• bin/validate
• every tests/*.sh test
• bash -n bin/* tests/*.sh
• shellcheck bin/* tests/*.sh
• actionlint
• git diff --check
• complete live bin/publish plan: description is the only organization metadata drift; canonical website is unchanged; no apply performed
• complete live bin/publish-community-health plan: adds profile/README.md and updates the generated repository README; no apply performed
• live bin/verify-manual-settings: credential and environment metadata pass; it intentionally reports the pre-merge four-pin live state against the governed six-pin target

Verification and deployment

Runtime verification is not applicable to repository governance and generated Markdown. After merge and separate live-mutation authorization:

bin/publish
bin/publish-community-health
bin/publish --apply
bin/publish-community-health --apply
bin/verify-manual-settings

An organization owner must open https://github.com/atrinik, choose View as: Public, select Customize pins in the Pinned section (or pin repositories when empty), arrange classic, atrinik, website, content, protocol, and playtester in that exact order, and select Save pins. Do not automate that step through an undocumented interface. Then inspect the public profile and links and rerun bin/verify-manual-settings.

No live organization or generated-repository changes were applied from this branch.

[zoeyrose]

Whole-diff review is complete at 014d1e6cb832d34ebd0dfc67d168948189261b2c. The single medium finding—an incorrect manual public-pin UI path—was fixed and validated; a fresh complete post-fix review found zero known actionable findings. All repository validation and required latest-head checks pass. Live organization/profile apply remains intentionally post-merge and separately authorized; the current four-pin read-only drift is documented for the organization-owner View as: Public → Customize pins → Save pins step.

[github-actions]

🎉 This PR is included in version 1.8.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀