multimodel-dev-os 1.0.0 → 2.0.0

package/docs/release-policy.md

@@ -31,3 +31,29 @@ No package shall be merged or released without:
 - Building the documentation site without dead links (`npm run docs:build`).
 - Running packaging validation (`npm pack --dry-run`).
 - Executing smoke tests on all templates.
+
+---
+
+## 4. NPM Publishing Pause & Roadmap Development
+
+To ensure high stability and thorough testing of the Template Galaxy and Model Compatibility Layers, package publishing to the public npm registry is paused during all `v1.2.x` minor releases:
+* **GitHub Repository (Source)**: Serve as the primary, active source branch containing unreleased v1.2+ features (such as template extensions, model registries, and CLI expansions).
+* **NPM Registry (Latest)**: Remains on the last approved stable version.
+* **v2.0.0 (Next Target)**: Will serve as the next stable release published to the npm registry, packaging the hardened registries and Template Galaxy features.
+
+### Local Source & Verification Procedures
+
+Contributors and developers must verify and test unreleased `v1.2.x` features locally rather than running publication steps:
+1. **Execute commands from the source binary:**
+   ```bash
+   node bin/multimodel-dev-os.js init
+   node bin/multimodel-dev-os.js verify
+   ```
+2. **Compile and test the package bundle locally:**
+   ```bash
+   npm pack
+   ```
+   This generates a local `.tgz` archive. Install it in a target test project to run validations.
+
+Never execute `npm publish` in the main workspace unless actively packaging the approved `v2.0.0` release.
+

package/docs/skill-authoring.md

@@ -0,0 +1,56 @@
+# Skill Authoring Guide
+
+This guide explains how to construct high-fidelity reusable skills for MultiModel Dev OS.
+
+## Overview
+
+Skills are custom prompts placed in the `.ai/skills/` directory of a project workspace. They instruct coding agents on exactly how to perform specific coding, refactoring, validation, or deployment routines.
+
+## Required Structure
+
+Every reusable skill file must be a Markdown (`.md`) file containing the following key sections:
+
+```markdown
+# Purpose
+Describe what this skill accomplishes.
+
+# Activation Trigger
+Specify when a developer or agent should invoke this skill.
+
+# Input Context
+List the dependencies, files, or information required before executing this skill.
+
+# Output Contract
+Define the expected deliverables, formats, or file updates.
+
+# Token Budget
+Expected prompt footprint and limits.
+```
+
+## Example Skill File
+
+```markdown
+# Purpose
+Deploy a Next.js Server Action with security gates.
+
+# Activation Trigger
+Trigger when building or modifying API endpoints / React Server Actions.
+
+# Input Context
+* Target action file
+* Schema validations definitions
+
+# Output Contract
+Return the modified action file containing secure CSRF/Origin validation rules.
+
+# Token Budget
+~500 tokens
+```
+
+## Validating a Skill
+
+To test your skill structure compliance, run:
+
+```bash
+node bin/multimodel-dev-os.js validate-skill my-skill-name
+```

package/docs/stable-protocol.md

@@ -1,6 +1,8 @@
-# Stable Protocol Specification (v1.0.0 Freeze)
+# Stable Protocol Specification (v1.1.0 Freeze)
 
-This document formalizes the official, frozen architectural layers and design contracts for the MultiModel Dev OS protocol, guaranteeing portability and long-term stability.
+This document formalizes the official, frozen architectural layers and design contracts for the MultiModel Dev OS protocol, guaranteeing portability and long-term stability across diverse AI coding agents.
+
+> **Best for**: Third-party client integrations, tool adapter developers, and engineering teams establishing robust AI coding guidelines.
 
 ---
 
@@ -33,7 +35,7 @@ MultiModel Dev OS enforces a three-tier design to decouple core workspace contex
 ## 2. Layer 1: Root Contracts
 
 The following root files serve as the workspace single source of truth and are completely frozen:
-- **`AGENTS.md`**: Defines team structures, boundaries, and model configurations.
+- **`AGENTS.md`**: Defines team structures, boundaries, and model configurations (Codex project memory / Antigravity AI workflow).
 - **`MEMORY.md`**: Preserves key context decisions, codebase state, and repository milestones.
 - **`TASKS.md`**: Tracks current active goals and backlog.
 - **`RUNBOOK.md`**: Operational scripts and workspace verify procedures.
@@ -52,7 +54,7 @@ The following directories and files under `.ai/` are strictly locked:
 
 ## 4. Layer 3: Adapters Setup
 
