ci+extension: release follow-ups (workflow contents:write + LICENSE)

Two follow-ups discovered after v0.1.0 published to Open VSX:

1. .github/workflows/publish-extension.yml: contents:read -> contents:write
   The "Attach .vsix files to GitHub Release" step in the publish job
   needs write access to repos/<owner>/<repo>/releases. Under contents:
   read it fails with HTTP 403 "Resource not accessible by integration",
   leaving the marketplace publish itself fine but no Release page +
   attached .vsix bundles for sideload distribution.

2. extension/LICENSE: MIT copy from repo root
   vsce package emits 'WARNING: LICENSE, LICENSE.md, or LICENSE.txt not
   found' because vsce only looks inside the package root (extension/),
   not at repo root. Copy keeps both surfaces in sync (same MIT text).

Both changes are CI/packaging only — no extension code or runtime
behaviour affected. Effective from the next tag push (extension-v0.1.1
or whatever the next release is).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: George-iam

.github/workflows/publish-extension.yml

@@ -19,7 +19,7 @@ on:
   workflow_dispatch:
 
 permissions:
-  contents: read
+  contents: write
 
 jobs:
   build:

extension/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 AXME AI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.