New extension: CobaltVDisk

[kx1bx1]

CobaltVDisk is an enhancement of rxFS by 0832. Its main focus is speed improvements and new features like file size limits, permissions, and more. While I'm planning and coding for CobaltVDisk, I've decided to create this PR now with a 'placeholder' commit, and that's why /extensions/kx1bx1/cobaltvdisk.js is empty right now.

The versioning scheme

CobaltVDisk uses a structured, time-based versioning scheme; full details will be documented once implementation is complete. TL;DR: You don't have to read this.

CobaltVDisk goes by a '3-monthly' update schedule. If any changes to CobaltVDisk were made by me, a PR will be made as a 'cumulative update' to CobaltVDisk.

Every CobaltVDisk update string looks like this:

XX(H)Z, Checkpoint Y

X: The two digits of the year (2025 -> 25)
Z: The 'half' of the year (December -> 2)
Y: The number of prior releases (i. e. Checkpoint 1 -> Checkpoint 2)

Why use the MIT license?

My choice of using the MIT license instead of the GPL-3.0 license is not only due to brevity, but also due to the fact that I want CobaltVDisk to be aligned with TurboWarp’s existing ecosystem and extension practices. MIT is rather open and easy to understand for users, and it's quite permissive, so that's what I used.

Full disclosure: this extension was LLM-generated

TL;DR: You don't have to read this if you do not care about LLM-generated code. If it writes bad code, it won't be accepted anyway.

This extension's code is purely LLM-generated. When I say this, I do not mean I only generated it in one prompt. I bring my models to a high standard, and you could probably count 50 prompts that assess security, stability, and speed with CobaltVDisk. If AI-generated code is used, it should meet or exceed human-quality standards.

Models used:

1. Primarily Gemini 3.0 Pro
2. Gemini 2.5 Pro (initial development)
3. GPT 5.0, 5.1, and 5.2 (bug testing)

I do intend to do the 'ultimate test' of CobaltVDisk by creating a project which primarily uses it, to ensure I can mark this PR ready-to-review.

Why so few commits?

This PR is planned to only have 5-10 commits because one commit is supposed to be one CobaltVDisk update after development is finished. This PR will be squashed or rebased once development is complete.

About this PR

• This extension shows properly in the Extensions Gallery
• This extension was properly linted
• This extension was properly formatted
• This extension was properly validated
• Development for this extension is finished

These are relatively easy checks to pass because, well, the 'extension' code is literally just comments until I finish development.

Planned features

In this context, "Completed" does not mean "Added to this branch". It means that the feature is done on my side. I don't commit new features to this PR.

Feature	Priority	Status
Core filesystem operations	High	Completed
Filesystem import and export	High	Completed
Permissions system	High	Completed
Per-sprite permissions (ACL)	Medium	Completed
New features	Medium	Completed
User experience improvements	Medium	Completed
Extension banner	Medium	Completed
Extension documentation	Low	Completed
Testing	High	Not started