-IDE adapters translate centralized rules to tool-specific paths:
+IDE adapters translate centralized rules to tool-specific paths (Cursor project rules / Claude Code project instructions):
 - **Cursor**: Linked via root `.cursorrules`
 - **Claude**: Linked via root `CLAUDE.md`
 - **Gemini**: Linked via `.gemini/settings.json`
@@ -64,3 +66,5 @@ IDE adapters translate centralized rules to tool-specific paths:
 
 - **Stable**: Root files, scaffolding directories, CLI subcommand signatures, and standard config structures.
 - **Experimental**: Custom check overrides under `.ai/checks/` and stack-specific context routing.
+
+Explore our [Upgrades & Migration Guide](/migration-guide) or [Release Quality Checklist](/v1-checklist) for staging controls.

package/docs/template-authoring.md

@@ -0,0 +1,65 @@
+# Custom Template Authoring Guide
+
+This guide explains how to author a custom workspace configuration template for MultiModel Dev OS.
+
+## Overview
+
+A template packages a set of boilerplate markdown files (`AGENTS.md`, `MEMORY.md`, `TASKS.md`, `RUNBOOK.md`), a central `.ai/config.yaml` file, and stack-specific context files and skills.
+
+## Structure of a Template Source
+
+A template resides in the `examples/` directory of the project, or can be loaded dynamically from a custom path using `--registry` if declared in the registry.
+
+```
+examples/my-custom-template/
+├── AGENTS.md                   # Core workspace contracts
+├── MEMORY.md
+├── TASKS.md
+├── RUNBOOK.md
+└── .ai/
+    ├── config.yaml             # Core configuration rules
+    ├── context/                # Context templates
+    │   ├── project-brief.md
+    │   ├── architecture.md
+    │   └── context-budget.md
+    └── skills/                 # Custom reusable skill files
+        └── custom-action.md
+```
+
+## Creating a Registry Entry
+
+Add your template metadata to `.ai/templates/registry.yaml`:
+
+```yaml
+templates:
+  my-custom-template:
+    name: "my-custom-template"
+    description: "My custom framework stack workspace baseline."
+    stack: "My Framework, TypeScript, PostgreSQL"
+    skill: "custom-action.md"
+    skillDesc: "Framework specific secure execution rules."
+    category: "Web"
+    status: "stable"
+    maturity: "production-ready"
+    required_files:
+      - AGENTS.md
+      - MEMORY.md
+      - TASKS.md
+      - RUNBOOK.md
+      - .ai/config.yaml
+      - .ai/context/project-brief.md
+      - .ai/skills/custom-action.md
+```
+
+## Validation Rules
+
+You can validate your template configuration using the CLI:
+
+```bash
+node bin/multimodel-dev-os.js validate-template my-custom-template
+```
+
+Validation ensures:
+1. The template metadata matches the registry schema.
+2. The template source directory exists.
+3. All files listed in `required_files` are present.

package/docs/token-optimization.md

