Claiming namespace ferrite-engineering

### Namespace

ferrite-engineering

### Ownership

- [x] The namespace is not currently owned on Open VSX (verify by a search on [open-vsx.org](https://open-vsx.org))

### Account Age

- [x] The GitHub ID making this request has at least 12 months of public history

### VS Code Publisher with Repo

- [x] The namespace is also a publisher account on the VS Code Marketplace (check by browsing https://marketplace.visualstudio.com/publishers/{publisher}) and has an extension published there with a repo specified in its package.json file.

### VS Code Publisher without Repo

- [ ] The namespace is also a publisher account on the VS Code Marketplace and does not have published extensions or has published extensions with no GitHub repos.

### Not a VS Code Marketplace Publisher

- [ ] The namespace is not a publisher account on the VS Code Marketplace

### All Other Cases

- [ ] You are unable to provide the inputs required in the three options above. This option will take the longest to process.

### Claim evidence

**Option 1 — VS Code Publisher with Repo.** Sub-option selected:

- [x] The extension repo, public or private, is owned by the GitHub ID making this request (same org)

Evidence:

- **Open VSX namespace:** `ferrite-engineering` — created via `ovsx create-namespace`, currently `"verified": false`.
- **VS Code Marketplace publisher:** `ferrite-engineering` ("Ferrite Engineering") — https://marketplace.visualstudio.com/publishers/ferrite-engineering
- **Five extensions published 2026-09-12**, each carrying `repository.url` = `https://github.com/Ferrite-Engineering/crux-vscode.git` in its `package.json`:
- `ferrite-engineering.wavecrux`
- `ferrite-engineering.lintcrux`
- `ferrite-engineering.simcrux`
- `ferrite-engineering.netcrux`
- `ferrite-engineering.edacrux` (extension pack)

All five are published at 0.1.0 on both the VS Code Marketplace and Open VSX.
- **Repository ownership:** `Ferrite-Engineering/crux-vscode` is owned by the GitHub organization **Ferrite-Engineering**. The GitHub ID making this request, **@martin-robert-fink**, is an **owner/admin** of that organization (GitHub account created 2017-09-08, ~9 years of public history).
- **Repository visibility:** `crux-vscode` is currently **private**; it becomes public with our 1.0 open-core release later this month. Option 1's selected sub-option explicitly admits a repo that is "public or private" so long as it is owned by the same org, which is the case here. Happy to supply any additional proof of org ownership the reviewers would like in the meantime.
- **Eclipse identity:** Eclipse account `martinfink` (uid 758615); Eclipse Publisher Agreement `open-vsx` v1.1 signed; the Eclipse profile's GitHub handle is `martin-robert-fink`, matching the Open VSX login used to create the namespace.

The namespace matches the Marketplace publisher name exactly, so there is no risk of confusion between extensions published on the VS Code Marketplace and those on Open VSX — they are the same five extensions from the same publisher.

Verify the ferrite-engineering namespace on open-vsx.org, the matching VS Code Marketplace publisher, and ownership of Ferrite-Engineering/crux-vscode by @martin-robert-fink. Check the listed repository URLs and organization ownership; done means the evidence supports approving the namespace claim.

Written by the indexing model from the issue text.