chore: created docs 0.9.x (#1184)

## Description

Step 10/11 of the minor release process: snapshots the current docs into
`docs/versioned_docs/version-0.9.x/` via `yarn docs:version 0.9.x`.
Source-code references pinned to SHA `0e95b8934` (the commit
`release/0.9` was cut from). Adds `0.9.x` to `docs/versions.json` and
creates the matching `versioned_sidebars/version-0.9.x-sidebars.json`.
Audited: zero `/blob/main/` refs survived the rewrite, zero broken
cross-links across 480 versioned files.

> [!IMPORTANT]
> Merge AFTER v0.9.0 has been published to npm. The docs publish
workflow ships the merged docs immediately, and we don't want users to
see v0.9.x docs that point at unreleased code.

### Introduces a breaking change?

- [ ] Yes
- [x] No

### Type of change

- [ ] Bug fix (change which fixes an issue)
- [ ] New feature (change which adds functionality)
- [x] Documentation update (improves or adds clarity to existing
documentation)
- [ ] Other (chores, tests, code style improvements etc.)

### Tested on

- [ ] iOS
- [ ] Android

### Testing instructions

N/A — pure docs versioning snapshot, no runtime change.

### Screenshots

### Related issues

### Checklist

- [x] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [x] I have updated the documentation accordingly
- [x] My changes generate no new warnings

Author: msluszniak

docs/versioned_docs/version-0.9.x/01-fundamentals/01-getting-started.md

@@ -0,0 +1,216 @@
+---
+title: Getting Started
+slug: /fundamentals/getting-started
+keywords:
+  [
+    react native,
+    react native ai,
+    react native llm,
+    react native qwen,
+    react native llama,
+    react native executorch,
+    executorch,
+    on-device ai,
+    pytorch,
+    mobile ai,
+  ]
+description: 'Get started with React Native ExecuTorch - a framework for running AI models on-device in your React Native applications.'
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+## What is ExecuTorch?
+
+[ExecuTorch](https://executorch.ai) is a novel AI framework developed by Meta, designed to streamline deploying PyTorch models on a variety of devices, including mobile phones and microcontrollers. This framework enables exporting models into standalone binaries, allowing them to run locally without requiring API calls. ExecuTorch achieves state-of-the-art performance through optimizations and delegates such as Core ML and XNNPACK. It provides a seamless export process with robust debugging options, making it easier to resolve issues if they arise.
+
+## React Native ExecuTorch
+
+React Native ExecuTorch is our way of bringing ExecuTorch into the React Native world. Our API is built to be simple, declarative, and efficient. Additionally, we provide a set of pre-exported models for common use cases, so you don't have to worry about handling exports yourself. With just a few lines of JavaScript, you can run AI models (even LLMs 👀) right on your device—keeping user data private and saving on cloud costs.
+
+## Compatibility
+
+React Native Executorch supports only the [New React Native architecture](https://reactnative.dev/architecture/landing-page).
+
+If your app still runs on the old architecture, please consider upgrading to the New Architecture.
+
+For supported React Native and Expo versions, see the [Compatibility table](../07-other/01-compatibility.mdx).
+
+## Installation
+
+Installation takes two steps: install the core package, then install a resource fetcher adapter that matches your project type. If you want to implement your own model fetching logic instead, see [this document](../08-resource-fetcher/02-custom-adapter.md).
+
+### 1. Install the core package
+
+<Tabs groupId="package-manager">
+  <TabItem value="npm" label="npm">
+
+    ```bash
+    npm install react-native-executorch
+    ```
+
+  </TabItem>
+  <TabItem value="pnpm" label="pnpm">
+
+    ```bash
+    pnpm add react-native-executorch
+    ```
+
+  </TabItem>
+  <TabItem value="yarn" label="yarn">
+
+    ```bash
+    yarn add react-native-executorch
+    ```
+
+  </TabItem>
+</Tabs>
+
+### 2. Install a resource fetcher
+
+Pick the adapter that matches your project. We recommend the Expo adapter when your app uses Expo; use the bare adapter for projects without Expo.
+
+#### Expo projects
+
+<Tabs groupId="package-manager">
+  <TabItem value="npm" label="npm">
+
+    ```bash
+    npm install react-native-executorch-expo-resource-fetcher expo-file-system expo-asset
+    ```
+
+  </TabItem>
+  <TabItem value="pnpm" label="pnpm">
+
+    ```bash
+    pnpm add react-native-executorch-expo-resource-fetcher expo-file-system expo-asset
+    ```
+
+  </TabItem>
+  <TabItem value="yarn" label="yarn">
+
+    ```bash
+    yarn add react-native-executorch-expo-resource-fetcher expo-file-system expo-asset
+    ```
+
+  </TabItem>
+</Tabs>
+
+#### Bare React Native projects
+
+<Tabs groupId="package-manager">
+  <TabItem value="npm" label="npm">
+
+    ```bash
+    npm install react-native-executorch-bare-resource-fetcher @dr.pogodin/react-native-fs @kesha-antonov/react-native-background-downloader
+    ```
+
+  </TabItem>
+  <TabItem value="pnpm" label="pnpm">
+
+    ```bash
+    pnpm add react-native-executorch-bare-resource-fetcher @dr.pogodin/react-native-fs @kesha-antonov/react-native-background-downloader
+    ```
+
+  </TabItem>
+  <TabItem value="yarn" label="yarn">
+
+    ```bash
+    yarn add react-native-executorch-bare-resource-fetcher @dr.pogodin/react-native-fs @kesha-antonov/react-native-background-downloader
+    ```
+
+  </TabItem>
+</Tabs>
+
+:::warning
+Before using any other API, you must call `initExecutorch` with a resource fetcher adapter at the entry point of your app:
+
+```js
+import { initExecutorch } from 'react-native-executorch';
+import { ExpoResourceFetcher } from 'react-native-executorch-expo-resource-fetcher';
+// or BareResourceFetcher for bare react-native projects
+
+initExecutorch({ resourceFetcher: ExpoResourceFetcher });
+```
+
+Calling any library API without initializing first will throw a `ResourceFetcherAdapterNotInitialized` error.
+:::
+
+Our library offers support for both bare React Native and Expo projects. Please follow the instructions from [Loading models section](./02-loading-models.md) to make sure you setup your project correctly. We encourage you to use Expo project if possible. If you are planning to migrate from bare React Native to Expo project, the link (https://docs.expo.dev/bare/installing-expo-modules/) offers a guidance on setting up Expo Modules in a bare React Native environment.
+
+If you plan on using your models via require() instead of fetching them from a url, you also need to add following lines to your `metro.config.js`:
+
+```json
+// metro.config.js
+...
+    defaultConfig.resolver.assetExts.push('pte')
+    defaultConfig.resolver.assetExts.push('bin')
+...
+```
+
+This allows us to use binaries, such as exported models or tokenizers for LLMs.
+
+:::warning
+When using Expo, please note that you need to use a custom development build of your app, not the standard Expo Go app. This is because we rely on native modules, which Expo Go doesn’t support.
+:::
+
+:::info
+Because we are using ExecuTorch under the hood, you won't be able to build iOS app for release with simulator selected as the target device. Make sure to test release builds on real devices.
+:::
+
+Running the app with the library:
+
+<Tabs groupId="package-manager">
+  <TabItem value="npm" label="npm">
+
+    ```bash
+    npm run <ios|android> -- -d
+    ```
+
+  </TabItem>
+  <TabItem value="pnpm" label="pnpm">
+
+    ```bash
+    pnpm <ios|android> -d
+    ```
+
+  </TabItem>
+  <TabItem value="yarn" label="yarn">
+
+    ```bash
+    yarn <ios|android> -d
+    ```
+
+  </TabItem>
+</Tabs>
+
+## Building from source
+
+To build the library from source instead, clone the repository and initialize submodules:
+
+```bash
+git clone -b release/0.9 https://github.com/software-mansion/react-native-executorch.git
+cd react-native-executorch
+
+git submodule update --init --recursive packages/react-native-executorch/third-party/common
+
+yarn
+```
+
+## Supporting new models in React Native ExecuTorch
+
+Adding new functionality to the library follows a consistent three-step integration pipeline:
+
+1. **Model Serialization:** Export PyTorch model for a specific task (e.g. object detection) into the `*.pte` format, which is optimized for the ExecuTorch runtime.
+
+2. **Native Implementation:** Develop a C++ execution layer that interfaces with the ExecuTorch runtime to handle inference. This layer also manages model-dependent logic, such as data pre-processing and post-processing.
+
+3. **TS Bindings:** Finally, implement a TypeScript API that bridges the JavaScript environment to the native C++ logic, providing a clean, typed interface for the end user.
+
+## Good reads
+
+If you want to dive deeper into ExecuTorch or our previous work with the framework, we highly encourage you to check out the following resources:
+
+- [ExecuTorch docs](https://pytorch.org/executorch/stable/index.html)
+- [React Native RAG](https://blog.swmansion.com/introducing-react-native-rag-fbb62efa4991)
+- [Offline Text Recognition on Mobile: How We Brought EasyOCR to React Native ExecuTorch](https://blog.swmansion.com/bringing-easyocr-to-react-native-executorch-2401c09c2d0c)

docs/versioned_docs/version-0.9.x/01-fundamentals/02-loading-models.md

@@ -0,0 +1,133 @@
+---
+title: Loading Models
+---
+
+import Tabs from '@theme/Tabs';
+import TabItem from '@theme/TabItem';
+
+There are three different methods available for loading model files, depending on their size and location.
+
+## Prerequisites
+
+In our library, you can use two different resource fetching mechanisms. One is implemented using Expo FileSystem, the other one uses external library. We encourage you to use implementation utilizing Expo if possible.
+
+To use the Expo adapter, please add these libraries:
+
+<Tabs groupId="package-manager">
+  <TabItem value="npm" label="npm">
+
+    ```bash
+    npm install react-native-executorch-expo-resource-fetcher expo-file-system expo-asset
+    ```
+
+  </TabItem>
+  <TabItem value="pnpm" label="pnpm">
+
+    ```bash
+    pnpm add react-native-executorch-expo-resource-fetcher expo-file-system expo-asset
+    ```
+
+  </TabItem>
+  <TabItem value="yarn" label="yarn">
+
+    ```bash
+    yarn add react-native-executorch-expo-resource-fetcher expo-file-system expo-asset
+    ```
+
+  </TabItem>
+</Tabs>
+
+and then add the following code in your React Native app:
+
+```typescript
+import { initExecutorch } from 'react-native-executorch';
+import { ExpoResourceFetcher } from 'react-native-executorch-expo-resource-fetcher';
+
+initExecutorch({
+  resourceFetcher: ExpoResourceFetcher,
+});
+```
+
+If you cannot use Expo in your project, proceed with the following steps:
+
+<Tabs groupId="package-manager">
+  <TabItem value="npm" label="npm">
+
+    ```bash
+    npm install react-native-executorch-bare-resource-fetcher @dr.pogodin/react-native-fs @kesha-antonov/react-native-background-downloader
+    ```
+
+  </TabItem>
+  <TabItem value="pnpm" label="pnpm">
+
+    ```bash
+    pnpm add react-native-executorch-bare-resource-fetcher @dr.pogodin/react-native-fs @kesha-antonov/react-native-background-downloader
+    ```
+
+  </TabItem>
+  <TabItem value="yarn" label="yarn">
+
+    ```bash
+    yarn add react-native-executorch-bare-resource-fetcher @dr.pogodin/react-native-fs @kesha-antonov/react-native-background-downloader
+    ```
+
+  </TabItem>
+</Tabs>
+
+and
+
+```typescript
+import { initExecutorch } from 'react-native-executorch';
+import { BareResourceFetcher } from 'react-native-executorch-bare-resource-fetcher';
+
+initExecutorch({
+  resourceFetcher: BareResourceFetcher,
+});
+```
+
+## Loading
+
+### Load from React Native assets folder (for files < 512MB)
+
+```typescript
+useExecutorchModule({
+  modelSource: require('../assets/lfm2_5.pte'),
+});
+```
+
+### Load from remote URL
+
+For files larger than 512MB or when you want to keep size of the app smaller, you can load the model from a remote URL (e.g. HuggingFace).
+
+```typescript
+useExecutorchModule({
+  modelSource: 'https://.../lfm2_5.pte',
+});
+```
+
+### Load from local file system
+
+If you prefer to delegate the process of obtaining and loading model and tokenizer files to the user, you can use the following method:
+
+```typescript
+useExecutorchModule({
+  modelSource: 'file:///var/mobile/.../lfm2_5.pte',
+});
+```
+
+:::note
+The downloaded files are stored in documents directory of your application.
+:::
+
+## Predefined Models
+
+Our library offers out-of-the-box support for multiple models. To make things easier, we created aliases for our model exported to `pte` format. For full list of aliases, check out: [API Reference](../06-api-reference/index.md#models---classification)
+
+## Example
+
+The following code snippet demonstrates how to load model and tokenizer files using `useLLM` hook:
+
+```typescript
+import { models, useLLM } from 'react-native-executorch';
+const llm = useLLM({ model: models.llm.lfm2_5_1_2b_instruct() });
+```