Skip to content

fix(registry): canonicalize julia-professional-registry entry to JuliaProfessionalRegistry (G22) - #44

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/axiom-jl-registry-infra-kr7t4a
Jul 1, 2026
Merged

fix(registry): canonicalize julia-professional-registry entry to JuliaProfessionalRegistry (G22)#44
hyperpolymath merged 1 commit into
mainfrom
claude/axiom-jl-registry-infra-kr7t4a

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

  • Companion to fix(identity): canonicalize to JuliaProfessionalRegistry (G22) julia-professional-registry#44 (same branch name claude/axiom-jl-registry-infra-kr7t4a) — renames this repo's record of that registry from the old HyperpolymathRegistry identity to the canonical JuliaProfessionalRegistry.
  • verisim/seed/repos.a2ml: [repo.HyperpolymathRegistry][repo.JuliaProfessionalRegistry].
  • worker/data/repos.json + worker/data/index.json: matching name/prefixed/github fields; github corrected to the real hyperpolymath/julia-professional-registry slug (previously pointed at a non-existent repo).
  • uuid untouched in all three files — this is a rename, not a new registration.

Known pre-existing issue (out of scope here)

worker/data's uuid (c9cbb683-...) does not match the uuid recorded in the repo's own CLADE.a2ml (2efe00c2-...). That's drift between the heuristic worker/data backfill (#40) and the authoritative per-repo CLADE.a2ml, unrelated to this identity rename — flagging for a separate fix rather than touching it here.

Test plan

🤖 Generated with Claude Code

…aProfessionalRegistry (G22)

Companion to the julia-professional-registry CLADE.a2ml rename in the same
branch. Renames the repo's record from the old HyperpolymathRegistry identity
to the canonical JuliaProfessionalRegistry name across:

- verisim/seed/repos.a2ml: [repo.HyperpolymathRegistry] -> [repo.JuliaProfessionalRegistry]
- worker/data/repos.json + worker/data/index.json: matching name/prefixed/github
  fields, and github corrected to the real hyperpolymath/julia-professional-registry
  slug (previously pointed at a non-existent repo).

uuid is left untouched in all three files — this is a rename, not a new
registration. NOTE: worker/data's uuid (c9cbb683-...) does not match the
uuid recorded in the repo's own CLADE.a2ml (2efe00c2-...); that's a
pre-existing drift between the heuristic worker/data backfill (#40) and the
authoritative per-repo CLADE.a2ml, unrelated to this identity rename — left
as-is, flagging for a separate fix.
@sonarqubecloud

sonarqubecloud Bot commented Jul 1, 2026

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review July 1, 2026 13:15
@hyperpolymath
hyperpolymath merged commit b96a5b0 into main Jul 1, 2026
20 of 21 checks passed
@hyperpolymath
hyperpolymath deleted the claude/axiom-jl-registry-infra-kr7t4a branch July 1, 2026 13:15
hyperpolymath added a commit to hyperpolymath/julia-professional-registry that referenced this pull request Jul 1, 2026
## Summary
- Canonicalizes this repo's identity to **JuliaProfessionalRegistry**,
resolving the three-way name conflict: `JuliaProfessionalRegistry`
(Registry.toml, already canonical), `HyperpolymathRegistry` (CLADE
`canonical-name` + `[forges]` + 21 doc files),
`julia-professional-registry` (actual repo slug).
- `CLADE.a2ml`: `canonical-name`/`prefixed-name` →
`JuliaProfessionalRegistry`; old name preserved in `status.aliases[]`;
uuid untouched.
- `[forges]`: corrected to the real
`hyperpolymath/julia-professional-registry` slug — the old entries
pointed at a GitHub repo that doesn't exist (404).
- Swept 21 doc/metadata files; GitHub clone URLs and the post-clone `cd`
target now point at the real slug rather than the fictional old name.
- `STATE.a2ml` project/name aligned; the "G22 pending" note is resolved.

## Companion PR
Coordinated with hyperpolymath/gv-clade-index#44 (same branch name
`claude/axiom-jl-registry-infra-kr7t4a`), which renames the matching
`[repo.HyperpolymathRegistry]` seed entry and worker data. Land together
to avoid desync.

## Test plan
- [x] `grep -rn HyperpolymathRegistry` — only the intentional
`aliases[]` entry and its explanatory comment remain
- [x] `tests/idris2/ValidateTest.idr` deliberately untouched (documents
historical bug, already asserts `JuliaProfessionalRegistry`)
- [ ] Owner review of the CLADE identity change

🤖 Generated with [Claude Code](https://claude.com/claude-code)
hyperpolymath added a commit that referenced this pull request Jul 2, 2026
…data (#46)

Found while double-checking the state of main after #44/#45 merged.
verisim/seed/repos.a2ml was NOT valid TOML — tomllib.load() errored
before this fix. Four bugs, all pre-existing (not introduced by #44/#45):

- [repo..git-private-farm] and [repo..github]: repo names starting with
  a literal dot produce an empty key segment between the two dots
  (repo + "" + git-private-farm) — a hard TOML parse error. Quoted:
  [repo.".git-private-farm"] / [repo.".github"].
- [repo.hyperpolymath.github.io] and [repo.EchoTypes.jl]: these parse
  (dots are valid bare-key separators) but as 3-level nested tables
  (repo.hyperpolymath.github.io, repo.EchoTypes.jl) instead of the
  clearly-intended single table keyed by the literal name — silently
  wrong structure, not a parse error. Every sibling .jl-suffixed entry
  in the file already quotes correctly (e.g. [repo."Axiom.jl"]); these
  two just missed it. Quoted to match.
- [repo.verisimdb-data] was declared TWICE (line 374, hand-curated:
  clade=db, completion=50; line 2650, from the 2026-06-25 heuristic
  backfill: clade=rm, completion=0) — TOML forbids redeclaring a table,
  so this alone made the file unparseable regardless of the key-quoting
  bugs above. Kept the original (line 374); removed the backfill
  duplicate. worker/data/repos.json's single verisimdb-data entry had
  the same problem in miniature (it held the backfill's clade=rm
  values) — reconciled to match the surviving canonical entry.

Verified: `python3 -c "import tomllib; tomllib.load(...)"` now succeeds
(319 repo entries) and worker/data/{repos,index}.json still validate as
JSON (JSON keys are always quoted, so it can't have the same key-parsing
bug, but repos.json's verisimdb-data value was wrong regardless).
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