# AmoosedWeb 0.27.1 compatibility

This is the package and runtime compatibility record for the 0.27.1 source release. A local package build is not a registry publication.

| Component | Version or contract | Platform and coupling |
| --- | --- | --- |
| Chrome extension | 0.27.1, Manifest V3, Chrome 116+ | Reads the current v1 carrier/index contract. Install or update it separately from a site deployment. |
| Site runtime | 0.27.1 route export and generated site | Keep `/amoosed.com/` runtime files from one compiler build together. Host the virtual app fallback and service-worker scope at the same origin as the ordinary site. |
| npm compiler | `amoosedweb-compiler@0.27.1` | Node.js 22+; intended for Windows, Linux, macOS. `amoosedweb-cli@0.27.1` is a compatibility shim depending on the matching compiler and reader. |
| npm reader | `amoosedweb-reader@0.27.1` | Node.js 22+; reads verified resources but does not execute the app. |
| NuGet tool | `AmoosedWeb.Compiler 0.27.1` | .NET 10 tool, Windows x64 native executable. |
| NuGet reader | `AmoosedWeb.Reader 0.27.1` | .NET 10 library, Windows x64 runtime through an exact-version `AmoosedWeb.Native 0.27.1` dependency. |
| Native C/C++ Reader review | Windows x64 `AmoosedWebGameReader 0.28.17-preview`, C ABI revision `16`; Linux x64 `0.28.10-preview`, revision `14` | The Windows source build, callback transport fixture, SDK archive, and installed consumers pass locally. The older Linux archive remains at revision 14. Neither archive is a published SDK download. |
| Native .NET runtime review | `AmoosedWeb.GameReader.Native 0.28.17-preview` | Local Windows x64 prebuilt binary NuGet dependency for the native .NET Reader previews; not the published `AmoosedWeb.Native` package. |
| Native .NET Reader reviews | `AmoosedWeb.Reader.NativePreview 0.28.17-preview` and `AmoosedWeb.Reader.NativeDefaultPreview 0.28.17-preview` | Local .NET 10 review packages with an exact `AmoosedWeb.GameReader.Native 0.28.17-preview` dependency. Clean Windows x64 consumers pass; neither replaces the published CLI-backed Reader. |
| Native Node Reader review | Windows x64 `0.28.17-preview.1`; Linux x64 `0.28.14-preview.3` | Local Node-API tarballs. The Windows package uses revision 16 for standard and injected transports and omits its JavaScript codec fallback; the Linux package still uses revision 14. Neither replaces the published npm Reader. |

The **wire format remains v1**. 0.27.1 does not add a carrier mode or change the index/footer format. That gives an intended read path for 0.26.0 sites with a 0.27.1 reader, but a version number alone is not proof that every old or future combination works. Use `amw verify-site` and the host preflight with the actual site and key before updating a deployment. Build and publish the site runtime and carriers as one release; avoid mixing files from separate builds.

## Upgrade a generated project

1. Save the existing project and its `.amw/` private keys and release snapshots offline. Commit or stash project edits. Keep the keys out of Git and the Pages upload.
2. Install the 0.27.1 compiler from npm or NuGet when published. Confirm with `amw --version`.
3. Run `amw update-project YOUR_PROJECT`. It refuses a dirty Git tree, updates only unchanged starter files, and reports customized files for manual review. Commit the project update.
4. Build to a fresh output directory. Run `amw verify-site OUTPUT` and `amw check-host http://127.0.0.1:PORT/ KEY` against the local static host. For an external index, pass the `.amwkey` or ICO credential; for a hosted favicon index omit it.
5. Exercise the Chrome mode switch, external-key import, member unlock, download, and return path locally. Publish the verified Pages folder only after those checks.

`amw export-runtime OUTPUT` writes a version-matched route set for existing sites. Keep its `route-contract.json` beside the exported files as an integration checklist; it is not a public runtime route.

## Validation record

The 0.27.0 Windows x64 baseline passed local Chromium journeys and recovered the demo's 17 resources through its native CLI. For 0.27.1 on 2026-10-25, the Node suite passed 134 tests with one optional large test skipped; the local Pages release, npm package smoke, and package-license inventory passed. The Windows and Linux plain-C preview fixtures also passed protected-memory and carrier checks locally. The 0.27.1 change is a prospective licensing update and does not alter the v1 carrier format. The Chromium automation does not drive the native side-panel gesture or system save picker; verify those manually. Linux and macOS execution of the published npm/NuGet packages still needs its own consumer gate before those platforms are labeled supported. No live Cloudflare or registry deployment is implied by this matrix.