Registrations blocked - broken entry in registry.json (Portablelle/veilance-market)

[Leequidice]

validate-registry.mjs fails on the full merged registry because entry for https://github.com/Portablelle/veilance-market returns 404 (repo is private, renamed, or deleted). Since the validator checks the whole array, not just new entries, this is currently blocking every open registration PR, including mine (#95 - registry.json does not validate).

Confirmed independently by running scripts/validate-registry.mjs locally against a fresh merge of main + my branch.

[BlackAporia]

Same situation on our side (GameShield #86): blocked solely by the dead Portablelle/veilance-market row still on main. The removal PR is #93 — it passes both validators but the registration bot skips it because it touches 2 files, so it needs a maintainer merge. Merging it should let #86/#95/#97/#98/#99 and the rest flow through unattended.

[shariqazeem]

Also blocked by this — Aether (#98).

The Registrations bot merges my branch cleanly (merged: 63 on main, 1 added (shariqazeem/aether-strk20), 0 updated) and explicitly reports my own entry as fine, then stops on the pre-existing entry #36 and logs not applied this run. So the failure is entirely in the row already on main, not in any of the queued branches.

That now makes at least four of us hitting the identical wall (#86, #95, #97, #98), and there are 18 open registration PRs — the oldest from 15 Aug. Nothing has been applied since #85 on 17 Aug 10:54.

Merging #93 should clear the whole queue in one action: it is a push to main touching registry.json, which re-triggers Registrations and re-scans every open PR, so none of us needs to re-push.

[starkience]

Fixed, and the queue is clear.

What was wrong. validate-registry.mjs checks every entry in the file rather than the ones a pull request touches. When Portablelle/veilance-market started answering 404 it therefore failed every registration behind it. @Leequidice's diagnosis was exactly right, and none of you could have fixed it - you add one row and have no business editing somebody else's.

Done:

• chore: remove unavailable Veilance Market registry entry #93 applied, with the removal recorded in registry-removals.json. That unblocked the queue.
• The validator now compares against main. A problem with a row that is already there is reported and the run passes; a problem with an entry your change introduces still fails it. So this cannot happen again.
• Registrations that were only ever blocked by this have been applied.

Four needed hand-repair because their registry.json did not parse - a stray ],, a duplicated brace, a strk20.json pasted inside an entry. The bot resolves conflicts, but it cannot read a file that is not JSON. Those entries were taken from the branches and added: Adyton (#72), Tacit (#58), Veilfolio (#52), solmate (#50).

One is still out. builder-of-web3/Alias (#61) answers 404. Make the repository public and it will apply itself on the next run.

Nothing needs re-pushing.

[odinfree]

its KOIs fault.

[Portablelle]

its KOIs fault.

Always