@@ -0,0 +1,27 @@
+# Token Optimization & Budget Policy
+
+In agentic coding workflows, token overheads are the single largest source of API latency and cost. MultiModel Dev OS integrates tools and policies to optimize context inputs.
+
+---
+
+## 1. Caveman Mode
+* **Goal**: Reduce baseline context token footprint by ~79%.
+* **CLI Flag**: `node bin/multimodel-dev-os.js init --caveman`
+* **Behavior**: Instantiates minimal `.caveman.md` files for `AGENTS.md`, `MEMORY.md`, `TASKS.md`, and `RUNBOOK.md`, omitting explanatory files and dense markdown guidelines.
+
+---
+
+## 2. Context Budget Auditing
+* Define strict context bounds inside [.ai/context/context-budget.md](file:///F:/multimodel-dev-os/.ai/context/context-budget.md).
+* **CLI Command**: `node bin/multimodel-dev-os.js doctor --tokens`
+  * Checks if build outputs or caches (`node_modules/`, `dist/`, `.next/`, `build/`) are missing from `.gitignore` or are being exposed to LLM scan scopes.
+
+---
+
+## 3. Policy Guidelines
+
+### Keep Checklist Files Short
+Use `TASKS.md` exclusively for active sprint tasks. Move completed or historical backlogs to archive directories or logs.
+
+### Model Handoff Compression
+When switching from reasoning models to quick-fixing models, use [.ai/prompts/compress-context.md](file:///F:/multimodel-dev-os/.ai/prompts/compress-context.md) to distill findings into high-density prompts.

package/docs/v2-migration.md

@@ -0,0 +1,31 @@
+# MultiModel Dev OS v2 Migration Guide
+
+This guide describes how to migrate your developer configurations and workspace setup to the new Layered Architecture of MultiModel Dev OS v2.
+
+## What is Changing
+
+* **Version 1.1.0 and prior:** Handled flat configurations directly at the project root with individual configurations manually copied across.
+* **Version 2.0.0 (and source milestones 1.2–1.5):** Establishes a clean, three-layered architecture where root contracts (`AGENTS.md`, `MEMORY.md`, `TASKS.md`, `RUNBOOK.md`) are automatically routed to adapters via the `.ai/` directory.
+
+## Migration Steps
+
+### 1. Upgrade the CLI
+Run the latest v2 setup utility via npx:
+```bash
+npx multimodel-dev-os@latest init --template general-app
+```
+
+### 2. Move Legacy Configuration Files
+If you have custom system instructions or rules:
+* Move `.cursorrules` custom rules to `.ai/skills/` as custom markdown skills.
+* Re-generate adapter links:
+  ```bash
+  npx multimodel-dev-os@latest init --adapter cursor --adapter claude
+  ```
+
+### 3. Verify Migration Integrity
+Run diagnostics to verify that ignored folders, boundaries, and files are clean:
+```bash
+npx multimodel-dev-os@latest doctor
+npx multimodel-dev-os@latest validate
+```

package/docs/v2-release-checklist.md

@@ -0,0 +1,30 @@
+# v2 Release Checklist
+
+Use this checklist to verify compliance before publishing `multimodel-dev-os` to the npm registry.
+
+## Pre-Flight Requirements
+
+- [x] Ensure version string in `package.json` is set to `2.0.0`.
+- [x] Verify version strings in documentation and install scripts (`scripts/install.sh`, `scripts/install.ps1`) align with the release.
+- [x] Run full release verification:
+  ```bash
+  npm run verify
+  ```
+- [x] Run registry checks:
+  ```bash
+  node bin/multimodel-dev-os.js validate --all-registries
+  ```
+- [x] Run release doctor:
+  ```bash
+  node bin/multimodel-dev-os.js doctor --release
+  ```
+
+## Packaging Verification
+
+- [x] Execute dry pack run:
+  ```bash
+  npm pack --dry-run
+  ```
+- [x] Inspect generated tarball file listing to verify only necessary directories (`.ai/`, `adapters/`, `bin/`, `docs/`, `examples/`, `scripts/`, `assets/`) are included.
+- [x] Verify that the prepublish guard is bypassed only for the official production run.
+- [x] Confirm no `.env` or sensitive `.npmrc` configurations are packaged.

package/docs/v2-roadmap.md

@@ -0,0 +1,95 @@
+# MultiModel Dev OS — v2.0.0 Roadmap
+
+This document outlines the development path, stabilization targets, and migration roadmap leading to the `v2.0.0` stable release of MultiModel Dev OS.
+
+---
+
+## 1. Release Objective
+
+The primary goal of the **v2.0.0 release** is to promote the experimental features introduced in `v1.2.0` (Template Galaxy, Model Compatibility Layer, and Android Expo template) into officially frozen, production-grade core components, and resume stable package publication to the public npm registry.
+
+> [!IMPORTANT]
+> **v2.0.0 is the active stable release.** NPM publishing is resumed, consolidating the Template Galaxy and Model registries.
+
+---
+
+## 2. Key Stabilization Targets
+
+### A. Template Galaxy Stabilization
+* Standardize the schema for template configurations under `.ai/schema/template.schema.json`.
+* Harden the built-in templates (`nextjs-saas`, `wordpress-site`, `ecommerce-store`, `seo-landing-page`, `expo-react-native-android`, `general-app`) to ensure they pass validation checks across diverse OS environments.
+
+### B. Model Registry Stabilization
+* Freeze the `.ai/models/` structure:
+  * `registry.yaml` — Core provider mappings and model metadata.
+  * `providers.yaml` — API endpoint declarations.
+  * `routing-presets.yaml` — Optimized task routing configurations.
+  * `local-models.yaml` — Offline execution definitions.
+* Standardize validation rules inside `validate` and `doctor` commands to verify YAML configuration syntax and compatibility.
+
+### C. Adapter Registry Stabilization
+* Freeze `.ai/adapters/registry.yaml`.
+* Extend support mapping for emerging developer tools (e.g. Continue, Cline, Roo Code, Aider, Windsurf).
+* Ensure cross-linking logic maintains strict custom boundaries so that updates in `AGENTS.md` synchronize with adapter targets without wiping user overrides.
+
+### D. Android Expo Template Stabilization
+* Hardening the `examples/expo-react-native-android/` foundation.
+* Verify clean execution of EAS Build and environment configurations on local developer machines and CI runner platforms.
+
+### E. CLI Compatibility Pass
+* Ensure the new subcommands introduced in `v1.2.0` are fully backward-compatible with `v1.0.0` and `v1.1.0` CLI patterns:
+  * `models` / `show-model`
+  * `providers`
+  * `route-model`
+  * `adapters` / `show-adapter`
+  * `skills` / `show-skill`
+  * `doctor --tokens`
+  * `validate --template`
+
+---
+
+## 3. Package Publishing Checklist
+
+Before executing the `v2.0.0` release on the npm registry, the following steps must be completed:
+
+1. [x] Set version to `2.0.0` in `package.json`.
+2. [x] Ensure `scripts/prepublish-guard.js` allows the publish (since version starts with `2.`).
+3. [x] Run all verification suites:
+   ```bash
+   npm run verify
+   ```
+4. [x] Build documentation static bundles cleanly:
+   ```bash
+   npm run docs:build
+   ```
+5. [x] Perform a dry-run publish to review package hygiene:
+   ```bash
+   npm publish --dry-run
+   ```
+6. [x] Set the required publication environment variable:
+   * **PowerShell:** `$env:MMDO_ALLOW_PUBLISH="true"`
+   * **Bash:** `export MMDO_ALLOW_PUBLISH=true`
+7. [x] Publish the package to the public registry:
+   ```bash
+   npm publish --access public
+   ```
+
+---
+
+## 4. Migration Notes: npm latest to v2.0.0
+
+* **Direct Upgrades**: Projects running the last stable npm package (e.g., `1.1.0` / `1.0.0`) can migrate to `2.0.0` by executing `npx multimodel-dev-os@latest init --force` or installing the package locally.
+* **Registry Release**: Now that v2.0.0 is released, cloning the repository is no longer required to access Layer 1 templates or model registries. Simply run:
+  ```bash
+  npx multimodel-dev-os@latest init
+  ```
+* **Configuration Upgrades**: Existing `.ai/` folders can be upgraded by running `init --force` to pull the new centralized registries (`.ai/models/` and `.ai/adapters/`) into the workspace.
+
+---
+
+## 5. Final Release Gate
+
+The `v2.0.0` release requires:
+1. 100% pass rate on all automated linter and verifier checks.
+2. Complete documentation updates across all guides and discovery indices.
+3. Explicit maintainer sign-off on local testing of the Android Expo template.

package/examples/expo-react-native-android/.ai/config.yaml

@@ -0,0 +1,22 @@
+# Mobile App configuration
+
+project:
+  name: "expo-react-native-android"
+  description: "Production-ready Android mobile app with Expo, React Native, and EAS builds."
+  version: "1.0.0"
+
+mode: "standard"
+
+adapters:
+  cursor: false
+  claude: false
+  gemini: false
+  vscode: false
+  antigravity: false
+
+skills:
+  directory: ".ai/skills/"
+  auto_load: true
+
+prompts:
+  directory: ".ai/prompts/"

package/examples/expo-react-native-android/.ai/context/architecture.md

@@ -0,0 +1,18 @@
+# Mobile App Architecture Map
+
+This document establishes key folder boundaries and separation of concerns.
+
+## Layout Folder Structure
+
+```
+mobile/
+  app/                      # Expo Router screens & layouts
+  components/               # Reusable UI theme primitives
+  services/                 # API Clients, storage abstractions
+  hooks/                    # Custom custom hook libraries
+  tests/                    # Jest testing configurations
+```
+
+## Core Foundations
+1. **API Communications**: Handled exclusively under `/services/api-client.ts`.
+2. **Device State**: Sensitive keys kept out of Async Storage, saved in `expo-secure-store`.

package/examples/expo-react-native-android/.ai/context/context-budget.md

@@ -0,0 +1,4 @@
+# Context Budget Settings
+
+- Max file rules size: 4000 tokens.
+- Restrict loading of `/node_modules` or `.expo/` compiler cache files in assistant requests.

package/examples/expo-react-native-android/.ai/context/model-map.md

@@ -0,0 +1,6 @@
+# Model Mapping for Mobile Codebase
+
+| Tasks | Model Choice | Rationales |
+| :--- | :--- | :--- |
+| Mocking Native Components / React Hooks | Claude 3.5 Sonnet | Strong TypeScript and code reasoning |
+| Testing configurations / layout updates | Gemini 1.5 Flash | Fast verification loops |

package/examples/expo-react-native-android/.ai/context/project-brief.md

@@ -0,0 +1,9 @@
+# Project Brief: Android Mobile Client
+
+## Overview
+Scaffolds a production-grade React Native app utilizing Expo Go, EAS CLI, and TypeScript. 
+
+## Goals
+- Establish secure storage profiles (`expo-secure-store`).
+- Construct environment splits via `eas.json` (development, staging, production).
+- Implement responsive layout layouts and offline warnings.

package/examples/expo-react-native-android/.ai/session-logs/.gitkeep

@@ -0,0 +1 @@
+# Placeholder

package/examples/expo-react-native-android/.ai/skills/expo-android-build.md

@@ -0,0 +1,11 @@
+# Skill: Expo Android EAS Build Checks
+
+## Purpose
+Ensures that app.json, eas.json, and environment variables are verified before launching an EAS Build.
+
+## Activation Trigger
+Running `EAS build` or preparing staging/production releases.
+
+## Safe Verification Check
+- Assert `android.package` is set to `com.multimodel.devos` in `app.json`.
+- Confirm `eas.json` contains `preview` and `production` profiles.

package/examples/expo-react-native-android/AGENTS.md

@@ -0,0 +1,20 @@
+# MultiModel Dev OS - Android App Agents Specification
+
+This document defines agent roles and boundaries for the Expo React Native Android application.
+
+## Development Stack Guidelines
+
+- **Framework**: Expo + React Native + TypeScript
+- **State Management**: Zustand / React Context
+- **Navigation**: Expo Router (File-based)
+- **UI System**: Vanilla React Native + Tailwind CSS (NativeWind v4)
+
+## CLI Executables Matrix
+
+| Command | Action | Agent Role |
+| :--- | :--- | :--- |
+| `npm run lint` | Code style audit | Coder / Reviewer |
+| `npm run test` | Jest test suite execution | QA Tester |
+| `npx expo start` | Local development server | Coder |
+| `npx eas build --platform android --profile preview` | Build staging APK bundle | DevOps |
+| `npx eas build --platform android --profile production` | Build Play Store AAB release | DevOps |

package/examples/expo-react-native-android/MEMORY.md

@@ -0,0 +1,13 @@
+# Android App Architecture Memory & Constraints
+
+## Technical Baseline
+- **Build Tooling**: EAS CLI (Expo Application Services)
+- **Android Target**: API level 34 (Android 14)
+- **Minimum SDK**: API level 23 (Android 6.0)
+
+## Security Guidelines
+- **No Hardcoded Secrets**: All keys (API endpoints, tokens) must be injected dynamically via Expo Config `extra` parameters using `.env` files.
+- **Secure Storage**: Sensitive auth tokens must be saved using `expo-secure-store`. Do NOT use standard `AsyncStorage` for passwords or tokens.
+
+## Package Identity
+- **Android Package Name**: `com.multimodel.devos` (defined in `app.json`)

package/examples/expo-react-native-android/README.md

@@ -0,0 +1,101 @@
+# Expo React Native Android Boilerplate
+
+This template provides a production-ready React Native boilerplate configured for Android delivery using Expo, EAS Build, secure environment profile separation, automated API retries, and unit tests.
+
+---
+
+## 1. Directory Structure
+
+```
+├── app.json                  # Expo application static configurations
+├── eas.json                  # EAS Build pipeline profiles
+├── app.config.ts             # Dynamic env profiles selector
+├── jest.config.js            # Jest testing suite configuration
+├── src/
+│   ├── app/
+│   │   └── _layout.tsx       # Root layout, NetInfo listeners, and screen boundaries
+│   ├── lib/
+│   │   └── secure-storage.ts # Safe wrapper for expo-secure-store (key/value device encryption)
+│   └── services/
+│       └── api-client.ts     # Fetch API wrapper with timeout thresholds and auto-retries
+```
+
+---
+
+## 2. Environment Variables & App Configuration
+
+We decouple environment configurations in [app.config.ts](file:///f:/multimodel-dev-os/examples/expo-react-native-android/app.config.ts) using `APP_ENV`.
+
+### Supported Profiles
+1. **Development (`development`)**:
+   * API Url: `http://10.0.2.2:3000/api` (Localhost mapping for Android Emulator)
+2. **Staging (`staging`)**:
+   * API Url: `https://staging-api.multimodel.dev`
+3. **Production (`production`)**:
+   * API Url: `https://api.multimodel.dev`
+
+### To launch a specific environment locally:
+```bash
+# Start with staging parameters
+APP_ENV=staging npx expo start
+
+# Start with production parameters
+APP_ENV=production npx expo start
+```
+
+---
+
+## 3. EAS Build Setup
+
+We configure three build targets in [eas.json](file:///f:/multimodel-dev-os/examples/expo-react-native-android/eas.json) to separate local debugging from store delivery.
+
+### Build Commands
+```bash
+# 1. Build local development client (Internal testing APK with debugging tools)
+eas build --profile development --platform android
+
+# 2. Build staging/preview release (Internal testing APK)
+eas build --profile preview --platform android
+
+# 3. Build production release (Signed Android App Bundle (.aab) ready for Google Play Store)
+eas build --profile production --platform android
+```
+
+> [!CAUTION]
+> **No-Secrets Policy**: Do not commit actual `owner` or `projectId` credentials into `app.json` or environment files. Fill in placeholders locally during project provisioning.
+
+---
+
+## 4. API Client & Secure Storage
+
+### API Retry Loop
+The [api-client.ts](file:///f:/multimodel-dev-os/examples/expo-react-native-android/src/services/api-client.ts) automatically retries requests up to 3 times on transient network failures before aborting. You can enable offline mock responses by setting:
+```typescript
+const USE_MOCK_DATA = true;
+```
+
+### Encrypted Key-Value Storage
+Use the [secure-storage.ts](file:///f:/multimodel-dev-os/examples/expo-react-native-android/src/lib/secure-storage.ts) class to securely store credentials (like JWT tokens) on the device using keychain encryption:
+```typescript
+import { SecureStorage } from '../lib/secure-storage';
+
+// Write credential
+await SecureStorage.setItem('auth_token', 'JWT-TOKEN-DATA');
+
+// Retrieve credential
+const token = await SecureStorage.getItem('auth_token');
+```
+
+---
+
+## 5. Pre-flight Play Store Release Checklist
+
+Ensure you complete these steps before submitting `production` bundles:
+1. **Change package name**: Update `"package": "com.multimodel.devos"` in `app.json` to your unique identifier.
+2. **Update version parameters**: Set unique `"version"` and incremental `"versionCode"` in `app.json` for every build.
+3. **Configure App Signing Keys**: Ensure your keystore is generated securely on EAS or imported safely from local credentials. Do not commit keystores to Git.
+4. **Permissions Audit**: Verify that only required permissions (like `INTERNET`) are enabled in `app.json`.
+5. **Run tests**:
+   ```bash
+   npm test
+   ```

package/examples/expo-react-native-android/RUNBOOK.md

@@ -0,0 +1,36 @@
+# Mobile Staging Operations & Build Runbook
+
+This document details common development, testing, and release build workflows.
+
+---
+
+## 1. Local Testing & Execution
+
+Start local bundler:
+```bash
+npm run start
+```
+Run Jest unit tests:
+```bash
+npm run test
+```
+
+---
+
+## 2. Staging / Preview Builds
+
+Build staging APK locally or remotely using EAS CLI:
+```bash
+# Preview build for internal testing (requires EAS account configured)
+npx eas build --platform android --profile preview
+```
+
+---
+
+## 3. Production Play Store release
+
+Build production Play Store package (AAB):
+```bash
+npx eas build --platform android --profile production
+```
+ Ensure that your Google Play Console credentials and key keystores are linked securely inside the EAS dashboard.

package/examples/expo-react-native-android/TASKS.md

@@ -0,0 +1,14 @@
+# Active Mobile Application Backlog
+
+- [ ] Mobile App Initialization
+  - [ ] Configure `app.json` package namespace and icon directories
+  - [ ] Setup `eas.json` profiles
+- [ ] Core Integrations
+  - [ ] Implement API client with baseUrl environment variables
+  - [ ] Implement secure storage utility using `expo-secure-store`
+- [ ] App Features
+  - [ ] Setup Expo Router layout screens
+  - [ ] Design loading states and offline warning screens
+- [ ] Quality Assurance
+  - [ ] Add Jest test setups
+  - [ ] Build staging APK via `npx eas build`