yumi-agent 0.0.1__tar.gz

yumi_agent-0.0.1/CHANGELOG.md

@@ -0,0 +1,242 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.0.1] - Unreleased
+
+### Added
+
+- **Brand-new web UI** — a custom React + Vite + TypeScript + Tailwind
+  single-page app (`yumi/ui/frontend/`) replacing the old Reflex UI. It ships
+  pre-built as static assets served by the core server under `/app`, so end
+  users need **no Node and no extra install** (`yumi --ui` just opens the
+  browser). Pages: Chat (streaming, tool-call cards, tool-confirmation,
+  file upload, mic input + spoken replies, sessions with pin/rename/search),
+  Tools, a Stats dashboard, tabbed Settings, Schedules, Memory search, a
+  first-run setup wizard, and a ⌘K command palette.
+- **Persistent token-usage tracking** — each assistant turn's prompt/completion
+  tokens are recorded to SQLite (`token_usage` table) and survive restarts.
+- **`GET /stats`** — aggregated tool, token, session, and tool-call metrics for
+  the dashboard.
+- **`POST /tts/synthesize`** — text-to-speech for in-browser spoken replies
+  (reuses the configured TTS provider).
+
+### Changed
+
+- `pip install yumi-agent` now includes local FastEmbed, Whisper STT,
+  microphone wake-word dependencies, DashScope cloud STT/TTS, and the pre-built
+  web UI. Only local-GPU Qwen TTS (`[tts-local]`) remains an optional extra;
+  model weights and embedding assets are still downloaded on demand.
+- `yumi --ui` no longer requires Node.js or a Reflex dev server; it verifies the
+  core server is running and opens the browser at its `/app` page.
+- Default conversation context raised to 30 recent + 15 cross-session related
+  messages.
+- Migrated PDF ingestion from the end-of-life `PyPDF2` to `pypdf`; added explicit
+  `pydantic` and `av` (PyAV) dependencies.
+
+### Fixed
+
+- Core (agent loop + memory storage):
+  - **SQLite is now the authoritative write** for every message; the LanceDB
+    vector index is a derived, best-effort write that is rebuilt from SQLite when
+    needed — so an index hiccup can no longer lose a canonical message (the write
+    order was previously inverted).
+  - Added `Memory.rebuild_index_from_sqlite()` to drop and regenerate the LanceDB
+    query index from SQLite (e.g. after changing the embedding model, or to repair
+    drift).
+  - Removed the never-consumed `embedding_jobs` / `vector_index_records` queue
+    (it grew unbounded and was dead scaffolding; embeddings are generated inline
+    and the index is rebuilt from SQLite on demand).
+  - Chat: a malformed-tool-call retry no longer re-sends and re-persists the
+    user's message on each attempt.
+- Pre-release hardening (web UI + voice):
+  - Cloud STT (Gemini/DashScope/Grok) now transcodes browser WebM/MP4 recordings
+    to WAV via PyAV, and the mic upload filename matches the real container
+    (Safari/iOS), so microphone input works across providers and browsers.
+  - The mic button is disabled with a hint when STT is off; spoken-reply (TTS)
+    failures now surface a toast instead of failing silently; "Test voice" saves
+    the current selection first and no longer leaks audio URLs.
+  - Added a DashScope/Qwen API-key field to Settings → Voice (previously
+    unconfigurable from the browser).
+  - Chat: collapsing the sidebar can no longer strand you with no controls; a
+    failed message reload no longer wipes the transcript; the active session
+    persists across refreshes.
+  - The Settings "Configuration Storage" note now shows the correct path
+    (`~/.yumi/config.json`), command (`yumi --config`), and an accurate
+    (non-"encrypted") description of how keys are stored.
+  - `/stats` runs off the event loop and aggregates the full trace buffer (not a
+    500-row slice); per-turn token persistence no longer reloads the full config.
+  - The UI self-hosts the Inter font (no external CDN) and code-splits routes for
+    a lighter initial load; a server-unreachable banner and a discoverable setup
+    wizard were added.
+
+### Removed
+
+- The Reflex web UI and the `[ui]` optional dependency extra.
+- Windows `system` TTS now uses the built-in SAPI voice through PowerShell,
+  matching the zero-dependency spoken-reply path already available on macOS and
+  Linux.
+
+## Development Notes - 2026-06-28
+
+### Added
+
+- **Cloud speech-to-text providers.** Alongside local Whisper, `stt_provider` now
+  accepts three no-download cloud backends that reuse your existing provider API
+  keys: `openai` (OpenAI transcription — `gpt-4o-mini-transcribe`,
+  `gpt-4o-transcribe`, `whisper-1`; honors `openai_base_url` for OpenAI-compatible
+  proxy / Azure endpoints), `gemini` (Gemini 2.5 models transcribe inline audio
+  via `gemini_api_key`), and `dashscope` (Qwen3-ASR `qwen3-asr-flash` via the
+  shared DashScope key). `yumi --setup` configures them; `YUMI_STT_PROVIDER`
+  accepts the new values.
+- **OpenAI text-to-speech.** `tts_provider = openai` speaks replies through the
+  OpenAI speech API (`gpt-4o-mini-tts` / `tts-1` / `tts-1-hd`) using
+  `openai_api_key`, joining `system` / `dashscope` / `qwen`. Output is WAV so it
+  plays through the same zero-config local backends (`winsound` / `aplay` /
+  `afplay`) as the other providers.
+- **Redesigned setup wizard.** `yumi --setup` is now a navigable,
+  alternate-screen step flow (AI model → memory → voice input → spoken replies →
+  messaging) with back/next navigation, a calm progress rail, an immediate test
+  line per feature, and on-demand extra installs. Non-interactive / piped
+  invocations degrade gracefully and cancel cleanly on closed stdin.
+- **Missing-credential preflight.** Launching the server or a bridge surfaces any
+  configured cloud feature whose API key is absent — fatally for the chat model,
+  as a non-blocking warning for memory / voice — via `missing_credentials()`.
+- **TTS environment overrides**: `YUMI_TTS_PROVIDER`, `YUMI_TTS_VOICE`,
+  `YUMI_TTS_MODEL`, `YUMI_TTS_LANGUAGE`, mirroring the existing `YUMI_STT_*`.
+
+### Changed
+
+- `rich` is now a base dependency (used for the redesigned wizard rendering).
+
+## Development Notes - 2026-06-19
+
+### Changed
+
+- **Internal restructure (`yumi/core/`): platform / features split.** Modules
+  were reorganized into `yumi/core/platform/` (cross-cutting infra),
+  `yumi/core/features/<feature>/` (self-contained capabilities), and a slim
+  `yumi/core/api/` HTTP composition root, with a strict dependency rule
+  (features → platform, never the reverse) enforced by tests. The old import
+  paths were retired — no compatibility shims remain, so only the new paths are
+  importable. See `docs/MIGRATION_PLATFORM_FEATURES.md` for the full old→new map.
+- **Batteries-included base install.** `pip install yumi-agent` now bundles the
+  LLM providers (OpenAI / Gemini / Claude, incl. DeepSeek), the Telegram +
+  Discord bridges, and file ingestion, so they work out of the box. Only heavy /
+  system-dependent features remain as extras (`[ui]`, `[stt]`, `[voice]`,
+  `[tts]`, `[tts-local]`), and `yumi --setup` offers to install those on demand
+  when you enable the feature. The now-redundant
+  `[openai]`/`[gemini]`/`[claude]`/`[deepseek]`/`[providers]`/`[telegram]`/
+  `[discord]`/`[line]`/`[files]` extras were removed (folded into the base).
+
+### Security
+
+- `~/.yumi/config.json` is now written atomically with `0o600` and the parent
+  directory chmod'd to `0o700` so cloud API keys, Telegram/LINE tokens, the
+  Picovoice access key, and `lan_secret` aren't readable by other local users.
+- Built-in `read_file` / `list_files` tools default to **require_confirmation**
+  (opt out via `local_tools_always_allow`) and reject paths inside `~/.ssh`,
+  `~/.aws`, `~/.gnupg`, `~/.yumi`, plus `*.pem` / `*.key` / `id_rsa*` /
+  `authorized_keys` / `credentials` files. Mitigates prompt-injection from
+  uploaded data trying to exfiltrate local secrets.
+- `YUMI_CORS_ORIGINS=*` combined with `_ALLOW_CREDENTIALS=true` now raises at
+  startup rather than silently demoting credentials.
+- Provider exception text on `PUT /config/model` failure is logged
+  server-side; the HTTP response now carries a generic hint so SDK error
+  bodies (which can include URLs / partial credentials) don't leak.
+
+### Added
+
+- **Discord bridge**: chat with Yumi from a Discord bot — `yumi --server --discord`
+  or `yumi --discord` (gateway connection, no public URL needed). Tool confirmations
+  are Allow / Deny / Always-allow buttons; allowlist via `DISCORD_ALLOWED_USER_IDS`.
+  Ships in the base install. Joins the existing Telegram and LINE bridges.
+- **SDK robustness (`YumiAgent`)**: logs via the `yumi.sdk` logger instead of
+  `print`; exposes `is_connected` and an optional `on_error` callback; resolves the
+  connection inside the reconnect loop so a transient connection-bootstrap failure
+  at startup no longer permanently kills the client; `register()` now raises on a
+  duplicate or empty tool name; and `yumi.run()` configures the default agent via
+  the public `run_in_background(...)` instead of touching private attributes.
+- **Microphone wake-word voice mode**: `yumi --server --voice` (composable
+  with `--telegram`) attaches a Picovoice + faster-whisper loop. New optional
+  extras: `[voice]` (sounddevice + webrtcvad + pvporcupine) and `[stt]`
+  (faster-whisper). New config keys: `voice_owner_id`,
+  `voice_porcupine_access_key`, `voice_porcupine_keyword_path`,
+  `voice_porcupine_sensitivity`, `voice_input_device`, `voice_silence_ms`,
+  `voice_max_utterance_ms`, `voice_vad_aggressiveness`, `voice_wake_word`.
+  Environment: `YUMI_VOICE_ENABLED`, `YUMI_VOICE_OWNER_ID`, `PV_ACCESS_KEY`.
+- **Spoken replies (text-to-speech)**: Yumi can talk back. Three backends behind
+  one provider choice — `system` (macOS `say` / Linux `espeak`, zero-dependency
+  default), `dashscope` (Qwen3-TTS via the Alibaba Cloud DashScope API), and
+  `qwen` (Qwen3-TTS run locally on a GPU). `yumi --setup` configures it (with an
+  immediate test line); `yumi --speak "..."` is a smoke test; `--server --voice`
+  speaks replies automatically; Telegram `/voice on|off` and Discord
+  `!voice on|off` switch a chat between text and audio replies. New config keys
+  `tts_provider`, `tts_voice`, `tts_model`, `tts_api_key`, `tts_language`; new
+  extras `[tts]` (DashScope) and `[tts-local]` (local qwen). Environment:
+  `DASHSCOPE_API_KEY`, `DASHSCOPE_BASE_URL`.
+- **Proactive messaging modes**: `proactive_mode` (`off` | `smart` | `scheduled`) with `proactive_schedule_times`, `proactive_schedule_interval_minutes`, and `proactive_schedule_require_idle`. Legacy JSON without `proactive_mode` derives mode from `proactive_enabled`; `proactive_enabled` is still saved and synced from mode on load. Environment: `YUMI_PROACTIVE_MODE`, `YUMI_PROACTIVE_SCHEDULE_TIMES`, `YUMI_PROACTIVE_SCHEDULE_INTERVAL_MINUTES`, `YUMI_PROACTIVE_SCHEDULE_REQUIRE_IDLE`.
+- **`local_timezone`** in `config.json`: IANA zone for user-facing wall time (chat clock, proactive context, proactive quiet hours, proactive daily limit calendar). Legacy JSON key `proactive_quiet_hours_timezone` is still read on load; prefer **`YUMI_LOCAL_TIMEZONE`** over `YUMI_PROACTIVE_QUIET_HOURS_TIMEZONE` at runtime.
+- Proactive messaging: `proactive_check_interval_jitter_ratio`, `proactive_unreplied_escalation_jitter_ratio`, and `proactive_check_in_probability` for less rigid scheduling; matching `YUMI_PROACTIVE_*` environment variables.
+
+### Fixed
+
+- Chat **`[Current Time]`** and proactive context clocks honor **`local_timezone`** (IANA) instead of showing raw UTC when the server runs in UTC (e.g. Docker). When unset, they use the host OS local timezone.
+- LINE webhook handler now ACKs 200 within LINE's ~1s retry window: signature
+  verification stays in the request path, but chat-turn execution runs in a
+  background task. Eliminates duplicate user messages under load.
+- `<thinking>` / `<redacted_thinking>` parser holds back trailing `<` so a tag
+  split across stream chunks is no longer leaked as visible text.
+- Memory `list()` (observations + long_term) now pushes the `session_id`
+  filter into the `WHERE` clause before applying `LIMIT`; busy multi-session
+  DBs no longer silently drop matching rows.
+- `LanceDBBackend.format_timestamp` now produces UTC so it round-trips with
+  `parse_timestamp_num` (which has always interpreted the string as UTC).
+- OpenAI streaming tool-call delta with `index=None` (older Azure / some
+  vLLM builds) no longer crashes the chunk collector.
+- Proactive scheduler releases the session lock before sending so a real
+  user message isn't blocked behind LLM generation + inter-message delays;
+  `record_sent` uses the actual send-start time, not the pre-LLM time.
+- Voice loop no longer leaks the Porcupine native handle when audio source
+  init fails; lifespan shutdown stops the source so the blocking executor
+  read returns immediately instead of leaving a zombie thread.
+- Whisper provider lazy `_load_model` is now lock-guarded so two concurrent
+  first transcriptions don't both download/load the model.
+
+## Development Notes - 2026-04-20
+
+### Changed
+
+- **Repository split**: this `yumi-agent` package is now the open-source single-user / LAN core. Higher-layer identity, policy, billing, and remote-pairing features live outside L1 and extend the core via the `yumi.core.platform.plugins` port system (`IdentityProvider`, `QuotaPolicy`, `BotPool`, `MemoryFactory`, `SessionScope`, `EdgeScope`, `AuditSink`, `BillingHook`, `RouteExtender`, `MiddlewareExtender`).
+- The OSS HTTP API now boots with `single_user` defaults: requests resolve to the local identity (`_local`), there is no Bearer auth requirement, and there are no quotas, billing, or account scoping.
+- CLI surface trimmed to `--server`, `--ui`, `--chat`, `--telegram`, `--line`, `--edge`, `--demo`, `--setup`, `--cleanup`, `--cleanup-memory`. Provisioning, migration, and public remote-access commands belong to higher layers.
+- `yumi.core.platform.security.connection` is now LAN-only (`mode="direct"`); remote profile bootstrap, persistence, and alternate connection variants moved out of L1.
+- `yumi.core.platform.security.auth` now exposes only `YumiLanCode` and helpers; signed Bearer tokens and refresh-token flows moved out of L1.
+- LINE bridge (`yumi.line.handlers`, `yumi.line.bridge`) is now stateless single-user; account-linking and per-user overrides moved out of L1.
+- Removed dependency pins on `slowapi` and `alembic` (rate-limit + DB migrations live outside L1). The optional `postgres` extra is no longer published from OSS.
+
+### Internal
+
+- New `yumi/core/platform/plugins/` package with `Identity`, `LOCAL_IDENTITY`, `Protocol` ports, single-user defaults, a runtime registry, and `entry_points`-based plugin discovery (`yumi.plugins` group).
+
+## Early Development Notes
+
+### Changed
+
+- Internal Python layout: split user config into `yumi.core.features.config` package, prompts into `yumi.core.features.prompts`, memory helpers (`constants`, `tool_replay`, `embedding_state`), CLI as `yumi.cli` package with `terminal_chat`, streaming/error helpers, and renamed `yumi/tools/bootstrap.py` (was `setup.py`) for tool registration. User-facing HTTP routes, CLI commands, and SDKs are unchanged.
+- Restricted default browser CORS for the core API to localhost-style origins, with explicit env vars for widening access.
+- Refactored the core HTTP server into the `yumi.core.api` composition root, with shared HTTP infrastructure in `yumi.core.platform.http` and per-feature routers under `yumi.core.features.*`, to reduce module-level global state and improve testability.
+- Expanded CI-safe tests: chat streaming, credential validation, CLI environment selection, edge WebSocket handshake, health endpoint, and cross-SDK contract tests (Python/Go/TypeScript/Java schema shape verification).
+- Clarified public API stability, deployment hardening, and package metadata for external users.
+- Replaced deprecated LanceDB `table_names()` checks with `list_tables()`-first compatibility helpers in memory storage to remove deprecation warnings on current releases.
+- Added `build` to the development extras and documented a local pre-release smoke check for maintainers.
+- Added `yumi --cleanup-memory` to clear persisted memory without deleting saved config, prompts, profiles, or connection codes.
+
+## Initial Development Baseline - 2026-04-11
+
+### Added
+
+- Initial documented release baseline: local-first agent, CLI (`yumi`), FastAPI server, Reflex web UI, multi-language edge SDKs, HTTP API and docs.

