Skip to content

feat(registry): register rsr-julia-library-template-repo - #45

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/register-julia-template-repo
Jul 1, 2026
Merged

feat(registry): register rsr-julia-library-template-repo#45
hyperpolymath merged 1 commit into
mainfrom
claude/register-julia-template-repo

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

Registers the new rsr-julia-library-template-repo (a fork of rsr-template-repo, specialised for registered Julia libraries — see hyperpolymath/rsr-julia-library-template-repo#2) in the clade registry.

  • verisim/seed/repos.a2ml: new [repo.rsr-julia-library-template-repo] entry. lineage = "standalone" with parent = "rsr-template-repo"not "derived", that's not a valid lineage_type per repo.vcl's ENUM. "standalone" + non-empty parent already has precedent in this file (e.g. [repo.anvomidav]parent = "nextgen-languages").
  • worker/data/{repos,index}.json: matching entries, uuid 4b68a627-5811-4c73-bdad-052dfbdbbe90 (matches the repo's own CLADE.a2ml, generated fresh via uuid4() — not the deterministic-v5 scheme worker/data otherwise uses, consistent with the pre-existing uuid-scheme drift already flagged in fix(registry): canonicalize julia-professional-registry entry to JuliaProfessionalRegistry (G22) #44).

(This was originally a second commit on the claude/axiom-jl-registry-infra-kr7t4a branch, but #44 merged before I pushed it, so it's rebased onto current main as its own PR.)

Test plan

  • python3 -c "import json; json.load(...)" on both worker JSON files — valid
  • New TOML section validated in isolation (the seed file has a pre-existing, unrelated parse error at [repo..git-private-farm] — not touched here)
  • Owner review

🤖 Generated with Claude Code

New repo (fork of rsr-template-repo, specialised for registered Julia
libraries — see hyperpolymath/rsr-julia-library-template-repo#2).

- verisim/seed/repos.a2ml: new [repo.rsr-julia-library-template-repo]
  entry. lineage = "standalone" with parent = "rsr-template-repo" (not
  "derived" -- that's not a valid lineage_type per repo.vcl's ENUM;
  "standalone" + non-empty parent already has precedent in this file,
  e.g. [repo.anvomidav] parent = "nextgen-languages").
- worker/data/{repos,index}.json: matching entries, uuid
  4b68a627-5811-4c73-bdad-052dfbdbbe90 (matches the repo's own
  CLADE.a2ml, generated fresh via `uuid4()`, not the deterministic-v5
  scheme worker/data otherwise uses -- consistent with the pre-existing
  uuid-scheme drift already flagged in the companion G22 commit on this
  branch).
@sonarqubecloud

sonarqubecloud Bot commented Jul 1, 2026

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review July 1, 2026 21:03
@hyperpolymath
hyperpolymath merged commit f19b29c into main Jul 1, 2026
20 of 21 checks passed
@hyperpolymath
hyperpolymath deleted the claude/register-julia-template-repo branch July 1, 2026 21:04
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