chore(governance): stop declaring repository identity in settings.yml

[hyperpolymath]

probot/settings applies this file on every push to the default branch, so the four identity
keys it declared are instructions, not documentation. The estate has already paid for exactly this:
.github/settings.yml once read name: "{{REPO}}", GitHub collapsed the illegal braces to dashes,
the repository renamed itself to -REPO- on every push, its old URL 404'd, and it was read as a
deleted repository.

This repo still declared name, description, homepage and private.

The repair is convergence on the source of truth, not new content:

• the header becomes the template's own header, which documents the incident and the rule
  ("THIS FILE MUST NEVER DECLARE REPOSITORY IDENTITY");
• the four identity keys are removed; everything else is unchanged — same repository settings,
  same 18 labels;
• repository identity and visibility stay set out of band, once, by the owner.

Verified with the estate's own gate, scripts/check-no-placeholders.sh, whose settings.yml guard
runs in template repos too (that exemption is how the original incident went unseen). On this
branch the guard reports clean.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 7d76d40c-5977-40cf-80a5-b9c24db8454d

📥 Commits

Reviewing files that changed from the base of the PR and between 867bd6a and 8f6c739.

📒 Files selected for processing (1)

• .github/settings.yml

 _________________________________________________________
< Eliminate bugs. Ship early. Sleep well. Pick all three. >
 ---------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud