Add new repository entry for veilos

[Investorquab]

What are you building?

VeilOS is a privacy control layer for Starknet. Before you shield, send
privately, or unshield through the live STRK20 pool, it shows exactly what
a normal transaction would expose (sender, recipient, amount, timing).
After the transaction, it runs "Attack My Privacy" — an honest, labeled
analysis (protected / observable / potential correlation / unable to
determine) using real Starkscan pool data, never an invented score.

The hard part wasn't the privacy math — STRK20 already handles that. It
was the operational reality of getting a brand-new wallet actually working
on mainnet: registration needs gas before it can register, Ready X and
Xverse enforce different connection-authorization ordering, and figuring
out which assets are actually live for shielding versus just documented
as "any ERC-20."

Who's building it?

Solo builder (Investorquab). Independent Starknet/EVM developer with
hackathon builds across other ecosystems (Celo, HSK Chain, Pharos,
GenLayer), including work as a technical teaching assistant at hackathon
events.

Checklist

• [✅ ] I added one object to registry.json and did not modify anyone else's entry
• [✅ ] slug is lowercase, hyphenated, and not already taken
• [✅ ] repo_url is public
• [✅] telegram has a bare username for everyone on the team

[github-actions]

This branch's registry.json could not be read - it has unresolved conflict markers, or it is not valid JSON. Fix it on the branch and this will pick it up again.

[Investorquab]

@starkience-team this PR has had "1 workflow awaiting approval" pending
for 4 days now (blocking Registrations/apply from running). Could someone
approve it so it can merge? Deadline is approaching. Thanks!