yumi_agent-0.0.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,42 @@
+# 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, caste, color, 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:
+
+- 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:
+
+- 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 without 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.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at the contact method described in [SECURITY.md](SECURITY.md) (or your project’s designated contact). All complaints will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

yumi_agent-0.0.1/COMMERCIAL.md

@@ -0,0 +1,15 @@
+# Commercial use and partnerships
+
+Yumi is distributed under the **Apache License 2.0** (see [LICENSE](LICENSE)). That license governs use, modification, and distribution of the source code in this repository.
+
+## If you are a business
+
+Many companies use Apache-licensed software in products and services without a separate agreement. If you need:
+
+- **Enterprise support**, training, or custom integration
+- **A separate proprietary license** or **dual-licensing** discussion
+- **Partnership** or **sponsorship** inquiries
+
+please contact the project maintainers through the channels listed on the repository (for example, GitHub Discussions, email listed in maintainer profiles, or your company’s usual open-source contact process).
+
+This file does **not** add restrictions beyond the Apache 2.0 license; it only points to where commercial conversations can start.

yumi_agent-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,123 @@
+# Contributing to Yumi
+
+Thank you for your interest in contributing. This document describes how to set up a development environment, run tests, and submit changes.
+
+## Development setup
+
+```bash
+# After forking, replace <your-user> with your GitHub username:
+git clone https://github.com/<your-user>/yumi-agent.git
+cd yumi-agent
+python -m venv .venv
+source .venv/bin/activate   # Windows: .venv\Scripts\activate
+pip install -e ".[dev]"
+```
+
+Optional: install [pre-commit](https://pre-commit.com/) hooks after cloning:
+
+```bash
+pre-commit install
+```
+
+## Running tests
+
+See [docs/TESTING.md](docs/TESTING.md) for context. From the repository root:
+
+```bash
+pytest
+```
+
+CI (see [.github/workflows/ci.yml](.github/workflows/ci.yml)) runs on each push and PR: Python (`compileall`, `ruff` check + format check, `pytest`, `pytest --cov=yumi.core.api`, `pyright`), plus TypeScript, C++, Go, Swift, Java, Rust, Kotlin, Dart, and C# SDK builds.
+
+The canonical upstream for issues and PRs is [github.com/wenxijiao/yumi-agent](https://github.com/wenxijiao/yumi-agent) (use your fork’s `git clone` URL locally as above).
+
+## Releases (PyPI & npm)
+
+Maintainers can publish **after** bumping versions in [`pyproject.toml`](pyproject.toml) (Python) and [`yumi/sdk/typescript/package.json`](yumi/sdk/typescript/package.json) (TypeScript) to match the git tag.
+
+Before pushing a release tag, run a local smoke check from a fresh `.[dev]` environment:
+
+```bash
+pytest
+python -m build
+```
+
+1. Create an annotated tag: `git tag -a v0.0.1 -m "v0.0.1"` and `git push origin v0.0.1`.
+2. Configure PyPI **Trusted Publishing** for this repository and workflow file (`release.yml`) with the `pypi` and `testpypi` GitHub environments. The Python publish job uses OIDC, so there is no long-lived PyPI API token to store.
+3. Configure repository **Secrets**:
+   - `NPM_TOKEN` — [npm automation token](https://docs.npmjs.com/creating-and-viewing-access-tokens) with publish rights for `yumi-sdk`.
+4. The [Release workflow](.github/workflows/release.yml) runs on `v*` tags: builds the Python wheel/sdist and publishes to PyPI, and publishes the TypeScript package to npm. The npm job is skipped if `NPM_TOKEN` is missing.
+
+Forks and contributors without the publish environment or npm secret will not run the publish steps.
+
+## Repository administration (maintainers)
+
+Settings to apply in the GitHub web UI after forking or migrating the repository:
+
+**About panel** — keep the description as `One API to let AI call functions in any language, on any device.` and use the topics:
+
+```
+ai-agent, tool-calling, multi-language, edge-computing, llm, iot,
+function-calling, raspberry-pi, swift, typescript, cpp, python,
+ai-tools, websocket, local-first
+```
+
+**Social preview** — `assets/social-preview.png` is embedded in [`README.md`](README.md) for the project home page, but GitHub does **not** read social previews from the repo automatically. For link unfurls on social platforms, also upload it manually under **Settings → General → Social preview → Edit → Upload an image**.
+
+**Recommended toggles:**
+
+- **Releases** — create one for each version tag (`v0.0.1`, etc.).
+- **Discussions** — enable for community Q&A.
+- **Wiki** — disable (documentation lives in [`docs/`](docs/)).
+- **Sponsorship** — enable if applicable.
+- **Pages** — optional landing page using `docs/` content.
+
+## Code style
+
+- Prefer matching existing patterns in the file you edit.
+- Python 3.10+ type hints (`str | None` instead of `Optional[str]` where consistent).
+- Run `ruff check yumi tests` and `ruff format yumi tests` if configured (see `.pre-commit-config.yaml`).
+
+## Compatibility expectations
+
+- Treat the `yumi` CLI, documented HTTP API, and generated SDK templates as the main user-facing surfaces.
+- Avoid adding undocumented dependencies on internal modules such as `yumi.core.*` unless the change is clearly marked as internal-only.
+- If a change affects a public workflow or contract, update `README.md`, `docs/HTTP_API.md`, and `CHANGELOG.md` in the same PR.
+
+## What not to commit
+
+Do **not** commit:
+
+- `__pycache__/`, `*.pyc`, `*.pyo`
+- `.venv/`, local IDE-only paths
+- `*.egg-info/` (generated by editable installs)
+- Build artifacts under `yumi/ui/.web/`, `yumi/sdk/**/node_modules/`, `yumi/sdk/cpp/build/`, etc. (see [.gitignore](.gitignore))
+
+If you accidentally committed generated files, remove them from the index with `git rm --cached <path>` and ensure they are listed in `.gitignore`.
+
+## Issues before pull requests
+
+For **non-trivial** changes (new features, public API changes, refactors, or anything that needs design discussion), **open an issue first** and describe the problem or proposal. Link that issue from your pull request so maintainers can triage and avoid duplicate work.
+
+Small, obvious fixes (typos, clear one-line bugs, documentation corrections) may go straight to a pull request without a prior issue.
+
+## Pull requests
+
+1. Fork the repository and create a branch from `main`.
+2. Make focused changes; prefer one logical concern per PR when possible.
+3. Add or update tests when you change behavior.
+4. Describe **what** changed and **why** in the PR description.
+
+## Community standards
+
+Please read [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).
+
+## Security issues
+
+Do **not** open a public issue for security vulnerabilities. See [SECURITY.md](SECURITY.md).
+
+## SDKs (Go, Swift, Java, C++, TypeScript)
+
+- **Go / Java / C++ / TypeScript** SDKs are built on Linux in CI.
+- **Swift** SDK is built on a **macOS** runner (Package platforms include Apple OSes).
+- **Unreal Engine (UE5)** modules require a local UE installation; CI does not compile UE5. See [yumi/sdk/README.md](yumi/sdk/README.md).

yumi_agent-0.0.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

yumi_agent-0.0.1/MANIFEST.in

@@ -0,0 +1,23 @@
+include CHANGELOG.md
+include CODE_OF_CONDUCT.md
+include COMMERCIAL.md
+include CONTRIBUTING.md
+include SECURITY.md
+include llms.txt
+graft assets
+graft docs
+# Ship the pre-built web UI; exclude its source/build toolchain.
+graft yumi/ui/static
+prune yumi/ui/frontend/node_modules
+prune yumi/ui/frontend/dist
+prune yumi/ui/__pycache__
+prune yumi/sdk/typescript/node_modules
+prune yumi/sdk/typescript/dist
+prune yumi/sdk/swift/.build
+prune yumi/sdk/swift/.swiftpm
+prune yumi/sdk/java/target
+prune yumi/sdk/csharp/bin
+prune yumi/sdk/csharp/obj
+prune _enterprise_seed
+global-exclude *.py[cod]
+global-exclude .DS_Store