Upgrade and archived documentation

These guides describe verified published TypeScript packages, audited against 549b9870acb6af239faf79245179a4f1f7e60cdb. This is not a compatible update to the old Rust Host/Capability runtime. Installation records the exact release matrix and protocol peers.

From TypeScript 0.1.0 to the current matrix

1. Record the application's lockfile, exact installed exports and runtime host. Source version strings alone are insufficient.
2. Select the verified published matrix: Core/Engine and principal adapters 0.2.0, CLI 0.19.0, DB/Storage 0.1.1. Retain exact versions and the lockfile; do not replace only one transitive dependency with latest. If using source-built vendor archives, build all of them from the same pinned revision.
3. Review configuration preflight and new resource lifetime behavior. Source bindConfig reads sources before business setup; inspection still executes trusted module top-level code.
4. Upgrade oRPC client and server to 2.0.0-beta.42 together. The source has no v1 wire compatibility path. Review middleware repetition and client fetch behavior.
5. For Bun HTTP, review the public /bun listener and explicit ingress policy. Listener availability does not make its loopback example a production ingress policy.
6. Existing one-input operations remain supported. For contextual operations, declare context: true and supply trusted per-call binding. Review optional Manage, confirmation/approval gates and independent CLI/MCP selections; descriptor metadata never grants service authorization.
7. Run focused service/entry tests and regenerate owned outputs. Review migration histories separately; package upgrade does not apply database migrations.

See configuration, Web, Auth and testing. Check actual registry artifacts before selecting the new source package versions; a source release commit alone does not establish npm availability. Manage is implemented as an optional finite-operation adapter, not a persistent control plane or automatic Console integration.

From the Rust generation

Treat this as application migration, not a package rename. Inventory business services, stored data, authentication audiences, ownership policies and host effects. Reassemble ordinary TypeScript plugins with exact dependencies and cleanup. Move one entry at a time and test its shared service policy. Do not copy old Cargo/Host/Capability or dynamic Marketplace commands into a TypeScript application.

No automatic Rust-to-TypeScript migrator or data conversion tool is provided. Preserve old data and review schema/identity changes explicitly. The existing Notes/Tasks cases demonstrate new boundaries; they do not automatically migrate arbitrary old applications.

Where the old pages went

Old documentation is retained under legacy/rust-site/content in this repository and remains readable at the pre-refactor source snapshot. It is excluded from the current sidebar, search, Markdown catalog and sitemap. This preserves history without presenting retired contracts as current facts.

Former documentation routes redirect to this migration page in the same language. The redirect explains the generation change rather than claiming an exact tutorial correspondence. Old site/Marketplace source is also retained under legacy/rust-site; it is inactive in the docs CLI build. No Marketplace host cutover, catalog trust change or Console/Relay migration is part of this documentation update.

For a deployed old application, use its version-matched archive and installed artifacts. For a new TypeScript application, start with Quickstart.