Claiming namespace arkenstone-labs

### Namespace

arkenstone-labs

### Ownership

- [x] The namespace is not currently owned on Open VSX.

### 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 and has an extension published there with a repository specified in its `package.json`.

### Claim evidence

The `arkenstone-labs` namespace is the publisher of AppliedML LSP on both registries:

- VS Code Marketplace publisher: https://marketplace.visualstudio.com/publishers/arkenstone-labs
- VS Code Marketplace extension: https://marketplace.visualstudio.com/items?itemName=arkenstone-labs.appliedml
- Open VSX extension: https://open-vsx.org/extension/arkenstone-labs/appliedml
- Extension repository: https://github.com/arkenstone-lab/amlc-lsp
- Commit authored by the requesting GitHub ID (`chris-in-the-shell`): https://github.com/arkenstone-lab/amlc-lsp/commit/7c58369ddddf0dbd7563347e4c15a1f7f86d969b

The extension manifest identifies the repository above and uses `arkenstone-labs` as its publisher. I am requesting owner access so the namespace and its published extension can be shown as verified.

Review the linked VS Code Marketplace publisher, Open VSX extension, and extension repository, especially the package.json repository and publisher entries. Confirm that the namespace is unowned and that the supplied commit ties the requester to the repository. Done means granting owner access so the namespace and extension can be shown as verified.

Written by the indexing model from the issue text.