How it works
There is no hidden service in the loop. The CLI writes files, the report explains what changed, and you keep control of the extension tree. The public claims are limited to the paths we have already run end-to-end.
Run the CLI against a local extension folder or a fixture tree. It finds manifest.json and the files that matter.
Convert the manifest, swap the common MV2 APIs, and keep ambiguous code paths visible as warnings.
Inspect the HTML output locally, validate it in Chrome, and decide what still needs manual work.
Verified end-to-end
Buying flow