Skip to content

docs: drop moved renderer link and mark repository as hand-edited - #1

Merged
zoeyrose merged 1 commit into
mainfrom
docs/profile-hand-edited
Nov 14, 2026
Merged

zoeyrose merged 1 commit into
mainfrom
docs/profile-hand-edited

Conversation

@zoeyrose

@zoeyrose zoeyrose commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

Summary

Fixes the public Atrinik organization profile and stops describing this repository as generated.

  • profile/README.md: removes the renderer row from the project table. atrinik/renderer moved out of the organization in October; gh api repos/atrinik/renderer now resolves to seraphinastudios/tilewright-renderer.
  • README.md: the note said these files are generated from atrinik/github-settings and must not be edited directly. That generator was retired on 2026-11-14, so the note now says the repository is edited by hand through pull requests.

Intent brief

  • Goal: the public profile links only repositories that are in the atrinik organization, and the README no longer tells people (or agents) to edit a retired generator instead of this repository.
  • Decisions:
    • Remove the renderer row rather than repoint it. The table is titled "The project" and lists Atrinik's own repositories; linking a Seraphina Studios repository there would misdescribe it as part of the organization.
    • atrinik/editor, which also moved, is not linked anywhere in this repository, so nothing else needed changing. The word "editor" in the classic row describes Classic's own editor.
    • Keep a short mention of atrinik/github-settings in the note so readers who remember the old flow know it no longer applies.
  • Constraints: wording and structure of the profile otherwise unchanged; no setting, ruleset, secret or workflow-state changes.
  • Out of scope: issue forms, the pull-request template, CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md and the dependency-review workflow are untouched.

Implementation / behavior

Two Markdown edits, one commit. None of the files carried a "generated" header comment; the only generated-file note was the README paragraph.

Validation

  • Links checked: every github.com/atrinik/NAME link in the repository resolved with gh api repos/atrinik/NAME. All are in atrinik except renderer, which redirects to seraphinastudios/tilewright-renderer and was removed. atrinik/atrinik#168 (open) and atrinik/atrinik/docs/PROVENANCE.md exist; https://atrinik.org/, https://atrinik.org/downloads/ and https://zoeysr.com return 200.
  • Rendered Markdown checked: both files rendered through the GitHub Markdown API. The project table renders with a header and five rows, and the README note renders as one paragraph.
  • No CI is required on this repository; the dependency-review workflow runs on the pull request as usual.

Limitations / follow-up

  • Ordering dependency: atrinik/github-settings (main) still describes this repository as a generated target that must never be hand-edited (AGENTS.md) and still ships bin/publish-community-health with its community-health/ source, which the owner's login can still run. The installed atrinik-development skills (for example atrinik-github-governance) also still tell agents to "run the publisher plan before --apply". Both step-1 pull requests are the dependency: the github-settings tooling-removal PR (removes the publisher and community-health/, corrects AGENTS.md) and the atrinik-development skill-correction PR (stops telling agents to run the publisher). Until both merge, an --apply run of the publisher would overwrite this repository and restore the old "do not edit" note. Merging this pull request first is safe as long as nobody runs the publisher in the meantime; nothing here depends on those PRs otherwise.
  • Profile paragraph to settle before step 1 deletes community-health/: the publisher copy is newer than this repository, not older. community-health/profile/README.md on github-settings main carries the closing paragraph the owner merged in docs(profile): describe creator tools as current practice github-settings#100 on 2026-10-18 ("Atrinik's creators shape the game world with whatever tools serve the work, including AI tools; …"), and it already has no renderer row (#99). This repository was last synced on 2026-10-12 (d520570), so it still shows the superseded "Human creators direct the game world" paragraph, which this pull request keeps unchanged because its scope is links and the generated-file note. That paragraph is the only content difference between the two copies. Follow-up: carry the #100 paragraph over in a separate pull request to this repository before the step-1 tooling-removal PR deletes community-health/, so the approved wording does not survive only in git history.
  • If the renderer should still be credited from the Atrinik profile as an external dependency, that is a wording change for a separate pull request.
  • The crates.io trusted-publisher entry for atrinik/renderer is an owner-only action tracked elsewhere.

🤖 Generated with Claude Code

The organization profile listed atrinik/renderer, which moved out of the
organization in October and now redirects to another organization. Remove
that row; every other linked repository is still in atrinik.

The README said these files are generated from atrinik/github-settings and
must not be edited directly. That generator was retired on 2026-11-14, so
say instead that the repository is edited by hand through pull requests.

Co-Authored-By: Claude <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

None

@zoeyrose

Copy link
Copy Markdown
Member Author

Self-review

Reviewed: the whole diff of this pull request (README.md, profile/README.md) and the code it touches, by fresh-context independent reviewers given the intent brief.

  • Round 0: head b0b6544944e0774eb4e2364a2ea2c09f69e1ac1c (whole diff).
  • Round 1: head b0b6544944e0774eb4e2364a2ea2c09f69e1ac1c (whole diff plus the round-0 PR body change).

The head commit has not changed since round 0. All fixes were PR-body edits only; there are no fix commits.

Coverage limit: the PR-body edits made to handle the round-1 findings (the corrected profile-paragraph bullet and the rewritten ordering-dependency bullet) were not covered by a further review round that found nothing. The commit content itself was reviewed twice with no finding against the files.

Findings

  1. P3 README.md:8, round 0: hand-edit note can merge before the retired publisher is removed; the PR did not record the ordering dependency. Fixed in the PR body (Limitations / follow-up). No commit; head unchanged.
  2. P2 profile/README.md:48, round 1: the Limitations bullet said the publisher holds older profile text; it actually holds the newer, owner-approved docs(profile): describe creator tools as current practice github-settings#100 paragraph that was never published. Fixed in the PR body: bullet corrected, and a follow-up named to carry the #100 paragraph over in a separate PR before step 1 deletes community-health/. The paragraph itself is not changed here because this PR's scope is links and the generated-file note. No commit.
  3. P3 README.md:8, round 1: the ordering-dependency bullet named only github-settings AGENTS.md, while the atrinik-development skills also tell agents to run the publisher. Fixed in the PR body: both step-1 pull requests (tooling removal and skill correction) are named as the dependency. No commit.

@zoeyrose
zoeyrose marked this pull request as ready for review November 14, 2026 19:13
@zoeyrose zoeyrose self-assigned this Nov 14, 2026
@zoeyrose
zoeyrose requested a review from a team November 14, 2026 19:13
@zoeyrose
zoeyrose merged commit b1f3da0 into main Nov 14, 2026
3 checks passed
@zoeyrose
zoeyrose deleted the docs/profile-hand-edited branch November 14, 2026 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant