v0.1.0

The first public release: an AI-native content management system in one
server binary plus PostgreSQL. Content is stored as structured blocks,
themes are data compiled to CSS with sandboxed templates, plugins are
WebAssembly components that can only do what they declare, and every
install browses the official marketplace and update channel out of the
box. Linux (x86_64, arm64) and macOS (arm64) archives, a multi-arch
container image, and the quick start in the README.

Since the second release candidate:

• curl -fsSL https://vyasa.site/install.sh | sh installs the release
  for your platform (checksum verified) into ~/vyasa and puts vyasa
  on your PATH; the one source is install.sh in this repository.
• The website moved to its own repository, vyasa-cms/website; it still builds its docs from docs/ here.
• Testing a site address (/setup/verify-url and the setup wizard's site
  step) only fetches public addresses, through the same guard as link
  checks and plugin fetches. A loopback or private address is reported as
  local and untested (local, site_url_local) instead of unreachable.
• Dependencies moved to their current majors: sqlx 0.9, wasmtime 49,
  zip 8, ed25519-dalek 3 and html5ever 0.40; the admin builds with vite 8,
  vitest 5 and TypeScript 6.
• The official marketplace (marketplace.vyasa.site) and update channel
  (updates.vyasa.site) are built in, trusted through keys compiled into
  the binary. The registry_url, registry_trusted_keys,
  update_channel_url and update_trusted_keys options and the setup
  wizard's updates step are gone; operators can mirror or switch either
  source off in vyasa.toml. Upgrade note: stored values of those
  options are deleted (migration 52).
• A theme carrying script must be signed to be uploaded by hand.
  vyasa theme pack builds and signs one. plugin_trusted_keys is now
  package_trusted_keys (the old name still works).
• Marketplace plugins are checked against the author key in their
  listing, so sites no longer need each author's key.

v0.1.0-rc.2

Second release candidate.

• Demo mode (VYASA_DEMO__ENABLED) for running a public sandbox, and a
  ready-made demo stack in deploy/demo/.
• The project website and documentation in website/.
• Upload endpoints describe their file field in the API reference.
• The release smoke test pulls every image it needs.