# AmoosedWeb 0.27.0 compatibility

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

| Component | Version or contract | Platform and coupling |
| --- | --- | --- |
| Chrome extension | 0.27.0, Manifest V3, Chrome 116+ | Reads the current v1 carrier/index contract. Install or update it separately from a site deployment. |
| Site runtime | 0.27.0 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.0` | Node.js 22+; intended for Windows, Linux, macOS. `amoosedweb-cli@0.27.0` is a compatibility shim depending on the matching compiler and reader. |
| npm reader | `amoosedweb-reader@0.27.0` | Node.js 22+; reads verified resources but does not execute the app. |
| NuGet tool | `AmoosedWeb.Compiler 0.27.0` | .NET 10 tool, Windows x64 native executable. |
| NuGet reader | `AmoosedWeb.Reader 0.27.0` | .NET 10 library, Windows x64 runtime through an exact-version `AmoosedWeb.Native 0.27.0` dependency. |

The **wire format remains v1**. 0.27.0 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.0 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.0 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

Windows x64 local checks on 2026-10-23: Node tests passed (112 passed, one optional large test skipped); local Chromium journeys passed; the optional 32 MiB Chrome streaming scenario passed earlier in the same development cycle; the 0.27.0 Pages release and npm compiler/reader/shim package smoke passed; and the .NET reader listed and recovered the demo's 17 resources through the 0.27.0 native CLI. The Chromium automation does not drive the native side-panel gesture or system save picker; verify those manually. Linux and macOS package execution need their own machines or CI runs before labeling native archives for those systems as tested. No live Cloudflare or registry deployment is implied by this matrix.