build(deps): bump react from 19.2.4 to 19.2.5

.github/dependabot.yml

@@ -0,0 +1,7 @@
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10

.github/workflows/ci.yml

@@ -0,0 +1,34 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+jobs:
+  validate:
+    name: Build, lint, and typecheck
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build
+        run: npm run build
+
+      - name: Lint
+        run: npm run lint
+
+      - name: Typecheck
+        run: npm run typecheck

.github/workflows/release.yml

@@ -0,0 +1,77 @@
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+permissions:
+  contents: write
+
+jobs:
+  validate:
+    name: Validate release tag
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Release checks
+        run: npm run release:check
+
+      - name: Verify package tarballs
+        run: npm run release:pack
+
+  github_release:
+    name: Create GitHub Release
+    runs-on: ubuntu-latest
+    needs: validate
+
+    steps:
+      - name: Create release
+        uses: softprops/action-gh-release@v2
+        with:
+          generate_release_notes: true
+          draft: false
+          prerelease: false
+
+  npm_publish:
+    name: Publish npm packages
+    runs-on: ubuntu-latest
+    needs: validate
+    if: ${{ secrets.NPM_TOKEN != '' }}
+
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          registry-url: https://registry.npmjs.org
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build packages
+        run: npm run build
+
+      - name: Publish omniforge
+        run: npm publish -w omniforge --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

CHANGELOG.md

@@ -0,0 +1,27 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com), and this project adheres to [Semantic Versioning](https://semver.org).
+
+## [0.1.0] - 2026-04-09
+
+### Added
+- Local-first, open-source AI automation app with LLM-powered agent generation.
+- End-user CLI (`omniforge`) for onboarding, creating agents, and managing automations.
+- Local-first runtime with encrypted secrets and portable state in `~/.omniforge/`.
+- Provider support through [providers/catalog.json](providers/catalog.json): Anthropic, OpenAI, Gemini, Ollama, DeepSeek, xAI, Groq, Mistral, OpenRouter.
+- Reusable skills framework in [skills/](skills/) with markdown playbooks and YAML frontmatter.
+- Agent scheduling with timezone-aware daily execution (optional).
+- Cross-platform scheduler auto-start management (`omniforge scheduler-service install|status|uninstall`).
+- Built-in tools: file I/O, web search, HTTP requests, terminal execution, patch application.
+- Bounded context history (default 60 messages, configurable via `OMNIFORGE_MAX_CONTEXT_MESSAGES`).
+- Agent state persistence with checkpointing under `~/.omniforge/agents/<agent-id>/`.
+- Open-source governance: `LICENSE`, `CONTRIBUTING.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`.
+- CI/CD workflows: build, lint, typecheck on PR; automated release to GitHub and npm on version tags.
+- Dependabot configuration for weekly npm dependency updates.
+
+### Security
+- Zero vulnerabilities verified with `npm audit --omit=dev`.
+- Secrets encrypted at rest in `~/.omniforge/params.json`.
+- Local-first data model keeps user data and provider keys off remote servers.

CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at:
+siddak.bath@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,47 @@
+# Contributing to OmniForge
+
+Thanks for contributing to OmniForge.
+
+## Development setup
+
+1. Fork and clone the repository.
+2. Install dependencies:
+   - `npm install`
+3. Validate workspace health:
+   - `npm run check`
+4. Run the CLI in development mode:
+   - `npm run dev:cli -- --help`
+
+## Pull request checklist
+
+Before opening a PR, ensure all of the following are true:
+
+- `npm run build` passes.
+- `npm run lint` passes.
+- `npm run typecheck` passes.
+- You updated docs when behavior changed.
+- You included tests when practical.
+- You kept changes focused and backwards compatible where possible.
+
+## Commit and PR guidance
+
+- Use clear, imperative commit messages.
+- Keep PRs small and reviewable.
+- Explain motivation, design decisions, and risks.
+- Link related issues in the PR description.
+
+## Reporting issues
+
+When filing bugs, include:
+
+- Expected behavior
+- Actual behavior
+- Reproduction steps
+- Operating system and Node.js version
+- Relevant logs (with secrets redacted)
+
+## Security issues
+
+Do not open public issues for vulnerabilities.
+
+Please report via the process in [SECURITY.md](SECURITY.md).