16f-rename-ultraviolet: rename the product in README and NOTICE prose - #10
Merged
Conversation
The product is Ultraviolet. This renames the product name in prose on the two
public surfaces and changes nothing else. Two files, 25 insertions, 25 deletions.
README.md -- 23 occurrences of HackTUI become Ultraviolet. Includes the H1 at
:313 (`# Running HackTUI`, a heading outside the fence, which opens at :317)
and the clone URL and `cd` lines at :209-210, which ARE inside a ```bash
fence and are renamed by owner decision because the repository is already
github.com/HackTuah/Ultraviolet. The old URL redirects, which is why it read
fine and was still stale.
NOTICE -- 2 occurrences at :1 and :4. Added to scope mid-review after a
reviewer found that README:966 directs the reader to NOTICE for attribution
while NOTICE still named the old product: the two agreed before this commit
and would not have after it.
Identifiers are deliberately untouched: hacktui_ 36 -> 36 and HACKTUI_ 7 -> 7 in
README, holytrinity 2 -> 2 tree-wide. Those belong to the script slice (SCR-71),
which does not exist yet -- `ls tools/rename` fails at this tree -- so the
tree-reproduction proof that slice carries is not applicable to this commit and
was not asked of it.
Five review rounds, two independent reviewers per round on the same tree. Round 5
returned a split verdict: r1 PASS, r2 FAIL on one finding -- FINDINGS.md:82's
"occurrence counts" heading also covering two `wc -l` line counts -- which the
owner dispositioned residual, evidence correct and one word wrong. No round 6, no
edit. Remaining residuals R-2, R-3, R-4, R-A, R-B, R-C are held for owner.
Evidence in internal/slices/16f-rename-ultraviolet/FINDINGS.md: every count pair
before and after, command-written, re-derived independently by both round-5 lanes
and closed against the diff stat (README 23+23 = 46, NOTICE 2+2 = 4).
Issue: SCR-71. Milestone 3a.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VNdY6wVS773UJgrHUeBN3Y
Reviewed-diff: sha256:311107009372da129a9821f3efc52ff81cb94a782373c67dd5d5a67fcc2a840e
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
1 participant
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.
Prose rename of the product name on the two public surfaces. Two files, 25 insertions, 25 deletions. No behaviour change.
README.md — 23 occurrences of HackTUI become Ultraviolet, including the H1 at
:313(outside the fence, which opens at:317) and the clone URL andcdlines at:209-210, which are inside a ```bash fence and are renamed by owner decision because the repository is alreadygithub.com/HackTuah/Ultraviolet. The old URL redirects, which is why it read fine and was still stale.NOTICE — 2 occurrences at
:1and:4. Added to scope mid-review:README:966directs the reader to NOTICE for attribution, so renaming one without the other would have broken a cross-reference that agreed before this commit.Identifiers are deliberately untouched —
hacktui_36 → 36,HACKTUI_7 → 7,holytrinity2 → 2 tree-wide. Those belong to the script slice (SCR-71), which does not exist yet:ls tools/renamefails at this tree. The tree-reproduction proof that slice carries therefore does not apply to this commit and was not asked of it.Review
Five rounds, two independent reviewers per round on the same tree. Round 5 returned a split verdict — r1 PASS, r2 FAIL on one finding (
FINDINGS.md:82's "occurrence counts" heading also covering twowc -lline counts) — which the owner dispositioned residual: evidence correct, one word wrong. No round 6, no edit. Residuals R-2, R-3, R-4, R-A, R-B, R-C are held for owner.The commit's tree is
0ca6aa9b403da36de41af3fa4449efecb8150088, which is exactly the tree both round-5 lanes read and the treeREVIEW.signoffcertifies. No drift between review and commit.Evidence:
internal/slices/16f-rename-ultraviolet/FINDINGS.md— every count pair before and after, command-written, re-derived independently by both lanes and closed against the diff stat (README 23+23 = 46, NOTICE 2+2 = 4).Issue: SCR-71. Milestone 3a.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VNdY6wVS773UJgrHUeBN3Y