feat: initial commit - Jhonny Editor

- Adicionado estrutura completa do projeto
- Configurado MCP server para Premiere Pro
- Adicionado documentação e skills
- Configurado Gitignore para o projeto

code/docs/uxp-hybrid-addon-receipt.md

@@ -0,0 +1,61 @@
+# UXP Hybrid addon-layout receipt
+
+Adobe's public Hybrid build guide requires a temporary Hybrid manifest with
+manifest version 6 or newer, `addon.name`, and
+`requiredPermissions.enableAddon`. Its documented bundle structure includes a
+root `main.js` entrypoint and one `.uxpaddon` at each of these bundle-relative
+paths:
+
+```text
+mac/x64/<addon name>.uxpaddon
+mac/arm64/<addon name>.uxpaddon
+win/x64/<addon name>.uxpaddon
+```
+
+The production panel deliberately remains manifest v5 with no addon declaration
+or addon permission. Do not run this procedure against `uxp-plugin/`; use a
+separate, local development bundle after obtaining an authorized Hybrid SDK.
+
+`npm run native:hybrid-addon-receipt` reads that local bundle and an already
+verified Hybrid SDK header receipt. Its current schema-v2 output records the
+root entrypoint's relative path, byte count, and SHA-256 digest alongside the
+three addon artifacts, minimal manifest facts, and canonical header-receipt
+digest. It does not copy or parse the development entrypoint or manifest, or
+copy addon binaries, SDK headers, archive, absolute paths, signing material,
+or host responses.
+
+```powershell
+npm run native:hybrid-addon-receipt -- `
+  --plugin-root C:\hybrid-evidence\benchmark-plugin `
+  --sdk-header-receipt C:\hybrid-evidence\uxp-hybrid-headers.json `
+  --output C:\hybrid-evidence\benchmark-addon-layout.json
+```
+
+Use `--validate-only` to examine the local bundle without producing a receipt,
+or `--check` to compare a regenerated receipt with a reviewed local file. A
+reviewer who has access to both local receipts can verify the binding without
+receiving the development bundle:
+
+```powershell
+npm run native:hybrid-addon-receipt:verify -- `
+  --input C:\hybrid-evidence\benchmark-addon-layout.json `
+  --sdk-header-receipt C:\hybrid-evidence\uxp-hybrid-headers.json `
+  --print-canonical-sha256
+```
+
+The verifier accepts existing schema-v1 receipts, which intentionally contain
+only the three addon artifacts, and current schema-v2 receipts with exactly one
+root `main.js` entrypoint. It does not invent an entrypoint for v1 receipts.
+New generation always produces v2.
+
+The verifier checks the documented layout and the supplied header-receipt
+identity. It does **not** prove that `main.js` requires an addon, that a binary
+was compiled with the SDK, has the advertised architecture, is signed or
+notarized, can load in UXP Developer Tool, exposes the benchmark adapter, is an
+MCP capability, or behaves in a licensed Premiere host. Those remain separate
+build, signing, UDT installation, and licensed-host gates. It records a valid
+manifest `host.minVersion` (the build guide's example is 25.6); the separate
+benchmark evidence requires the actual Premiere host to be 26.2 or newer.
+
+Official references: [Hybrid Plugins](https://developer.adobe.com/premiere-pro/uxp/plugins/hybrid-plugins/)
+and [Building Hybrid Plugins](https://developer.adobe.com/premiere-pro/uxp/plugins/hybrid-plugins/build).